[closed] Re: FW: W3C XML ID ambiguity

Thanks for getting back to us, Ann.

/ "Bassetti, Ann" <ann.bassetti@boeing.com> was heard to say:
| Hello Norm, Bert, and others --
|
| (First, I apologize for my tardy response. I apparently overlooked
| Norm's original query, in my vacation email stack. Thanks for pinging
| me, Norm!)
|
| My colleagues really appreciate the time you took to consider this
| issue. (I'm really only the intermediary in this discussion.)  Of course
| they are a bit disappointed in the outcome, since you didn't end up
| agreeing with the solution they suggested. But they realize that you are
| considering a broad range of architectural issues, and accept your
| decision.
|
| Bottom line is that just really want this to work, and they won't really
| know until they try, which will be a few months hence. Apparently Boeing
| has a lot hanging in the balance. Once my colleagues start actually
| implementing, they'll let you know if there are problems. 
|
| Thanks again for your attention to our issue!
|
| Best -- Ann
|
| Ann Bassetti
| Web Integration Manager
| Boeing Information Technology
| Computing and Network Operations
| telephone:  425-957-5161
| pager:  206-797-3762
| email:  ann.bassetti@boeing.com
|
| -----Original Message-----
| From: Norman Walsh [mailto:Norman.Walsh@Sun.COM] 
| Sent: Friday, June 10, 2005 10:32 AM
| To: Bassetti@nwalsh.com; Bassetti, Ann
| Cc: public-xml-id@w3.org; Bugbee, Larry; Bert Bos; Reid, Travis S;
| Gerstmann, Jerry P; Meadows, Joe
| Subject: RE: FW: W3C XML ID ambiguity
|
| Ann,
|
| The XML Core WG has considered the issue you raised[1] at length. While
| opinion on this issue may remain divided, we believe that the consensus
| rests with the status quo. At least, within the XML Core WG, that is the
| consensus position. In brief:
|
| 1. The use of "xml:id" is consistent with xml:lang and xml:space.
|
| 2. The xml: prefix cannot be bound to other URIs, nor can other prefixes
|    be bound to the XML namespace name so the complxity that would arise
|    from those circumstances does not occur in practice.
|
| 3. While there are some issues with canonicalization, we perceive
|    these to be problems with the C14N specification.
|
| We hope that the discussion that followed your comment has been valuable
| and that you are satisified with our resolution of these issues. If you
| are not, please let us know.
|
|                                         Be seeing you,
|                                           norm
|
| [1] http://lists.w3.org/Archives/Public/public-xml-id/2005Apr/0013
|
| -- 
| 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.

                                        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.