(Review has been created. Annotation 'assigned' has been removed. Annotation 'waiting' has been removed.) |
|||
| Line 9: | Line 9: | ||
|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. | |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. | ||
|Domain=General | |Domain=General | ||
| − | |CompetencyQuestion=Objects in StateA must have at least one value for property property1, Objects in StateB must have at most one value for property property2, Objects in StateC must have exactly one value for property property3, | + | |CompetencyQuestion=Objects must have a unique state, Object states must belong to a single collection of non-duplicate elements (i.e. to a set), The possible states are: StateA StateB and StateC, An object can have three different states, Objects in StateA must have at least one value for property property1, Objects in StateB must have at most one value for property property2, Objects in StateC must have exactly one value for property property3, |
| − | |ContentODPDescription=The pattern contains | + | |ContentODPDescription=The pattern contains three classes, one for representing objects, another for representing object states, and a third one for representing sets of states. Besides, it contains object properties for relating objects and states (which are subproperties of those defined in the Situation pattern [http://ontologydesignpatterns.org/wiki/Submissions:Situation]) and for relating states and sets of states (reused from the CollectionEntity pattern [http://ontologydesignpatterns.org/wiki/Submissions:CollectionEntity]) and a datatype property for defining the size of a set of states (reused from the Set pattern [http://ontologydesignpatterns.org/wiki/Submissions:Set]). |
| + | |||
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. | 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. | ||
|ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl | |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl | ||
| Line 61: | Line 62: | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | [[Category:Review assigned]] | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| Line 68: | Line 78: | ||
|Event=WOP:2013 | |Event=WOP:2013 | ||
}} | }} | ||
| − | |||
| − | |||
| − | |||
| − | |||
|
Last modified date is: 2013-08-30 |
Diagram
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 11696) 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'
