implements
Definition
If x 'implements' y, then x is an 'actual' entity, y is a 'specified' entity, and x is asserted to correspond to y as its concrete realization for a given period of time or in a given analytical context.
Details
Related terms
Notes
Example:
In a design study, candidate compressor models from different vendors are each asserted to implement the specified compressor C-201, to evaluate which candidates satisfy the design requirements.
The ASME pumps with serial numbers 457636 and 457711 implement (have been installed as) the P-101 pump described in the specification.
Scope note:
The 'implements' relation is central to the intended use of IDO. It allows for a record of concrete individuals corresponding to specified individuals — whether through physical installation over time, or through analytical association in a design case. Typically, a serial-numbered physical artefact is installed as the counterpart of a "specification" individual (a "tag") at one time, and later replaced with another serial-numbered physical artefact; alternatively, candidate objects may be associated with specifications for the purpose of simulation or case evaluation. The 'implements' relation carries semantic restrictions only to ensure no object is both Actual and Specified. No further constraints are given, to allow 'implements' relationships even where restrictions on the specification object are inconsistent with those on the implementing object.
Iof usage note:
'implements' records that a concrete individual (classified as 'actual') corresponds to an individual in the asset specification (classified as 'specified'). This correspondence may be physical — as when a serial-numbered artefact is installed at a tag position — or analytical, as when a candidate object is evaluated against a specification in a design simulation. Because OWL DL lacks temporal indexing, the relation is defined atemporally: it does not encode when or whether a physical installation occurred.
An asset model with 'implements' relationships supports compatibility checks for implementing objects, to uncover possible violations of requirements. This requires a transformation of the asset model, as follows: replace each 'implements'/'implementedBy' relationship with identity (owl:sameAs) and replace classifications as 'specified' or 'actual' with just 'object' for the participant individuals. Any semantic inconsistency between the specified object and the implementing object may then be discovered by OWL reasoning.
In process design, 'implements' may be used to associate a candidate object with a specification for the purpose of case analysis (e.g., simulating six design cases). In this use, the relation expresses analytical correspondence — the candidate is evaluated as-if it were the installed counterpart — without implying that physical deployment has occurred.
The mechanism for checking requirement consistency on 'implements' relationships must be implemented as a transformation that is external to the OWL ontology.
When 'implements' is used to record physical installation, the period of correspondence should be recorded using OWL annotations on the relation instance, or through a detailed representation using 'role'. This enables prescriptive objects to be matched with installed objects for selected points or periods in time.
Taxonomy
Property Operations
Used By
More info
Explanatory note
The domain and range restrictions to disjunct classes 'actual' and 'specified' prevent chains of 'implements' relationships.