W3C home > Mailing lists > Public > xmlschema-dev@w3.org > May 2000

Towards schema-validator conformance testing: error output

From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
Date: 12 May 2000 15:29:51 +0100
To: xmlschema-dev@w3.org
Message-ID: <f5bd7mrhme8.fsf@cogsci.ed.ac.uk>
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'
     version='XSV of 2000/05/11 13:59:11'
     instanceStatus='2 errors'>
 <invalid resource='file:/d:/Henry/xmlinter/xmlschema/tiny.xml'
          line='7' char='65'>required attribute {None}:y not present</invalid>
 <invalid resource='file:/d:/Henry/xmlinter/xmlschema/tiny.xml'
          line='10' char='33'>attribute type check failed for {None}:z: 0&#60;1</invalid>

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.

  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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:14:46 UTC