• To: xml-dev@l...
• Subject: RE: So maybe ID isn't a problem after all.
• From: "Champion, Mike" <Mike.Champion@S...>
• Date: Fri, 9 Nov 2001 15:51:36 -0500

> -----Original Message-----
> From: Tim Bray [mailto:tbray@t...]
> Sent: Friday, November 09, 2001 3:41 PM
> To: xml-dev@l...
> Subject:  So maybe ID isn't a problem after all.
> 
>
> 
> So where's the problem?  When you're trying to process an
> XLink/XPointer into something and the only thing you know
> about it is that it's XML. 

I'd like to use getElementById() in well-formed XML, or when processing
instances of a DTD I don't control but for which I "know" that a certain
attribute has unique values.  If I could easily slip in an id-ness
declaration out of band somehow, the DOM implementation will do a fair
amount of work for me that is tedious to do by hand. I'm not a heavy user of
XSLT, but I suspect that a similar use case exists for the id() function.

• Follow-Ups:
  • Re: So maybe ID isn't a problem after all.
    • From: "Jonathan Borden" <jborden@m...>

• Prev by Date: RE: Re: determining ID-ness in XML
• Next by Date: Re: Re: determining ID-ness in XML
• Previous by thread: Re: So maybe ID isn't a problem after all.
• Next by thread: Re: So maybe ID isn't a problem after all.
• Index(es):
  • Date
  • Thread