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

RE: issue checking

From: <paul.downey@bt.com>
Date: Wed, 11 Oct 2006 12:40:40 +0100
Message-ID: <2A7793353757DB4392DF4DFBBC95225504BFEF06@I2KM11-UKBR.domain1.systemhost.net>
To: <gcowe@origoservices.com>, <public-xsd-databinding@w3.org>

wow George, that's great - I'll find a way of combining this 
with my edtodo and xref reports ..

-----Original Message-----
From: George Cowe [mailto:gcowe@origoservices.com]
Sent: Wed 10/11/2006 9:24 AM
To: public-xsd-databinding@w3.org
Cc: Downey,P,Paul,XSL1 R
Subject: issue checking
Hi Paul
Re-analysis of the issues list in relation to the existing patterns and examples for completeness. (ACTION 77)

Attached is a set of XSL which highlight 1) issues with no pattern, and 2) patterns with no examples

The patterns.xml and examples.xml files have been updated to correct some issue numbers which were incorrectly allocated and to match xml:ids across the documents. However there are still some inconsistencies where for example a pattern has several examples which leads to no direct link between the patterns.xml and examples.xml (e.g pattern="Include" but examples="IncludeRelative" and "IncludeFullPath")

I manually created a small xml file with a list of the issues which need patterns/examples which drives the process (issues-requiring-examples.xml).

The two output files are
1) issues-but-no-patterns.txt
2) patterns-but-no-examples.txt (some of these do have examples - its just that the names don't match the pattern - making it difficult to automate the match)

There is a build.xml ant file to run the process.

I guess the next thing is to actually create the patterns and examples :)

Received on Wednesday, 11 October 2006 11:41:51 UTC

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