On 11/07/15 19:03, Syd Bauman wrote:
<xenoData>, IMHO, is intended to make the easy case easy, not to make the complex case possible (in large part because the complex case is already possible -- e.g., you can put mods:* as a child of <bibl>, or put it in your <teiHeader> attach it to the <bibl> with <link>).
I agree with Syd here. Martin's proposed use case is rather specialised.
The easy case, the one which quite a few large projects have expressed a desire for, is to have a consistent place to put the METS record from which the <teiHeader> was derived, or the Dublin Core metadata that you derived from the <teiHeader> for whatever purpose, but don't want to re-generate on the fly.
Exactly.
I, for one, had never envisioned non-XML data inside <xenoData>, and think it would be a bad idea to permit it.
I don't think we're in a position to permit or not permit anything inside <xenoData> : it is explicitly non-TEI data, so all bets are off. Of course if it's not well-formed XML it will need to be wrapped in a CDATA section or similar.