This Version : http://guava.iis.sinica.edu.tw/r4r/
Previous Version : 20140910.ttl
Latest Published: May 2015 (http://guava.iis.sinica.edu.tw/r4r)
Chinese Version : 中文/R4R: 資料再次使用關聯性的知識本體
Contributors: Guan-Shuo Mai
R4R is a light-weight ontology for representing general relationships of resource for publication and reusing. It asserts that a certain reusing context occurred and determined by its two basic relations, namely, isPackagedWith and isCitedBy. The isPackagedWith relation declares the resource is ready to be reused by incorporating License and Provenance information. The cites relation is an exceptional to isCitedBy which occurs only two related objects cite each other at the same time. Five resource objects including article, data, code, provenance and license are major class concepts to represent in this ontology.
r4r:RRObject: Any resource served as a component for publication and reusing is defined as a Reusing Related Object (RRObject). It can be a knowledge unit for research purposes, or any resource that has relations similar to the relations between article, data and code.
r4r:RRPolicy: Any mechanism designed for relating to RRObject for reusing purposes is defined as a Reusing Related Policy (RRPolicy). RRPolicy is free to be extended for more issues such as security and trust for its subclasses concepts.
r4r:Article: An object is presented mainly as textual form but not exclusively. It is not limited for representing research publications only, and may be presented in a variety of article formats such as: blog articles, encyclopedia articles (a primary division of encyclopedia content; Wikipedia entry pages), Usenet or web forum articles, even non-textual based resources like spoken articles (articles produced in the forms of video clips and audio recordings such as Vlogs/Video blogs, podcasts and audiobooks) are such cases.
r4r:Data: Data is presented in a structure form such as dataset, algorithms, models, metadata schema or ontologies. There are other forms of data, for instance, tables, figures or nanopublication. Other text based supplement materials like review, comments, and feedbacks are also included.
r4r:Code: Any collection of computer instructions is written in human-readable computer language, and served for programming and executing the Data of RRObject.
r4r:Provenance: metadata, metadata about metadata, or version information. Descriptive metadata can be represented as part of the Provenance.
r4r:License: The authorization of the use and reuse of the referred resource, as well as the document recording that authorization.
r4r:locateAt: is used to relate a machine-readable representation of the RRObject's identification, such as DOI, URI, URL, etc. It is used as the basic relation description for resource publication and reusing. A complete R4R resource representation (RRObject isPackagedWith RRPolicy) shares the same property, r4r:locateAt with RRObject.
r4r:hasTime: describes the creation time of the RRObject. It is used as the basic relation description for resource publication and reusing. A complete R4R resource representation (RRObject isPackagedWith RRPolicy) shares the same property, r4r:locateAt with RRObject.
r4r:hasProvenance: is used for relating subclass of RRObject to its provenance information when RRPolicy is not ready to use. It is used as the basic relation description for resource publication.
r4r:hasLicense: declares the use of license information for RRObject and its subclass when RRPolicy is not ready to use. It is used as the basic relation description for resource publication.
r4r:isPartOf: describes partial relationships with temporal and spatial constraints, and carries with it some characteristics such as being transitive. A isPartOf B only if A and B share the same time and location. Data can be part of data; code can be part of code or data; data like keywords or sentences can also be described as part of the Article; metadata can be part of provenance as long as two objects carry partial and transitive relations.
r4r:isPackagedWith: is used for relating RRObject and RRPolicy for accomplishing a particular component, RRPolicy. This relation is served for the reusing context.
r4r:isCitedBy: Any resource (A) is referenced by any other resource (B) when the publication time of A is before B. isCitedBy is used to describe this relation.
When it is used as the basic relation description for resource publication, r4r:isCitedBy can be used to describe relations between article, data, or code of RRObject.
When it is used for reusing context, r4r:isCitedBy relates any resource that reuses RRObject for citation, and the reusing context is enriched by the packaging of RRPolicy.
r4r:cites: Any resource (A) is referenced by any other resource (B) only when the publication time of A is equal to B. “cites” is used to describe this relation.
When it is used as the basic relation description for resource publication, r4r:cites can be used to describe relations between article, data, or code of RRObject.
When it is used for reusing context, r4r:cites relates any resource that reuses RRObject for citation, and the reusing context is enriched by the packaging of RRPolicy.
r4r:inReusingContext: this is an annotation property that assists curators to describe the dataset of Article/Data/Code as a dcat:Dataset or the provenance of r4r:Provenance as a prov:Entity when the context is for Reusing.