Re:base64 encoding JPG ... uh yes. That is what we have binaryObject for.
Otherwise, agreed.
James
--
Dr James Cummings, Academic IT, University of Oxford
-----Original Message-----
From: Hugh Cayless [philomousos@gmail.com]
Received: Thursday, 08 Oct 2015, 12:47
To: Syd Bauman [s.bauman@neu.edu]; TEI Council [tei-council@lists.tei-c.org]
Subject: Re: [tei-council] xenodata/@scope
Syd, I think your conception of what xenoData is for is much narrower than
mine. I would use it for related data that for some reason doesn't quite
fit into my TEI. That might be because it isn't TEI, or even XML, or it
might be because TEI doesn't quite do the trick for representing it. I
agree that Base64 encoding your JPEG and bunging it in there would be dumb,
but maybe having a manifest of linked images in a non-TEI format might not
be. A FOAF representation of the social network represented in my document
might be fine too. The problem statement in the original ticket begins "People
sometimes want to attach metadata to a TEI document that doesn't fit into
an existing header element." Isn't that what we should implement, having
agreed that's not a bad idea?
On Thu, Oct 8, 2015 at 12:10 PM, Syd Bauman
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. -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council PLEASE NOTE: postings to this list are publicly archived