Altova Mailing List Archives

RE: [xml-dev] The subsetting has begun

From: "Cavnar-Johnson, John" <JCavnar-Johnson@----.--->
To: xml-dev@-----.---.---
Date: 2/26/2003 7:13:00 PM
As fascinating as this is, what does it have to do with subsetting XML?

> -----Original Message-----
> From: Alaric B. Snell [mailto:alaric@a...]
> Sent: Wednesday, February 26, 2003 1:10 PM
> To: ari@c...
> Cc: Simon St.Laurent; xml-dev@l...
> Subject: Re: [xml-dev] The subsetting has begun
> On Wednesday 26 February 2003 19:00, K. Ari Krupnikov wrote:
> > <!DOCTYPE A [
> > ]>
> > <A>
> >   <B>
> >     <D id="d1">
> >       <any> children D might have, just to make it more
> interesting</any>
> >     </D>
> >   </B>
> >   <C>
> >     <D ref="d1"/>
> >   </C>
> > </A>
> Ah, but that's implementing a form of pointer on top of the underlying
> tree
> structure by nominating a part of the tree - that, otherwise, would
> nothing but that 'id' equalled 'd1' - and giving it some semantics.
> Yet again, unless your program explicitly went to the effort of
> up
> the id references itself, any parser would still show the D within B
> the
> D within C to be different elements. Even in XPath, they are
> The
> DTD declares that the second D is linked to the first in some way, but
> doesn't say that this is supposed to be an identity constraint, so it
> still
> doesn't make it a DAG, it merely potentially *suggests* a DAG
viewpoint of
> the tree :-)
> It would be a DAG if, instead of the second D, you could write:
> <?xml-ptr d1?>
> ...with <?xml-ptr?> being defined as being substituted for the element
> whose
> ID is d1 during parsing.
> But anyway! I'm splitting hairs and have been doing so all day! Stop
> baiting
> me! :-)
> --
> A city is like a large, complex, rabbit
>  - ARP
> -----------------------------------------------------------------
> The xml-dev list is sponsored by <>, an
> initiative of OASIS <>
> The list archives are at
> To subscribe or unsubscribe from this list use the subscription
> manager: <>


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.