W3C home > Mailing lists > Public > www-tag@w3.org > January 2003

Re: Options for dealing with IDs

From: Chris Lilley <chris@w3.org>
Date: Tue, 7 Jan 2003 23:52:33 +0100
Message-ID: <17477938031.20030107235233@w3.org>
To: www-tag@w3.org, "David Orchard" <dorchard@bea.com>

On Tuesday, January 7, 2003, 11:18:26 PM, David wrote:


DO> Paul,

DO> Sure XPointer looks at the infoset.  But how does the infoset get the idattr
DO> property?  If I build a streaming parser for XPointer that uses xml:idattr,
DO> I've got to scan every element for an idattr attribute when looking for IDs.
DO> For example:
DO> <myxml>
DO>  <child1>
DO>    <grandchild1>
DO>      <greatgrandchild xml:idattr="name">
DO>         <greatgreatgrandchild name="3">

DO> I'm not saying this is an insurmountable problem.  It just is a deficiency.

I agree and that should be noted in a revised version of the options
document. A scoped solution requires checking every element both for
the current in-scope attribute declared as ID and also for xml:idAttr
attributes just in case somewhere there is a declaration of a new
attribute of type ID.

Although, searching for an id seems to require visiting all nodes in
the document anyway, at least until a match is found.



-- 
 Chris                            mailto:chris@w3.org
Received on Tuesday, 7 January 2003 17:52:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:15 GMT