[tei-council] ODD notes
Lou Burnard
lou.burnard at computing-services.oxford.ac.uk
Wed Jul 11 09:48:28 EDT 2007
Here's a brief list of some ODD issues raised by Sylvain Loiseau when I
met him in Paris last week.
1. Can an ODD document contain more than one <schemaSpec> element? The
schema permits this, but the current toolkit expects to produce only one
set of outputs. So either multiple schemaSpec elements should generate
an error or the current toolkit needs enhancing
2. Why is <attRef> not a member of model.oddRef?
3. If ODD is meant to be fully general there ought to be some way of
specifying the base collection of modules which are to be combined by
reference from within a schemaSpec, defaulting to "tei". A @base
attribute on the schemaSpec might do this (not to be confused with
xml:base however)
4. When deleting (eg) an elementSpec, why is it necessary to specify the
module? this is redundant, surely.
5. Should the text of the TEI Guidelines not include a <schemaSpec>
somewhere, generating (presumably) tei_all?
6. We don't specify anywhere in what circumstances order is significant
for the declarations within a <schemaSpec>, nor that only the
declarations contained by one (either directly or via moduleRef,
specGrpRef etc) are used in the output schema. Should declarations not
so contained generate an error?
7. What is the rationale for declaring classes local to a module instead
of as part of the infrastructure module?
Sylvain, for those who don't know him, is (amongst other interesting
things) working on a project at LIMSI to convert the French wikipedia
into TEI XML markup
More information about the tei-council
mailing list