From owner-incits-v1@incits-v1.org Sat Jun 2 12:47:27 2007 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Date: Sat, 02 Jun 2007 15:46:03 -0400 From: Patrick Durusau Subject: INCITS-V1: Schema errors 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: 1180813613-68ad00060000-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: 1180813613 X-ASG-Whitelist: Client X-ASG-Orig-Subj: Schema errors X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at insimail.com Greetings! I kept getting errors when trying to run the schema documentation program so I ran SQC against wml.xsd at its highest paranoid setting. From the report you will see below you will notice two XPath errors. The reason is easy enough to find: uniqueContextAnchorIdsInsideMath does not exist outside of shared-math.xsd and only at those two calls. I don't know what it was supposed to say so I can't fix it. I didn't check the RELAX NG version or the other schemas. BTW, I am going to have to generate separate reports for a lot of the schemas (I will have to see if I need to include the shared ones.). It is a reflection of the very low level components that can be recombined at a very low level. But there is no documentation for the schema organization so I had to hand construct it by examining each file. The division of the schemas will make it more difficult to get an overview of the element models and attribute lexical/value spaces on any kind of systematic basis. I seem to remember there was some talk about schema viewing as part of the TC 45 process. Did that result in any software? I suppose I could write an UR schema that imports all the others and run documentation against it. Against wml.xsd it is running about 19 MB of html pages so it may be something that I do late in the afternoon and let it run overnight. The only think I don't know is how the software is going to react to having any element imported more than once. I guess I could run a test case to see what it does. Maybe wml.xsd and vml-main.xsd as the latter calls wml.xsd. The software may just clutch its side and fall over. ;-) I will report back on what I find out. Hope everyone is having a great weekend! Patrick ***Error Report*** 2007-06-02T14:10:41 No node in <xsd:element maxOccurs="unbounded" minOccurs="1" name="oMath" nillable="false" type="CT_OMath"> <xsd:annotation> <xsd:documentation>Office Math</xsd:documentation> </xsd:annotation> <xsd:unique name="uniqueContentAnchorIdsInsideMath"> <selector xpath="m:annotation/m:content"/> <field xpath="@id"/> </xsd:unique> <xsd:unique name="uniqueContextAnchorIdsInsideMath"> <selector xpath="m:annotation/m:context"/> <field xpath="@id"/> </xsd:unique> </xsd:element> corresponds to <xsd:selector xpath="m:annotation/m:content"/> defined in <xsd:unique name="uniqueContentAnchorIdsInsideMath"> <selector xpath="m:annotation/m:content"/> <field xpath="@id"/> </xsd:unique> . Invalid XPath starting from http://schemas.openxmlformats.org/officeDocument/2006/math:oMath:m:annotation/m:content. No node in <xsd:element maxOccurs="unbounded" minOccurs="1" name="oMath" nillable="false" type="CT_OMath"> <xsd:annotation> <xsd:documentation>Office Math</xsd:documentation> </xsd:annotation> <xsd:unique name="uniqueContentAnchorIdsInsideMath"> <selector xpath="m:annotation/m:content"/> <field xpath="@id"/> </xsd:unique> <xsd:unique name="uniqueContextAnchorIdsInsideMath"> <selector xpath="m:annotation/m:context"/> <field xpath="@id"/> </xsd:unique> </xsd:element> corresponds to <xsd:selector xpath="m:annotation/m:context"/> defined in <xsd:unique name="uniqueContextAnchorIdsInsideMath"> <selector xpath="m:annotation/m:context"/> <field xpath="@id"/> </xsd:unique> . Invalid XPath starting from http://schemas.openxmlformats.org/officeDocument/2006/math:oMath:m:annotation/m:context. 2007-06-02T14:11:12 -- 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!