Submissions:Parameter

From Odp

Revision as of 23:13, 21 February 2010 by AldoGangemi (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 7114


General description

Name: Parameter
Submitted by: AldoGangemi
Also Known As:
Intent: To represent parameters to be used for a certain concept.
Domains:
Competency Questions:
Solution description:
Reusable OWL Building Block: http://ontologydesignpatterns.org/cp/owl/parameter.owl (862)
Consequences:
Scenarios:
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The Parameter Content OP locally defines the following ontology elements:

ObjectProperty hasParameter (owl:ObjectProperty) A Concept can have a Parameter that constrains the attributes that a classified Entity can have in a certain Situation, e.g. a 4WheelDriver Role definedIn the ItalianTrafficLaw has a MinimumAge parameter on the Amount 16.
hasParameter page
ObjectProperty isParameterFor (owl:ObjectProperty) A Concept can have a Parameter that constrains the attributes that a classified Entity can have in a certain Situation, e.g. a 4WheelDriver Role definedIn the ItalianTrafficLaw has a MinimumAge parameter on the Amount 16.
isParameterFor page
DatatypeProperty hasParameterDataValue (owl:DatatypeProperty) Parametrizes values from a datatype. For example, a Parameter AgeForDriving hasParameterDataValue 18 on datatype xsd:int, in the Italian traffic code. In this example, AgeForDriving isDefinedIn the Norm ItalianTrafficCodeAgeDriving.

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'.

hasParameterDataValue page
Class Concept (owl:Class) A concept is a SocialObject, and isDefinedIn a Description .

Once defined, a Concept can be used in other descriptions.

The classifies relation relates concepts to entities at some time

Concept page
Class Parameter (owl:Class) A Concept that classifies something having a certain value, e.g. 'High' can be said of people taller than 185 cm.

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)))

Parameter page


Scenarios

Scenarios about Parameter

No scenario is added to this Content OP.

Reviews

Reviews about Parameter

There is no review about this proposal. This revision (revision ID 7114) takes in account the reviews: none

Other info at evaluation tab

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.

Personal tools
Quality Committee
Content OP publishers