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

Re: Options for dealing with IDs

From: Norman Walsh <Norman.Walsh@Sun.COM>
Date: Tue, 07 Jan 2003 14:21:51 -0500
To: www-tag@w3.org
Message-ID: <871y3og3zk.fsf@nwalsh.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

<stage-direction>
Norm leans forward, trying to see what's at the bottom of this particular
slippery slope. Stepping gingerly forward...</stage-direction>

If we're going to start changing what IDs mean, and how they're
identified (and I have real reservations about doing so), I wonder if
we should simultaneously try to fix the most common error I see in XML
documents with respect to ID values: users trying to use unique values
that do not satisfy the "Name" production as IDs:

  <employee id="Norman Walsh"/>
  <component id="001324"/>
  etc.

I've seen several variations of the latter example where the name of
the ID attribute was not "id". I don't think the options that force
people to use the name "id" are very friendly.

                                        Be seeing you,
                                          norm

- -- 
Norman.Walsh@Sun.COM    | Linux. Because rebooting is for hardware
XML Standards Architect | upgrades.
Web Tech. and Standards |
Sun Microsystems, Inc.  | 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>

iD8DBQE+GyjPOyltUcwYWjsRAgTIAJ0bzRnQeVMq6ExrVNVJmFfk40fHVgCeODmC
y0w3jkuL3uYQQVnsJUc1MwQ=
=b3Bl
-----END PGP SIGNATURE-----
Received on Tuesday, 7 January 2003 14:21:56 GMT

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