Presented by KFL at WebSci 2015, Oxford, June 28 – July 1, 2015.
SNAP:DRGN & CIDOC-CRM conversation
Friday, May 15, 2015: King’s College London
Attending: Gabriel Bodard (GB), Arianna Ciula (AC), Øyvind Eide (OE), Faith Lawrence (FL), Christian-Emil Ore (CEO), Paul Rissen (PR), Valeria Vitale (VV), Hafed Walda (HW).
Apologies: John Bradley, Steve Stead.
We have three main topics of discussion:
- personal relationships (the SNAP “bond” ontology);
- co-references (and the inferences that derive from them);
- SNAP use of ontologies, and mapping to CRM.
1. Personal relationships/bonds
- CEO: The CRM defines several types of relationship (e.g. event, group, unilateral, family)
- GB: SNAP will eventually need to cover many more than just family/household relationships, as we currently have in the ontology
- OE: Is the aim to map all SNAP relationships to the CRM ontology, so we can always represent SNAP in CRM?
- FL: gave a summary of snap ontology
- (digression on equivalences between [lawd|crm|foaf|snap|etc.]:Person; is this a union set, rather than a single overlapping definition?)
- dual-classes of relationships: serious/casual/legally recognized; social contracts; intimate; household; foster/adopted/inlaw/claimed;
- gender (and other assumptions) not modelled in top-level classes, but could (maybe should) be?
- CEO: we can model all of these with group relationships, and then type them. Maybe we should make a recommendation for extending CRM with SNAP classes?
- GB: can we model non-family relationships (at the top-level)?
- [Not currently.]
- CEO: We should probably leave events out of the typology for now.
- VV: How can “ContractualRelationship” and “Relationship” be siblings?
- (GB: rename “Rel” ~~> “QualifierRel”)
- GB: then let’s just list all the new non-family relationships we need, and worry about grouping them (or not) later.
- OE: Suggest a follow-up meeting on CRM-INF (with Steve Stead, Dominic Oldman and Hugh Cayless).
- PR: BBC programmes ontology defines relationships by membership to groups
- could build on snap bonds for new relationships; useful for scholarly/journalistic claims, inference etc.
2. Co-references–both unambiguous and suggested (and inference)
- OE: distinguishing explicit and implicit co-reference:
- implicit co-reference is what all scholarly systems do, x=y.
- explicit co-reference requires attributing statement to someone
- a negative co-reference has no common target
- do co-references need a target?
- CEO: CRM doesn’t model identity, per se; two entities with different ids are therefore two different entities. CRM can’t express conflicting/untrue information.
- AC: it’s the expressing of conflicting opinions that is the problem there, if you want to keep both.
- HW: is identity a combination of person and context?
- CEO: They have different identifiers/are in different data-spaces.
- OE: SNAP needs to make explicit co-reference statements (with “belief system” over the top). Do we want fuzzy reliability values on them? (GB: no!)
3. SNAP ontology(ies)
- AC: lawd:hasAttestation/hasCitation == crm:isReferredToBy ?
- AC: lawd:nameAttestation == crm:appellation ?
- AC: CRM-inf might be more useful for Scenario 3 (unambiguous and unproblematic co-reference) than Scenario 4 (scholarly commentary about co-references/relationship), because CRM is a bit deterministic.
As you probably know, the pilot SNAP:DRGN project ended in December 2014, and although there are nearly seven hundred thousand person records visible through the public triplestore (SNAP 1 – SNAP 673934), we are currently lacking a user-friendly way to search within and find these records. (We’re working on this, as we’ll report here soon.) Most of the person records in SNAP so far are from LGPN, Trismegistos and PIR, but if you have a reference to PIR² M 436, say, or LGPN V.2 Θουκυδίδης 11, and want to find the SNAP URI with which to annotate your texts, there’s no obvious way to know that these are SNAP 9024 and 33624 respectively. Continue reading How to find people in the SNAP graph
Broadly speaking, there are three categories of project that deal with ancient person or name data which we would like to see collaborating with SNAP:DRGN. For the sake of argument I’ll call these “prosopographies”, “person and name authorities” and “digital editions containing named entities.” Continue reading Different types of SNAP partner projects
- AB Meeting 3 minutes (pdf)
SNAP:DRGN Advisory Board (AB)
3nd meeting Skype (voice only) 2015-02-23
Present: Øyvind Eide (ØE, chair), Fabian Koerner (FK), Robert Parker (RP), Laurie Pearce (LP), Charlotte Roueché (CR, until 17:35), Rainer Simon (RS), Gabriel Bodard (GB, principal investigator) Continue reading Third Advisory Board meeting minutes
As we come to the end of the first year of SNAP:DRGN funding, and start planning applications for follow-up funding, it is worth rehearsing the main academic and other benefits of the SNAP:DRGN projects and the prosopographical-onomastic graph that we hope it feeds into. Continue reading Who does SNAP:DRGN serve?
We have often been asked:
“SNAP” contains the word “Ancient,” which suggests a rather inclusive definition of classical antiquity, but “DRGN” includes “Greco-Roman”, which implies more traditional restriction. Are you interested in prosopographies from outside the strictly Greek and Roman world?
Yes! (Short answer.)
Longer answer is in two parts: Continue reading FAQ: What are the limits of SNAP content?