Prototyping catalogue validation

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

This describes some of the prototyping I'm doing to illustrate where I 
think the catalogue validation process is going.

I've taken input from the "ironman" description and the "halfway" 
description and created a DTD incorporating some of my own thoughts that I 
described in my previous message.

Please note that the changes I made to make it work are not cast in stone, 
nor am I suggesting these will be the final ways things will work.  I just 
wanted to get enough done to get something prototyped.  We've been doing a 
lot of talking around the processes without actually implementing anything, 
so I wanted to get some rubber on the road and see how things started 
falling together (or apart!).

So, please go to the work directory, in the Contributions section, and you 
will find reference to:

    catalogue-prototype-20010706-1330.zip
    (note this file may be removed and unavailable when viewing the archive)

Unpacking this file you will find the following files:

    test.bat           - invocation of Saxon for test catalogue

    submissions.dtd    - document model for instance pointing to all catalogues
    suite-config.dtd   - document model for configuring a test suite with all
                         of the parameters being validated in the catalogue
    collcat.dtd        - document model of a collection of tests submitted
                       - derived from the ironman and halfway documents
    disc.dtd           - copy of document model for discretionary items
                       - no changes since last worked on by Ken

    testcat.xml        - a test catalogue with only two test cases
                       - does anyone have a catalogue similar to ironman?
    xsltconfig.xml     - configuration of the test suite software for XSLT
    xsltdisc.xml       - copy of discretionary items (last copy by Ken)
    xsltsubs.xml       - submission instance pointing to only the test 
catalogue

    valcat.xsl         - script to validate catalogues of a submission

I have not taken the time to document these because I wanted everyone to 
get the flavour of what I was planning to do.  Now is the time to kill any 
misconceptions I may have about what is expected for genericization of the 
test suite.

Note that the test suite build tool will be shaped quite similarly to this 
catalogue validation tool from the perspective of finding information from 
multiple sources.

I look forward to any comments before I continue with this.

Thanks!

........................ Ken


--
G. Ken Holman                      mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.               http://www.CraneSoftwrights.com/s/
Box 266, Kars, Ontario CANADA K0A-2E0     +1(613)489-0999   (Fax:-0995)
Web site:     XSL/XML/DSSSL/SGML/OmniMark services, training, products.
Book:  Practical Transformation Using XSLT and XPath ISBN 1-894049-06-3
Article: What is XSLT? http://www.xml.com/pub/2000/08/holman/index.html
Next public instructor-led training:      2001-08-12,08-13,09-19,10-01,
-                                               10-04,10-22,10-29,02-02

Training Blitz: 3-days XSLT/XPath, 2-days XSLFO in Ottawa 2001-10-01/05