Agreements ontology

IRI:
http://promsns.org/def/agr
Version IRI:
http://promsns.org/def/agr/1.3
Current version:
1.3
Authors:
http://orcid.org/0000-0002-8742-7730
Imported Ontologies:
http://www.w3.org/ns/org
http://www.w3.org/ns/prov-o#
Other formats:
Ontology source in RDF (turtle)
Further documentation & examples:
This ontology on GitHub

Abstract

This Agreements Ontology is designed to model 'agreements' which are social contracts that include licenses, laws, contracts, Memoranda of Understanding, standards and definitional metadata. Agreements' purposes are to effect the behaviour of Agents that use Entities or undertake Activities. This ontology defines those effects as further actions (Requirment Resolutions) that satisfy stated Requirements articulated within the Agreement. The Requirement Resolutions can compelled to be performed with one of a number of different Imperatives such as MUST, SHOULD etc. This ontology's purpose is to support data sharing by making explicit the relationships between agreements and data, agreements and actions and agreements and Agents (people and organisations). Eventually it will also help with the interplay between different classes of agreements.

Table of Content

  1. Classes
  2. Object Properties
  3. Named Individuals
  4. Annotation Properties
  5. Namespace Declarations
Image of all Agreements ontology classes and properties

Figure 1: All the Agreements ontology classes and their properties

Classes

Agreementc back to ToC or Class ToC

IRI: http://promsns.org/def/agr#Agreement

A collection of Requirements.
has super-classes
collection
has sub-classes
Licensec
is in range of
had agreementop, requirement of, scope ofop, within scopeop

Imperativec back to ToC or Class ToC

IRI: http://promsns.org/def/agr#Imperative

An Imperative is the force with which a Requirement compels an Agents within the scope of an Agreement containing that Requirment to take action expressed in a RequirementResolution.
has super-classes
plan
is in range of
had imperativeop

Licensec back to ToC or Class ToC

IRI: http://promsns.org/def/agr#License

A specialised Agreement pertaining to licensing. This subclass introduces no restrictions to Agreement but is defined in this ontology due to the common expected use of Agreements for licenses. Its inclusion also indicated how (by subclassing) laws, MoUs and other specialised Agreements should be made.
has super-classes
Agreementc

Requirementc back to ToC or Class ToC

IRI: http://promsns.org/def/agr#Requirement

An action that may be requested of an agent requiring demonstrable fullfillment via a RequirmentResolution action with an imperative given by a RequirementLevel. The RequirmentResolution is thus conducted in accordance with the instructions implicit or explicit in the Requirement. A Requrement is a specialised version of both a Creative Commons Requirement (a cc:Requirement is "an action that may or may not be requested of you") and a prov:Plan ("A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals").
has super-classes
plan
requirementc
had imperativeop exactly 1 Imperativec
was member ofop some Agreementc
is in range of
requires, satisfiesop

Requirement Resolutionc back to ToC or Class ToC

IRI: http://promsns.org/def/agr#RequirementResolution

An action (a prov:Activity) that resolves one or more Requirements. Since a Requirement is a subclass of prov:Plan, a Requirement Resolution is then a prov:Activity which is conducted according to the Plan.
has super-classes
activity
satisfiesop some Requirementc
is in domain of
satisfiesop

Object Properties

had agreementop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#hadAgreement

Anything (an endurant thing like a Dataset or a Car) or a perdurant thing (like a course of action or a process) can have a related Agreement that affects Agents related to the production, use or agency related to the thing. The way Agreements affect Agents is through the articulation of Requirements - required actions - which exist with varying imperatives.
has super-properties
was influenced by
has range
Agreementc

had imperativeop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#hadImperative

Something (permissive domain for this property) had an imperative according to a particular Imperative. e.g. Requirement X: "Undertake Action Y" hadImperative agr:MUST This indicates the Requirment MUST be stafisfied by the undertaking of Action Y. The Imperative individuals are sources from RFC2119 (https://www.ietf.org/rfc/rfc2119.txt).
has super-properties
had plan
has range
Imperativec

had scopeop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#hadScope

has super-properties
was influenced by
is inverse of
scope ofop

satisfied byop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#satisfiedBy

satisfied by
has super-properties
was influenced by
is inverse of
satisfiesop

satisfiesop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#satisfies

A Requirement Resolution may satisfy Requirement(s)
has super-properties
was influenced by
has domain
Requirement Resolutionc
has range
Requirementc
is inverse of
satisfied byop

scope ofop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#scopeOf

An Agent is within the scopeOf an Agreement if that Agent, or members of it if it is a collection Agent such as a Group or Organisation, are bound by that Agreement's requirements within a certain Agreement use scenario.
has super-properties
was influenced by
has range
Agreementc
is inverse of
had scopeop

was member ofop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#wasMemberOf

has super-properties
was influenced by
is inverse of
had member

within scopeop back to ToC or Object Property ToC

IRI: http://promsns.org/def/agr#withinScopeOf

inverse of hasWithinScope
has super-properties
was influenced by
has range
Agreementc

Named Individuals

MAYni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#MAY

belongs to
requirement levelc

MUSTni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#MUST

belongs to
requirement levelc

MUST NOTni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#MUST_NOT

belongs to
requirement levelc

Nicholas Carni back to ToC or Named Individual ToC

IRI: https://orcid.org/0000-0002-8742-7730

Contact Nicholas on nicholas.car@csiro.au
belongs to
agentc

OPTIONALni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#OPTIONAL

belongs to
requirement levelc

REQUIREDni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#REQUIRED

belongs to
requirement levelc

SHALLni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#SHALL

belongs to
requirement levelc

SHALL NOTni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#SHALL_NOT

belongs to
requirement levelc

SHOULDni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#SHOULD

belongs to
requirement levelc

SHOULD NOTni back to ToC or Named Individual ToC

IRI: http://promsns.org/def/agr#SHOULD_NOT

belongs to
requirement levelc

Annotation Properties

has partap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/hasPart

has sub-properties
requiresap

is part ofap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/isPartOf

has sub-properties
requirement ofap

requirement ofap back to ToC or Annotation Property ToC

IRI: http://promsns.org/def/agr#requirementOf

has super-properties
is part ofap
has range
Agreementc

requiresap back to ToC or Annotation Property ToC

IRI: http://promsns.org/def/agr#requires

has super-properties
has partap
has range
Requirementc

sourceap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/source

Namespace Declarations back to ToC

default namespace
http://promsns.org/def/agr#
dc
http://purl.org/dc/elements/1.1/
owl
http://www.w3.org/2002/07/owl#
prov
http://www.w3.org/ns/prov#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
dct
http://purl.org/dc/terms/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.