m (Review has been assigned.) |
m (Review has been assigned.) |
||
| Line 68: | Line 68: | ||
|Event=WOP:2013 | |Event=WOP:2013 | ||
}} | }} | ||
| + | [[Category:Review assigned]] | ||
[[Category:Review assigned]] | [[Category:Review assigned]] | ||
[[Category:Review assigned]] | [[Category:Review assigned]] | ||
[[Category:Review assigned]] | [[Category:Review assigned]] | ||
|
Last modified date is: 2013-08-02 |
Diagram
| Name: | Object with states |
|---|---|
| Submitted by: | RaúlGarcía-Castro |
| Also Known As: | |
| Intent: | An object can have different states for which different restrictions apply. The goal of the pattern is to allow modelling the different states of an object and the restrictions on such object for its different states. |
| Domains: | |
| Competency Questions: | |
| Solution description: | The pattern contains two classes, one for representing objects and another for representing object states, and one object property for stating that an object has a certain state.
For applying the pattern, first all the possible states of the object must be created as instances of the state class using the Value Partition pattern (http://www.w3.org/TR/swbp-specified-values/). Then, different classes must be defined to represent the object in each of the states and state-specific restrictions must be applied to those classes; the object class must be defined as a disjoint union of these classes. |
| Reusable OWL Building Block: | 1 (491) |
| Consequences: | The pattern requires modelling states as individuals instead of as literals. |
| Scenarios: | A sample scenario is the following. A software defect created in an issue tracker must have a creator and be associated to a certain software product. Once it is checked that the defect is reproducible, it must be assigned to some developer and have a certain priority. However, before checking the defect reproducilibty the defect must not have either asignee or priority. |
| Known Uses: | http://delicias.dia.fi.upm.es/ontologies/alm-istack.owl |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The Object with states Content OP locally defines the following ontology elements:
property1 (owl:ObjectProperty) This property can be used to describe an object.
This is a sample property, when instantiating the pattern it must be renamed with a meaningful name.
property1 page property2 (owl:ObjectProperty) This property can be used to describe an object.
This is a sample property, when instantiating the pattern it must be renamed with a meaningful name.
property2 page property3 (owl:ObjectProperty) This property can be used to describe an object.
This is a sample property, when instantiating the pattern it must be renamed with a meaningful name.
property3 page
Object (owl:Class) Objects are entities that have different states and that in each state different restrictions on their properties apply.
Object page ObjectStateA (owl:Class) This class represents those objects that are in certain state.
This is a sample class, when instantiating the pattern it must be renamed with a meaningful name.
ObjectStateA page ObjectStateB (owl:Class) This class represents those objects that are in certain state.
This is a sample class, when instantiating the pattern it must be renamed with a meaningful name.
ObjectStateB page ObjectStateC (owl:Class) This class represents those objects that are in certain state.
This is a sample class, when instantiating the pattern it must be renamed with a meaningful name.
ObjectStateC page State (owl:Class) States are the different states that an object can have. States must belong to a single collection of non-duplicate elements (i.e., to a set).
State pageThis is a sample instance, when instantiating the pattern it must be renamed with a meaningful name.
StateA pageThis is a sample instance, when instantiating the pattern it must be renamed with a meaningful name.
StateB pageThis is a sample instance, when instantiating the pattern it must be renamed with a meaningful name.
StateC pageOntology including the content ontology design pattern for modelling objects with states.
No scenario is added to this Content OP.
This revision (revision ID 11650) takes in account the reviews: Object with states (AlessandroAdamou about Object with states, RinkeHoekstra about Object with states, BenedictoRodriguezCastro about Object with states, BenedictoRodriguezCastro about Object with states 2)
Other info at evaluation tab
|
Submission to event |
|---|
'Ontology Design Patterns'
