Re: architectural processing with nsgmls/jade for queryloc

[Gerhard Stenzel <stenzel@xxxxxxxxxx>]

Thanks Peter,

[Gerhard Stenzel <stenzel@xxxxxxxxxx> on Thu, 11 Jun 1998 14:22:14 +0000]
> Where is my "http://test/cgi?test"; gone? I would expect it between the two
> QUERYLOC lines. Is this expectation wrong?

>The queryloc form does not include #PCDATA in its content, and
>therefore the content of your URLLOC element is not considered
>architectural (since the default setting for ArcIgnDA is cArcIgnD).
I tried

<!ATTLIST urlloc
          id       ID   #REQUIRED
          HyTime   NAME #FIXED "queryloc"
          notation (URL) #FIXED "URL"
          ArcIgnDA nArcIgnD #IMPLIED
>

and

<!ATTLIST #NOTATION HyTime
   ArcIgnDa CDATA #FIXED nArcIgnD
 ...

Result is the same: missing URL. What am I doing wrong here?

>This is because it is the content of the client (urlloc) element that
>is given to the query notation processor, not the content of the
>architectural (queryloc) element.
>The queryloc form was designed this way to account for the possibility
>that the query itself might not be a simple string, and instead might
>be expressed as a set of elements conforming to a particular query
>architecture, in which case it would almost certainly not work to
>process only the HyTime architectural instance.

Let me see, if I understand this:
A HyTime engine could work on the HyTime architectural instance of the
document,
because there are all the elements it knows, but in the case of a queryloc it
must
use the client instance of the document to get access to the actual query
information.
Is this a correct summary?
If yes, does this meam a HyTime engine always has to work with both instances?
Or should I better forget the architectural instance and work on the other one
instead
from the beginning?

Thanks, Gerhard





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