http://purl.com/net/conflict#Recording
Recordings are tricky: in our scenario it's important to have a class' recording' because we want to capture the difference between a piece of information as recorded and as happened / lived. In the log books and service records, lots of events are recorded but often we are not sure how precise their correspondance with reality is.
This duality generates a further problem: when should we also instantiate the actual event and when not (eg being on ship, vs the event of an official recording that someone was on a ship) ?
Instances of conflict:Recording can have the following properties:
| PROPERTY | TYPE | DESCRIPTION | RANGE |
|---|---|---|---|
| From class owl:Thing | |||
| dc:creator | owl:AnnotationProperty | owl:Thing | |
| dc:description | owl:AnnotationProperty | owl:Thing | |
| dc:title | owl:AnnotationProperty | owl:Thing | |
@prefix : <http://purl.com/net/conflict#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
:Recording a owl:Class ;
rdfs:comment """Recordings are tricky: in our scenario it's important to have a class' recording' because we want to capture the difference between a piece of information as recorded and as happened / lived. In the log books and service records, lots of events are recorded but often we are not sure how precise their correspondance with reality is.
This duality generates a further problem: when should we also instantiate the actual event and when not (eg being on ship, vs the event of an official recording that someone was on a ship) ?"""^^rdf:XMLLiteral ;
rdfs:subClassOf :Event .