W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > October 2006

ISSUE-12 - status of the patterns detector

From: <paul.downey@bt.com>
Date: Wed, 25 Oct 2006 12:22:30 +0100
Message-ID: <2A7793353757DB4392DF4DFBBC95225504BFEF90@I2KM11-UKBR.domain1.systemhost.net>
To: <public-xsd-databinding@w3.org>

Herin a status report on the detection of patterns.

We have an XSLT to detect patterns in an XSD or WSDL document.
This also reports any elements or attributes not covered by our patterns:


The detector is generated from patterns.xml:


using a stylesheet:


You can see the result of running this against each of our patterns
in the examples directory:


e.g. the "StringElement" pattern:


is demonstrated by the a "StringElement" example:


which presents the output of the patterns detector run against the Schema:


The source code, including the ant task used to run
the detector and build the overview documents, is all in:


Still to-do:

  * optionally follow imports and includes
    - avoid processing the same schema more than once

  * more testing with non-example schemas
    - collect patterns, ensure we don't miss-fire

  * we need more test assertions when running against the example documents
    - eg example includes-patterns="a,b,c" excludes-patterns="d,e,f"

  * reported line number for an 'unknown' XPaths is always '-1' 
    - an artifact of running Saxon from a Java stream

  * consider citing and counting the detected schema fragments 
      which match a pattern 
    - report the matched XPath results?
  * wrap the detector up as a validation service 
    - (possibly best done as a JSP if we continue to use Saxon?)

Received on Wednesday, 25 October 2006 11:22:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:57 UTC