Difference between revisions of "Oddbyexample"
(→Documentation) |
(→Tech support) |
||
Line 47: | Line 47: | ||
== Tech support == | == Tech support == | ||
− | + | No formal technical support is provided for Oddbyexample. If you post a question to the TEI-L list, though, other users may respond with help. | |
== User community == | == User community == |
Revision as of 02:12, 29 November 2012
Contents
- 1 Synopsis
- 2 Features
- 3 User commentary
- 4 System requirements
- 5 Source code and licensing
- 6 Support for TEI
- 7 Language(s)
- 8 Documentation
- 9 Tech support
- 10 User community
- 11 Sample implementations
- 12 Current version number and date of release
- 13 History of versions
- 14 How to download or buy
- 15 Additional notes
Synopsis
This utility attempts to work out the minimal TEI customization needed to validate a collection of files. The XSLT (version 2) stylesheet which traverses a nominated directory tree looking for *.xml files which have <TEI> or <teiCorpus> root elements. It analyzes the collection of elements and attributes in the resulting corpus, and compares that to the whole of TEI P5. An ODD file is generated which:
- loads the required modules
- deletes any elements which are not used
- deletes any attributes (including class attributes) which are not used by each element
- for every attribute which has a TEI "data.enumerated" datatype, constructs a closed <valList> enumerating the values actually used.
From this you can construct a target schema.
Features
User commentary
Please sign all comments.
System requirements
Memory capacity is likely to be an issue for large corpuses. It's not going to read a giant corpus unless you have a great deal of memory to assign to Java. For situations like this, it is suggested that you construct a smaller corpus of representative sample documents and work with that. After generating a schema, you can validate your entire corpus, and each time you find an invalid document, add it to your smaller corpus and start again.
Source code and licensing
open source
Support for TEI
Oddbyexample is not yet able to:
- derive simplified content models (beyond what Roma already does)
- add new elements and derive content models for them
- deal with non-TEI namespaces
- generate attribute datatypes with complex regexps not already specified in TEI specifications
- create new Schematron constraints etc
Language(s)
XSLT
Documentation
The script assumes you have the TEI package which has a file called "/usr/share/xml/tei/odd/p5subset.xml". If you don't have that, grab http://www.tei-c.org/release/xml/tei/odd/p5subset.xml, put the file somewhere, and add a "tei" parameter to point at it. (Alternatively, you can check out the TEI source and generate p5subset.xml yourself, by running "make p5subset.xml" in the P5 directory.)
Here's a sample command to run Oddbyexample:
saxon -o my.odd oddbyexample.xsl oddbyexample.xsl corpus=/wherever/you/have/yourfiles/
Tech support
No formal technical support is provided for Oddbyexample. If you post a question to the TEI-L list, though, other users may respond with help.
User community
Sample implementations
Current version number and date of release
History of versions
How to download or buy
Grab getfiles.xsl and oddbyexample.xsl from Sourceforge (http://tei.svn.sourceforge.net/viewvc/tei/trunk/Stylesheets/tools/oddbyexample.xsl)