[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XPointer crisis

• To: Joe English <jenglish@f...>
• Subject: Re: XPointer crisis
• From: Christian Nentwich <c.nentwich@c...>
• Date: 04 Feb 2002 17:16:56 +0000
• Cc: xml-dev@l...
• In-reply-to: <200202041652.g14GqKj07104@d...>
• References: <1012819375.1075.12.camel@w...> <20020201144101.E29819@r...> <1012587257.27106.38.camel@l...> <p05100303b8807575e600@[192.168.155.106]> <1012587257.27106.38.camel@l...> <20020201123611.D29819@r...> <5.1.0.14.0.20020201134448.029015c8@157.189.161.214> <200202012136.g11LaZj26264@d...> <200202041652.g14GqKj07104@d...>

> > > reference) a DTD, W3C XML Schema, or other infoset-augmenting
> > > resource.  As an added bonus, the recipient doesn't have to
> > > retrieve (and process!) the DTD/XSD/what-have-you.
> > As a negative, the ID values won't be in a hashtable after parsing,
> Why wouldn't they be?  An XML parser could still build an
> index from known ID-bearing attributes, and use the index
> when possible.  There's no reason why an application

But the point of this argument was that xml:id was not necessary.. so
how can the parser know which attributes are ID-bearing without a DTD,
XSD, or xml:id attribute?

Or was your intention to suggest that the application should build the
hashtable? In that case, I would be disappointed if the parser didn't do
it for me, because it's a very common operation and I'm lazy.

Christian Nentwich

• References:
  • Re: XPointer crisis
    • From: Christian Nentwich <c.nentwich@c...>
  • Re: XPointer crisis
    • From: Daniel Veillard <veillard@r...>
  • Re: XPointer crisis
    • From: "Simon St.Laurent" <simonstl@s...>
  • XPointer crisis
    • From: "David G. Durand" <david@d...>
  • Re: XPointer crisis
    • From: Daniel Veillard <veillard@r...>
  • Re: XPointer crisis
    • From: Jonathan Robie <jonathan.robie@s...>
  • Re: XPointer crisis
    • From: Joe English <jenglish@f...>
  • Re: XPointer crisis
    • From: Joe English <jenglish@f...>

• Prev by Date: Re: XPointer crisis
• Next by Date: Categories of Web Service messages: data-oriented vs action-oriented
• Previous by thread: Re: XPointer crisis
• Next by thread: Re: XPointer crisis
• Index(es):
  • Date
  • Thread