Linking Ancient World Data

Hugh Cayless
Duke Collaboratory for Classics Computing
@hcayless on Twitter

DC3


Josh Sosin, Ryan Baumann, Hugh Cayless


“The Duke Collaboratory for Classics Computing, the DC3, is a no-nonsense, interdisciplinary, results-oriented research group devoted to the creation and care of standards, services, and tooling for digital classics and beyond. We aim to be flexible, durable, and to leverage the strengths of our many partnerships so as to be a collection of parts flying in loose formation. Like the plane.” blogs.library.duke.edu/dcthree

EpiDoc: epidoc.sf.net

TEI: www.tei-c.org

Linked Data

  • Available on the web (whatever format) but with an open licence, to be Open Data
  • ★★ Available as machine-readable structured data (e.g. excel instead of image scan of a table)
  • ★★★ As above plus non-proprietary format (e.g. CSV instead of excel)
  • ★★★★ All the above plus: Use open standards from W3C (RDF and SPARQL) to identify things, so that people can point at your stuff
  • ★★★★★ All the above, plus: Link your data to other people’s data to provide context

- Tim Berners-Lee’s Linked Data Ratings System

Linked Data ≠ Semantic Web

Papyri.info


  • The Duke Databank of Documentary Papyri
  • The Heidelberger Gesamtverzeichnis der griechischen Papyrusurkunden Ägyptens
  • The Advanced Papyrological Information System
  • Trismegistos
  • The Bibliographie Papyrologique
DDbDP Transcriptions
HGV Data about the documents
APIS Catalog records from institutions holding the documents
Trismegistos Issues identifying numbers and metadata about / analysis of documents
BP Bibliography

if


@prefix dc:    <http://purl.org/dc/terms/> .

<http://papyri.info/ddbdp/o.erem;;37/source>
        dc:relation    <http://papyri.info/hgv/2535/source> .
          

and


<http://papyri.info/apis/hermitage.apis.103/source>
        dc:relation    <http://papyri.info/ddbdp/o.erem;;37/source> .
            

then


<http://papyri.info/hgv/2535/source>
        dc:relation    <http://papyri.info/apis/hermitage.apis.103/source> .
            

Let's take a walk: http://papyri.info/ddbdp/p.bacch;;12, http://papyri.info/ddbdp/bgu;16;2600

So:


<http://papyri.info/ddbdp/p.bacch;;12/source>
        dc:source  <http://papyri.info/ddbdp/p.bacch;;12/work> .
          

and:


<http://papyri.info/ddbdp/p.bacch;;12/work>
        dc:source  <http://papyri.info/ddbdp/p.bacch;;12/original> .
          

which means we can say (for example):


<http://papyri.info/ddbdp/p.bacch;;12/original>
        lawd:foundAt  <http://pleiades.stoa.org/places/736896#this> .
          

http://papyri.info/ddbdp/p.bacch;;12/original is a Non-Information Resource (NIR), and it redirects to http://papyri.info/ddbdp/p.bacch;;12, which is an Information Resource (IR)

Pelagios: pelagios-project.blogspot.com

an OA annotation:


<http://papyri.info/ddbdp/o.erem;;37/annotation/0b48ac2c6f4708d1271aa115b1cf3e12>
        a               oa:Annotation ;
        rdfs:label      "Theben (Charax)" , "Theben" ;
        oa:hasBody      <http://pleiades.stoa.org/places/991398#this> ;
        oa:hasTarget    <http://papyri.info/ddbdp/o.erem;;37> ;
        oa:motivatedBy  oa:linking 
          

lawd.info


  • supply types and properties for ancient texts and artifacts where there are no usable/convenient alternatives
  • link existing vocabularies together
  • do just enough work, no more

Thanks! Questions?