I have some doubts as well, in a past mail exchange about <xeno> I
suggested some similar use cases advocating for a more granular way to
associate a metadata set with part of the TEI doc. My position is that we
should discuss this with more deeply at the f2f, and abstain from including
this att in the release, for the moment.
f
2015-10-06 16:43 GMT+02:00 Hugh Cayless
I wanted to ask, before it’s too late, whether we’re all happy with @scope on <xenodata>. I’m not very fond of it, to be honest. I might use xenodata in the following scenarios:
1) I generated my TEI (particularly its metadata/header) from another source, and I want to capture that source. 2) I have related data in another format, maybe GeoJSON for mentioned places, or MODS records for my bibliography that I want to embed.
In nether case would @scope really help me...I was under the impression that we were going to defer categorizing xenodata until we had requests from people using it.
What do we think?
-- 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
-- Fabio Ciotti Dipartimento di Studi letterari, Filosofici e Storia dell’arte Università di Roma Tor Vergata President "Associazione Informatica Umanistica Cultura Digitale" (AIUCD)