Presentation delivered to the Standards of Networking Ancient Prosopographies meeting, held in London, March 31-April 1, 2014. It discusses nomisma.org and kerameikos.org datasets that can contribute to SNAP, the Roman Imperial Social Network (RISN) dataset, under development, and the open source EAC-CPF editing and publication software, xEAC (https://github.com/ewg118/xEAC)

1. The Roman Imperial Social Network
and other things
Ethan Gruber
American Numismatic Society
gruber@numismatics.org
@ewg118

2. 1. http://nomisma.org
http://nomisma.org/id/augustus
VIAF, Getty, BM, DBpedia

3. SPARQL
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX dcterms: <http://purl.org/dc/terms/>
PREFIX nm: <http://nomisma.org/id/>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX geo: <http://www.w3.org/2003/01/geo/wgs84_pos#>
SELECT ?object ?findspot ?lat ?long ?title WHERE {
?type nm:authority nm:augustus .
?object nm:type_series_item ?type ; nm:findspot ?findspot .
?findspot geo:lat ?lat ; geo:long ?long .
OPTIONAL {?object dcterms:title ?title}
}

4. 2. http://kerameikos.org
VIAF, Getty, DBpedia, BM, LGPN, etc.

5. Extract owl:sameAs concepts
directly from VIAF
(e.g., BnF, GND)

6. 3. Roman Imperial Social Network (RISN)
Tom Elliott's Emperors CSV Nomisma Emperors CSV
DBpedia
PHP*
*https://github.com/ewg118/xEAC/blob/master/tools/dbpedia-to-eac.php
EAC-CPF XML Stubs
PIR RDF

7. EAC-CPF: Encoded Archival Context –
Corporate Bodies, Persons, Families
 Name authority
 Biographical
information
 Related entities
 Related resources
http://eac.staatsbibliothek-berlin.de/
http://socialarchive.iath.virginia.edu/

8. Creating, editing, and publishing EAC-CPF with xEAC
XForms web applications: https://github.com/ewg118/xEAC

11. http://admin.numismatics.org/xeac/id/alexander_the_great

12. otherRecordId: http://nomisma.org/id/augustus
SPARQL: RDF query for related objects

13. The Challenge: Maintaining Relationships
*Now able to handle import/parse of RDF ontologies

14. Create Stub
Create relationship to
existing EAC-CPF record

15. <foaf:Person rdf:about="http://admin.numismatics.org/xeac/id/alexander_the_great">
<skos:altLabel>Alexander the Great</skos:altLabel>
<skos:altLabel xml:lang="ja">アレクサンドロス3世</skos:altLabel>
<skos:prefLabel xml:lang="en">Alexander the Great</skos:prefLabel>
<skos:altLabel xml:lang="nl">Alexander de Grote</skos:altLabel>
<skos:altLabel xml:lang="de">Alexander der Große</skos:altLabel>
<skos:altLabel xml:lang="es">Alejandro Magno</skos:altLabel>
<skos:related rdf:resource="http://dbpedia.org/resource/Alexander_the_Great"/>
<my:childOf xmlns:my="http://example.org/my#"
rdf:resource="http://admin.numismatics.org/xeac/id/philip_ii_of_macedon"/>
</foaf:Person>
Export: RDF and TEI

16. Next Steps
 Finish form: Represent all EAC-CPF elements and attributes
 Test for scalability
 Interface with more APIs
 Improve public interface, especially searching and browsing
 Incorporate SPARQL endpoint for social network graph visualization
 Follow evolving best practices in RDF/linked open data

17. Next Steps
 Finish form: Represent all EAC-CPF elements and attributes
 Test for scalability
 Interface with more APIs
 Improve public interface, especially searching and browsing
 Incorporate SPARQL endpoint for social network graph visualization
 Follow evolving best practices in RDF/linked open data