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

RE: Options for dealing with IDs

From: Paul Grosso <pgrosso@arbortext.com>
Date: Tue, 07 Jan 2003 16:27:59 -0600
Message-Id: <4.3.2.7.2.20030107162112.03e2ecb8@172.27.10.30>
To: <www-tag@w3.org>

At 14:18 2003 01 07 -0800, David Orchard wrote:

>Sure XPointer looks at the infoset.  But how does the infoset get the idattr
>property? 

Maybe we are discussing things on different planes.

You appear to be talking about writing code to process
XPointers by looking at raw XML.

I'm talking more about the specs.

My point is that the XPointer specs are already written
based on the infoset, and they (as specs) don't need to
care how things got into the infoset.

> If I build a streaming parser for XPointer that uses xml:idattr,

If you build something that isn't an XML parser, you're on your own.
I see no reason for W3C specs to care about that scenario.

If you build an XML parser and it doesn't provide the infoset with
the necessary values, then that parser cannot be used in applications
that require such values.  The XPointer specs right now make clear
what values they require from the infoset.  A processor that doesn't 
provide the necessary infoset is not a compliant XPointer processor.

paul
Received on Tuesday, 7 January 2003 17:28:22 GMT

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