Submissions:Componency

From Odp

Jump to: navigation, search


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: 9077

Graphical representation

Diagram

Image:componency.jpg

General description

Name: componency
Submitted by: ValentinaPresutti
Also Known As: composition
Intent: To represent (non-transitively) that objects either are proper parts of other objects, or have proper

parts.

Domains:

Parts and Collections

Competency Questions:
  • What is this object component of? What are the components of this object?
Solution description: -
Reusable OWL Building Block: http://www.ontologydesignpatterns.org/cp/owl/componency.owl (1013)
Consequences: This Content OP allows designers to represent part-whole relations. It allows to distinguish between parts and proper parts. Relation of proper part is not transitive, and implies a simple part of relation, which is transitive. Temporal indexing is not expressible. To solve this issue see the time indexed part of Content OP.
Scenarios: The turbine is a proper part of the engine, both are parts of a car. Furthermore, the engine and the battery are proper parts of the car.
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The Componency Content OP locally defines the following ontology elements:

Class Object (owl:Class) Any physical, social, or mental object, or a substance. Can be component only of other objects, and can be composed of only other objects.

Object page

ObjectProperty hasComponent (owl:ObjectProperty) The hasPart relation without transitivity, holding between an Object (the system) and another (the component), and assuming a Design that structures the system Object. The componency Content OP uses the transitive reduction logical pattern to preserve transitive on the superproperty from the part of Content OP. In practice, the part of acts here as the transitive reduction of the componency Content OP.

hasComponent page

ObjectProperty isComponentOf (owl:ObjectProperty) The inverse of the hasComponent object property.

isComponentOf page

Additional information

This Content OP defines the above elements, it also includes the elements of part of Content OP.

Scenarios

Scenarios about Componency

No scenario is added to this Content OP.

Reviews

Reviews about Componency

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

Other info at evaluation tab


Modeling issues

Modeling issues about Componency

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers