Diagram
Name: | Parameter |
---|---|
Submitted by: | AldoGangemi |
Also Known As: | |
Intent: | To represent parameters to be used for a certain concept. |
Domains: | |
Competency Questions: | |
Solution description: | A basic pattern to represent parameters over concepts. Implemented with simple classes and properties. |
Reusable OWL Building Block: | 1 (491) |
Consequences: | |
Scenarios: | |
Known Uses: | |
Web References: | |
Other References: | |
Examples (OWL files): | |
Extracted From: | |
Reengineered From: | |
Has Components: | |
Specialization Of: | |
Related CPs: |
The Parameter Content OP locally defines the following ontology elements:
More complex parametrization requires workarounds. E.g. AgeRangeForDrugUsage could parametrize data value: 14 to 50 on the datatype: xsd:int. Since complex datatypes are not allowed in OWL1.0, a solution to this can only work by creating two 'sub-parameters': MinimumAgeRangeForDrugUsage (that hasParameterDataValue 14) and MaximumAgeRangeForDrugUsage (that hasParameterDataValue 50), which are components of the main Parameter AgeRangeForDrugUsage.
Ordering on subparameters can be created by using or specializing the object property 'precedes'.
Once defined, a Concept can be used in other descriptions.
The classifies relation relates concepts to entities at some time
However, in order to formally represent this constraint, we need to add an anonymous type to a parameter instance, using a property that convey the semantics of the parameter, e.g.:
High rdf:type Person and (some hasHeight (Height and (oneOf isTallerThan 185) and (oneOf hasUnitOfMeasure centimeter)))
The parameter content ontology design pattern. This CP is extracted from the DOLCE Ultra Lite ontology. It represents parameters which are constraints or selections on observable values.
No scenario is added to this Content OP.
This revision (revision ID 9108) takes in account the reviews: none
Other info at evaluation tab