<xenoData> is not intended to be a dumping ground where you get to put your JPEG page images or JSON FOAF data or KML snippets. It's intended to be a place to put extracts of either the (non-TEI) metadata you used to generate your TEI header (but want to keep in its original form for some reason), or the (non-TEI) metadata you generated from your TEI header (and want to keep around for later processes, presumably).
That's not how I see it, to be honest. I would put exactly those sorts of things in it (with the exception of JPEGs). I would hope that any data in <xenoData> would be mirrored in some form or another in the teiHeader, but that may not always be practical. Cheers, Martin On 15-10-08 09:10 AM, Syd Bauman wrote:
Raff --
No, it would not help at all to make @scope a pointer to a specific element, or to use some other attribute to do the same thing. But worse, it would cause confusion, because (e.g.) if it pointed to <sourceDesc> does that mean that the (non-TEI) metadata is about "the source of this TEI document" or about the <sourceDesc> itself?
The <fileDesc> doesn't point to what its metadata applies to, the <revisionDesc> doesn't point to what its metadata applies to. Why should <xenoData> be different? Well, because we're collapsing two different uses (<non-TEI-description-of-source> and <non-TEI-description-of-this-file>; or /TEI/teiHeader/fileDesc/sourceDesc/xenoData and /TEI/teiHeader/fileDesc/xenoData; or whatever) into one, and differentiating them with an attribute.
<xenoData> is not intended to be a dumping ground where you get to put your JPEG page images or JSON FOAF data or KML snippets. It's intended to be a place to put extracts of either the (non-TEI) metadata you used to generate your TEI header (but want to keep in its original form for some reason), or the (non-TEI) metadata you generated from your TEI header (and want to keep around for later processes, presumably).
Would it help to make @scope a reference to a specific TEI element in the header, à la @decls? A reference to sourceDesc or msDesc would unambiguously indicate what the xenoData are about (or is equivalent / alternative to). The downside is that there must be corresponding TEI metadata for this to work, but maybe that's not a bad thing?
Disclaimer: I'm jumping into this late, so apologies if this suggestion may appear naive at this point in the conversation.