http://www.altova.com/ Altova accelerates application development and data management projects with software and solutions that enhance productivity and maximize results. As an innovative, customer-focused company and the creator of XMLSpy and other leading XML, data administration, UML, and Web services tools, Altova is the choice of over 3 million clients worldwide, including virtually every Fortune 500 company. With customers ranging from vast development teams in the world’s largest organizations to progressive one-person shops, Altova’s line of software applications fulfills a broad spectrum of business needs. Altova is an active member of the World Wide Web Consortium (W3C) and Object Management Group (OMG) and is committed to delivering standards-based platform-independent solutions that are powerful, affordable, and easy to use. Altova was founded in 1992 and has headquarters in Beverly, Massachusetts and Vienna, Austria. en-us Copyright © 2005, 2006, 2007 Altova GmbH. All rights reserved. Altova, XMLSpy, MapForce, StyleVision, SemanticWorks, SchemaAgent, UModel, DiffDog, and Authentic are trademarks and/or registered trademarks of Altova GmbH in the United States and/or other countries. The names of and reference to other companies and products mentioned herein may be the trademarks of their respective owners. Tue, 03 Jun 2008 10:00:00 EDT Tue, 03 Jun 2008 10:00:00 EDT Authentic RSS Editor, visit www.altova.com for details pr@altova.com webmaster@altova.com http://www.altova.com/images/logos/altova_right_120.gif http://www.altova.com/ 120 24 Altova Logo On 28/01/2012 23:00, Costello, Roger L. wrote: > > Why can element B2 reference type XYZ without a default namespace declaration but element A1 couldn't? > > /Roger > > Chameleon includes are described differently in XSD 1.1 from the way they are described in XSD 1.0, though the intent was merely to provide a more rigorous description, not to change the behaviour. In 1.1 the description is in terms of a stylesheet: see http://www.w3.org/TR/2012/PR-xmlschema11-1-20120119/#chameleon-xslt When this stylesheet sees type="xyz", it transforms it into type="n:xyz", where n is a namespace prefix that has been bound to the new target namespace. More generally, the effect of the chameleon include is to take the included no-namespace schema, and transform it (a) so that all components are declared to be in the target namespace, and (b) all references to components in no namespace are converted into references to components in the target namespace with the same local name. Michael Kay Saxonica]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324313.html Hi Folks, The following schema document is erroneous because the element A1 is trying to reference a type XYZ in no-namespace: A.xsd ---------------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org" elementFormDefault="qualified"> <xs:include schemaLocation="B.xsd"/> <xs:simpleType name="XYZ"> <xs:restriction base="xs:string"> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> <xs:element name="A1" type="XYZ" /> </xs:schema> ---------------------------------------------------------------------- The error is fixed by adding a default namespace declaration: A.xsd ---------------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org" xmlns="http://www.example.org" elementFormDefault="qualified"> <xs:include schemaLocation="B.xsd"/> <xs:simpleType name="XYZ"> <xs:restriction base="xs:string"> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> <xs:element name="A1" type="XYZ" /> </xs:schema> ---------------------------------------------------------------------- Good. Now let's remove the element A1 and remove the default namespace declaration. This is a valid schema: A.xsd ---------------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.example.org" elementFormDefault="qualified"> <xs:include schemaLocation="B.xsd"/> <xs:simpleType name="XYZ"> <xs:restriction base="xs:string"> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> </xs:schema> ---------------------------------------------------------------------- Notice that the schema document includes B.xsd. Let's look at it. It is a no-namespace schema document: B.xsd ---------------------------------------------------------------------- <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="B2" type="XYZ" /> </xs:schema> ---------------------------------------------------------------------- Since A.xsd has a targetNamespace the B.xsd schema document is namespace-coerced to the namespace of A.xsd. Observe that element B2 references type XYZ which is in A.xsd. When I validate A.xsd it validates fine. Hey! How can that be? Recall that I removed the default namespace declaration from A.xsd. Why can element B2 reference type XYZ without a default namespace declaration but element A1 couldn't? /Roger]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324312.html =============== CALL FOR PAPERS =============== The 6th International Symposium on Rules: Research Based and Industry Focused, Montpellier, France, August 27-29, 2012. http://2012.ruleml.org The International Symposium on Rules, RuleML, has evolved from an annual series of international workshops since 2002, international conferences in 2005 and 2006, and international symposia since 2007. This year the RuleML Symposium will be held in conjunction with ECAI 2012, the 20th biennial European Conference on Artificial Intelligence, in Montpellier, France, August 27-29, 2012. RuleML 2012 will be the host of the 7th AIS SigPrag International Conference on Pragmatic Web (ICPW 2012). Objectives ============================================ RuleML-2012@ECAI is a research-based, industry-focused symposium: its main goal is to build a bridge between academia and industry in the field of rules and semantic technology, and so to stimulate the cooperation and interoperability between business and research, by bringing together rule system providers, participants in rule standardization efforts, open source communities, practitioners, and researchers. The concept of the symposium has also advanced continuously in the face of extremely rapid progress in practical rule and event processing technologies. As a result, RuleML-2012will feature hands-on demonstrations and challenges alongside a wide range of thematic tracks. It will thus be an exciting venue to exchange new ideas and experiences on all issues related to the engineering, management, integration, interoperation, and interchange of rules in distributed enterprise intranets and open distributed environments. We invite you to share your ideas, results, and experiences: as an industry practitioner, rule system provider, technical expert and developer, rule user or researcher, exploring foundations, developing systems and applications, or using rule-based systems. Topics ============================================ We invite high-quality submissions related to (but not limited to) one or more of the following topics: * Rules and Automated Reasoning * Logic Programming and Non-monotonic Reasoning * Int. Conference track on Pragmatic Web (see track description below) * Rule-Based Policies, Reputation and Trust * Rule-based Event Processing and Reaction Rules * Fuzzy Rules and Uncertainty * Rule Transformation, Extraction and Learning * Vocabularies, Ontologies, and Business rules * Rules in online-market research and online marketing * Rule Markup Languages and Rule Interchange * General Rule Topics Important Dates ============================================ Abstract submission: March 25, 2012 Paper submission: April 1, 2012 Notification of acceptance/rejection: May 20, 2012 Camera-ready copy due: June 10, 2012 RuleML-2012 dates: August 27-29, 2012 Submission guidelines ============================================ Papers must be in English and must be submitted at http://www.easychair.org/conferences/?conf=ruleml2012 as: * Full Papers (15 pages in the proceedings) * Short Papers (8 pages in the proceedings) Please upload all submissions as PDF files based on the LNCS format ( http://www.springer.de/comp/lncs/authors.html). The selected papers will be published in book form in the Springer Lecture Notes in Computer Science (LNCS) series. Organization ============================================ General Chairs: Grigoris Antoniou, Institute of Computer Science, FO.R.T.H., GR Guido Governatori, NICTA, Australia Program Chairs: Antonis Bikakis, University College London, UK Adrian Giurca, Brandenburg University of Technology, DE Satellite Events ============================================ The RuleML2012 Conference is also hosting * The 7th AIS SigPrag International Conference Track on Pragmatic Web * The RuleML2012 Doctoral Consortium: http://2012.ruleml.org/phdconsortium * The 6th International Rule Challenge: http://2012.ruleml.org/rulechallenge Int. Conference on Pragmatic Web (ICPW 2012) ============================================ The conference track on PRAGMATIC WEB is part of RuleML-2012 and centred around the study of "pragmatics" in the Semantic Web. That is, it draws attention to how communicative actions are performed by agents via Web media and illuminates how mutual understanding and commitments to actions can evolve in (agent) conversations. This year the Pragmatic Web conference track has a special focus on the applications of rule-based technologies and AI agent technologies for the Pragmatic Web. Topics of Interest include one or more of the following topics (but are not limited to): * Rule-Based Distributed/Multi-Agent Systems * Rules, Agents and Norms * Rule-Based Communication, Dialogue and Argumentation Models * Vocabularies / ontologies for pragmatic primitives (e.g. speech acts, deontic primitives) * Pragmatic Web reasoning and distributed rule inference / rule execution For further information about the Pragmatic Web see http://www.pragmaticweb.info/ RuleML 2012 Doctoral Consortium ============================================ The RuleML 2012 Doctoral Consortium is an initiative of the International Symposium on Rules, RuleML, to attract and promote Ph.D. research in the area of Rules and Markup Languages. The doctoral symposium offers to students a close contact with leading experts on the field, as well as the opportunity to present and discuss their ideas in a dynamic and friendly setting. The accepted thesis descriptions will be presented to an interested audience and subject to discussion with a panel of senior researchers, and we expect submissions on any (but not limited to) of this year's RuleML2012@ECAI topics. Students are invited to submit an original description of their work addressing the following aspects: * A clear formulation of the research question. * An identification of the significant problems in the field of research.. * An outline of the current knowledge of the problem domain, as well as the state of existing solutions. * A presentation of any preliminary ideas, the proposed approach and the results achieved so far. * A sketch of the applied research methodology. * A description of the Ph.D. project's contribution to the problem solution. * A discussion of how the suggested solution is different, new, or better as compared to existing approaches to the problem. Accepted submissions will be published in internal proceedings and later on published in CEUR Workshop Proceedings (http://www.ceur-ws.org) volume of RuleML. Important Dates ---------------------------------------- Paper submission: June 25, 2012 Notification of acceptance/rejection: July 16, 2012 Camera-ready copy due: July 30, 2012 Doctoral Consortium date: August 27, 2012 Submission guidelines ---------------------------------------- Thesis descriptions are limited to 8 pages in English using LNCS format ( http://www.springer.de/comp/lncs/authors.html) and submitted electronically in PDF format jointly with a maximum 5 page CV. Please submit to: http://www.easychair.org/conferences/?conf=ruleml2012consortium If you have no EasyChair account, then you should sign up for an account at https://www.easychair.org/account/signup.cgi?conf=ruleml2012consortium Chairs ---------------------------------------- Grzegorz J. Nalepa, AGH University of Science and Technology, Kraków, Poland Monica Palmirani, CIRSFID-University of Bologna, Italy 6th International Rule Challenge ============================================ The International RuleML2012@ECAI Challenge is one of the highlights of the RuleML2012 conference. The challenge is dedicated to practical experiences with rule-oriented applications. In particular, submissions of benchmarks/evaluations, demos, case studies/use cases, experience reports, best practice solutions (e.g. design patterns, reference architectures, models), rule-based implementations/tools/applications, demonstrations of engineering methods, implementations of rule standards (e.g. RuleML, RIF, SBVR, PRR, rule-based Event Processing languages, BPMN+rules, BPEL+rules,...), rules + industrial standards (e.g. XBRL, MISMO, Accord,...), and industrial problem statements are particularly encouraged. Key themes of the International RuleML2012@ECAI Challenge include (but they are NOT limited to) the following: * Industrial rule-based applications includiong rule-based Web applications * Demos related to the RuleML2012@ECAI Topics * Extensions and implementations of rule standards: W3C RIF, RuleML, SBVR,... * Editing environments and IDEs for Web rules * Benchmarks and comparison results for rule engines * Distributed rule bases and rule services * Reports on industrial experience about rule systems Previous challenge editions were in Ft Lauderdale, Florida ( http://2011.ruleml.org/america/challenge ), in Washington, DC ( http://2010.ruleml.org/ruleml-2010-challenge.html ), in Las Vegas, Nevada ( http://2009.ruleml.org/challenge ) and Orlando, Florida ( http://2008.ruleml.org/challenge.php and http://2007.ruleml.org/index-Dateien/Page787.htm). RuleML2012Challenge is the first edition taking place in Europe. Important Dates ---------------------------------------- Abstract submission: March 6, 2012 Paper submission: May 25, 2012 Notification of acceptance/rejection: July 1, 2012 Camera-ready copy due: July 15, 2012 RuleML Challenge date: TBA Submission guidelines ---------------------------------------- Submissions to the International RuleML2012@ECAI Challenge consist of: 1. An early 1 page abstract announcing the application. 2. An open-source or commercial demo 3. A demo paper, using LNCS format, describing research, implementation, and technical details of your submission. Submit both the demo and the paper to http://www.easychair.org/conferences/?conf=ruleml2012challenge. Would you have an online demo please indicate in the description paper an URL were it can be tested and evaluated. If you have no EasyChair account, then you should sign up for an account at https://www.easychair.org/account/signup.cgi?conf=ruleml2012challenge Chairs ---------------------------------------- Adrian Giurca, Yuh-Jong Hu and Dumitru Roman]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324292.html Thanks for the suggestion, Clemens, but I see that its use requires obtaining a free license key, plus it appears to be Windows only. Those aspects would prevent me from including it in the OASIS UBL distribution. That xjparse is a portable JAR file allows me to use that today in the distribution. There are both Windows and shell demonstration scripts that run for users of the UBL package. I've filed a report on xjparse and will make a note to this list when this issue has been repaired by Norm: https://github.com/ndw/xjparse/issues/1 . . . . . . . . . Ken At 2012-01-11 17:45 +0100, office xml-tools.com wrote: >Dear Ken, > >you could use the free XML ValidatorBuddy Command Line Tool (for Windows) >which is available at: http://www.xml-tools.com/download.htm > >I was able to successfully validate your sample files. The tool also uses >the Xerces 3.1 parser internally. If one of the XML documents is invalid an >exit code of -1 is returned, otherwise it returns 0. > >This would be the output on calling: >valbuddy.exe -v -verbose test2.xml > >XML ValidatorBuddy command-line Tool >By xml-tools.com, Copyright 2012 > >G:\Users\xml\Ken Holman\test2.xml: invalid >Line: 6, Col: 6 : no declaration found for element 'doc' >Line: 2, Col: 8 : no declaration found for element 'test' > > >And this is the output on calling: >Valbuddy.exe -v -verbose -s test.xsd test2.xml > >XML ValidatorBuddy command-line Tool >By xml-tools.com, Copyright 2012 > >G:\Users\xml\Ken Holman\test2.xml: valid > > >Best regards > >Clemens Uhlenhut >http://www.xml-tools.com > > > >-----Original Message----- >From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] >Sent: Dienstag, 10. Jänner 2012 18:33 >To: xmlschema-dev@w3.org >Subject: Re: Invoking schema validation processors > >At 2012-01-10 11:54 -0500, Michael Glavassevich wrote: > >If Xerces is performing DTD and XSD validation at the same time it's > >because the application (xjparse in this case) configured it [1] (by > >accident?) to do so. There are multiple ways to get Xerces to do XSD > >validation [2] only. > >What I cannot see at that FAQ is how to accomplish this from the command >line. > >The UBL community's users are running validation from batch files. > >Thanks, again, for any guidance. > >. . . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324140.html Dear Ken, you could use the free XML ValidatorBuddy Command Line Tool (for Windows) which is available at: http://www.xml-tools.com/download.htm I was able to successfully validate your sample files. The tool also uses the Xerces 3.1 parser internally. If one of the XML documents is invalid an exit code of -1 is returned, otherwise it returns 0. This would be the output on calling: valbuddy.exe -v -verbose test2.xml XML ValidatorBuddy command-line Tool By xml-tools.com, Copyright 2012 G:\Users\xml\Ken Holman\test2.xml: invalid Line: 6, Col: 6 : no declaration found for element 'doc' Line: 2, Col: 8 : no declaration found for element 'test' And this is the output on calling: Valbuddy.exe -v -verbose -s test.xsd test2.xml XML ValidatorBuddy command-line Tool By xml-tools.com, Copyright 2012 G:\Users\xml\Ken Holman\test2.xml: valid Best regards Clemens Uhlenhut http://www.xml-tools.com -----Original Message----- From: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com] Sent: Dienstag, 10. Jänner 2012 18:33 To: xmlschema-dev@w3.org Subject: Re: Invoking schema validation processors At 2012-01-10 11:54 -0500, Michael Glavassevich wrote: >If Xerces is performing DTD and XSD validation at the same time it's >because the application (xjparse in this case) configured it [1] (by >accident?) to do so. There are multiple ways to get Xerces to do XSD >validation [2] only. What I cannot see at that FAQ is how to accomplish this from the command line. The UBL community's users are running validation from batch files. Thanks, again, for any guidance. . . . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324139.html "G. Ken Holman" <gkholman@CraneSoftwrights.com> wrote on 01/10/2012 12:32:41 PM: > At 2012-01-10 11:54 -0500, Michael Glavassevich wrote: > >If Xerces is performing DTD and XSD validation at the same time it's > >because the application (xjparse in this case) configured it [1] (by > >accident?) to do so. There are multiple ways to get Xerces to do XSD > >validation [2] only. > > What I cannot see at that FAQ is how to accomplish this from the command line. You could use one of Xerces' validation samples [3] instead. > The UBL community's users are running validation from batch files. > > Thanks, again, for any guidance. > > . . . . . . . . . . . . Ken > > > -- > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ > G. Ken Holman mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > Legal business disclaimers: http://www.CraneSoftwrights.com/legal [3] http://xerces.apache.org/xerces2-j/samples-jaxp.html#SourceValidator Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrglavas@ca.ibm.com E-mail: mrglavas@apache.org]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324130.html At 2012-01-10 16:01 +0000, Michael Kay wrote: >I suspect that some parsers interpret the presence of a <DOCTYPE> >declaration as an instruction to perform DTD validation, Precisely. I could analyze that that is what was wrong, but I have no guidance from the documentation on how to get my users running command-line scripts to turn off DTD validation but preserve the entity processing. Hence my post to the list. BTW, I've had no problems with Saxon performing the validation exactly as I need, but the old (ancient) version of 9SA that I have doesn't appear to return a non-zero return code on a validation error. Reading the invocation arguments in the help provided when no arguments are supplied doesn't appear to offer any way to impact the return code. Thanks for confirming my analysis of the situation. My only issue is that I'm using all these tools from the command line and not from inside a program and so I am limited to what can be offered from and to a script. . . . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324129.html At 2012-01-10 11:54 -0500, Michael Glavassevich wrote: >If Xerces is performing DTD and XSD validation at the same time it's >because the application (xjparse in this case) configured it [1] (by >accident?) to do so. There are multiple ways to get Xerces to do XSD >validation [2] only. What I cannot see at that FAQ is how to accomplish this from the command line. The UBL community's users are running validation from batch files. Thanks, again, for any guidance. . . . . . . . . . . . . Ken -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324128.html Michael Kay <mike@saxonica.com> wrote on 01/10/2012 11:01:46 AM: > On 10/01/2012 15:14, G. Ken Holman wrote: > > Hi, folks! And happy new year! > And to you, Ken > > > > Can anyone help me with the invocations of Xerces and Altova W3C > > Schema validation? These processors are reporting problems with valid > > XML documents and I'm hoping that with the right incantations I'll get > > rid of the error messages. > > > > If I don't use external parsed general entities, everything is fine. > > When I do, the processors are expecting to find element DTD > > declarations that do not exist. > I suspect that some parsers interpret the presence of a <DOCTYPE> > declaration as an instruction to perform DTD validation, and that most > of your problems here are that you don't actually want DTD validation > done. If Xerces is performing DTD and XSD validation at the same time it's because the application (xjparse in this case) configured it [1] (by accident?) to do so. There are multiple ways to get Xerces to do XSD validation [2] only. > A lot of the confusion here seems to be that DTD validation and > XSD validation are happening at the same time and the messages from both > are getting mixed up. > > Michael Kay > Saxonica [1] http://xerces.apache.org/xerces2-j/faq-pcfp.html#faq-3 [2] http://xerces.apache.org/xerces2-j/faq-pcfp.html#faq-4 Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrglavas@ca.ibm.com E-mail: mrglavas@apache.org]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324127.html On 10/01/2012 15:14, G. Ken Holman wrote: > Hi, folks! And happy new year! And to you, Ken > > Can anyone help me with the invocations of Xerces and Altova W3C > Schema validation? These processors are reporting problems with valid > XML documents and I'm hoping that with the right incantations I'll get > rid of the error messages. > > If I don't use external parsed general entities, everything is fine. > When I do, the processors are expecting to find element DTD > declarations that do not exist. I suspect that some parsers interpret the presence of a <DOCTYPE> declaration as an instruction to perform DTD validation, and that most of your problems here are that you don't actually want DTD validation done. A lot of the confusion here seems to be that DTD validation and XSD validation are happening at the same time and the messages from both are getting mixed up. Michael Kay Saxonica > > A transcript is below. I'm invoking Xerces using Norm's xjparse with > the "-S" option. The "test3" example illustrates that for Xerces XSD > validation is detecting the bad content even while the processor > complains about the DTD declarations being missing ... which goes > farther than Altova. > > Thank you for any guidance anyone may have regarding invocations. > > . . . . . . . . . Ken > > T:\ftemp>type test.xsd > <?xml version="1.0" encoding="UTF-8"?> > <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" > elementFormDefault="qualified"> > <xs:element name="doc"> > <xs:complexType> > <xs:sequence> > <xs:element name="test"/> > </xs:sequence> > </xs:complexType> > </xs:element> > </xs:schema> > > T:\ftemp>type test1.xml > <?xml version="1.0" encoding="UTF-8"?> > <doc><test/></doc> > > T:\ftemp>w3cschema test.xsd test1.xml > Xerces... > No validation errors. > Saxon... > No validation errors. > Altova... > The XML data is valid. > > T:\ftemp>type test2.xml > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE doc > [ > <!ENTITY test SYSTEM "test2.ent"> > ]> > <doc>&test;</doc> > > T:\ftemp>type test2.ent > <?xml version="1.0" encoding="UTF-8"?> > <test/> > > T:\ftemp>w3cschema test.xsd test2.xml > Xerces... > Attempting validating, namespace-aware parse > Error:file:///T:/ftemp/test2.xml:6:6:Element type "doc" must be declared. > Error:file:///T:/ftemp/test2.ent:2:8:Element type "test" must be > declared. > Parse succeeded (0.250) with 2 errors and no warnings. > Saxon... > No validation errors. > Altova... > The XML data is invalid. > No external markup declarations present - referenced entity '&test;' > must be declared. > > T:\ftemp>type test3.xml > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE doc > [ > <!ENTITY test SYSTEM "test3.ent"> > ]> > <doc>&test;</doc> > > T:\ftemp>type test3.ent > <?xml version="1.0" encoding="UTF-8"?> > <testbad/> > > T:\ftemp>w3cschema test.xsd test3.xml > Xerces... > Attempting validating, namespace-aware parse > Error:file:///T:/ftemp/test3.xml:6:6:Element type "doc" must be declared. > Error:file:///T:/ftemp/test3.ent:2:11:Element type "testbad" must be > declared. > Error:file:///T:/ftemp/test3.ent:2:11:cvc-complex-type.2.4.a: Invalid > content was found starting with element 'testbad'. One of '{test}' is > expected. > Parse succeeded (0.340) with 3 errors and no warnings. > Saxon... > Validation error on line 2 column 11 of test3.ent: > In content of element <doc>: The content model does not allow > element <testbad> to appear > here. Expected: test (See > http://www.w3.org/TR/xmlschema-1/#cvc-complex-type clause 2.4) > Altova... > The XML data is invalid. > No external markup declarations present - referenced entity '&test;' > must be declared. > > T:\ftemp> > > -- > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ > G. Ken Holman mailto:gkholman@CraneSoftwrights.com > Google+ profile: https://plus.google.com/116832879756988317389/about > Legal business disclaimers: http://www.CraneSoftwrights.com/legal > > >]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324126.html Hi, folks! And happy new year! Can anyone help me with the invocations of Xerces and Altova W3C Schema validation? These processors are reporting problems with valid XML documents and I'm hoping that with the right incantations I'll get rid of the error messages. If I don't use external parsed general entities, everything is fine. When I do, the processors are expecting to find element DTD declarations that do not exist. A transcript is below. I'm invoking Xerces using Norm's xjparse with the "-S" option. The "test3" example illustrates that for Xerces XSD validation is detecting the bad content even while the processor complains about the DTD declarations being missing ... which goes farther than Altova. Thank you for any guidance anyone may have regarding invocations. . . . . . . . . . Ken T:\ftemp>type test.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <xs:element name="doc"> <xs:complexType> <xs:sequence> <xs:element name="test"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> T:\ftemp>type test1.xml <?xml version="1.0" encoding="UTF-8"?> <doc><test/></doc> T:\ftemp>w3cschema test.xsd test1.xml Xerces... No validation errors. Saxon... No validation errors. Altova... The XML data is valid. T:\ftemp>type test2.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE doc [ <!ENTITY test SYSTEM "test2.ent"> ]> <doc>&test;</doc> T:\ftemp>type test2.ent <?xml version="1.0" encoding="UTF-8"?> <test/> T:\ftemp>w3cschema test.xsd test2.xml Xerces... Attempting validating, namespace-aware parse Error:file:///T:/ftemp/test2.xml:6:6:Element type "doc" must be declared. Error:file:///T:/ftemp/test2.ent:2:8:Element type "test" must be declared. Parse succeeded (0.250) with 2 errors and no warnings. Saxon... No validation errors. Altova... The XML data is invalid. No external markup declarations present - referenced entity '&test;' must be declared. T:\ftemp>type test3.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE doc [ <!ENTITY test SYSTEM "test3.ent"> ]> <doc>&test;</doc> T:\ftemp>type test3.ent <?xml version="1.0" encoding="UTF-8"?> <testbad/> T:\ftemp>w3cschema test.xsd test3.xml Xerces... Attempting validating, namespace-aware parse Error:file:///T:/ftemp/test3.xml:6:6:Element type "doc" must be declared. Error:file:///T:/ftemp/test3.ent:2:11:Element type "testbad" must be declared. Error:file:///T:/ftemp/test3.ent:2:11:cvc-complex-type.2.4.a: Invalid content was found starting with element 'testbad'. One of '{test}' is expected. Parse succeeded (0.340) with 3 errors and no warnings. Saxon... Validation error on line 2 column 11 of test3.ent: In content of element <doc>: The content model does not allow element <testbad> to appear here. Expected: test (See http://www.w3.org/TR/xmlschema-1/#cvc-complex-type clause 2.4) Altova... The XML data is invalid. No external markup declarations present - referenced entity '&test;' must be declared. T:\ftemp> -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324125.html On 06/01/2012 08:26, Karl Stubsjoen wrote: > > I am kicking myself! > > Now the real challenge and probably a lot off topic.. > I have a base schema class. > I have a working schema class. It includes base and certain elements > extend base types. > I compile the base class with Xsd2Code. > I think there is probably a better forum for asking questions about the Xsd2Code product, which is probably unfamiliar to most people on this list. Michael Kay Saxonica]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324101.html I am kicking myself! Now the real challenge and probably a lot off topic.. I have a base schema class. I have a working schema class. It includes base and certain elements extend base types. I compile the base class with Xsd2Code. I compile the working schema with Xsd2Code with instructions to not compile the included schema rules. The objective: write generic code for the base class and strongly tied code for the working class hoping that I can easily invoke my core business objects that is expecting the base schema code. The problem is there doesn't seem to be support for an xs:extension. There is some other trickiness going on too, but anyone have experience with this? Karl On Jan 5, 2012 7:59 PM, "G. Ken Holman" <gkholman@cranesoftwrights.com> wrote: > At 2012-01-05 17:48 -0700, Karl Stubsjoen wrote: > >> I have an element that extends a complex type but the additional >> attribute with a simple type definition is not being enforced. The >> attribute is enforced, just not it's simple type. Have I defined >> something incorrectly? >> > > I think this is one of those "don't kick yourself" problems. > > Here they are: >> >> <!-- to be used in extension below --> >> <xs:complexType name="ProjXm_QueryType"> >> <xs:sequence> >> <xs:element ref="command"/> >> <xs:element ref="parameters"/> >> <xs:element ref="fields" minOccurs="0"/> >> </xs:sequence> >> </xs:complexType> >> >> >> <!-- extends the above and adds a name attribute of specified simple type >> --> >> <xs:element name="SharedDB"> >> <xs:complexType> >> <xs:complexContent> >> <xs:extension base="ProjXm_QueryType"> >> <xs:attribute name="name" >> type="simpleType_**SharedDBQueries" /> >> > > Here you've just augmented your element with an attribute .... > > </xs:extension> >> </xs:complexContent> >> </xs:complexType> >> </xs:element> >> >> <!-- expected values for name attribute -> >> <xs:simpleType name="simpleType_**SharedDBQueries"> >> <xs:restriction base="xs:NCName"> >> <xs:enumeration value="insert"/> >> <xs:enumeration value="update"/> >> </xs:restriction> >> </xs:simpleType> >> >> >> <!-- sample xml (snipped) --> >> <SharedDB> >> <command> >> <name>insertxx</name><!-- would expect validation to fail here >> --> >> > > ... but you've put an element in your XML for testing. > > <type>StoredProcedure</type> >> <action>NonQuery</action> >> </command> >> <parameters> >> ... >> </SharedDB> >> > > I think if you had <SharedDB name="insertxx"> you would find the problem > NCName flagged. I just copied your exact schema fragment into a bogus > schema below and you'll see the attribute is being validated by both Xerces > and Saxon. > > I hope this helps. > > . . . . . . . . . . . . . Ken > > ~/t/ftemp $ cat karl.xsd > <?xml version="1.0" encoding="UTF-8"?> > <xs:schema xmlns:xs="http://www.w3.org/**2001/XMLSchema<http://www.w3.org/2001/XMLSchema> > " > elementFormDefault="qualified"**> > <!-- to be used in extension below --> > <xs:complexType name="ProjXm_QueryType"> > <xs:sequence> > <xs:element ref="command"/> > <xs:element ref="parameters"/> > <xs:element ref="fields" minOccurs="0"/> > </xs:sequence> > </xs:complexType> > > > <!-- extends the above and adds a name attribute of specified simple type > --> > <xs:element name="SharedDB"> > <xs:complexType> > <xs:complexContent> > <xs:extension base="ProjXm_QueryType"> > <xs:attribute name="name" > type="simpleType_**SharedDBQueries" /> > </xs:extension> > </xs:complexContent> > </xs:complexType> > </xs:element> > > <!-- expected values for name attribute --> > <xs:simpleType name="simpleType_**SharedDBQueries"> > <xs:restriction base="xs:NCName"> > <xs:enumeration value="insert"/> > <xs:enumeration value="update"/> > </xs:restriction> > </xs:simpleType> > > <xs:element name="command"> > <xs:complexType/> > </xs:element> > <xs:element name="fields"> > <xs:complexType/> > </xs:element> > <xs:element name="parameters"> > <xs:complexType/> > </xs:element> > </xs:schema> > ~/t/ftemp $ cat karl.xml > <?xml version="1.0" encoding="UTF-8"?> > <SharedDB name="insert"> > <command/> > <parameters/> > </SharedDB> > ~/t/ftemp $ w3cschema karl.xsd karl.xml > Xerces... > Attempting validating, namespace-aware parse > Parse succeeded (0.131) with no errors and no warnings. > Saxon... > No validation errors > ~/t/ftemp $ cat karlbad1.xml > <?xml version="1.0" encoding="UTF-8"?> > <SharedDB namex="insert"> > <command/> > <parameters/> > </SharedDB> > ~/t/ftemp $ w3cschema karl.xsd karlbad1.xml > Xerces... > Attempting validating, namespace-aware parse > Error:file:///Users/admin/t/**ftemp/karlbad1.xml:2:26:cvc-**complex-type.3.2.2: > Attribute 'namex' is not allowed to appear in element 'SharedDB'. > Parse succeeded (0.135) with 1 error and no warnings. > Saxon... > Validation error on line 2 column 26 of karlbad1.xml: > Attribute @namex is not allowed on element <SharedDB> (See > http://www.w3.org/TR/**xmlschema-1/#cvc-complex-type<http://www.w3.org/TR/xmlschema-1/#cvc-complex-type>clause 3) > No validation errors > ~/t/ftemp $ cat karlbad2.xml > <?xml version="1.0" encoding="UTF-8"?> > <SharedDB name="insertx"> > <command/> > <parameters/> > </SharedDB> > ~/t/ftemp $ w3cschema karl.xsd karlbad2.xml > Xerces... > Attempting validating, namespace-aware parse > Error:file:///Users/admin/t/**ftemp/karlbad2.xml:2:26:cvc-**enumeration-valid: > Value 'insertx' is not facet-valid with respect to enumeration '[insert, > update]'. It must be a value from the enumeration. > Error:file:///Users/admin/t/**ftemp/karlbad2.xml:2:26:cvc-**attribute.3: > The value 'insertx' of attribute 'name' on element 'SharedDB' is not valid > with respect to its type, 'simpleType_SharedDBQueries'. > Parse succeeded (0.146) with 2 errors and no warnings. > Saxon... > Validation error on line 2 column 26 of karlbad2.xml: > FORG0001: Value "insertx" contravenes the enumeration facet "update, > insert" of the type > simpleType_SharedDBQueries (See http://www.w3.org/TR/** > xmlschema-1/#cvc-complex-type<http://www.w3.org/TR/xmlschema-1/#cvc-complex-type>clause 3) > No validation errors > ~/t/ftemp $ > > > -- > Contact us for world-wide XML consulting and instructor-led training > Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h > Crane Softwrights Ltd. http://www.CraneSoftwrights.**com/x/<http://www.CraneSoftwrights.com/x/> > G. Ken Holman mailto:gkholman@**CraneSoftwrights.com<gkholman@CraneSoftwrights.com> > Google+ profile: https://plus.google.com/**116832879756988317389/about<https://plus.google.com/116832879756988317389/about> > Legal business disclaimers: http://www.CraneSoftwrights.**com/legal<http://www.CraneSoftwrights.com/legal> > > >]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324098.html At 2012-01-05 17:48 -0700, Karl Stubsjoen wrote: >I have an element that extends a complex type but the additional >attribute with a simple type definition is not being enforced. The >attribute is enforced, just not it's simple type. Have I defined >something incorrectly? I think this is one of those "don't kick yourself" problems. >Here they are: > ><!-- to be used in extension below --> > <xs:complexType name="ProjXm_QueryType"> > <xs:sequence> > <xs:element ref="command"/> > <xs:element ref="parameters"/> > <xs:element ref="fields" minOccurs="0"/> > </xs:sequence> > </xs:complexType> > > ><!-- extends the above and adds a name attribute of specified simple type --> > <xs:element name="SharedDB"> > <xs:complexType> > <xs:complexContent> > <xs:extension base="ProjXm_QueryType"> > <xs:attribute name="name" >type="simpleType_SharedDBQueries" /> Here you've just augmented your element with an attribute .... > </xs:extension> > </xs:complexContent> > </xs:complexType> > </xs:element> > ><!-- expected values for name attribute -> > <xs:simpleType name="simpleType_SharedDBQueries"> > <xs:restriction base="xs:NCName"> > <xs:enumeration value="insert"/> > <xs:enumeration value="update"/> > </xs:restriction> > </xs:simpleType> > > ><!-- sample xml (snipped) --> > <SharedDB> > <command> > <name>insertxx</name><!-- would expect validation to > fail here --> ... but you've put an element in your XML for testing. > <type>StoredProcedure</type> > <action>NonQuery</action> > </command> > <parameters> > ... > </SharedDB> I think if you had <SharedDB name="insertxx"> you would find the problem NCName flagged. I just copied your exact schema fragment into a bogus schema below and you'll see the attribute is being validated by both Xerces and Saxon. I hope this helps. . . . . . . . . . . . . . Ken ~/t/ftemp $ cat karl.xsd <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> <!-- to be used in extension below --> <xs:complexType name="ProjXm_QueryType"> <xs:sequence> <xs:element ref="command"/> <xs:element ref="parameters"/> <xs:element ref="fields" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- extends the above and adds a name attribute of specified simple type --> <xs:element name="SharedDB"> <xs:complexType> <xs:complexContent> <xs:extension base="ProjXm_QueryType"> <xs:attribute name="name" type="simpleType_SharedDBQueries" /> </xs:extension> </xs:complexContent> </xs:complexType> </xs:element> <!-- expected values for name attribute --> <xs:simpleType name="simpleType_SharedDBQueries"> <xs:restriction base="xs:NCName"> <xs:enumeration value="insert"/> <xs:enumeration value="update"/> </xs:restriction> </xs:simpleType> <xs:element name="command"> <xs:complexType/> </xs:element> <xs:element name="fields"> <xs:complexType/> </xs:element> <xs:element name="parameters"> <xs:complexType/> </xs:element> </xs:schema> ~/t/ftemp $ cat karl.xml <?xml version="1.0" encoding="UTF-8"?> <SharedDB name="insert"> <command/> <parameters/> </SharedDB> ~/t/ftemp $ w3cschema karl.xsd karl.xml Xerces... Attempting validating, namespace-aware parse Parse succeeded (0.131) with no errors and no warnings. Saxon... No validation errors ~/t/ftemp $ cat karlbad1.xml <?xml version="1.0" encoding="UTF-8"?> <SharedDB namex="insert"> <command/> <parameters/> </SharedDB> ~/t/ftemp $ w3cschema karl.xsd karlbad1.xml Xerces... Attempting validating, namespace-aware parse Error:file:///Users/admin/t/ftemp/karlbad1.xml:2:26:cvc-complex-type.3.2.2: Attribute 'namex' is not allowed to appear in element 'SharedDB'. Parse succeeded (0.135) with 1 error and no warnings. Saxon... Validation error on line 2 column 26 of karlbad1.xml: Attribute @namex is not allowed on element <SharedDB> (See http://www.w3.org/TR/xmlschema-1/#cvc-complex-type clause 3) No validation errors ~/t/ftemp $ cat karlbad2.xml <?xml version="1.0" encoding="UTF-8"?> <SharedDB name="insertx"> <command/> <parameters/> </SharedDB> ~/t/ftemp $ w3cschema karl.xsd karlbad2.xml Xerces... Attempting validating, namespace-aware parse Error:file:///Users/admin/t/ftemp/karlbad2.xml:2:26:cvc-enumeration-valid: Value 'insertx' is not facet-valid with respect to enumeration '[insert, update]'. It must be a value from the enumeration. Error:file:///Users/admin/t/ftemp/karlbad2.xml:2:26:cvc-attribute.3: The value 'insertx' of attribute 'name' on element 'SharedDB' is not valid with respect to its type, 'simpleType_SharedDBQueries'. Parse succeeded (0.146) with 2 errors and no warnings. Saxon... Validation error on line 2 column 26 of karlbad2.xml: FORG0001: Value "insertx" contravenes the enumeration facet "update, insert" of the type simpleType_SharedDBQueries (See http://www.w3.org/TR/xmlschema-1/#cvc-complex-type clause 3) No validation errors ~/t/ftemp $ -- Contact us for world-wide XML consulting and instructor-led training Free 5-hour video lecture: XSLT/XPath 1.0 & 2.0 http://ude.my/uoui9h Crane Softwrights Ltd. http://www.CraneSoftwrights.com/x/ G. Ken Holman mailto:gkholman@CraneSoftwrights.com Google+ profile: https://plus.google.com/116832879756988317389/about Legal business disclaimers: http://www.CraneSoftwrights.com/legal]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324094.html I have an element that extends a complex type but the additional attribute with a simple type definition is not being enforced.  The attribute is enforced, just not it's simple type.  Have I defined something incorrectly?  Here they are: <!-- to be used in extension below -->     <xs:complexType name="ProjXm_QueryType">         <xs:sequence>             <xs:element ref="command"/>             <xs:element ref="parameters"/>             <xs:element ref="fields" minOccurs="0"/>         </xs:sequence>     </xs:complexType> <!-- extends the above and adds a name attribute of specified simple type -->     <xs:element name="SharedDB">         <xs:complexType>             <xs:complexContent>                 <xs:extension base="ProjXm_QueryType">                     <xs:attribute name="name" type="simpleType_SharedDBQueries" />                 </xs:extension>             </xs:complexContent>         </xs:complexType>     </xs:element> <!-- expected values for name attribute ->     <xs:simpleType name="simpleType_SharedDBQueries">         <xs:restriction base="xs:NCName">             <xs:enumeration value="insert"/>             <xs:enumeration value="update"/>         </xs:restriction>     </xs:simpleType> <!-- sample xml (snipped) -->     <SharedDB>         <command>             <name>insertxx</name><!-- would expect validation to fail here -->             <type>StoredProcedure</type>             <action>NonQuery</action>         </command>         <parameters>     ...     </SharedDB> Thanks, Karl..]]> http://www.altova.com/list/xmlschema-dev/201201/msg1000324091.html Hi, trying to use the online validator on Wikipedia XML docu- ments and schemas (cf. <URI:http://www.w3.org/2001/03/webdata/xsv?docAddrs=http://de.wikipedia.org/w/index.php?title=Vorlage:Infobox_Ort_in_Griechenland/XML%26action%3Draw+http://de.wikipedia.org/w/index.php?title=User:Revvar/VM/XML-Schema%26action%3Draw&warnings=on&style=xsl>) yields: | validator crash during target reading | Error: can't retrieve "http://de.wikipedia.org/w/index.php?title=Vorlage:Infobox_Ort_in_Griechenland/XML&action=raw": 403 Forbidden This ("403 Forbidden") is most probably due to the online validator not supplying a "User-Agent" header (or using a default one too common) and thus being rejected by Wikipe- dia; this policy is explained a bit at <URI:http://www.mediawiki.org/wiki/API%3aFAQ#do_I_get_HTTP_403_errors.3F>. So - if this is the case - it would be nice if the online validator could provide a suitable "User-Agent" header. Some information on how to achieve that with Python is available inter alia at <URI:http://stackoverflow.com/questions/120061/fetch-a-wikipedia-article-with-python>. Thanks in advance, Tim P. S.: There's also a typo in "report problems (and sucesses!) to xmlschema-dev (archive)" :-).]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323884.html Piotr Sipika wrote: > > [] to compile: > $ gcc `xml2-config --cflags --libs` zoo.c -o zoo > No, this is wrong command line order. Specifying the libraries before the objects has always been wrong even though it has worked on Linux it will never work on Windows or other environments. Instead $ gcc `xml2-config --cflags` zoo.c -o zoo `xml2-config --libs` or even $ gcc zoo.c -o zoo `xml2-config --cflags --libs` since the compile flags are not position dependent but the library specifications are. -- Earnie -- https://sites.google.com/site/earnieboyd/]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323816.html Many thanks Piotr Happy Holidays Andy On Dec 15, 2011, at 7:01 PM, Piotr Sipika wrote: > Hi Andy, > >> I am setting up the xml schema namespace the same way eclipse does when >> you create a new XSD or XML file. I entered >> *http://www.w3.org/2001/XMLSchema-instance*in the address bar of my >> browsers and got quite a surprise! >> > The XML Namespace spec(1) states that the namespace URI need not be a > valid URL (i.e. point to a valid document on the network). In other > words, you are declaring your namespaces correctly. > >> http://www.w3.org/TR/xmlschema-1/#no-xsi is very confusing. > If you look at section 3.2.7 (first table) at that location, you'll see > that using 'xsi:type' is perfectly fine. > >> where does libxml get the schema lang schema/dtd? As a test I put some >> typos in my xsd file. libxml generated an error when I tried to validate >> the xsd file as expected? > You don't have to worry about libxml retrieving resources at namespace > locations, that does not happen. Only the actual URI string matters (as > per (1)). > >> what URL should I be using? >> >> Do I need to make a special call to cause the libxml to use this other >> location? > Nope, you're using the right URIs, no network access is necessary. > >> Would you be willing to send my your sample C program? > Sure thing (I should have done so in my original reply). > > [] to compile: > $ gcc `xml2-config --cflags --libs` zoo.c -o zoo > > [] sample run: > $ ./zoo zoo.xml ZooRequest.xsd > Attempting to validate zoo.xml with ZooRequest.xsd > Document in zoo.xml is valid > > [] contents of zoo.xml: > $ cat zoo.xml > <?xml version="1.0" encoding="UTF-8"?> > <zoo:cageRequest xmlns:zoo="http://www.example.org/Zoo" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <animal xsi:type="zoo:Fish"> > <name>Blue Fin Tuna</name> > <numberOfFins>4</numberOfFins> > </animal> > </zoo:cageRequest> > > Hope you get things sorted out. > > Piotr > > > (1) - http://www.w3.org/TR/REC-xml-names/#ns-decl > <zoo.c>]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323795.html /** * Sample namespace XSD validation program. * Released into public domain. * Piotr Sipika */ #include <stdlib.h> #include <stdio.h> #include <libxml/xmlschemas.h> #include <libxml/parser.h> #include <libxml/tree.h> int main(int argc, char * argv[]) { if (argc != 3) { fprintf(stderr, "Need file name and schema file name\n"); return EXIT_FAILURE; } const char *pczFile = argv[1]; const char *pczSchema = argv[2]; xmlInitParser(); xmlDocPtr pDoc = xmlReadFile(pczFile, NULL, XML_PARSE_NONET); if (!pDoc) { fprintf(stderr, "Unable to read %s\n", pczFile); xmlCleanupParser(); return EXIT_FAILURE; } xmlDocPtr pSchemaDoc = xmlReadFile(pczSchema, NULL, XML_PARSE_NONET); if (!pSchemaDoc) { fprintf(stderr, "Unable to read %s\n", pczSchema); xmlFreeDoc(pDoc); xmlCleanupParser(); return EXIT_FAILURE; } // create actual schema xmlSchemaParserCtxtPtr pSchemaCtxt = xmlSchemaNewDocParserCtxt(pSchemaDoc); if (!pSchemaCtxt) { fprintf(stderr, "Unable to create schema context\n"); xmlFreeDoc(pDoc); xmlFreeDoc(pSchemaDoc); xmlCleanupParser(); return EXIT_FAILURE; } xmlSchemaPtr pSchema = xmlSchemaParse(pSchemaCtxt); if (!pSchema) { fprintf(stderr, "Unable to create schema\n"); xmlSchemaFreeParserCtxt(pSchemaCtxt); xmlFreeDoc(pDoc); xmlFreeDoc(pSchemaDoc); xmlCleanupParser(); return EXIT_FAILURE; } xmlSchemaValidCtxtPtr pValidCtxt = xmlSchemaNewValidCtxt(pSchema); if (!pValidCtxt) { fprintf(stderr, "Unable to create validity context for schema\n"); xmlSchemaFree(pSchema); xmlSchemaFreeParserCtxt(pSchemaCtxt); xmlFreeDoc(pDoc); xmlFreeDoc(pSchemaDoc); xmlCleanupParser(); return EXIT_FAILURE; } fprintf(stdout, "Attempting to validate %s with %s\n", pczFile, pczSchema); xmlSchemaFreeParserCtxt(pSchemaCtxt); xmlFreeDoc(pSchemaDoc); int iError = xmlSchemaValidateDoc(pValidCtxt, pDoc); if (iError == 0) { fprintf(stdout, "Document in %s is valid\n", pczFile); } else { fprintf(stdout, "Document in %s is NOT valid\n", pczFile); } xmlSchemaFree(pSchema); // xmlSchemaFreeParserCtxt(pSchemaCtxt); xmlFreeDoc(pDoc); // xmlFreeDoc(pSchemaDoc); xmlCleanupParser(); return EXIT_SUCCESS; }]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323782.html Hi Piortr I still can not validate xml that uses xml schema extensions. I think I figured out what the problem might be, but do not know how to resolve i. I wonder if the problem is with the way I set up my xml namespace? <zoo:cageRequest xmlns:zoo="http://www.example.org/Zoo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> I am setting up the xml schema namespace the same way eclipse does when you create a new XSD or XML file. I entered http://www.w3.org/2001/XMLSchema-instance in the address bar of my browsers and got quite a surprise! <xs:annotation> <xs:documentation><p>This schema should never be used as such: <a href="http://www.w3.org/TR/xmlschema-1/#no-xsi">the XML Schema Recommendation</a> forbids the declaration of attributes in this namespace</p> </xs:documentation> </xs:annotation> http://www.w3.org/TR/xmlschema-1/#no-xsi is very confusing. where does libxml get the schema lang schema/dtd? As a test I put some typos in my xsd file. libxml generated an error when I tried to validate the xsd file as expected? what URL should I be using? Do I need to make a special call to cause the libxml to use this other location? My app will be running on a private network and not have access to www.w3.org, Do I need to copy a dtd or something to my local env? thanks in advance Andy p.s. Bellow is a long email I was going to send before I got the surprise I mentioned above. There is a nice code example of how how to validate. Its much simpler than the other examples I have seen posted in the past On Dec 13, 2011, at 7:19 AM, Piotr Sipika wrote: > > I wrote a sample program (in C) to attempt to mimic what you have, and > was able to successfully validate the instance against the schema you > provided. > Would you be willing to send my your sample C program? I must be missing a function call somewhere? My XML/XSD files that do not use extensions validate so I think my basic code structure is correct. In your original post you mentioned "xmllint". I did not know about that tool. All of my files validate according to xmllint.I stepped through xmllint to see how it worked. Its very complicated. I must have missed something. Looking at the xmllint source I was able to simplify my code and get rid some some memory leaks. Here is my simplified code listing based on the xmllint source const char *schemaFileNameStr = ...; // http://xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaNewParserCtxt xmlSchemaParserCtxtPtr ctxt = xmlSchemaNewParserCtxt(schemaFileNameStr); //http://xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaSetParserErrors xmlSchemaSetParserErrors(ctxt, (xmlSchemaValidityErrorFunc) fprintf, (xmlSchemaValidityWarningFunc) fprintf, stderr); xmlSchemaPtr wxschemas = xmlSchemaParse(ctxt); if (wxschemas == NULL) { NSLog(@"******* ERROR schema %@ failed to compile\n", xmlSchemaFilePath); return ret; } xmlSchemaFreeParserCtxt(ctx); for (all the xml files) { // http://www.xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaNewValidCtxt xmlSchemaValidCtxtPtr vctxt = xmlSchemaNewValidCtxt(wxschemas); // http://xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaSetValidErrors xmlSchemaSetValidErrors(vctxt, (xmlSchemaValidityErrorFunc) fprintf, (xmlSchemaValidityWarningFunc) fprintf, stderr); // http://xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaValidateDoc int error = xmlSchemaValidateDoc(vctxt, doc); if (error == 0) { ret = YES; } else if (error > 0) { ret = NO; fprintf(stderr, "%s fails to validate\n", filename); } else { ret = NO; // validation generated an internal error } xmlSchemaFreeValidCtxt(vctxt); } <?xml version="1.0" encoding="UTF-8"?> <zoo:cageRequest xmlns:zoo="http://www.example.org/Zoo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <animal xsi:type="zoo:Fish"> <name>Blue Fin Tuna</name> <numberOfFins>4</numberOfFins> </animal> </zoo:cageRequest> element animal: Schemas validity error : Element 'animal', attribute 'xsi:type': The attribute 'xsi:type' is not allowed. element numberOfFins: Schemas validity error : Element 'numberOfFins': This element is not expected. DOCUMENT version=1.0 standalone=true ELEMENT zoo:cageRequest namespace zoo href=http://www.example.org/Zoo namespace xsi href=http://www.w3.org/2001/XMLSchema-instanc... ELEMENT animal ATTRIBUTE xsi:type TEXT content=zoo:Fish ELEMENT name TEXT content=Blue Fin Tuna ELEMENT numberOfFins TEXT content=4]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323779.html On 15/12/2011 10:40, Costello, Roger L. wrote: > Hi Folks, > > Consider a schema, S1, with targetNamespace, tns1. > > Schema S2 has targetNamespace tns2, where tns1 is not equal to tns2. Schemas do not have a target namespace. I think you are referring to schema documents. > > And so forth. > > S1 imports S2 which imports S3 which ... > > There are N schemas. No, there is one schema. There are N schema documents. > > S1 has only one import element -- it imports S2. > > Suppose I add to S1 import elements to S3, S4, ..., Sn. If S1 was already a valid schema document, then it contained no references to components defined in S3, S4, etc, and therefore the new import declarations are redundant, and therefore the schema constructed from this collection of schema documents is not affected. (It's very much the same as adding an "import" in a Java source file for a class or package that isn't then referenced from the code.) However, the schema construction model is not defined very formally, and many aspects are implementation-defined, so your mileage may vary. Michael Kay Saxonica]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323767.html Hi Folks, Consider a schema, S1, with targetNamespace, tns1. Schema S2 has targetNamespace tns2, where tns1 is not equal to tns2. And so forth. S1 imports S2 which imports S3 which ... There are N schemas. S1 has only one import element -- it imports S2. Suppose I add to S1 import elements to S3, S4, ..., Sn. And make no other changes to S1. Let S1' be the altered S1. Is S1' = S1? Does S1' have the same functionality as S1? /Roger]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323766.html On 12/12/2011 09:12 PM, Andy Davidson wrote: > Does anyone know if libxml2 > supports http://www.w3.org/TR/xmlschema-0/#DerivExt ? > Yes, it does. The rest of the message was libxml2-specific, so I took the liberty of replying to it and 'returning' it to the libxml2 mailing list. P]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323729.html Does anyone know if libxml2 supports http://www.w3.org/TR/xmlschema-0/#DerivExt ? thanks in advance Andy Begin forwarded message: > From: Andy Davidson <andy_davidson@apple.com> > Date: December 12, 2011 6:10:14 PM PST > To: xml@gnome.org > Subject: libxml2 does xmlSchemaValidateDoc() support xml schema extensions? > > Hi > > I am using libxml2. I use xmlSchemaValidateDoc() to make sure my xml is valid. Recently we started using Extension to define new complexTypes. > > The description for extensions can be found at http://www.w3.org/TR/xmlschema-0/#DerivExt > > These instance do not validate using libxml2. I am able to validate these instance using java version "1.6.0_29" > > > Attached is my test Zoo.xsd, and the instance I am trying to validate > > > > > <complexType name="Animal"> > <sequence> > <element name="name" type="string" /> > </sequence> > </complexType> > > <complexType name="Fish"> > <complexContent> > <extension base="zoo:Animal"> > <sequence> > <element name="numberOfFins" type="integer" /> > </sequence> > </extension> > </complexContent> > </complexType> > > My xml instance is > > <?xml version="1.0" encoding="UTF-8"?> > <zoo:cageRequest xmlns:zoo="http://www.example.org/Zoo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > <animal xsi:type="zoo:Fish"> > <name>Blue Fin Tuna</name> > <numberOfFins>4</numberOfFins> > </animal> > </zoo:cageRequest> > > xmlSchemaValidateDoc() generates the following output > element animal: Schemas validity error : Element 'animal', attribute 'xsi:type': The attribute 'xsi:type' is not allowed. > element numberOfFins: Schemas validity error : Element 'numberOfFins': This element is not expected. > > the error returned is 1871 for instance > > xmlDebugDumpDocument() produces > > DOCUMENT > version=1.0 > standalone=true > ELEMENT zoo:cageRequest > namespace zoo href=http://www.example.org/Zoo > namespace xsi href=http://www.w3.org/2001/XMLSchema-instanc... > ELEMENT animal > ATTRIBUTE xsi:type > TEXT > content=zoo:Fish > ELEMENT name > TEXT > content=Blue Fin Tuna > ELEMENT numberOfFins > TEXT > content=4 > (gdb) > > > Do I need to tweak my validation code ? > > > (this is an ObjC listing) > > > > const char *schemaFileNameStr = [xmlSchemaFilePath cStringUsingEncoding: NSASCIIStringEncoding]; > > // http://www.xmlsoft.org/html/libxml-parser.html#xmlReadFile > // second arg, null, is document encoding > // XML_PARSE_NONET option means "Forbid network access" > xmlDocPtr schemaDoc = xmlReadFile(schemaFileNameStr, NULL, XML_PARSE_NONET); > NSString *errorMsgRoot = @"**** ERROR: POSXMLSchemaValidator.m createAndAddValidatorFor:, "; > if (schemaDoc == NULL) { > /* the schema cannot be loaded or is not well-formed */ > NSLog(@"%@ the schema: %s can not be loaded or is not well-formed", errorMsgRoot, schemaFileNameStr); > return ret; > } > > // http://www.xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaNewDocParserCtxt > xmlSchemaParserCtxtPtr parserCtxt = xmlSchemaNewDocParserCtxt(schemaDoc); > if (parserCtxt == NULL) { > /* unable to create a parser context for the schema */ > xmlFreeDoc(schemaDoc); > NSLog(@"%@ unable to create a parser context for schema %s", errorMsgRoot, schemaFileNameStr); > return ret; > } > > // http://www.xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaParse > xmlSchemaPtr schema = xmlSchemaParse(parserCtxt); > if (schema == NULL) { > /* the schema itself is not valid */ > xmlSchemaFreeParserCtxt(parserCtxt); > xmlFreeDoc(schemaDoc); > NSLog(@"%@ the schema %s is not valid", errorMsgRoot, schemaFileNameStr); > return ret; > } > > // http://www.xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaNewValidCtxt > xmlSchemaValidCtxtPtr validCtxt = xmlSchemaNewValidCtxt(schema); > if (validCtxt == NULL) { > /* unable to create a validation context for the schema */ > xmlSchemaFree(schema); > xmlSchemaFreeParserCtxt(parserCtxt); > xmlFreeDoc(schemaDoc); > NSLog(@"%@ unable to validation context for schema %s", errorMsgRoot, schemaFileNameStr); > return ret; > } > > //xmlSchemaFree(schema); causes crash when we try to use validCtxt > xmlSchemaFreeParserCtxt(parserCtxt); > xmlFreeDoc(schemaDoc); > > // http://www.xmlsoft.org/html/libxml-xmlschemas.html#xmlSchemaValidateDoc > int error = xmlSchemaValidateDoc(validCtxt.validCtxt, doc); > if (error == 0) { > NSLog(@"document is a valid instance of %@", schemaFileName); > ret = YES; > } > > > Is this a bug? > > thanks in advance > > Andy >]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323711.html I think that this is a namespace issue. You will need to register the "xsi" namespace to the libXML2 engine and then use its prefix in your XPath expressions. The way to do that varies by language. On 12/08/2011 06:08 PM, Andy Davidson wrote: > Hi > > I am trying use libxml2 to parse the following xml. > > <?xmlversion="1.0"encoding="UTF-8"?> > <zoo:cageRequest > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:zoo="http://www.example.org/Zoo" > xsi:schemaLocation="http://www.example.org/Zoo ../XSD/ZooRequest.xsd "> > <animalxsi:type="zoo:Fish"> > <name>tuna</name> > <numberOfFins>4</numberOfFins> > </animal> > </zoo:cageRequest> > > I need to do some special processing based on the value of xsi:type. > I eventual get a a xmlNodePtr that points to > > <animalxsi:type="zoo:Fish"> > <name>tuna</name> > <numberOfFins>4</numberOfFins> > </animal> > > I can not seem to select the attribute. "@*" works but is not going to > work long term. > > "@xsi:type" and "@type" did not work > > thanks > > Andy]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323686.html On 12/08/2011 09:58 PM, Liam R E Quin wrote: > Since libxml is stuck on XPath 1, you can use explicit xsi:type > attributes but not type annotations that result from schema validation > episodes - you'd need an XPath 2 engine for that, such as Saxon. > >> I eventual get a a xmlNodePtr that points to >> >> <animal xsi:type="zoo:Fish"> >> <name>tuna</name> >> <numberOfFins>4</numberOfFins> >> </animal> >> >> I can not seem to select the attribute. "@*" works but is not going to work long term. >> >> "@xsi:type" and "@type" did not work > > You need to bind the prefix xsi to the right URI in the namespace > context before evaluating the expression. Google for xpath and > namespaces. Then you can use @xsi:type. As Liam wrote, you'll need to register all the namespaces you intend to use in your XPath searches with the XPath context. The code would look something like: xmlXPathContextPtr pContext = xmlXPathNewContext(pDoc); .... if (xmlXPathRegisterNs(pContext, (xmlChar*)"xsi", (xmlChar*)"http://www.w3.org/2001/XMLSchema-instance") != 0) { fprintf(stderr, "Failed to register xsi\n"); } if (xmlXPathRegisterNs(pContext, (xmlChar*)"zoo", (xmlChar*)"http://www.example.org/Zoo") != 0) { fprintf(stderr, "Failed to register zoo\n"); } xmlXPathObjectPtr pObj = xmlXPathEvalExpression(pzXPath, pContext); //etc... The pertinent libxml2 example can be found here: http://www.xmlsoft.org/examples/xpath1.c Hope this helps. P]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323687.html On Thu, 2011-12-08 at 17:08 -0800, Andy Davidson wrote: > Hi > > I am trying use libxml2 to parse the following xml. > > <?xml version="1.0" encoding="UTF-8"?> > <zoo:cageRequest > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:zoo="http://www.example.org/Zoo" > xsi:schemaLocation="http://www.example.org/Zoo ../XSD/ZooRequest.xsd "> > <animal xsi:type="zoo:Fish"> > <name>tuna</name> > <numberOfFins>4</numberOfFins> > </animal> > </zoo:cageRequest> > > I need to do some special processing based on the value of xsi:type. Since libxml is stuck on XPath 1, you can use explicit xsi:type attributes but not type annotations that result from schema validation episodes - you'd need an XPath 2 engine for that, such as Saxon. > I eventual get a a xmlNodePtr that points to > > <animal xsi:type="zoo:Fish"> > <name>tuna</name> > <numberOfFins>4</numberOfFins> > </animal> > > I can not seem to select the attribute. "@*" works but is not going to work long term. > > "@xsi:type" and "@type" did not work You need to bind the prefix xsi to the right URI in the namespace context before evaluating the expression. Google for xpath and namespaces. Then you can use @xsi:type. Liam -- Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/ Pictures from old books: http://fromoldbooks.org/]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323617.html Hi I am trying use libxml2 to parse the following xml. <?xml version="1.0" encoding="UTF-8"?> <zoo:cageRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:zoo="http://www.example.org/Zoo" xsi:schemaLocation="http://www.example.org/Zoo ../XSD/ZooRequest.xsd "> <animal xsi:type="zoo:Fish"> <name>tuna</name> <numberOfFins>4</numberOfFins> </animal> </zoo:cageRequest> I need to do some special processing based on the value of xsi:type. I eventual get a a xmlNodePtr that points to <animal xsi:type="zoo:Fish"> <name>tuna</name> <numberOfFins>4</numberOfFins> </animal> I can not seem to select the attribute. "@*" works but is not going to work long term. "@xsi:type" and "@type" did not work thanks Andy]]> http://www.altova.com/list/xmlschema-dev/201112/msg1000323616.html