HelveticaI previously got xsv to validate some sample xml files (can't remember exactly which ones though), but cannot get it to validate much of anything now. I have put several attempts on my personal web site: http://www.realtime.net/~mburns/po.xml cut and paste directly out of the primer, and the schema for it: http://www.realtime.net/~mburns/po.xsd The only thing I changed in the xml file was to add Monaco xmlns:xsi = "http://www.w3.org/2000/10/XMLSchema-instance" 28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; xsi:noNamespaceSchemaLocation = "po.xsd" Helvetica28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;That brings up one of my burning questions: Given the initial contents of po.xml and po.xsd as shown in the primer, how in the world is a parser supposed to connect the two? What are all or some or the recommended way for a parser to determine which schema to use. I added these two attributes to the top level element in po.xml and it still does not seem to find the schema and use it. When I run the xerces parser on this with schema validation turned on it complains that: [Error] po.xml:6:4: Element type "purchaseOrder" must be declared. [Error] po.xml:7:26: Element type "shipTo" must be declared. [Error] po.xml:8:15: Element type "name" must be declared. [Error] po.xml:9:17: Element type "street" must be declared. [Error] po.xml:10:15: Element type "city" must be declared. [Error] po.xml:11:16: Element type "state" must be declared. ... If I rename the po.xsd file so it can't be found, then xerces does not complain, so it appears it is not looking for the specified file. What am I missing? It appears clear to me that the xerces parser only recognizes the 1999 spec and I am guessing that the xsv only recognizes the 2000/10 spec. I have created a bunch of test cases using both the sample that comes with xerces (personal-schema.xml + personal.xsd) and the po.xml + po.xsd that I copied from the primer. I have created both 1999 and 2000 versions of each and still have been having poor luck getting much to validate properly. All of these are in http://www.realtime.net/~mburns/ 1999 spec samples: http://www.realtime.net/~mburns/po99.xml + po99.xsd <<- copied from primer and changed to 1999 format http://www.realtime.net/~mburns/personal-schema.xml + personal.xsd << - works with xerces as expected http://www.realtime.net/~mburns/personal-schema-fails.xml + personal.xsd <<- xerces reports errors as expected Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Helvetica28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; 2000 spec samples: http://www.realtime.net/~mburns/po.xml + po.xsd <<- copied from primer http://www.realtime.net/~mburns/personal-schema-2000.xml + personal-2000.xsd http://www.realtime.net/~mburns/personal-schema-2000-fails.xml + personal-2000.xsd Those last two I can get to run through xsv but don't understand the results, it does not seem to be validating and I don't understand why not: - - - - - - - - snip - - - - - - - - - - Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;Schema validating with XSV 1.166/1.77 of 2000/09/28 15:54:50Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;• Target:Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; http://www.realtime.net/~mburns/personal-schema-2000-fails.xmlLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;    (Real name: http://www.realtime.net/~mburns/personal-schema-2000-fails.xml     Length: 1267 bytes     Last Modified: Wed, 11 Oct 2000 16:07:06 GMT     Server: Apache/1.2.5) • docElt:Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; {None}personnelLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; • No declaration for document root found, validation was lax • schemaLocs: None -> personal-2000.xsd • The schema(s) used for schema-validation had no errors • instanceAssessed: true • No schema-validity problems were found in the target Low-level XML well-formedness and/or validity processing output Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Warning: Document has no DTD, validating abandoned (detected at end of prolog of document http://www.realtime.net/~mburns/personal-2000.xsd)Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Schema resources involved Attempt to import a schema document fromMonaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; http://www.realtime.net/~mburns/personal-2000.xsdLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; for no namespace, failed Helvetica28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;/- - - - - - - - snip - - - - - - - - - - I get a little bit of success (I think) with po.xml: - - - - - - - - snip - - - - - - - - - - Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;Schema validating with XSV 1.166/1.77 of 2000/09/28 15:54:50Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;• Target:Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; http://www.realtime.net/~mburns/po.xmlLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;    (Real name: http://www.realtime.net/~mburns/po.xml     Length: 1106 bytes     Last Modified: Wed, 11 Oct 2000 15:28:00 GMT     Server: Apache/1.2.5) • docElt:Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; {None}purchaseOrderLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; • Validation was strict, starting with typeMonaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; {None}:PurchaseOrderTypeLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; • schemaLocs: None -> po.xsd • The schema(s) used for schema-validation had no errors • instanceAssessed: true • No schema-validity problems were found in the target Low-level XML well-formedness and/or validity processing output Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Warning: Document has no DTD, validating abandoned (detected at end of prolog of document http://www.realtime.net/~mburns/po.xsd)Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Schema resources involved Attempt to import a schema document fromMonaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; http://www.realtime.net/~mburns/po.xsdLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; for no namespace, succeeded Helvetica28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;/- - - - - - - - snip - - - - - - - - - - Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; At least it seems to be finding the po.xsd, but this tells me that did not validate the schema. Finally I have on other sample Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;http://www.realtime.net/~mburns/USAddress.xml that seems to have a bit more success. At least it seems to like the schema and apply it to the xml file. Helvetica28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;- - - - - - - - snip - - - - - - - - - - Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;Schema validating with XSV 1.166/1.77 of 2000/09/28 15:54:50Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;• Target:Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; http://www.realtime.net/~mburns/USAddress.xmlLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;    (Real name: http://www.realtime.net/~mburns/USAddress.xml     Length: 287 bytes     Last Modified: Tue, 10 Oct 2000 18:21:09 GMT     Server: Apache/1.2.5) • docElt:Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; {None}billToLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; • Validation was strict, starting with typeMonaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; [Anonymous]Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; • schemaLocs: None -> primerSchema.xsd • The schema(s) used for schema-validation had no errors • instanceAssessed: true • 6 schema-validity problems were found in the target Low-level XML well-formedness and/or validity processing output Monaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Warning: Document has no DTD, validating abandoned (detected at end of prolog of document http://www.realtime.net/~mburns/primerSchema.xsd)Lucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; Schema resources involved Attempt to import a schema document fromMonaco28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; http://www.realtime.net/~mburns/primerSchema.xsdLucida Grande28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; for no namespace, succeeded Problems with the schema-validity of the targetFFFF,0000,0000 FFFF,0000,0000http://www.realtime.net/~mburns/USAddress.xml:1:119:0000,0000,FFFF Invalid per 0000,3333,7777cvc-complex-type.1.2: element billTo must be empty but is notFFFF,0000,0000 http://www.realtime.net/~mburns/USAddress.xml:2:9:0000,0000,FFFF Invalid per 0000,3333,7777src-resolve: undeclared element {None}:nameFFFF,0000,0000 http://www.realtime.net/~mburns/USAddress.xml:3:9:0000,0000,FFFF Invalid per 0000,3333,7777src-resolve: undeclared element {None}:streetFFFF,0000,0000 http://www.realtime.net/~mburns/USAddress.xml:4:9:0000,0000,FFFF Invalid per 0000,3333,7777src-resolve: undeclared element {None}:cityFFFF,0000,0000 http://www.realtime.net/~mburns/USAddress.xml:5:9:0000,0000,FFFF Invalid per 0000,3333,7777src-resolve: undeclared element {None}:stateFFFF,0000,0000 http://www.realtime.net/~mburns/USAddress.xml:6:9:0000,0000,FFFF Invalid per 0000,3333,7777src-resolve: undeclared element {None}:zip 28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;Helvetica/- - - - - - - - snip - - - - - - - - - - In conclusion, I would like to get the po.xml and po.xsd example working with xsv so I can start testing out my own schema ideas using variations on po. I would also like to have a copy of xsv locally so I can use it offline. There was a hint that it was possible but not easy. I got ltxml to build locally, what else is required for xsv? Thanks for all your help. On Tuesday, October 10, 2000, at 10:33 AM, Martin Gudgin wrote: Michael,0000,0000,0000  0000,0000,0000 XSV is the 'latest and greatest'. The version that supports the 22nd Sept WD is at[1] ( the W3C is having some mirroring problems at the moment so you may have some trouble getting that URL to resolve )0000,0000,0000  0000,0000,0000 Can you post your instance and schema? ( you can e-mail them to me or send me URLs )0000,0000,0000  0000,0000,0000 The reason XSV is not complaining is because it's doing LAX validation. ( the line that says  'No declaration for document root found, validation was lax'is the clue here ). I'm guessing that you don't have a global element declaration in the schema for the document element in your instance. If I can see the schema and instance I should be able to give more explicit help...0000,0000,0000  0000,0000,0000 Regards0000,0000,0000  0000,0000,0000 Martin Gudgin0000,0000,0000 DevelopMentor0000,0000,0000  0000,0000,0000 [1] 1999,1999,FFFFhttp://www.w3.org/2000/09/webdata/xsv0000,0000,0000  0000,0000,0000 P.S. Cool sig...0000,0000,0000 ----- Original Message -----0000,0000,0000 From: 1999,1999,FFFFMichael Burns0000,0000,0000 To: 1999,1999,FFFF'xmlschema-dev@w3.org'0000,0000,0000 Sent: Monday, October 09, 2000 11:19 PM0000,0000,0000 Subject: Trying to validate a sample xml file against a schema I am develo ping.0000,0000,0000 ArialI am new to this list, but spent quite a bit of time reading and trying things0000,0000,0000Helvetica ArialArialout today, so hopefully this is not a newby or RTFM question:0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialQuestion:0000,0000,0000Helvetica ArialArialWhat is the best tool to use to validate an xml file and schema pair?0000,0000,0000Arial ArialI have tried the xerces DOM parser, XML Instance from TIBCO (Extensiblity),0000,0000,0000Helvetica ArialArialthe xmlnorm program that is part of ltxml and the web based XSV.0000,0000,0000Helvetica ArialArialNone of them seems to match the primer examples very well.0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialBackground:0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialI am developing a tool to build a schema according to the latest draft0000,0000,0000Helvetica ArialArialstandard: 1999,1999,FFFFhttp://www.w3.org/TR/2000/WD-xmlschema-0-20000922/0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialI have made quite a bit of progress using the xerces parser with it's validation0000,0000,0000Helvetica ArialArialturned on.  It is now complaining about something in my schema (which I am0000,0000,0000Helvetica ArialArialnot free to share with you, Sorry).  So, I started cutting and pasting samples0000,0000,0000Helvetica ArialArialfrom the primer to see if it complained about the examples from the primer too.0000,0000,0000Helvetica ArialArialSure enough it does.   So, I was pursuing other validation tools.  I downloaded0000,0000,0000Helvetica ArialArialthe ltxml-1.2 tools that were recently posted.  Got those built ok. :-)0000,0000,0000Helvetica ArialArialThen I tried xmlnorm -sxV on the problematic xml file but it said:0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialWarning: Document has no DTD, validating abandoned.0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialI will pursue looking into the sources for the xmlnorm and see if there are some0000,0000,0000Helvetica ArialArialparser options I have to turn on to enable schema based validation.0000,0000,0000Helvetica ArialArialAny clues??0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialIn the mean time I tried out your web based validator (I guess this is what0000,0000,0000Helvetica ArialArialpeople are calling XSV on the list): 1999,1999,FFFFhttp://www.w3.org/2000/09/webdata/xsv0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialIt says:0000,0000,0000Helvetica ArialArialSchema validating with XSV 1.166/1.77 of 2000/09/28 15:54:500000,0000,0000Arial 72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial• Target: 72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Helveticafile:/export/home/ht/xsvlog/@15848.4uploaded72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;0000,0000,0000Helvetica 64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial   (Real name: C:\ModelCompilerTestPen\doc\MOresult.xml)64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;0000,0000,0000Arial 72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial• docElt: Helvetica{None}objects72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;0000,0000,0000Arial Arial• No declaration for document root found, validation was lax0000,0000,0000Arial Arial• schemaLocs:0000,0000,0000Arial Arial• The schema(s) used for schema-validation had no errors0000,0000,0000Arial Arial• instanceAssessed: true0000,0000,0000Arial Arial• No schema-validity problems were found in the target0000,0000,0000Arial 28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L; 28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;ArialWhich initially led me to believe that my schema was really OK.28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;0000,0000,0000Helvetica ArialArialHowever, when I intentionally screwed up the schema It did not complain0000,0000,0000Helvetica ArialArialat all.   When I changed an element tag in my xml file so that it was not0000,0000,0000Helvetica ArialArialfound in the schema, it still did not complain. 0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialI tried some other samples of valid xml and xsd such as the one that0000,0000,0000Helvetica ArialArialcomes as a sample with xerces.   personal-schema.xml and personal.xsd0000,0000,0000Helvetica ArialArialI changed an element tag 'person' to 'persona' and now the xerces parser0000,0000,0000Helvetica ArialArialcomplains:0000,0000,0000Helvetica ArialArial[Error] personal-schema.xml:5:27: Element type "persona" must be declared.0000,0000,0000Arial Arial[Error] personal-schema.xml:5:27: Attribute "id" must be declared for element type "persona".0000,0000,0000Arial Arial[Error] personal-schema.xml:41:14: The content of element type "personnel" must match "(##any:uri=)+".0000,0000,0000Arial Arial[Error] personal-schema.xml:41:14: An element with the identifier "Big.Boss" must appear in the document.0000,0000,0000Arial Arialpersonal-schema.xml: 2423 ms (37 elems, 19 attrs, 122 spaces, 146 chars)0000,0000,0000Helvetica Helvetica 0000,0000,0000Helvetica ArialArialBut XSV does not complain at all:0000,0000,0000Helvetica ArialArialSchema validating with XSV 1.166/1.77 of 2000/09/28 15:54:500000,0000,0000Arial 72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial• Target: 72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Helveticafile:/export/home/ht/xsvlog/@15856.4uploaded72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;0000,0000,0000Helvetica 64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial   (Real name: C:\sasmkb\xml\parsers\xerces-1_2_0\data\personal-schema.xml)64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;0000,0000,0000Arial 72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;Arial• docElt: Helvetica{None}personnel72L;64L;92L;120L;148L;176L;204L;232L;260L;288L;316L;344L;372L;0000,0000,0000Arial Arial• No declaration for document root found, validation was lax0000,0000,0000Arial Arial• schemaLocs:0000,0000,0000Arial Arial• The schema(s) used for schema-validation had no errors0000,0000,0000Arial Arial• instanceAssessed: true0000,0000,0000Arial Arial• No schema-validity problems were found in the target0000,0000,0000Arial 28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;