- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 08 Jan 2008 02:15:50 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=2753 ------- Comment #2 from cmsmcq@w3.org 2008-01-08 02:15 ------- For some readers of the spec, I think it would also be useful to identify the graphical notation used, and to explain what the different kinds of arrows mean, and at least in a general way what the diagram is intended to convey. (As one data point: I know one reader who reports that he recognizes the diagram to be UML, but says he has not yet succeeded in understanding it. >From time to time he turns to one or the other of the various UML books he has bought to try to bring himself to learn UML, with the intention of looking up what the arrows mean, but he reports difficulty looking up the meaning of the diagram, since in order to read the rules for understanding the UML diagram he must apparently first know which of the nine classes of UML diagram this is. I point out that this is the kind of UML most frequently encountered, and he agrees but points out that 'the kind you see most frequently' is not a label on any of the sections in any of his books. If the spec expects him as a reader, he says, then the spec would do better not to assume quite so much background in UML.) I'd propose some sample text to say what notation the diagram is in and the essentials of what it conveys, but I've never understood the diagram myself, so I don't know what the paragraph would say.
Received on Tuesday, 8 January 2008 02:15:56 UTC