Branch/Resource Model: Person

[annabelleee]

Person branch as discussed during May 2018 meetings. Branch JSON to follow.

Steps to completion (updated):

• [ ] Metadata
• [ ] Diagram (using ARM WG notation)
• [ ] Sample Data
• [ ] Sample Concepts
• [ ] JSON of Arches branch based on diagram in ARM WG github repo
• [ ] Vote in comments to officially approve branch

[azaroth42]

Person model:

The slight differences from the whiteboard -- we didn't put in the predicates to birth and death, so I've used the generic ones. Secondly, Death as an Activity (murder / suicide) is an Activity, which requires a subclass in the ontology for Arches. As there's no distinction (at that point) between EoE+Activity and Death+Activity, I've put in the former. This also makes the generic predicates more appropriate.

[Habennin]

So this is represented in CRM predicates here:

https://docs.google.com/spreadsheets/d/1EYk1yhhBNWrKbVB0jV_1j8NJ-Egi5zWha7QrVvYvw3s/edit#gid=1743838490

Again the only hitch seems to be the question of start and end of existence. Here I would even say that the branch structure anticipation of the Arches programme also supports having subproperties and classes. We need a particular branch to talk about Birth and a different one for formation because they are fundamentally different types of events that we would want special predicates for in order to be able to track different types of causality (people don't give birth to organizations for example). If one wants to search for general comings into being and going out of being this is what the high level predicates are useful for: querying.

[workergnome]

I think that inheritance is of those philosophical questions worth talking through in detail--there's the need for specificity, as well as querying at a higher level.

Inheritance and class structures are a good way to do it--but it does mean that clients will need to both understand the ontology and provide a processing model that understands the implicit information within the class structure. We've leaned hard onto p2 as "tagging", as a different way to do this--less powerful, but there are benefits to that, as well.

The other option, which is also not supported by Arches, is multi-typing, which would let us explicitly add superclasses into the data.

(All of this is predicated on the data being consumed by applications other than Arches--if we're working entirely within the Arches infrastructure, we can do this entirely in code, which is another option.)

[azaroth42]

Birth and Death:

[Habennin]

here is some metadata and some examples https://docs.google.com/spreadsheets/d/1faeiBVz2vvkWYueOptCJJwK63pxXvM8P0f_-L0UNLxk/edit?usp=drive_web&ouid=115809866274616295104

[annabelleee]

See https://arm-test.getty.edu/graph_designer/074c8316-0b17-11ea-88e8-0242ac120005 for latest version of this model