SPEC ontology

Specification Bindingness Ontology

A classification of bindingness levels

Concept Scheme

URI
https://w3id.org/spec-ontology/bind
Creator(s)
Robert Matousek, Rik, Redmer Kronemeijer, Herman Drenth, Jos Hebing
Date
31 Januari 2024
Current version
1.2
Source
RDF (TTL)
License
Creative Commons Attribution 4.0 International

Abstract

The Specification Bindingness Ontology lists the key words used to indicate requirement levels as defined in RFC 2119. [RFC 2119]. It's part of the larger SPEC ontology. [SPEC]

Table of Contents

  1. Introduction
  2. Overview
  3. Classes
  4. Namespaces
  5. Legend
  6. References

Introduction

Several words are used to signify requirements in a specification. This ontology lists the key words used and how they should be interpreted. These include:

Overview

Figure 1: Ontology overview - diagram

Classes ↑

maycl

should, recommended (en), zou moeten, aanbevolen (nl)

URI https://w3id.org/spec-ontology/bind/May
Definition The item is truly optional.

Dit onderdeel is daadwerkelijk optioneel.
Parent class bindingnesscl

mustcl

must, required, shall (en), moet, vereist (nl)

URI https://w3id.org/spec-ontology/bind/Must
Definition An absolute requirement of the specification.

Een absolute vereiste van de specificatie.
Parent class bindingnesscl

must notcl

must not, shall not (en), mag niet, verboden (nl)

URI https://w3id.org/spec-ontology/bind/MustNot
Definition An absolute prohibition of the specification.

Een absoluut verbod van de specificatie.
Parent class bindingnesscl

shouldcl

should, recommended (en), zou moeten, aanbevolen (nl)

URI https://w3id.org/spec-ontology/bind/Should
Definition Valid reasons may exist in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

Geven een sterke wens aan, tenzij er een valide reden is om in een specifiek geval af te wijken. De implicaties daarvan moeten zorgvuldig gewogen zijn voordat er afgeweken wordt.
Parent class bindingnesscl

should notcl

should not, not recommended (en), zou niet moeten (nl)

URI https://w3id.org/spec-ontology/bind/ShouldNot
Definition Valid reasons may exist in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed.

Geven een ongewenste omstandigheid, waarvan volledige implicaties daarvan zorgvuldig gewogen moeten zijn voordat het in een specifiek geval toegestaan is.
Parent class bindingnesscl

Namespaces ↑

spec
http://purl.org/nen/spec
spec-bind
https://w3id.org/spec-ontology/bind
spec-cat
https://w3id.org/spec-ontology/cat
https://w3id.org/spec-ontology/doco
c4o
http://purl.org/spar/c4o/
doco
http://purl.org/spar/doco/
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#

Legend

cClasses
opObject Properties
fpFunctional Properties
dpData Properties
dpAnnotation Properties
pProperties
niNamed Individuals

References

[SPEC]
Matousek, R., et. al. The Specifications Ontology. 2023, URL: https://docs.crow.nl/spec-ontology/
[RFC 2119]
Bradner, S., Key words for use in RFCs to Indicate Requirement Levels. BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.