Reconstructions and Observations in Archival Resources

IRI:
https://w3id.org/roar
Version IRI:
https://w3id.org/roar/0.1
Current version:
0.1
Other visualisation:
Ontology source

Abstract

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.

Table of Content

  1. Classes
  2. Object Properties
  3. Data Properties
  4. Annotation Properties
  5. Namespace Declarations

Classes

bio:Birthc back to ToC or Class ToC

IRI: http://purl.org/vocab/bio/0.1/Birth

has super-classes
bio:Eventc
is in range of
bio:birthop

bio:Deathc back to ToC or Class ToC

IRI: http://purl.org/vocab/bio/0.1/Death

has super-classes
bio:Eventc
is in range of
bio:deathop

bio:Eventc back to ToC or Class ToC

IRI: http://purl.org/vocab/bio/0.1/Event

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 ] . ```
has super-classes
sem:Eventc
has sub-classes
bio:Birthc, bio:Deathc
is in range of
bio:eventop

Documentc back to ToC or Class ToC

IRI: https://w3id.org/roar#Document

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.
is in range of
documentedInop

Entityc back to ToC or Class ToC

IRI: https://w3id.org/roar#Entity

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.
has super-classes
hasLocationop some Locationc
hasPersonop some Personc
has sub-classes
Locationc, Personc
is in domain of
hasLocationop, hasPersonop, hasRelationop
is in range of
hasRelationop

Locationc back to ToC or Class ToC

IRI: https://w3id.org/roar#Location

A Location can be any type of place where another entity can be located.
has super-classes
Entityc
has sub-classes
LocationReconstructionc
is in range of
hasLocationop
is disjoint with
Personc

LocationObservationc back to ToC or Class ToC

IRI: https://w3id.org/roar#LocationObservation

A LocationObservation is a location that can be observed in a `roar:Document`.
has super-classes
Observationc

LocationReconstructionc back to ToC or Class ToC

IRI: https://w3id.org/roar#LocationReconstruction

A LocationReconstruction is the result of modelling one or multiple LocationObservation(s) into a single resource.
has super-classes
Locationc
Reconstructionc

Observationc back to ToC or Class ToC

IRI: https://w3id.org/roar#Observation

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.
has super-classes
prov:Entityc
documentedInop some Documentc
has sub-classes
LocationObservationc, PersonObservationc
is in domain of
locationInDocumentdp, onScandp
is disjoint with
Reconstructionc

Personc back to ToC or Class ToC

IRI: https://w3id.org/roar#Person

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.
has super-classes
Entityc
hasRelationop some Personc
pnv:hasNameop some pnv:PersonNamec
bio:eventop some bio:Eventc
has sub-classes
PersonReconstructionc
is in domain of
bio:birthop, bio:deathop, bio:eventop, pnv:hasNameop
is in range of
hasPersonop
is disjoint with
Locationc

PersonObservationc back to ToC or Class ToC

IRI: https://w3id.org/roar#PersonObservation

A PersonObservation is a person that can be observed in a `roar:Document`.
has super-classes
Observationc

PersonReconstructionc back to ToC or Class ToC

IRI: https://w3id.org/roar#PersonReconstruction

A PersonReconstruction is the result of modelling one or multiple PersonObservation(s) into a single resource.
has super-classes
Personc
Reconstructionc

pnv:PersonNamec back to ToC or Class ToC

IRI: https://w3id.org/pnv#PersonName

is in range of
pnv:hasNameop

prov:Activityc back to ToC or Class ToC

IRI: http://www.w3.org/ns/prov#Activity

The Activity in which the Derivation and thereby the Reconstruction was made. Use `rdfs:comment` to specify what the Activity did.
has super-classes
prov:qualifiedAssociationop some prov:Associationc
prov:wasAssociatedWithop some prov:Agentc
is in domain of
prov:qualifiedAssociationop, prov:wasAssociatedWithop
is in range of
prov:hadActivityop

prov:Agentc back to ToC or Class ToC

IRI: http://www.w3.org/ns/prov#Agent

The Person or Organisation that was involved in the Derivation. In other words, who made the Reconstruction?
is in domain of
prov:hadPlanop
is in range of
prov:agentop, prov:wasAssociatedWithop

prov:Associationc back to ToC or Class ToC

IRI: http://www.w3.org/ns/prov#Association

has super-classes
prov:hadPlanop some prov:Planc
prov:agentop some prov:Agentc
is in domain of
prov:agentop
is in range of
prov:qualifiedAssociationop

prov:Derivationc back to ToC or Class ToC

IRI: http://www.w3.org/ns/prov#Derivation

has super-classes
prov:hadActivityop some prov:Activityc
prov:entityop some Observationc
is in domain of
prov:entityop, prov:hadActivityop
is in range of
prov:qualifiedDerivationop

prov:Entityc back to ToC or Class ToC

IRI: http://www.w3.org/ns/prov#Entity

has sub-classes
Observationc, Reconstructionc
is in domain of
documentedInop
is in range of
prov:entityop, prov:wasDerivedFromop

prov:Planc back to ToC or Class ToC

IRI: http://www.w3.org/ns/prov#Plan

Use a `rdfs:comment` to describe the goal the Agent had in the Activity.
is in range of
prov:hadPlanop

Reconstructionc back to ToC or Class ToC

IRI: https://w3id.org/roar#Reconstruction

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.
has super-classes
prov:Entityc
prov:wasDerivedFromop some prov:Entityc
prov:qualifiedDerivationop some prov:Derivationc
has sub-classes
LocationReconstructionc, PersonReconstructionc
is in domain of
prov:qualifiedDerivationop, prov:wasDerivedFromop
is disjoint with
Observationc

schema:CreativeWorkc back to ToC or Class ToC

IRI: http://schema.org/CreativeWork

is equivalent to
Documentc

schema:Personc back to ToC or Class ToC

IRI: http://schema.org/Person

is equivalent to
Personc

schema:Placec back to ToC or Class ToC

IRI: http://schema.org/Place

is equivalent to
Locationc

sem:Eventc back to ToC or Class ToC

IRI: http://semanticweb.cs.vu.nl/2009/11/sem/Event

has sub-classes
bio:Eventc

Object Properties

bio:birthop back to ToC or Object Property ToC

IRI: http://purl.org/vocab/bio/0.1/birth

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 . ```
has super-properties
bio:eventop
has domain
Personc
has range
bio:Birthc

bio:deathop back to ToC or Object Property ToC

IRI: http://purl.org/vocab/bio/0.1/death

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 . ```
has super-properties
bio:eventop
has domain
Personc
has range
bio:Deathc

bio:eventop back to ToC or Object Property ToC

IRI: http://purl.org/vocab/bio/event/0.1

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.
has sub-properties
bio:birthop, bio:deathop
has domain
Personc
has range
bio:Eventc

documentedInop back to ToC or Object Property ToC

IRI: https://w3id.org/roar#documentedIn

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.
has domain
prov:Entityc
has range
Documentc

hasLocationop back to ToC or Object Property ToC

IRI: https://w3id.org/roar#hasLocation

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" ] . ```
has domain
Entityc
has range
Locationc

hasPersonop back to ToC or Object Property ToC

IRI: https://w3id.org/roar#hasPerson

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" ] . ```
has domain
Entityc
has range
Personc

hasRelationop back to ToC or Object Property ToC

IRI: https://w3id.org/roar#hasRelation

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" ] . ```
has domain
Entityc
has range
Entityc

pnv:hasNameop back to ToC or Object Property ToC

IRI: https://w3id.org/pnv#hasName

has domain
Personc
has range
pnv:PersonNamec

prov:agentop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#agent

has domain
prov:Associationc
has range
prov:Agentc

prov:entityop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#entity

has domain
prov:Derivationc
has range
prov:Entityc

prov:hadActivityop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#hadActivity

has domain
prov:Derivationc
has range
prov:Activityc

prov:hadPlanop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#hadPlan

has domain
prov:Agentc
has range
prov:Planc

prov:qualifiedAssociationop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#qualifiedAssociation

has domain
prov:Activityc
has range
prov:Associationc

prov:qualifiedDerivationop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#qualifiedDerivation

has domain
Reconstructionc
has range
prov:Derivationc

prov:wasAssociatedWithop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#wasAssociatedWith

has domain
prov:Activityc
has range
prov:Agentc

prov:wasDerivedFromop back to ToC or Object Property ToC

IRI: http://www.w3.org/ns/prov#wasDerivedFrom

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.
has domain
Reconstructionc
has range
prov:Entityc

Data Properties

locationInDocumentdp back to ToC or Data Property ToC

IRI: https://w3id.org/roar#locationInDocument

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).
has super-properties
top data property
has domain
Observationc

onScandp back to ToC or Data Property ToC

IRI: https://w3id.org/roar#onScan

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.
has super-properties
top data property
has domain
Observationc

relationTypedp back to ToC or Data Property ToC

IRI: https://w3id.org/roar#relationType

Used to specify the kind of relation (e.g. "patron") in a person to person relation as specified by `roar:hasRelation`.
has super-properties
top data property

roledp back to ToC or Data Property ToC

IRI: http://dbpedia.org/ontology/role

has equivalent properties
roledp

roledp back to ToC or Data Property ToC

IRI: https://w3id.org/roar#role

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'.
has equivalent properties
roledp
has super-properties
top data property

Annotation Properties

created byap back to ToC or Annotation Property ToC

IRI: http://purl.org/pav/createdBy

depictionap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/depiction

logoap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/logo

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/elements/1.1/title

Namespace Declarations back to ToC

default namespace
https://w3id.org/roar#
0-1
http://purl.org/vocab/bio/0.1/
dc
http://purl.org/dc/elements/1.1/
event
http://purl.org/vocab/bio/event/
foaf
http://xmlns.com/foaf/0.1/
ontology
http://dbpedia.org/ontology/
owl
http://www.w3.org/2002/07/owl#
pav
http://purl.org/pav/
pnv
https://w3id.org/pnv#
prov
http://www.w3.org/ns/prov#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
resources
https://www.leonvanwissen.nl/vocab/roar/docs/resources/
roar
https://w3id.org/roar/
schema-org
http://schema.org/
sem
http://semanticweb.cs.vu.nl/2009/11/sem/
vann
http://purl.org/vocab/vann/
w3id-org
https://w3id.org/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.