[tei-council] standoff

[Hugh Cayless]

METS is a pretty heavyweight solution. I’d use it if I wanted to bundle together a bunch of files with metadata. <xenoData> is lighter-weight and allows you to plop in arbitrary non-TEI (meta)data in your TEI file. And, yeah, <standoff> gives you a place to put existing tools to wire up your TEI document using TEI linking mechanisms. 

I can see all three being potentially useful. I suppose <xenoData> and <standoff> could be combined into a <miscellaneousCrap> container if you wanted, but I’m not sure there’s any advantage to that. I don’t think forcing people to learn METS in order to add a bit of Dublin Core to their TEI doc is wise.

Hugh

> On Nov 28, 2014, at 11:13 , Martin Holmes <mholmes at uvic.ca> wrote:
> 
> 
> 
> On 14-11-28 07:10 AM, Peter Stadler wrote:
>> 
>> Am 28.11.2014 um 15:24 schrieb Lou Burnard <lou.burnard at retired.ox.ac.uk>:
>> 
>>> I agree that we should not waste time re-inventing METS.
>> Why do we then bother with „xenoData“ and not tell people to use METS?
> 
> METS is one standard that some people use. I don't use it myself. I do 
> use lots of other standards (Dublin Core, OAI...) and I'd like to be 
> able to put that data in there.
> 
> We seem to be getting at least three different proposals completely 
> confused now. The METS thing arose out of Peter's idea of creating a 
> binary zip format for a TEI package. The xenoData thing is a place to 
> put _any_ metadata in a non-TEI namespace. The <standoff> element (as I 
> understand it, at least) is a place to put standoff TEI markup that 
> doesn't have a natural home.
> 
> Cheers,
> Martin
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived