From owner-incits-v1@incits-v1.org Mon Jun 4 03:29:59 2007 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Date: Mon, 04 Jun 2007 06:27:43 -0400 From: Patrick Durusau Subject: INCITS-V1: Documentation Report Sender: owner-incits-v1@incits-v1.org To: incits-v1@incits-v1.org Reply-to: incits-v1@incits-v1.org X-Accept-Language: en-us, en X-PMX-Version: 5.2.0.264296 X-ASG-Debug-ID: 1180952917-1867005b0000-E618Iy X-Barracuda-URL: http://10.10.100.8:8000/cgi-bin/mark.cgi X-Barracuda-Connect: unknown[66.110.197.207] X-Barracuda-Start-Time: 1180952917 X-ASG-Whitelist: Client X-ASG-Orig-Subj: Documentation Report X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at insimail.com Greetings! Just a quick report on my efforts to build documentation for the schemas in DIS 29500. As you saw from my note over the weekend, there is an XPath error in the shared-math.xsd schema. Well, ignoring that (it was a warning) I tried to load all of the schemas so I could produce one set of documentation. Note first of all that you have to set the Java heap to 64MB initial and 256MB maximum to get SQC to run. (IBM's schema checker) Second, for some odd reason there are five files, that it says it cannot find: dml-shapeDCamera.xsd dml-shapeDLighting.xsd dml-shapeDScene dml-shapeDScenePlane.xsd dml-shapeDStyles.xsd Since I generated the listing of files automatically and pasted them into the schema I am relatively sure that the file names and location are correct. (The other files that were loaded were in the same directory.) To make it even more of a puzzle, the pml-* schemas were listed after the dml-* schemas and they apparently were parsed. Actually what I think is happening is a very subtle schema namespace error. Here's why: XMLSpy gives the following error message: "unable to load schema with target namespace 'http://schemas.openxmlformats.org/drawing/2006/main' from 'dml-shapeDCamera.xsd'. Which is one of the few times that XMLSpy gives a better error message than SQC. ;-) But, if you look at dml-shapeDCamera.xsd you find: XMLSpy uses the MS XML parser and SQC uses Xerces so I don't think what I am seeing is an artifact of the software I am using. BTW, some schema documentation would be nice. Listing the namespaces (note the plural) of the various schemas, and the relationships between the schemas and the nature (import/include) of those relationships. Oh, and consistently in how the schemas are written would be nice as well. If the targetNamespace is going to be listed first, then do so in *all* cases. It really isn't that much effort and it make working with the schemas a lot easier. So, it looks like I am going to have to do separate documentation on the schemas separately, such as wml.xsd and all it includes. Hopefully I can get around the nsmespace problem with the dml files by creating a schema with a minimal namespace and just importing all of them into it. Maybe not. I will see what I can crank out by say mid-week. Hope everyone had a great weekend! Patrick PS: There are apparently looping definitions for some of the attributes that drives xnsdoc up the wall. SQC validates wml.xsd (well, save for the shared-math.xsd XPath errors) so I am not worried about it but just be aware that programs like xnsdoc are going to complain about it. I suspect it doesn't give useful definitions for those attributes considering the error messages. After I regenerate the documentation for wml.xsd I will check them and post a list of what it missed. I have filed a bug report with tech support for xnsdoc with the details. -- Patrick Durusau Patrick@Durusau.net Chair, V1 - Text Processing: Office and Publishing Systems Interface Co-Editor, ISO 13250, Topic Maps -- Reference Model Member, Text Encoding Initiative Board of Directors, 2003-2005 Topic Maps: Human, not artificial, intelligence at work!