- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 19 Dec 2008 11:20:06 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6325 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 http://markmail.org/message/or2ialckrngn5xdk <quote> 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. </quote> 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