Re: architectural processing with nsgmls/jade for queryloc

["W. Eliot Kimber" <eliot@xxxxxxxxxx>]

At 09:25 PM 6/11/98 +0000, Gerhard Stenzel wrote:

>>Remember, though, that even if you take the shortcut now, using HyTime
>>as you are to describe some of the semantics of your architecture will
>>mean that when more general tools become available, your data will
>>still work.
>                -----------------------------------
>Peter, I appreciate your comments/answers to my questions, but I am not shure
>if I share your optimism.

At SGML/XML Europe, I demonstrated my PHyLIS (Personal HyTime Link
Information System) tool, which is an attempt to construct a completely
general grove-based HyTime engine. One of the things it demonstrates is
processing using the model Peter describes (architecture instance plus
client instance). Once I implement queryloc (haven't yet, but will as soon
as possible), then it will be able to demonstrate Peter's point.  I expect
to have a usable version of PHyLIS up by the end of the week (I only barely
got it to work for my demo in Paris and then my computer died at the start
of three more weeks in Europe, so I still have a little work to do).  I'll
announce it's availability here and on comp.text.sgml.

Unfortunately, as currently implemented, Jade does not maintain the
required (by ISO/IEC 10744:1997) linkages between the client grove and
architectural instance groves. If it did, you would be able to use it to do
the processing as Peter describes. 

For ad-hoc processing you can get the same result just by processing the
client with functions that have built-in knowledge of the HyTime
architecture (or any other architecture you are implementing).  Not ideal
but easy enough to do.

Cheers,

Eliot
--
<Address HyTime=bibloc>
W. Eliot Kimber, Senior Consulting SGML Engineer
ISOGEN International Corp.
2200 N. Lamar St., Suite 230, Dallas, TX 95202.  214.953.0004
www.isogen.com
</Address>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist