Submissions:Object with states - Revision history

2013-08-30T11:30:55Z

Updated the pattern description.

2013-08-30T11:27:32Z

Updated the pattern description.

2013-08-30T11:22:52Z

Updated the pattern description.

2013-08-30T11:22:11Z

Updated the pattern description.

2013-08-30T11:20:13Z

Updated the pattern description.

2013-08-30T11:14:23Z

Imported from OWL file.

2013-08-30T11:00:04Z

Updated the pattern description.

2013-08-30T10:59:00Z

ValentinaPresutti: Review has been created. Annotation 'assigned' has been removed. Annotation 'waiting' has been removed.

2013-08-07T21:02:00Z

Review has been created. Annotation 'assigned' has been removed. Annotation 'waiting' has been removed.

LaurentLefort: Review has been assigned.

2013-08-02T12:37:56Z

Review has been assigned.

@@ Line 36: / Line 36: @@
 {{Has Element Template
 |HasElement=StateSet
 }}
 {{Additional information header}}

@@ Line 17: / Line 17: @@
 |Scenario=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.
 |KnownUse=http://delicias.dia.fi.upm.es/ontologies/alm-istack.owl
 |SpecializationOf=Situation
 |RelatedCP=CollectionEntity, Set

@@ Line 37: / Line 37: @@
 }}
 {{Additional information header}}
-Ontology including the content ontology design pattern for modelling objects with states.[[Category:Review assigned]]
+[[Category:Review assigned]]
 {{Scenarios about me}}
 {{Reviews about me}}

@@ Line 8: / Line 8: @@
 |Name=Object with 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,
 |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 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/cp/owl/situation.owl]]) and for relating states and sets of states (reused from the CollectionEntity pattern [[http://ontologydesignpatterns.org/cp/owl/collectionentity.owl]]) and a datatype property for defining the size of a set of states (reused from the Set pattern [[http://ontologydesignpatterns.org/cp/owl/set.owl]]).
 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
 |Consequences=The pattern requires modelling states as individuals instead of as literals.
@@ Line 42: / Line 42: @@
 {{Modeling issues about me}}
 {{My references}}

@@ Line 2: / Line 2: @@
 {{Graphical representation header}}
 {{Graphical representation
-|ImageName=
+|ImageName=ObjectWithStatesODP.png
 }}
 {{Content OP Proposal Template
 |SubmittedBy=RaúlGarcía-Castro
 |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl
-|Name=Object with states
+|Consequences=The pattern requires modelling states as individuals instead of as literals.
 }}
 {{Element list header}}
@@ Line 30: / Line 36: @@
 |HasElement=StateSet
 }}
 {{Additional information header}}
+Ontology including the content ontology design pattern for modelling objects with states.[[Category:Review assigned]]
 {{Scenarios about me}}
-{{Reviews about me}}{{Modeling issues about me}}{{My references}}
+{{Reviews about me}}
-Ontology including the content ontology design pattern for modelling objects with states.[[Category:Review assigned]]
+{{Modeling issues about me}}

@@ 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.
 |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, Objects must have a unique state, The possible states are: StateA StateB and StateC
+|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 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.
+|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.
 |ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl
@@ Line 61: / Line 62: @@
 {{Scenarios about me}}
 {{Reviews about me}}
@@ Line 68: / Line 78: @@
 |Event=WOP:2013
 }}