Syd Bauman wrote:
>* If you're beyond brave, try validating against the file
> 'testdictionaries.xsd' (which won't work, BTW):
> xmllint --noout --schema testdictionaries.xsd testdictionaries.xml
Syd is right that this _per se_ will not work, but what *will* work
jing testdictionaries.xsd testdictionaries.xml
If you're finding all this command-line stuff is making your
head spin, and you prefer commerical tools like
oXygen, XMetal, XML Spy etc, simply take testdictionaries.xsd
and xml.xsd, and put them where your tool finds schemas.
Then start working with a new document based on schema
>This turns out to be a bit tricky, as there are declarations in the
>'Test/dictionaries.odd' file that are intended to override the
>declarations in the source tree, and to be honest, I'm not sure which
>is the one an average user would want right now. (This is what we get
>for using the current CVS, rather than the released files, I guess.)
not quite. "testdictionaries.odd" is what it says, a test file,
not a model. It shows how a TEI customized schema which uses
dictionaries can be described, not what a typical user might want.
We don't currently have any recommended model schemas
or sample files. Those must be defined and created; the Test
suite is similar, but not the same.
As you can tell from Syd's interesting essay, there are a fair
few days to skin a TEI P5 cat, and not all of them are
yet adequately documented.
Hopefully, the TEI wiki will get going soon, so people will
be able to put up, and comment on, typical use cases.
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
OSS Watch: JISC Open Source Advisory Service