There are projects I probably would have used it for, had it been
available at the time, like the APIS data, which used a weird,
MARC-inspired text format for its data (see
https://github.com/papyri/idp.data/blob/master/APIS/berkeley/intake_files/be...,
for example). But it doesn't seem worth it to go back and
retro-convert it, and it's all in source control anyway.
On Tue, May 10, 2022 at 10:52 AM Bauman, Syd
To be fair, though, you asked about DCMI or OAI markup inside <xenoData>. The only time I have used <xenoData> I tucked some MARCXML or MODS info in there. But it was not a “real project” so much as an experiment for one, and there are no vestiges of that experiment left on my disk, it seems. The WWP used to have a flat database of “reception items” (i.e., reviews) of works in our textbase. That metadata was extracted from the flat database for all files, and is now stored in a <xenoData> in each individual file. The format used inside <xenoData> is just a single xqj:json element which holds a series of name-value pairs. (See Women Writers in Review for the front-end.)
________________________________ a few weeks ago i posted a query about usage of xenoData on tei-l and followed it up with a repeat on twitter. i was a bit surprised to receive absolutely zero response (full disclosure : i did get a reply from m.mueller but not to the question i asked) . so either no one is using this lovely tag or no one wants to admit to it. either of which seems somewhat of a problem. maybe, i thought, maybe the mandarins of the tei council know better? are any of you using it for real in a project?do you know any project which is?
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council