- Status: proposed
- Date: 2025-02-24
- Discussion: examples #13
Suggestion on how to add additional description components as extensions of I-ADOPT variables.
pending
This approach would require to model a variable as a child of an existing I-ADOPT Variable as demonstrated in this EnvThes example here. It is not possible to add these extensions (like statistical measures) as constraints, because these apply to the whole variable. In EnvThes we have added for now these extensions:
- https://w3id.org/env/puv#statistic for adding statistical measures
- https://w3id.org/env/puv#usesMethod for adding a method
- https://w3id.org/env/puv#uom for adding the used unit
- http://www.w3.org/ns/sosa/madeBySensor for adding the instrument
- Pros:
- easy to implement
- Cons
- not standardised which object properties should be used, but we could write guidelines
- might lead potentially to an explosion of definitions
- it is no more an I-ADOPT variable, so not clear if it can be modelled as a subconcept of an I-ADOPT variable
By using ISO 19131 - Data Product Specification (DPS), requirements for products description can be taken into account.
-
Pros:
- OMS ObservingProcedure (+ requirements) could be used to better describe the DataCaptureInformation from the DPS which intends to explain how the data needs to be captured.
- EBV products can be easily created.
-
Cons
- what are the object properties that can be used for these relationships captured in the UML?