Reconstructions and Observations in Archival Resources roar https://w3id.org/roar# Ontology to describe person, location etc. observations in archival resources. One or multiple observations can be bundled into a reconstruction that combines complementary (or sometimes conflicting) information from the observation(s) so that a single entity is reconstructed out of several entity observations from one or multiple sources. Reconstructions and Observations in Archival Resources 0.1 Even if there is no specific birth date mentioned in the source, it is recommended to provide a Birth event and estimate the dates based on other (life) events around the person. A concrete example would be the mentioning of a Baptism event, by which the date of birth can be estimated, for instance by setting the `sem:hasLatestEndTimeStamp` property to the date of the Baptism event. Example: ```ttl _:person1 a roar:PersonReconstruction ; rdfs:label "Susanna de Bock" ; pnv:hasName [ a pnv:PersonName ; pnv:baseSurname "Bock" ; pnv:givenName "Susanna" ; pnv:literalName "Susanna de Bock" ; pnv:surnamePrefix "de" ] ; bio:event [ a bio:Baptism ; bio:place _:location1 ; bio:principal _:person1 ; sem:hasActor [ a sem:Role ; sem:roleType [ a sem:RoleType ; rdfs:label "baptized" ] ; rdf:value _:person1 ] ; sem:hasTimeStamp "1697-02-28"^^xsd:date ] ; bio:birth [ a bio:Birth ; bio:principal _:person1 ; sem:hasActor [ a sem:Role ; sem:roleType [ a sem:RoleType ; rdfs:label "born" ] ; rdf:value _:person1 ] ; sem:hasLatestEndTimeStamp "1697-02-28"^^xsd:date ] ; roar:documentedIn _:saaId10160347 . ``` bio:birth Even if there is no specific death date mentioned in the source, it is recommended to provide a Death event and estimate the dates based on other (life) events around the person. A concrete example would be the mentioning of a Burial event, by which the death date can be estimated, for instance by setting the `sem:hasEarliestBeginTimeStamp` property to the date of the Burial event. Example: ```ttl _:person1 a roar:PersonReconstruction ; rdfs:label "Susanna de Bock" ; pnv:hasName [ a pnv:PersonName ; pnv:baseSurname "Bock" ; pnv:givenName "Susanna" ; pnv:literalName "Susanna de Bock" ; pnv:surnamePrefix "de" ] ; bio:event [ a bio:Burial ; bio:place _:location1 ; bio:principal _:person1 ; sem:hasActor [ a sem:Role ; sem:roleType [ a sem:RoleType ; rdfs:label "burried" ] ; rdf:value _:person1 ] ; sem:hasTimeStamp "1697-02-28"^^xsd:date ] ; bio:birth [ a bio:Birth ; bio:principal _:person1 ; sem:hasActor [ a sem:Role ; sem:roleType [ a sem:RoleType ; rdfs:label "born" ] ; rdf:value _:person1 ] ; sem:hasLatestEndTimeStamp "1697-02-28" ] ; bio:death [ a bio:Death ; bio:principal _:person1 ; sem:hasActor [ a sem:Role ; sem:roleType [ a sem:RoleType ; rdfs:label "died" ] ; rdf:value _:person1 ] ; sem:hasEarliestBeginTimeStamp "1697-02-21" ; # Estimated, 7 days earlier sem:hasLatestEndTimeStamp "1697-02-28" ] ; roar:documentedIn _:saaId10160347 . ``` bio:death Use to connect life events to a Person. Use more specific events, such as `bio:birth` and `bio:death` for respectively Birth and Death events. bio:event prov:agent prov:entity prov:hadActivity prov:hadPlan prov:qualifiedAssociation prov:qualifiedDerivation prov:wasAssociatedWith A Reconstruction is derived from one or several Observation(s) or Reconstruction(s). It is good practise to also specify the activity in which the derivation was made. This can be done by modelling a `prov:qualifiedDerivation` on the Reconstruction in which the Activity, Agent and Plan can be specified. prov:wasDerivedFrom pnv:hasName Refers to the Document (source, act, legislation etc.) in which the Observation is made. It is recommended to point to a resource (URI) provided by some institute/archive that hold key information on this source. You are, however, free to fill `roar:Document` with additional information. documentedIn Use to indicate that an Entity has a relation to a Location. Use a structured value to indicate a specific role of this Entity (e.g. Person) to the Location or to specify a temporal validity in which this Entity-Location relation is valid (use `sem` timestamp properties for this). Example: ```ttl :person1 a roar:PersonObservation ; roar:hasLocation [ rdf:value :location1 ; roar:role "resident" ; sem:hasBeginTimeStamp "1782-11-20" ; sem:hasEarliestEndTimesStamp "1782-11-20" ] . ``` hasLocation Use to indicate that an Entity has a relation to a Person. Use a structured value to indicate a specific role of this Entity (e.g. Location) to the Person or to specify a temporal validity in which this Entity-Person relation is valid (use `sem` timestamp properties for this). Use `roar:hasRelation` for Person to Person relations. Example: ```ttl :location1 a roar:LocationObservation ; roar:hasPerson [ rdf:value :person1 ; roar:role "residence" ; sem:hasBeginTimeStamp "1782-11-20" ; sem:hasEarliestEndTimesStamp "1782-11-20" ] . ``` hasPerson Relation to another person or organisation, defined by a structured value to indicate the kind of relation. *Example*: ```ttl :person1 a roar:Person ; schema:gender schema:Female ; roar:hasRelation [ rdf:value :person2 ; roar:relationType "mother" ] . :person2 a roar:Person ; schema:gender schema:Male ; roar:hasRelation [ rdf:value :person1 ; roar:relationType "firstborn son" ] . ``` hasRelation The locationInDocument property can hold any location reference relative to the Document an Observation is in. This can be used to indicate a location in the source, even when the source has not yet been digitized (then a roar:onScan can be used). locationInDocument This property can be used to indicate the location of the EntityObservation in the source, for instance if the roar:Document is too general (e.g. it refers to multiple pages). This should refer to a URI or filename and assumes the source is digitized. onScan Used to specify the kind of relation (e.g. "patron") in a person to person relation as specified by `roar:hasRelation`. relationType Can be used to indicate the role of an entity in a `roar:hasLocation` or `roar:hasPerson` relation. In case of a Person to Location relation (through `roar:hasLocation`), the `roar:role` can for instance be 'inhabitant' or 'visitor'. Similarly, the role of a Location to Person (through `roar:hasPerson`) is for example 'country cottage' or 'residence'. role bio:Birth bio:Death A life event from the bio vocabulary. It is recommended to include timestamp properties from the sem vocabulary. If the exact date is known, sem:hasTimeStamp can be used. If dates are uncertain, use the other properties: - sem:hasTimeStamp - sem:hasBeginTimeStamp - sem:hasEarliestBeginTimeStamp - sem:hasLatestBeginTimeStamp - sem:hasEndTimeStamp - sem:hasEarliestEndTimeStamp - sem:hasLatestEndTimeStamp To make a bio:Event compliant to a sem:Event, also define a role (next to the bio:principal or bio:partner) by defining a sem:hasRole: ```ttl _:event1 a bio:Event ; rdfs:label "Living on the Keizersgracht" bio:principal _:person1 ; sem:hasActor [ a sem:Role ; sem:roleType [ a sem:RoleType ; rdfs:label "Resident" ] ; rdf:value _:person1 ] . ``` bio:Event schema:CreativeWork schema:Person schema:Place sem:Event The Activity in which the Derivation and thereby the Reconstruction was made. Use `rdfs:comment` to specify what the Activity did. prov:Activity The Person or Organisation that was involved in the Derivation. In other words, who made the Reconstruction? prov:Agent prov:Association prov:Derivation prov:Entity Use a `rdfs:comment` to describe the goal the Agent had in the Activity. prov:Plan pnv:PersonName The source (e.g. document, act, legislation, text, picture, painting, recording, obelisk) in which some entity (e.g. Person or Location) can be observed. If the source that you are describing is not digitised or is not available as URI, you can define your own resource of class `roar:Document` and use for instance the properties defined by `schema:CreativeWork` to describe it. The `roar:onScan` property can then be used on an Observation to specify the location of the Entity in the source. Document Basic class to hold classes that can be combined with an Observation or Reconstruction class. Pre-modelled are Person and Location, but you are free to specify more types, such as Event or Organisation. Entity A Location can be any type of place where another entity can be located. Location A LocationObservation is a location that can be observed in a `roar:Document`. LocationObservation A LocationReconstruction is the result of modelling one or multiple LocationObservation(s) into a single resource. LocationReconstruction Something of a type 'Observation' is something that is mentioned or described in a 'Document' (described by roar:inDocument). Two common subclasses are PersonObservation and LocationObservation, but one can also think about EventObservation and other entities. Observation A Person is a human being that is mentioned in a Document. This can be a direct mention (e.g. 'Aaltie Jans') or indirect (e.g. 'husband of Aaltie Jans'), in which a name might not be known. Person A PersonObservation is a person that can be observed in a `roar:Document`. PersonObservation A PersonReconstruction is the result of modelling one or multiple PersonObservation(s) into a single resource. PersonReconstruction A 'Reconstruction' is a specific modelling of one or several entities of type 'Observation' into a single resource. The prov:wasDerivedFrom property is used to indicate on which Observations a Reconstruction was based. It is also possible to derrive a Reconstruction from other Reconstructions. Reconstruction