From owner-incits-v1@incits-v1.org Fri Jun 8 10:11:22 2007 MIME-Version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_WgTABQs//xrKY9QjvyGh4A)" Date: Fri, 08 Jun 2007 13:09:04 -0400 From: Patrick Durusau Subject: INCITS-V1: [Fwd: Re: Looping definitions?] 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: 1181322605-65ff00740000-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: 1181322605 X-ASG-Whitelist: Client X-ASG-Orig-Subj: [Fwd: Re: Looping definitions?] X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at insimail.com This is a multi-part message in MIME format. --Boundary_(ID_WgTABQs//xrKY9QjvyGh4A) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT Greetings! I mentioned that I was having trouble with xnsdoc (which uses Xerces) generating documentation for the OpenXML schemas. Well, turns out it is a problem in XML Schema. I will be seeing the XML Schema editor in August at Extreme Markup so I will be pressing him for a fix. Hope everyone is looking forward to a great weekend! Patrick -- 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! --Boundary_(ID_WgTABQs//xrKY9QjvyGh4A) Content-type: message/rfc822; name="Re: Looping definitions?" Content-disposition: inline; filename="Re: Looping definitions?" Return-path: Received: (qmail 56538 invoked from network); Thu, 07 Jun 2007 23:45:40 +0000 Received: from unknown (HELO smtprelay07.ispgateway.de) (80.67.29.7) by host437.ipowerweb.com with SMTP; Thu, 07 Jun 2007 23:45:40 +0000 Received: (qmail 1067 invoked from network); Thu, 07 Jun 2007 23:48:43 +0000 Received: from unknown (HELO BEAPRW311) (687282@[84.140.233.110]) (envelope-sender ) by smtprelay07.ispgateway.de (qmail-ldap-1.03) with SMTP for ; Thu, 07 Jun 2007 23:48:43 +0000 Date: Fri, 08 Jun 2007 01:48:41 +0200 From: mail@buldocs.com Subject: Re: Looping definitions? To: patrick@durusau.net Message-id: <001801c7a95e$60d10700$18b2a8c0@bea.de> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Mailer: Microsoft Outlook Express 6.00.2900.3028 Content-type: text/plain; format=flowed; charset=iso-8859-1; reply-type=response Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal Delivered-to: durusaun-patrick@durusau.net X-Account-Key: account2 References: <46601258.4070006@durusau.net> <002101c7a559$83917990$72caa8c0@bea.de> <46628F6A.4000706@durusau.net> Hello Patrick, the origin for these problems is an ambiguous part in the W3C XML-Schema specification concerning multiple imports for the same namespace URI. Please also read the following web pages about this issue: http://www.xmlopen.org/ooxml-wiki/index.php/Schema_Annexes http://www.xmlopen.org/ooxml-wiki/index.php/Talk:Schema_Annexes Since xnsdoc is essentially based on Apache Xerces for schema processing, this issue will not be fixed in xnsdoc, unless Apache Xerces changes its interpretation of the specification, keeping in mind that Xerces seems to implements what XML Schema experts recommend. A common solution for this problem is to build an "adapter schema" which is imported in place of the multiple existing imports, which uses xs:include directives to include all the schemas that reference the same namespace. Kurt buldocs support team http://www.buldocs.com ----- Original Message ----- From: "Patrick Durusau" To: Sent: Sunday, June 03, 2007 11:52 AM Subject: Re: Looping definitions? > Kurt, > > I have pasted the error log from xnsdoc below. > > Note that SQC (the IBM schema checker) at its most paranoid setting does > not report these errors. > > Hope you are having a great day! > > Patrick > > Error log: > > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/wml.xsd:5537:55 src-resolve: > Cannot resolve the name 'xml:space' to a(n) 'attribute declaration' > component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/wml.xsd:5537:55 > s4s-elt-invalid-content.1: The content of 'CT_Text' is invalid. Element > 'attribute' is invalid, misplaced, or occurs too often. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:6:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:6:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'simpleType > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:11:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:11:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'simpleType > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:16:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:16:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'simpleType > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:21:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:21:67 > src-resolve: Cannot resolve the name 'a:ST_Coordinate' to a(n) 'simpleType > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/shared-math.xsd:413:55 > s4s-elt-invalid-content.1: The content of 'CT_Text' is invalid. Element > 'attribute' is invalid, misplaced, or occurs too often. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:35:61 > src-resolve: Cannot resolve the name 'a:CT_PositiveSize2D' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:45:95 > src-resolve: Cannot resolve the name 'a:CT_NonVisualDrawingProps' to a(n) > 'type definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:50:117 > src-resolve: Cannot resolve the name > 'a:CT_NonVisualGraphicFrameProperties' to a(n) 'type definition' > component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:107:81 > src-resolve: Cannot resolve the name 'a:CT_Point2D' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:112:90 > src-resolve: Cannot resolve the name 'a:CT_Point2D' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:461:57 > src-resolve: Cannot resolve the name 'a:CT_Point2D' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:476:61 > src-resolve: Cannot resolve the name 'a:CT_PositiveSize2D' to a(n) 'type > definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:483:95 > src-resolve: Cannot resolve the name 'a:CT_NonVisualDrawingProps' to a(n) > 'type definition' component. > xnsdoc found an XML Schema error: > file:/C:/working/OfficeOpenXML-XMLSchema/dml-wordprocessingDrawing.xsd:488:119 > src-resolve: Cannot resolve the name > 'a:CT_NonVisualGraphicFrameProperties' to a(n) 'type definition' > component. > start processing 601 components > > > > mail@buldocs.com wrote: > >> Hello Patrick, >> >> we have forwarded your problem to our developers. Please allow us some >> time >> for a qualified answer, hopefully solving your problem. >> >> Please let us know if we can be of any further assistance. >> >> Best regards, >> >> Kurt >> buldocs support team >> http://www.buldocs.com >> >> >> ----- Original Message ----- From: "Patrick Durusau" >> >> To: >> Sent: Friday, June 01, 2007 2:34 PM >> Subject: Looping definitions? >> >> >>> Greetings! >>> >>> I have licensed a copy of xnsdoc to generate documentation for the >>> OpenXML schemas and have run into a possible problem. >>> >>> I did not capture the messages to a file but when generating the >>> documentation for vml-main.xsd (and wml.xsd as well) I got several >>> messages that xnsdoc was unable to resolve several attribute >>> definitions. >>> >>> I asked pi, who wrote the conversion to RELAX-NG for the XML Schemas and >>> he speculated that it may be looping definitions of the attributes that >>> are causing the problem. >>> >>> I can forward the zip file with the schemas (about 218 K) or you can >>> obtain the schemas from: >>> http://www.ecma-international.org/news/TC45_current_work/OfficeOpenXML-XMLSchema.zip >>> >>> The same messages appeared on both vml-main.xsd and wml.xsd, using both >>> the unlicensed version as well as the licensed version. (I was impressed >>> with the software so I bought a license this morning. Still working on >>> how to add headers/footers, etc.) >>> >>> Hope you are looking forward to a great weekend! >>> >>> Patrick >>> >>> -- >>> Patrick Durusau >>> patrick@durusau.net >>> Chair, V1 - Text Processing: Office and Publishing Systems Interface >>> Co-Editor, ISO 13250-5, Topic Maps -- Reference Model >> >> >> >> >> > > -- > 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! > > --Boundary_(ID_WgTABQs//xrKY9QjvyGh4A)--