implements
An object property with identifier http://rds.posccaesar.org/ontology/lis14/rdl/implements
| Source ontology | Industrial Data Ontology |
| explanatory note | The domain and range restrictions to disjunct classes 'actual' and 'specified' prevent chains of 'implements' relationships. |
| is primitive | true |
| natural language definition | If x 'implements' y, then x is a 'specified' entity, y is an 'actual' entity, and at some time, x is the same individual as y. |
| primitive rationale | 'implements' is used to express identity relationships that may vary over time. Because OWL lacks time indices, the representation is informal. |
| usage note | The mechanism for checking requirement consistency on 'implements' relationships must be implemented as a transformation that is external to the OWL ontology. |
| An asset model with 'implements' relationships supports compatibility checks for implementing objects, to uncover possible violations of requirements. This is 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 the specified object and the implementing object may then be discovered by OWL reasoning. | |
| Periods of 'implements' relationships should be recorded using OWL annotations, to enable prescriptive objects to be matched with installed objects for selected points or periods in time. A detailed representation using 'role' is also possible. | |
| See also | implementedBy |
| Example | Pump P-101 is a tag, and ACME pumps with serial numbers 457636 and 457711 implement (have been installed as) this pump. |
| scope note | The 'implements' relation is central to the intended use of IDO. It allows for a record of different individuals being installed or otherwise serving as a specified object over time. Typically, a serial-numbered artefact is installed as a "specification" individual (a "tag") at one time, and later replaced with another serial-numbered artefact. 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 (installed) object. |
| InverseOf | implementedBy |
| Disjoint with | none |
| Domain | Actual |
| Range | Specified |