Could those who have recently claimed that they only work in XML with the
TEI Guidelines explain how they deal with the mixed content issue? Are you
working only with TEI-lite?
When several TEI tag sets are combined into a project's DTD, there are
declarations that contain groups with occurrence indicators. This is not
particularly a problem for projects validating their XML markup in an SGML
environment. It does pose a few inconeniences for projects wishing to
retain DOCTYPE declarations in their files and use Internet Explorer (and
possible any future XML-compliant Web browser). The parser of course kicks
up a fuss when parsed charater data #PCDATA is declared to be allowable in
a group that uses connector indicators other than "or". Commenting out the
DOCTYPE declaration allows the file to be read by Internet Explorer. One
can imagine a use case of distance collaboration with validation against a
remote DTD to understand why this could be a concern.
Is this a good question for the FAQ? If so, how can it be broken down into
segments comprehensible to the novice or beginner.
Of course using XSLT to convert to HTML and validating the HTML gets
around this particular problem and ensures that material can be available
across a wider range of browsers. But it does not address the needs of
distributed work groups that might wish to use the cheap (i.e. free)
parser housed in a Web browser to validate files against a remote DTD.
XML developments certainly offer new opportunities for the distribution of
richly encoded texts. They also offer new opportunities for designing work
processes that can significantly match content providers (scholars) with
document handling specialists (geeks) without having both geek and scholar
reside in the same body.
<!ELEMENT Work_Team (GEEK*, SCHOLAR+)+>
Francois Lachance, Scholar-at-large
some threads tangle in tassles, others form the weft