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

RE: IDs considered harmful or why keys might be better than ID

• To: "John Cowan" <jcowan@r...>,"Jonathan Borden" <jborden@m...>
• Subject: RE: IDs considered harmful or why keys might be better than IDs...
• From: "Evan Lenz" <elenz@x...>
• Date: Mon, 12 Nov 2001 15:13:24 -0800
• Cc: "Eric van der Vlist" <vdv@d...>, <xml-dev@l...>
• Importance: Normal
• In-reply-to: <3BF05116.3020208@r...>

John Cowan wrote:
> Jonathan Borden wrote:
>
>
> > The only reason that I see the need for something really
> lightweight like
> > "xml:id" is that internal subsets are not well handled by
> common software
> > (e.g. SAX),
>
>
> Actually, SAX is able to report the types of attributes.  There is
> nothing in XML 1.0 requiring XML processors to make this information
> available, however.

I didn't realize that attribute types were not required to be reported, but
that certainly does seem to be the case[1].

> It would be interesting to know which XML processors don't report
> attribute type information for attributes declared in the internal
> subset.

XPath won't work properly with any XML processor that doesn't, so that would
indeed be interesting. It's good to know that SAX provides access to this
information.

Perhaps instead of adding something like xml:id, the next version or errata
or xml-dev RDDL-like effort just needs to tighten up the requirements about
what to report from the internal subset (that would be a short spec for
sure).

Evan Lenz
XYZFind Corp.

[1] "Definition: While they are not required to check the document for
validity, they are required to *process* all the declarations they read in
the internal DTD subset and in any parameter entity that they read, up to
the first reference to a parameter entity that they do not read; that is to
say, they must use the information in those declarations to normalize
attribute values, include the replacement text of internal entities, and
supply default attribute values." (emphasis in original)
http://www.w3.org/TR/REC-xml#proc-types

• Follow-Ups:
  • RE: IDs considered harmful or why keys might be better than IDs...
    • From: "Michael Kay" <michael.h.kay@n...>

• References:
  • Re: IDs considered harmful or why keys might be better than IDs...
    • From: John Cowan <jcowan@r...>

• Prev by Date: Re: So maybe ID isn't a problem after all.
• Next by Date: Re: IDs considered harmful or why keys might be better than IDs...
• Previous by thread: Re: IDs considered harmful or why keys might be better than IDs...
• Next by thread: RE: IDs considered harmful or why keys might be better than IDs...
• Index(es):
  • Date
  • Thread