Lists Home |
Date Index |
Rick Jelliffe wrote:
Not sure what you mean by "correctly marked up"? Serious question and here's
From: "Patrick Durusau" <email@example.com>
This ties the processing of the markup to the inline syntax in the
document instance, a bad thing in my opinion. The JITTs paradigm allows
you to impose structure upon the markup in the document instance, as
opposed to relying solely upon the inline syntax.
It is a limitation of the JITTs paradigm, which will be noticed by its
critics once all other criticisms fail, that it requires use of a DTD or
So the only way to know if the document is correctly marked up
is to have enough DTDs to cover every tag?
Assume we have a document instance that has markup that you have entered
using TEI and I have entered markup using DocBook in the same document. So
we have some elements that mark the same structures with different names,
may have some structures that occur in one and not the other.
Assume that you want to process the document using your TEI markup. With
a JITTs parser, the only markup that is recognized (let's assume in discard
mode) is your TEI markup and that feeds into an XSLT stylesheet for production
of a PDF file.
Assuming that your TEI markup complies with the TEI DTD, is the document
"marked up correctly"?
My answer would be yes, because what other test for correct markup can we
have other than compliance with a DTD/schema (by the recognized markup) that
can then be manipulated by stylesheets or other processing for that DTD or
The difference in the JITTs paradigm and the conventional view of processing
markup is that the latter burdens the inline syntax with compliance to a
particular set of rules prior to processing. Prior to processing, I would
argue that there is no correct or incorrect markup in a document instance.
If you really wanted to validate all the markup in a document, I can imagine
cases where that would be useful, then yes, the sum of the DTDs or schemas
would have to cover all the markup in the document. Unlikely in most cases
but I can see where that might be a requirement, such as validating both
a print and structural view of a document.
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
The list archives are at http://lists.xml.org/archives/xml-dev/
To subscribe or unsubscribe from this list use the subscription
Director of Research and Development
Society of Biblical Literature