W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2008

[Bug 6325] New: [DM] Type Hierarchy diagram confusing

From: <bugzilla@wiggum.w3.org>
Date: Fri, 19 Dec 2008 11:20:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-6325-523@http.www.w3.org/Bugs/Public/>


           Summary: [DM] Type Hierarchy diagram confusing
           Product: XPath / XQuery / XSLT
           Version: Recommendation
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Data Model
        AssignedTo: alb.w3c@gmail.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org

Comment from a reader/user who misread the type hierarchy diagram (appearing in
both DM and FO). See the thread starting at 


My mistake was I drew the wrong conclusion from the Type Hierarchy diagram:
http://www.w3.org/TR/xpath-datamodel/#types-hierarchy. There is a line from
xs:QName to xs:string on the diagram, which I was incorrect in thinking was
xs:QName -> xs:string. In reality it is of course two lines merging that
represent xs:QName -> xs:anyAtomicType, and xs:string -> xs:anyAtomicType. 

IMHO the edges of the graph on the diagram should state their direction. UML
has the transparent arrow head symbol to represent the direction for this
relationship. Something similar here would be a good idea.

Another point about this diagram: I think it's really confusing trying to
present two type hierarchies (schema types and item types) on one diagram. It
would be much better to split them into separate diagrams.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 19 December 2008 11:20:16 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:38 UTC