Submissions:Description Revision as of 12:17, 4 June 2008 by Admin (Talk | contribs) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2008-06-04

General description

Name:	Description
Submitted by:	User:ValentinaPresutti
Also Known As:
Intent:	To formally represent a conceptualization or a descriptive context.
Domains:
Competency Questions:	Which are the assumptions under which a certain thing is described? Which are the concepts involved in the description of a certain thing? What is the interpretation of this case/event/observation?
Solution description:
Reusable OWL Building Block:	1 (597)
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:	http://www.loa-cnr.it/ontologies/DUL.owl
Reengineered From:
Has Components:
Specialization Of:
Related CPs:	Submissions:Submissions:Classification Submissions:Submissions:Situation Submissions:Submissions:Description and situation

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 page

Reviews

Reviews about Description

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 1999) takes in account the reviews: none

Other info at evaluation tab