Dear Roberto, dear all,
very interesting following all these examples. However, I wonder if
there is another point to your colleague’s opinion. And the argument is
hardly new that the TEI allows for such a range of different encoding
approaches and subtle differences, that using TEI as a *machine
readable* exchange format is actually really hard.
So I think it is very easy to agree that having texts available online
allows for data reuse, and that having a format like TEI is a good
thing, as the format and its documentation make it easier for a *human*
to understand how to interpret that specific encoding schema.
But building tools that rely on machine readability using available TEI
sources beyond your control is a very different matter.
Taking the Deutsches Textarchiv as an example: They provide their texts
not only in TEI, but additionally in TCF, a format from the
computational linguistics community. So if machine readability is a top
priority, it seems to be easier to use a more constrained format than to
model this information in TEI. One could easily encode that information
in TEI, using feature structures or @ana or something, but probably not
in a way that one can be sure is understood by a software beyond one’s
So are there examples of tools that consume (at least a subset of) TEI
and that work beyond the community that defines the respective TEI
subset? Or would one simply export one’s data to other formats like TCF
or RDF if machine readability is an issue?
Am 06.10.2014 um 14:41 schrieb Roberto Rosselli Del Turco:
> Dear all,
> when discussing TEI-related stuff, and especially when praising the many
> virtues and advantages of TEI XML encoding, one of my favorite arguments
> is that not only TEI is a great format when aiming for long-term data
> preservation, but it also allows data interchange among different
> projects (that's one of the possible meanings of the 'I' in TEI, right?).
> A colleague and friend of mine who has a somewhat different opinion of
> TEI encoding, recently wrote an article where he stated that this
> advantage is just a theoretical one, because there are *no* projects
> actually sharing TEI data originating from somewhere else.
> I was going to fire up a mail to answer this claim, when I realized that
> I couldn't think, on the top of my head, of one or more projects doing
> exactly that: can you help me finding examples? and, if such interchange
> is less than expected/desirable, what could be the reason? projects
> jealously keeping all XML data private, or making those available with a
> very restrictive license?
> Thank you in advance,
Frederik Elwert M.A.
Centre for Religious Studies
Phone +49(0)234 32-24794