Re: xml:id versus xmlid

/ Elliotte Harold <elharo@metalab.unc.edu> was heard to say:
| Norman Walsh wrote:
|
|> This is simply misleading. The name xml:id requires no additional
|> complexity over the name xmlid. By analogy, the concept of an
|> element's natural language or the significance of whitespace in the
|> element "is so basic and fundamental that it should be usable by
|> everybody" and *it is* with attributes named xml:lang and xml:space.

Sorry, I was unclear, when I wrote this paragraph I meant that xml:id
reuqires no additional complexity *for the author*. No namespaces need
to be declared, nothing special needs to be done.

| On the implementer side, I have worked on the issue of xml: attributes in three

I concede that the implementor has to do more work.

| name. For xmlid, I simply need to say something like
|
| element.getAttributeValue("xmlid");
|
| For xml:id, by contrast, one must say something like:
|
| element.getAttributeValue("id", "http://www.w3.org/1998/XML/namespace");
|
| Frankly, I have to look up that string in Google every time I use it. With
| autocomplete in Eclipse, it's a little easier to type

That's a good point.

                                        Be seeing you,
                                          norm

-- 
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 Tuesday, 26 April 2005 14:18:27 UTC