- From: Grosso, Paul <pgrosso@ptc.com>
- Date: Wed, 10 Sep 2008 12:17:28 -0400
- To: <public-qt-comments@w3.org>
- Cc: <public-xml-core-wg@w3.org>
During our telcon of 2008 September 10 [1], the XML Core WG had consensus to endorse Henry's request that the definition of fn:id() be correct via erratum. Paul Grosso for the XML Core WG [1] http://lists.w3.org/Archives/Public/public-xml-core-wg/2008Sep/0016 > -----Original Message----- > From: public-xml-core-wg-request@w3.org On Behalf Of Henry S. Thompson > Sent: Wednesday, 2008 September 03 11:08 > To: public-xml-core-wg@w3.org > Subject: XPath2 F&O fn:id() broken wrt XPointer > > F&O defines fn:id [1], which retrieves element(s) with a given ID, as > you would expect wrt elements with attributes of type ID, but as > follows for elements: > > "The is-id property (See Section 5.5 is-id AccessorDM.) of the > element node is true, and the typed value of the element node is > equal to V under the rules of the eq operator using the Unicode code > point collation." > > So if we have > > <foo xml:id='baz'/> > > or > > <foo myid='baz'/> where myid is assigned type ID by schema validation > > the value of fn:id('baz') is the foo element, but if we have > > <foo> > <myid>baz</myid> where myid is assigned type ID by schema > validation > </foo> > > the value of fn:id('baz') is the myid element. > > This is out of sync with XML Schema's intentions, and, more to the > point for this WG, at odds with the XPointer framework spec's > definition of shorthand (barename) pointer resolution [2]. > > I think we should ask QT for an erratum. > > ht > > [1] http://www.w3.org/TR/xquery-operators/#func-id > [2] http://www.w3.org/TR/xptr-framework/#term-sdi
Received on Wednesday, 10 September 2008 16:18:05 UTC