Towards schema-validator conformance testing: error output

As part of trying to get to a position where we can compare output,
and also to accommodate full UNICODE support, I've been working on a
branch of XSV (see the branches of applyschema.py and XMLSchema.py called
'xmlout') which produces XML output rather than plain text.

Here's a sample:

<?xml version='1.0'?>
<xsv schemaLocs='http://foo -> tiny.xsd'
     schemaStatus='OK'
     rootType='{http://foo}:rtype'
     instanceAssessed='yes'
     validation='strict'
     schemaDocs='tiny.xsd'
     target='file:/d:/Henry/xmlinter/xmlschema/tiny.xml'
     docElt='{http://foo}root'
     version='XSV 1.130.2.1/1.54.2.3 of 2000/05/11 13:59:11'
     instanceStatus='2 errors'>
 <invalid resource='file:/d:/Henry/xmlinter/xmlschema/tiny.xml'
          code='cvc-complex-type.1.4'
          line='7' char='65'>required attribute {None}:y not present</invalid>
 <invalid resource='file:/d:/Henry/xmlinter/xmlschema/tiny.xml'
          code='cvc-attribute.1.2'
          line='10' char='33'>attribute type check failed for {None}:z: 0&#60;1</invalid>
</xsv>

Note that the 'code' attributes refer to the forthcoming tabulation of 
schema error and validation failure cases.  I envisage
schema-validator output being compared on the basis of these codes,
_inter alia_.

I'll be producing an XSL stylesheet to go with this to provide a view
more like the current style, but since I want to switch to 16-bit
support, and can't do that without doing this, the change is likely to 
come before the stylesheet.

How do people feel about this.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/

Received on Friday, 12 May 2000 10:29:56 UTC