This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
There are some cross-document references to sections and terms in the 1.0 documents that need to be updated to refer to the the 1.1 documents. 1. In third paragraph of section 2.2.1, there is a link to "Section 3.3 Construction from a PSVI" in DM 1.0. 2. In section 3.1.1, the first paragraph following the productions has a reference to "Section 17.1.1 Casting from xs:string and xs:untypedAtomic" in F&O 1.0. 3. In section 3.15.3, list item 4.a has a link to "Section 17.1 Casting from primitive types to primitive types" in F&O 1.0. 4. In the last sentence of section 3.16, there is a link to "Section 3.3.1.1 Element and Attribute Node Type Names" in DM 1.0. 5. In section 5.3, there is a link to "Section 3.2 Construction from an Infoset" in DM 1.0 in the first item in the first list, and a link to "Section 3.3 Construction from a PSVI" in DM 1.0 in the second item in the first list. 6. In Appendix A.1, the links to the extra-grammatical constraints, whitespace rules and grammar notes all link to XQuery 1.0 (or in the case of the XPath 2.1 draft, they link to XPath 2.0).
Fixed for XQuery - assigning to Mike for F&O, copying Norm for DM.
The changes to XQuery/XPath 3.0 look good, except for one nit: the references to sections in F&O 3.0 do not include the section number. For example, we find references to "Section Casting from xs:string and xs:untypedAtomic" and "Section fn:distinct-values," whereas the references to sections of XDM 3.0 include the section number, as in "Section 3.3.1.1 Element and Attribute Node Types." I'm not sure there were any problems in DM 3.0 or F&O 3.0 themselves - or if there were, and I noticed, I would have reported them against those drafts.
We believe this is fixed in the current draft.
Looks good.