This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
(part of the series of issues on FO31 review) The section 1.6 on the type system does not make clear what the relation is between item and list types. In particular, the first diagram starts with item, and has xs:anyAtomicType as a descendant. The second diagram also has xs:anyAtomicType in it, with xs:anySimpleType as parent. You may deduce from this that item == xs:anySimpleType, or more indirectly, item is a parent (and therefore an instance of) list types, but I doubt that is the intent. I have to admit I am not sure how this could be drawn differently, perhaps a note that explains the relation between diagram 1 and 2 better?
F+O merely copies these diagrams from the Data Model spec. There is no relation between item types and list types, other than the fact that both (unfortunately) use the same word "type" in their names. Item types fit into the hierarchy rooted at item(), which is defined in XDM, while list types fit into the hierarchy rooted at xs:anyType, which is defined in XSD. Comparing the two is a category error. We've made good progress in separating the concepts since XDM 1.0, which attempted to show both hierarchies on a single diagram.
Reclassified as F+O 3.1.
The introduction sentence calls out that the type system comprises two distinct subsystems that both include primitive atomic types. Mike will try to restructure the section to help clarify this. I am closing the bug but feel free to reopen with suggestions on further clarifications that you think would be helpful.
Seems reasonable, tx.