Policy Ontology

Living Document,

This version:
Issue Tracking:
Ieben Smessaert


The Policy ontology describes missing classes and properties to be able to define policies that needs to be executed.

1. Namespace

The Policy ontology namespace is https://w3id.org/DFDP/policy#.

The preferred prefix is pol:.

The discussed ontology’s version is 1.0.0.

2. Event

An Event (pol:Event) declares an event: something that occured on a Thing.

The Submit event (pol:Submit) is a type of event that describes the occurence of a submission.

To connect a Thing with the Event, the event property (pol:event) is used.

ex:T1 pol:event pol:Submit .

3. Policy

To associate a Thing with a Policy Execution (fno:Execution), the policy property (pol:policy) is used.

ex:HttpPolicy pol:policy [
  a fno:Execution ;
  fno:executes http:Request ;
  http:methodName "POST" ;
  http:requestURI <https://httpbin.org/post> ;
  http:headers (
      http:fieldName "Content-Type" ;
      http:fieldValue "application/ld+json"
] .

4. Redirect

A Redirect (pol:Redirect) defines a function that redirects to a specified URL on execution.

ex:RedirectPolicy pol:policy [
  a fno:Execution ;
  fno:executes pol:Redirect ;
  http:requestURI <https://example.org/>
] .


Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.


Normative References

S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119