- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 20 Jan 2005 16:47:51 +0000 (UTC)
- To: Norman Walsh <Norman.Walsh@Sun.COM>
- Cc: public-xml-id@w3.org
On Thu, 20 Jan 2005, Norman Walsh wrote: > > | It > | would be unfortunate if one Web browser never updated its concept of > | IDness where another maintained its IDness live with document changes, as > | the results for scripts, stylesheets, XForms, et al, would be radically > | different. If both behaviours are conformant, then interoperability will > | be hard to obtain. > > This problem already exists. At the moment ID assignment is only > normatively performed by the parser. Not even that, at the moment. xml:id is the first spec I know of that defines how processors are supposed to assign an ID to an element. The existence of a problem doesn't defend introducing the problem in other specifications. :-) > I believe that our statement, "Users of applications that provide > facilities for modifying XML documents may reasonably expect xml:id > processing to occur whenever a change is made to an ID value", will > encourage interoperability. I am not convinced that this will be enough, but I suppose it can be revisited in a future revision if interoperability is poor. I therefore retract this request. Cheers, -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 20 January 2005 16:47:54 UTC