CopyrightOnto - Copyright Ontology
A Copyright Ontology for Content Rights Management
An ontology is a formalisation of concepts and relations within a domain. The Copyright Ontology tries to formalise the copyright domain as a way to facilitate automated (or computer-supported) copyright management through the whole content value chain, as it is shaped by copyright law. Therefore, it does not focus just on the last step, end-users permissions to consume content, like many rights languages and ontologies do.
The copyright domain is quite complex, so the Copyright Ontology attempts its conceptualisation in three steps, which allows incrementally facing this process.
First, the objective is to represent the most primitive part, the Creation Model, the different shapes creations take along their lifecycle. Second the Action Model, the available actions that move creations along their life cycle. Finally, the Rights Model, which constraints what actions are favoured or restricted based on different legal regimes:
- Creation Model - different shapes of copyright creations along their lifecycle.
- Actions Model - copyright actions moving creations along their lifecycle.
- Rights Model - legal constructs regulating what actions are favoured or restricted. Different legal systems can be represented, from generic rights frameworks geared towards worldwide harmonisation like those proposed by the World Intellectual Property Organization (WIPO) to specific rights in a particular legal regime like the U.S. Digital Performance Right in Sound Recordings
Figure 1 shows and overview of how some of the concepts in these 3 models relate.
|Figure 1. Overview of how the main concepts in the Creation, Rights and Actions Models relate|
To facilitate the adoption of the Copyright Ontology, it is built on top of the generic ontology provided by the schema.org vocabulary, one of the best-known and more widely used data vocabularies, promoted by the leading search engines (Google, Yahoo, Bing and Yandex). An RDF version of schema.org has been used, which is automatically generated from the official RDFa version using pyRdfa using: