You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EDTF Levels 1 and 2 introduce qualification operators (?, ~ and %) which can be used to qualify dates or parts of dates as uncertain, approximate, or both uncertain and approximate. In Level 1 these operators can only qualify entire date expressions, while in Level 2 they can qualify parts of date expressions.
This kind of qualification seems to be precisely the kind of thing that the RDF reification vocabulary was developed for. Reification means making RDF statements about RDF statements. In this case, we are creating an RDF statement describing a datetime, and then creating another RDF statement that qualifies the former statement as uncertain, approximate, or both.
Both of these classes are subclasses of edtfo:QualifiedStatement to make it possible to query for all qualified statements regardless of whether they are uncertain or approximate or both.
An advantage of this approach is that qualified datetimes result in exactly the same triples as unqualified datetimes, so they can be queried without concern for qualification. When one wants to filter out or otherwise treat qualified statements differently, the separate qualification statements can be used.
Some disadvantages of this approach are that
it is verbose, and
it requires that both the subject and the object of the qualified statement be identified (i.e. they cannot be blank / anonymous nodes).
Fortunately, the new RDF-star specification seems to address both of these issues.
If I understand correctly, the following triples describing an EDTF expression for “approximately June 2004”:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
EDTF Levels 1 and 2 introduce qualification operators (
?
,~
and%
) which can be used to qualify dates or parts of dates as uncertain, approximate, or both uncertain and approximate. In Level 1 these operators can only qualify entire date expressions, while in Level 2 they can qualify parts of date expressions.This kind of qualification seems to be precisely the kind of thing that the RDF reification vocabulary was developed for. Reification means making RDF statements about RDF statements. In this case, we are creating an RDF statement describing a datetime, and then creating another RDF statement that qualifies the former statement as uncertain, approximate, or both.
See the following cases for examples:
The draft EDTF Ontology defines two classes that can be used to type instances of
rdf:Statement
as approximate or uncertain:edtfo:ApproximateStatement
edtfo:UncertainStatement
Both of these classes are subclasses of
edtfo:QualifiedStatement
to make it possible to query for all qualified statements regardless of whether they are uncertain or approximate or both.An advantage of this approach is that qualified datetimes result in exactly the same triples as unqualified datetimes, so they can be queried without concern for qualification. When one wants to filter out or otherwise treat qualified statements differently, the separate qualification statements can be used.
Some disadvantages of this approach are that
Fortunately, the new RDF-star specification seems to address both of these issues.
If I understand correctly, the following triples describing an EDTF expression for “approximately June 2004”:
…could be more succinctly expressed using RDF-star as follows:
Beta Was this translation helpful? Give feedback.
All reactions