Dear Sebastian and all,
maybe we can contribute something to the discussion with what we are
doing with the Hellespont Project. There we work with the TEI standard
in order to link from the text of the ancient author Thucydides to
archaeological entities of the Arachne database, using Arachne URIs.
The TEI files (transformed with XSLT) are the basis for further
visualisation of the text:
Furthermore, we are implementing at the moment a Hellespont Linked
Data interface where almost the whole Arachne database (beside others)
is available as RDF XML following the CIDOC CRM ontology.
What is still missing (regarding the question of TEI and Linked Data)
is the connection between our Linked Data RDF and the Arachne URIs
integrated in the TEI annotation of the text. Right now RDF data is
not available with the Arachne URIs themselves, but hopefully
development in this area will bridge the data sooner or later.
Is this interesting for you?
You can find all our data for download here:
Any comments are welcome!
Greetings from Cologne
Karen and Agnes.
Deutsches Archäologisches Institut, Berlin
Arbeitsstelle für Digitale Archäologie, Köln
German Archaeological Institute, Berlin
Cologne Digital Archaeology Laboratory
Zitat von Sebastian Rahtz <[log in to unmask]>:
> On 23 Oct 2013, at 13:05, Jennifer Eustis
> <[log in to unmask]> wrote:
>> I’ve been asked to investigate using linked data in TEI records.
>> This would concern mostly uri’s for names (personal, entities,
>> geographic) and subjects. I’ve really have found a lot of
>> information in terms of examples and ideas on how to do this. Is
>> anyone currently implemented linked data in their TEI records and
>> would they be willing to share some examples?
> Generally speaking, anyone who references an external resource from
> their TEI file is doing linked data in some sense;
> e.g. anyone who uses @ref on <persName>
> There's a distinction between
> * implicit linked data, i.e. TEI texts which encode information to
> a sufficient degree of richness and consistency to enable automated
> * explicit linked data, i.e. using <relation> elements to more or
> less directly record RDF triples.
> As an extreme example of the former, consider
> which is an RDF XML representation, using the CIDOC CRM ontology, of
> about Greek names from Lemnos. It's entirely derived from TEI XML
> source files, but thats not very typical
> A more realistic example might be the text represented at
> from which one could undoubtedly easily extract a data statement
> relating this object to
> I can't think offhand of a published resource using <relation>
> elements - I'll be interested to hear
> whether other people offer some.
> Sebastian Rahtz
> Director (Research) of Academic IT
> University of Oxford IT Services
> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431