Spec Terms

Classes

Accessibility Consideration
Conformance
Consideration
Extensibility
Functional level
Internationalization Consideration
Module
Privacy Consideration
Profile
Registration Consideration
Requirement
Security Consideration
Self-Review Questionnaire
Self-Review Questionnaire: Security and Privacy
Specification
variability

Accessibility Consideration^c back to ToC or Class ToC

IRI: urn:default:baseUri:#AccessibilityConsideration

has super-classes: Consideration^c

Conformance^c back to ToC or Class ToC

IRI: urn:default:baseUri:#Conformance

Consideration^c back to ToC or Class ToC

IRI: urn:default:baseUri:#Consideration

has sub-classes: Accessibility Consideration^c, Internationalization Consideration^c, Privacy Consideration^c, Registration Consideration^c, Security Consideration^c, Self-Review Questionnaire^c
is in range of: consideration^op

Extensibility^c back to ToC or Class ToC

IRI: urn:default:baseUri:#Extensibility

is in range of: extensibility^op

Functional level^c back to ToC or Class ToC

IRI: urn:default:baseUri:#ConformanceFunctionalLevel

is defined by: https://www.w3.org/TR/spec-variability/#subdivision-level

Functional levels — or in common usage simply levels — are used to group functionality into nested subsets, ranging from minimal or core functionality to full or complete functionally. Level 1 is the minimum or core of the technology. Level 2 includes all of level 1 plus additional functionality. This nesting continues until level n, which consists of the entire technology.

Internationalization Consideration^c back to ToC or Class ToC

IRI: urn:default:baseUri:#InternationalizationConsideration

has super-classes: Consideration^c

Module^c back to ToC or Class ToC

IRI: urn:default:baseUri:#ConformanceModule

is defined by: https://www.w3.org/TR/spec-variability/#subdivision-module

Modules are discrete divisions or functional groupings of the technology and do not necessarily fit in a simple hierarchical structure.

Privacy Consideration^c back to ToC or Class ToC

IRI: urn:default:baseUri:#PrivacyConsideration

has super-classes: Consideration^c

Profile^c back to ToC or Class ToC

IRI: urn:default:baseUri:#ConformanceProfile

is defined by: https://www.w3.org/TR/spec-variability/#subdivision-profile

A profile is a subset of the technology that supports a particular functional objective or a subset of a set of technologies defining how they are required to operate together (e.g., XHTML plus MathML plus SVG).

Registration Consideration^c back to ToC or Class ToC

IRI: urn:default:baseUri:#RegistrationConsideration

Registration considerations for collection of values or data at standards organisations, e.g., IANA, W3C.

has super-classes: Consideration^c

Requirement^c back to ToC or Class ToC

IRI: urn:default:baseUri:#Requirement

is in domain of: requirement level^op, requirement subject^op
is in range of: requirement^op, requirement reference^op

Security Consideration^c back to ToC or Class ToC

IRI: urn:default:baseUri:#SecurityConsideration

has super-classes: Consideration^c

Self-Review Questionnaire^c back to ToC or Class ToC

IRI: urn:default:baseUri:#SelfReviewQuestionnaire

has super-classes: Consideration^c
has sub-classes: Self-Review Questionnaire: Security and Privacy^c

Self-Review Questionnaire: Security and Privacy^c back to ToC or Class ToC

IRI: urn:default:baseUri:#SelfReviewQuestionnaireSecurityPrivacy

has super-classes: Self-Review Questionnaire^c

Specification^c back to ToC or Class ToC

IRI: urn:default:baseUri:#Specification

is defined by: urn:default:baseUri:#

variability^c back to ToC or Class ToC

IRI: urn:default:baseUri:#Variability

Object Properties

acknowledgements^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#acknowledgements

advisement^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#advisementLevel

has range: advisement^c

based on consensus^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#basedOnConsensus

build upon^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#buildUpon

has super-properties: defines^op

compliance with other specifications^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#complianceWithOtherSpecifications

composed of^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#composedOf

has super-properties: defines^op
has sub-properties: module^op

conformance^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#conformance

consideration^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#consideration

has range: Consideration^c

conventions^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#conventions

defines^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#defines

has sub-properties: build upon^op, composed of^op, functional level^op, profile^op

document status^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#documentStatus

error handling^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#errorHandling

example^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#example

exit criteria^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#exitCriteria

extensibility^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#extensibility

has range: Extensibility^c

functional level^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#functionalLevel

has super-properties: defines^op

implementation reports^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#implementationReports

intellectual property rights^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#intellectualPropertyRights

issue^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#issue

module^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#module

has super-properties: composed of^op

note^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#note

operative process^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#operativeProcess

profile^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#profile

has super-properties: defines^op

publication rules^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#publicationRules

requirement^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#requirement

has range: Requirement^c

requirement level^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#requirementLevel

has domain: Requirement^c

requirement reference^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#requirementReference

has domain: specification test case^c
is also defined as: annotation property

requirement subject^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#requirementSubject

has domain: Requirement^c

review process^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#reviewProcess

scope^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#scope

success criteria^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#successCriteria

suited for^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#suitedFor

terminology^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#terminology

has range: concept scheme^c

test case^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#testCase

has range: test case^c

test suite^op back to ToC or Object Property ToC

IRI: urn:default:baseUri:#testSuite

Named Individuals

a p iⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#API

belongs to: concept^c

advisement levelⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#AdvisementLevel

belongs to: concept scheme^c

c o u l d n o tⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#COULDNOT

belongs to: concept^c

canⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#can

belongs to: concept^c

cannotⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#cannot

belongs to: concept^c

classes of productsⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#ClassesOfProducts

is defined by: https://www.w3.org/TR/spec-variability/#cop

belongs to: concept scheme^c

clientⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Client

belongs to: concept^c

consumerⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Consumer

belongs to: concept^c

contentⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Content

belongs to: concept^c

content dataⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#ContentData

belongs to: concept^c

couldⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#could

belongs to: concept^c

discouragedⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#discouraged

belongs to: concept^c

encouragedⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#encouraged

belongs to: concept^c

foundation or abstractⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#FoundationOrAbstract

belongs to: concept^c

m a yⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#MAY

belongs to: concept^c

m i g h t n o tⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#MIGHTNOT

belongs to: concept^c

m u s tⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#MUST

belongs to: concept^c

m u s t n o tⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#MUSTNOT

belongs to: concept^c

mightⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#might

belongs to: concept^c

moduleⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Module

belongs to: concept^c

n o t r e c o m m e n d e dⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#NOTRECOMMENDED

belongs to: concept^c

notation syntaxⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#NotationSyntax

belongs to: concept^c

o p t i o n a lⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#OPTIONAL

belongs to: concept^c

playerⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Player

belongs to: concept^c

processorⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Processor

belongs to: concept^c

processor behaviourⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#ProcessorBehaviour

belongs to: concept^c

producer of contentⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#ProducerOfContent

belongs to: concept^c

producer of instructionsⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#ProducerOfInstructions

belongs to: concept^c

profileⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Profile

belongs to: concept^c

protocolⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Protocol

belongs to: concept^c

r e c o m m e n d e dⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#RECOMMENDED

belongs to: concept^c

r e q u i r e dⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#REQUIRED

belongs to: concept^c

requirement levelⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#RequirementLevel

is defined by: https://datatracker.ietf.org/doc/html/rfc2119; https://datatracker.ietf.org/doc/html/rfc8174; https://www.rfc-editor.org/info/bcp14

belongs to: concept scheme^c

responding agentⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#RespondingAgent

belongs to: concept^c

rules for deriving profilesⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#RulesForDerivingProfiles

belongs to: concept^c

s h a l lⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SHALL

belongs to: concept^c

s h a l l n o tⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SHALLNOT

belongs to: concept^c

s h o u l dⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SHOULD

belongs to: concept^c

s h o u l d n o tⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SHOULDNOT

belongs to: concept^c

s t r o n g l y d i s c o u r a g e dⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#STRONGLYDISCOURAGED

belongs to: concept^c

s t r o n g l y e n c o u r a g e dⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#STRONGLYENCOURAGED

belongs to: concept^c

serverⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#Server

belongs to: concept^c

set of eventsⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SetOfEvents

belongs to: concept^c

set of guidelinesⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SetOfGuidelines

belongs to: concept^c

specification categoryⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SpecificationCategory

is defined by: https://www.w3.org/TR/spec-variability/#spec-cat

belongs to: concept scheme^c

specification guidelinesⁿⁱ back to ToC or Named Individual ToC

IRI: urn:default:baseUri:#SpecificationGuidelines

belongs to: concept^c

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

Spec Terms

Table of Content

Classes

Accessibility Considerationc back to ToC or Class ToC

Conformancec back to ToC or Class ToC

Considerationc back to ToC or Class ToC

Extensibilityc back to ToC or Class ToC

Functional levelc back to ToC or Class ToC

Internationalization Considerationc back to ToC or Class ToC

Modulec back to ToC or Class ToC

Privacy Considerationc back to ToC or Class ToC

Profilec back to ToC or Class ToC

Registration Considerationc back to ToC or Class ToC

Requirementc back to ToC or Class ToC

Security Considerationc back to ToC or Class ToC

Self-Review Questionnairec back to ToC or Class ToC

Self-Review Questionnaire: Security and Privacyc back to ToC or Class ToC

Specificationc back to ToC or Class ToC

variabilityc back to ToC or Class ToC

Object Properties

acknowledgementsop back to ToC or Object Property ToC

advisementop back to ToC or Object Property ToC

based on consensusop back to ToC or Object Property ToC

build uponop back to ToC or Object Property ToC

compliance with other specificationsop back to ToC or Object Property ToC

composed ofop back to ToC or Object Property ToC

conformanceop back to ToC or Object Property ToC

considerationop back to ToC or Object Property ToC

conventionsop back to ToC or Object Property ToC

definesop back to ToC or Object Property ToC

document statusop back to ToC or Object Property ToC

error handlingop back to ToC or Object Property ToC

exampleop back to ToC or Object Property ToC

exit criteriaop back to ToC or Object Property ToC

extensibilityop back to ToC or Object Property ToC

functional levelop back to ToC or Object Property ToC

implementation reportsop back to ToC or Object Property ToC

intellectual property rightsop back to ToC or Object Property ToC

issueop back to ToC or Object Property ToC

moduleop back to ToC or Object Property ToC

noteop back to ToC or Object Property ToC

operative processop back to ToC or Object Property ToC

profileop back to ToC or Object Property ToC

publication rulesop back to ToC or Object Property ToC

requirementop back to ToC or Object Property ToC

requirement levelop back to ToC or Object Property ToC

requirement referenceop back to ToC or Object Property ToC

requirement subjectop back to ToC or Object Property ToC

review processop back to ToC or Object Property ToC

scopeop back to ToC or Object Property ToC

success criteriaop back to ToC or Object Property ToC

suited forop back to ToC or Object Property ToC

terminologyop back to ToC or Object Property ToC

test caseop back to ToC or Object Property ToC

test suiteop back to ToC or Object Property ToC

Data Properties

statementdp back to ToC or Data Property ToC

violates advicedp back to ToC or Data Property ToC