Characterizing CiTO properties – the CiTO Functions Ontology
[This post was modified on 20 October 2017 by David Shotton, to reflect the change in CiTO, the Citation Typing Ontology, of the name of the class cito:CitationAct to the new name cito:Citation, with a revised definition. This has required changing the text “cito:CitationAct” to “cito:Citation” in several places in this post. However, the sense of this post has not changed.]
CiTO, the Citation Typing Ontology, contains 41 object properties that can be used to characterize the nature of a bibliographic citation linking the citing paper to the citing paper, plus an equal number of their inverse properties. Some of these are also appropriate for the characterization of data citations, as described here.
These can be classified into factual properties (e.g. cito:usesDataFrom) and rhetorical properties, with the latter being sub-grouped into positive properties (e.g. cito:supports), neutral properties (e.g. cito:reviews) and negative ones (e.g. cito:critiques).
These sub-groupings are described in a new extension ontology, the CiTO Functions Ontology available from http://www.essepuntato.it/2013/03/cito-functions.
However, despite this extensive list of CiTO properties, there will be situations in which the purpose of making a citation cannot be adequately expressed using these CiTO properties. In such situations, it is now possible to use the new Open Annotation Data Model (http://www.openannotation.org/spec/core/) to define the reason for, or the nature of, the citation.
New CiTO class and properties to use with the Open Annotation Data Model
To make this straightforward, we require a mechanism that permits the citation itself to be objectified, so that it can become the object of an RDF triple defined using a URI. To facilitate this, we have added a new class to CiTO, cito:Citation, that defines and describes the citation itself:
cito:Citation
A citation is a conceptual directional link from a citing entity to a
cited entity, created by a human performative act of making a citation,
typically instantiated by the inclusion of a bibliographic reference
(biro:BibliographicReference) in the reference list of the citing entity,
or by the inclusion within the citing entity of a link, in the form of
a HTTP Uniform Resource Identifier (URI), to a resource on
the World Wide Web.
To complement this class, three new object properties have been added to CiTO:
cito:hasCitationCharacterization A property that links a cito:Citation to its characterization made by using a CiTO citation characterization property such as cito:confirms. cito:hasCitingEntity A property that relates a cito:Citation to the citing entity. cito:hasCitedEntity A property that relates a cito:Citation to the cited entity.
Adopting the same philosophy as used for the other CiTO object properties, we have avoided adding domain and range restrictions to these properties, enabling them to be used in circumstances that we do not foresee.
Reifying citation statements
This new CiTO class cito:Citation, and its accompanying new object properties cito:hasCitingEntity, cito:hasCitationCharacterization and cito:hasCitedEntity, can be employed to reify direct citation act statements made using the CiTO citation object property cito:cites or one of its sub-properties. For example, the following RDF statement:
:paperA cito:extends :paperB .
can be alternatively described as follows:
:thisCitation a cito:Citation ; cito:hasCitingEntity :paperA ; cito:hasCitationCharacterization cito:extends ; cito:hasCitedEntity :paperB .
This usage involved OWL2 punning, whereby a CiTO object property, such as the aforementioned cito:extends, is used as the object of the OWL assertion:
:thisCitation cito:hasCitationCharacterization cito:extends .
Using such OWL2 punning (described at http://www.w3.org/TR/2009/WD-owl2-new-features-20090611/#F12:_Punning), the CiTO object property is considered as a proper named individual of the class owl:Thing.
Such reification of citation acts can be very useful, since it permits one to combine these CiTO properties with other vocabularies, or to handle situations in which none of the citation characterizations available in CiTO are applicable. Such situations can be resolved by the creation of a user-defined citation characterization, for example by using the Open Annotation Data Model.
Introducing the Open Annotation Data Model
Use of the Open Annotation Data Model is well described by Robert Sanderson in his SlideShare presentation at http://www.slideshare.net/azaroth42/oai8-openanno. In this model, an annotation is described as a member of the class oa:Annotation, which has a body containing the annotation itself defined by oa:hasBody, and an annotation target (the thing to which the annotation relates) defined by oa:hasTarget, as shown in the following figure.
Using the Open Annotation Data Model to characterize citations
In our case, the target of the annotation is a member of the class cito:Citation, while the body, i.e. the textual content of the annotation itself, is described using the W3C Content Vocabulary (http://www.w3.org/TR/Content-in-RDF10/) as a member of the class cnt:ContentAsText, which the property cnt:chars relates to the text string actually providing the annotation.
As shown in the figure, an OA annotation can be further characterized by the motivation for making the annotation, defined by oa:isMotivatedBy. In our case, the appropriate motivation is oa:commenting, an instance of the class oa:Motivation.
Thus characterization of a bibliographic citation using the Open Annotation Data Model can take the following form:
:thisAnnotation a oa:Annotation; oa:motivatedBy oa:commenting ; oa:hasBody [ a cnt:ContentAsText ; cnt:chars "I'm citing that paper because it initiated this whole new field of research." ] ; oa:hasTarget [ a cito:Citation; cito:hasCitingEntity :PaperA ; cito:hasCitationEvent cito:cites ; cito:hasCitedEntity :PaperB ] .
Simple and flexible! We commend use of the Open Annotation Data Model to make such “free-hand” citation characterizations.
Do you have suggestions how to select a graph of citations when using the cito:CitationAct class?
When using “:paperA cito:cites :paperB”, you can select a graph of cited documents with a maximum distance of 3 with a property path construction in a sparql statement like
SELECT DISTINCT ?paper WHERE { ?paper cito:cites{,3}|(^cito:cites){,3} :paperA }
How can I do this when using instances of cito:CitationAct?
Dear Jan,
a possible solution to your question could be to replicate the behaviour you would like to track through the use of the following query:
SELECT DISTINCT ?paper
WHERE {
?paper (^cito:hasCitingEntity/cito:hasCitedEntity){,3} | (^cito:hasCitedEntity/cito:hasCitingEntity){,3} :paperA
}
This would be possible since
?paper1 cito:cites ?paper2
actually is equivalent to:
?paper1 ^cito:hasCitingEntity/cito:hasCitedEntity ?paper2
Does this answer your concern?
Thanks for your reply. (^cito:hasCitingEntity/cito:hasCitedEntity){,3}|… is an interesting expression I have not used before. It does the job.
I have been playing around with the CiTO ontology for some time. First I thought the new cito:CitationAct class was meant to replace the use of cito:cites as a predicate. Now I think I can use them both. cito:cites connects my publications and I create instances of cito:CitationAct to reify the cito:cites assertions.
NB. The property path in the sparql query in my first posting is not correct. To get cited and citedBy publications of publication (with max. distance of 3) you should use parentheses, like:
SELECT DISTINCT ?paper WHERE { (cito:cites|^cito:cites){,3} ?paper) }