Re: 2. Effect of normalisation step on the DOM/Infoset

/ Ian Hickson <ian@hixie.ch> was heard to say:
| On Thu, 20 Jan 2005, Norman Walsh wrote:
[...]
|> | Thus I disagree with this resolution.
|> 
|> Are you persuaded by my observations to change your mind?
|
| No. IMHO, specifications adding layers on top of the XML specification 
| should never change the infoset/DOM representation, only augment it. 

The Core WG reviewed this issue once again and stands by their
earlier resolution.

From the minutes[1] of the 26 Jan telcon:

normalization
-------------
http://lists.w3.org/Archives/Public/public-xml-core-wg/2005Jan/0052
http://lists.w3.org/Archives/Public/public-xml-id/2005Jan/0022

We want xml:id values to be normalized in the infoset.
Ian says browsers don't now do this; he doesn't like
the fact that we are changing the infoset values for
xml:id from what they would be in an infoset created
by an xml:id unaware processor.

But we are quite sure we do want to do this for xml:id.  
Given that we are changing the type of xml:id from CDATA 
to ID, it doesn't seem additionally problematic to normalize
its value too.  It won't break existing documents, since 
there can be no existing documents that use xml:id.  
Our proposed behavior is equivalent to putting something
in your internal subset declaring xml:id to be an id.

                                        Be seeing you,
                                          norm

[1] http://lists.w3.org/Archives/Public/public-xml-core-wg/2005Jan/0065.html

-- 
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.