Submissions:Description
From Odp
| If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 9087 |
Graphical representation
Diagram
General description
| Name: | Description |
|---|---|
| Submitted by: | ValentinaPresutti |
| Also Known As: | |
| Intent: | To formally represent a conceptualization or a descriptive context. |
| Domains: | |
| Competency Questions: |
|
| Solution description: | - |
| Reusable OWL Building Block: | http://www.ontologydesignpatterns.org/cp/owl/description.owl (983) |
| Consequences: | This CP allows the designer to represent both a (descriptive) context and the elements that characterize and are involved in that context. |
| Scenarios: | |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
Elements
The Description Content OP locally defines the following ontology elements:
Description (owl:Class) A description represents a conceptualization. It can be thought also as a descriptive
context that defines concepts in order to see a relational context out of a set of data or observations.
For example, a Plan is a description of some actions to be executed by agents in a certain way, with
certain parameters; a diagnosis is a description that provides an interpretation to a set of observed
entities, etc.
Description page Concept (owl:Class) A concept can be an idea, notion, role, or even a reified class, and is defined in a description.
Once defined, a concept can be used in other descriptions.
Concept page
is defined in (owl:ObjectProperty) A relation between a description and a concept, e.g. a workflow for a governmental
organization defines the role officer, or the Italian Traffic Law defines the role Vehicle. In order to be
used, a concept must be previously defined in another description. The defines object property is its inverse.
isDefinedIn page is concept used in (owl:ObjectProperty) a more generic relation holding between a description and a concept.
The uses concept object property is its inverse.
isConceptUsedIn page defines (owl:ObjectProperty) A relation between a Description and a Concept, e.g. a Workflow for a governmental Organization defines the Role 'officer', or 'the Italian Traffic Law defines the role Vehicle'. isDefinedIn is its inverse.
defines page uses concept (owl:ObjectProperty) A generic relation holding between a Description and a Concept. In order to be used, a Concept must be previously defined in another Description. This last condition cannot be encoded for object properties in OWL.
usesConcept pageAdditional information
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 9087) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
| Modeling issue | Competency question | Domains |
|---|---|---|
| Situation classification | What situations satisfy a certain description? What descriptions can be (partly) satisfied by that situation? What situations (partly) satisfying a certain description can emerge out of this dataset? |
References
