At Nancy (France), we are currently working on a project to improve some
features of Roma.
As you know, Roma is the tool that supports TEI customisation. It has been
developed by Sebastian Rahtz and Arno Mittelbach (2004).
Each customized specification output by Roma is an ODD file. From this file,
an XML DTD, XML Schema in the W3C schema language or in RelaxNG, etc. can be
generated, as well as the associated technical documentation.
Currently, within Roma, users select the desired TEI elements by choosing
from “flat lists”, as if elements were completely independent from each
others. For example, nothing prevents them from choosing an “item” element
but no “list” element. Underlying constraints are not made explicit to the
users. Hence, the resulting schema can be incoherent.
The aim of our current work is to improve on this particular point and to
insure (better) coherency of Roma's outputs.
Now, to start with, we are trying to get a clearer idea of possible
There are inconsistencies related to the element hierarchy, which we
consider a priority:
(1) you can select an element without selecting a parent of it (eg.
selecting the elements "tei", "title" but not the element "titleStmt")
(2) you can choose an element without selecting children of it (eg.
selecting the element "interpGrp" but not the element "interp"). Note: this
can either be a mistake or you may want the element to be empty.
There might be inconsistencies related to the class structure.
If you have encountered such "inconsistencies", if you happen to have clear
ideas about a typology, please share these with us!
Thanks in advance,
-- Ioan Bernevig, Veronika Lux-Pogodalla