NEPOMUK Sharing Ontology

OSCAF Recommendation 13.06.2012

Latest Version:: http://www.semanticdesktop.org/ontologies/2009/11/08/nso

This Version:: This file refers to the Revision 1.0 of NSO. Minor changes may be implemented in future revisions. With each new revision, the documentation and all serializations of the ontology will be updated. The URI identifying this version (but not the namespace) is http://www.semanticdesktop.org/ontologies/2009/11/08/nso/v1.0/

Editor:: Sebastian Trueg trueg@kde.org; Simon Scerri, DERI, scerrisimon@gmail.com


Ontology:: XML/RDFS Serialization: NSO (Data Graph Only); XML/RDFS Serialization: NSO (Metadata Graph Only); TriG Serialization: NSO (Graph Set)

Abstract

The Nepomuk Sharing Ontology defines basic classes and properties for defining permissions with respect to sharing information in a network.

Status of this document

This document arose from the work in KDE, acting upon the work done by Task-Force ontologies within the NEPOMUK project.

Ontology Visualisation

Ontology description

The Nepomuk Sharing Ontology defines basic classes and properties for defining permissions with respect to sharing information in a network.

Ontology Properties Description

Type	rdf:Property, rdfs:Resource
Domain	rdfs:Resource
Range	nco:Contact
Superproperties	--
Subproperties	--
Description	The subject resource is shared with the object contact. The resource and its subresources are transferred to the receiver. An existing sharedWithContact relation implies that updates on the resource should be transferred to the contact. The contact may ask for updates actively, then the sharing party's software should send a new copy of the shared resource to the contact. Domain should be either a nie:InformationElement or a pimo:Thing but no DataObject. This includes ncal:Event instances and other resources we find on a desktop. DataObjects are the specific binary stream where an Information Element is stored, and can't be shared because the recipient will form a new binary stream to store the data object. As there is no superclass of both nie:InformationElement and pimo:Thing, the domain is rdfs:Resource. One resource can be shared to multiple contacts, the cardinality is 0..n.

Type	rdf:Property, rdfs:Resource
Domain	rdfs:Resource
Range	nco:ContactGroup
Superproperties	--
Subproperties	--
Description	The subject resource is shared with all contacts belonging to the object contact group. The resource and its subresources are transferred to the receivers. An existing sharedWithGroup relation implies that updates on the resource should be transferred to the members belonging to the group. The contact may ask for updates actively, then the sharing party's software should send a new copy of the shared resource to the contact. Domain should be either a nie:InformationElement or a pimo:Thing but no DataObject. This includes ncal:Event instances and other resources we find on a desktop. DataObjects are the specific binary stream where an Information Element is stored, and can't be shared because the recipient will form a new binary stream to store the data object. As there is no superclass of both nie:InformationElement and pimo:Thing, the domain is rdfs:Resource. One resource can be shared to multiple contact groups, the cardinality is 0..n.