W3C home > Mailing lists > Public > www-dom-ts@w3.org > October 2001

Re: Updated dom-to-xsd.xsl, -to-dtd.xsl

From: Mary Brady <mbrady@nist.gov>
Date: Fri, 12 Oct 2001 11:14:50 -0400
Message-ID: <00ae01c15330$a35951c0$293b0681@HAPPY>
To: "Curt Arnold" <carnold@houston.rr.com>, <www-dom-ts@w3.org>
Thanks, Curt.  We've pulled it down and have 
already identified problems with the tests using 
this process.

--Mary
  ----- Original Message ----- 
  From: Curt Arnold 
  To: www-dom-ts@w3.org 
  Sent: Friday, October 12, 2001 3:20 AM
  Subject: Updated dom-to-xsd.xsl, -to-dtd.xsl


  I've updated dom-to-xsd.xsl to be consistent with the current versions of Sun's Multi Schema Validator (MSV) and XSV from the University of Edinburgh.   

  A DOM L1 schema can be produced by

  ant dom1-schema  ' approx 2 minutes build time

  A DOM L2 schema can be produced by

  ant dom2-schema ' approx 10 minutes build time

  Tests can be validated against the schemas by downloading Sun's MSV (http://www.sun.com/software/xml/developers/multischema) and then running


  java -jar \msv-20010910\msv.jar build\dom1.xsd tests\level1\core\*.xml

  or 

  java -jar \msv-20010910\msv.jar build\dom2.xsd tests\level2\core\*.xml

  I did check the DOM L2 schema by manually changing the namespace to Level-1 and validating the L1 tests and had no problem (other than 2 tests failing DTD validation against the dom1.dtd due to a missing raise clause in the DOM 1 spec that has been previously discussed).  

  I've also added interface="Node" to firstChild and similar methods in the tests that become ambiguous in DOM L2 since TreeWalker adds identically named methods.  This should allow the DOM L1 tests to validate against DOM L2+ schemas and DTDs and generate appropriate code.

  I did some spot checks with XSV, but doesn't take wildcards for instance documents so it isn't as friendly.
Received on Friday, 12 October 2001 11:16:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:45 GMT