30022 2016-11-29 07:17:01 +0000 [xdm 3.1] minor editorial changes in introduction and conformance 2016-12-07 15:06:02 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Data Model 3.1 Member-only Editors Drafts PC Linux RESOLVED FIXED P2 minor --- 1 liam andrew_coleman andrew_coleman public-qt-comments oldest_to_newest 128261 0 liam 2016-11-29 07:17:01 +0000 All very minor issues. 1. [introduction] [[ The data model is based on the [Infoset] (henceforth "Infoset"), but it requires the following new features to meet the [XQuery 3.1 Requirements]: ]] The features listed are not new to XQuery 3.1. It's also not true (e.g. we treat text nodes differently, and the XML Information Set is, strictly speaking, a glossary and not a data model). Suggest [[ The data model describes items similar to those of the [Infoset] (henceforth "Infoset"). It is written to provide a data model suitable for XPath, XQuery and XSLT, which was not a goal of the Infoset, and this leads to a number of differences, some of which are: ]] 2. [introduction] The bullet list, 1st item, mentions ... "that extend the XML Information Set" and should say Infoset. 3. s/accessible, but it does not specify/accessible but does not specify/ (the Infoset also doesn't specify this) 4. [[ Every node is one of the seven kinds of nodes defined in 6 Nodes ]] Erm, seven or six? Oh wait, it's a link to section 6. Boy, that's confusing! Maybe add the word "Section" before the link? 5. [Definition: the root node...] doesn't start a paragraph. 6. In 2.1.1 last bullet, add a coma after xs:untypedAtomic, since it's not a union type. 7. in 2.5 Sequences I read, "A sequence may contain any mixture of nodes, functions, and atomic values" - what about arrays and maps? (arguably they are derived from functions so maybe this is OK, but I think that fact would surprise many readers so it may be worth drawing out in a note) 8. the inheritance diagram XPathTypeHierarchy-3-anyAtomicTypes-3.1.png doesn't seem to mention xs:error Conformance - maybe add a note about xml:id and xml:base support being required? (this follows from the other specs I think) 128293 1 andrew_coleman 2016-12-07 15:06:02 +0000 All changes have been applied except xs:error which we discussed doesn't belong on that diagram since it is a union type.