Joshua Hutchinson wrote:
Shouldn't a TEI-Lite validator flag your second example as wrong, too? Looking over the TEI-Lite documentation, you could markup that information, but in a slightly different format.
That was just a general example. It was not meant to be specific to TEI.
Now, putting aside the fact that I doubt I'd ever bother to mark up an address to that exacting of a detail ;) ... Am I understanding the role of the validator properly in that it should choke on the first, since it doesn't, as far as I can tell, conform to TEI-Lite?
It will choke if you validate my example against the TEI DTD. But I could write a SOMETHING DTD that validates that example all right.
That seems acceptable to me. For instance, to continue you example above, if you wanted to add <place>, <name>, and <street> to the <address> markup, then you could put those elements in your personally DTD, which calls the TEI-Lite DTD, and then the validator should be able to parse it as acceptable code, right?
Yes.
But the question then becomes, will the standard transform be able to handle the new code in your DTD? If it just ignores what it doesn't understand, that would be acceptable, I'd think. But if the new tags cause the transform to choke, then we'd have a problem.
A standard TEI transform will simply ignore all tags he doesn't recognize. Just like a HTML browser does. -- Marcello Perathoner webmaster@gutenberg.org