W3C home > Mailing lists > Public > public-xml-id@w3.org > February 2005

[closed] Re: 4. ID assignment and the empty string

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Thu, 03 Feb 2005 08:43:33 -0500
To: Ian Hickson <ian@hixie.ch>
Cc: public-xml-id@w3.org
Message-ID: <873bwdzrlm.fsf_-_@nwalsh.com>
/ Ian Hickson <ian@hixie.ch> was heard to say:
| On Wed, 2 Feb 2005, Norman Walsh wrote:
|> 1. Rather than speaking of "ID assignment", the specification now
|> speaks of "ID type assignment": [...]
|> 2. We added a note to make it clear that application behavior (e.g.,
|> whether or not the getElementById() function actually accepts the
|> empty string as a legitimate value) is beyond the scope of this
|> specification. [...]
|> Please let us know if this change satisfies your comment. (Our CR 
|> decision call is tomorrow morning, so a prompt reply would be most 
|> appreciated.)
| This change does satisfy my concern, thanks!
|>   Application-level processing of IDs, including which elements can
|>   actually be addressed by which ID values, is beyond the scope of
|>   this specification.
| Just out of interest, which specification _does_ have this in scope?

The specifications that define the APIs that provide facilities for
addressing, I guess. The DOM spec could say that it's not possible to
use '' to address an element by ID. The foo spec could say that IDs
shorter than six characters aren't addressable. Etc.

                                        Be seeing you,

Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc.
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Received on Thursday, 3 February 2005 15:40:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:49 UTC