Difference between revisions of "Submissions:Object with states"

(Updated the pattern description.)
(Imported from OWL file.)
Line 2: Line 2:
 
{{Graphical representation header}}
 
{{Graphical representation header}}
 
{{Graphical representation
 
{{Graphical representation
−
|ImageName=ObjectWithStatesODP.png
+
|ImageName=
 
}}
 
}}
 
{{Content OP Proposal Template
 
{{Content OP Proposal Template
 +
|AlsoKnownAs=Object with states ontology
 +
|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.
 +
|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
 +
|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, Object states must belong to a single collection of non-duplicate elements (i.e., to a set), An object can have three different states, The possible states are: StateA, StateB and StateC
 +
|Consequences=The pattern requires modelling states as individuals instead of as literals.
 
|SubmittedBy=RaúlGarcía-Castro
 
|SubmittedBy=RaúlGarcía-Castro
 +
|ReusableOWLBuildingBlock=http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl
 
|Name=Object with states
 
|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/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
 
−
|Consequences=The pattern requires modelling states as individuals instead of as literals.
 
−
|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
 
 
}}
 
}}
 
{{Element list header}}
 
{{Element list header}}
Line 23: Line 19:
 
}}
 
}}
 
{{Has Element Template
 
{{Has Element Template
−
|HasElement=property1
+
|HasElement=isStateOf
−
}}
+
−
{{Has Element Template
+
−
|HasElement=property2
+
−
}}
+
−
{{Has Element Template
+
−
|HasElement=property3
+
 
}}
 
}}
 
{{Has Element Template
 
{{Has Element Template
 
|HasElement=Object
 
|HasElement=Object
−
}}
 
−
{{Has Element Template
 
−
|HasElement=ObjectStateA
 
−
}}
 
−
{{Has Element Template
 
−
|HasElement=ObjectStateB
 
−
}}
 
−
{{Has Element Template
 
−
|HasElement=ObjectStateC
 
 
}}
 
}}
 
{{Has Element Template
 
{{Has Element Template
Line 47: Line 28:
 
}}
 
}}
 
{{Has Element Template
 
{{Has Element Template
−
|HasElement=StateA
+
|HasElement=StateSet
−
}}
+
−
{{Has Element Template
+
−
|HasElement=StateB
+
−
}}
+
−
{{Has Element Template
+
−
|HasElement=StateC
+
 
}}
 
}}
 +
 
{{Additional information header}}
 
{{Additional information header}}
−
Ontology including the content ontology design pattern for modelling objects with states.
 
  
−
 
−
 
−
 
−
 
−
 
−
 
−
 
−
 
−
 
−
 
−
 
−
 
−
[[Category:Review assigned]]
 
 
{{Scenarios about me}}
 
{{Scenarios about me}}
−
{{Reviews about me}}
+
{{Reviews about me}}{{Modeling issues about me}}{{My references}}
−
{{Modeling issues about me}}
+
Ontology including the content ontology design pattern for modelling objects with states.[[Category:Review assigned]]
−
{{My references}}
+
−
{{Submission to event
+
−
|Event=WOP:2013
+
−
}}
+

Revision as of 11:14, 30 August 2013

Warning.gif

Warning!

This is an old revision. Go to current revision

Certified.png
This pattern has been certified.

Related submission, with evaluation history, can be found here

Working.gif Last modified date is: 2013-08-30

Graphical representation

Diagram (this article has no graphical representation)

General description

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:
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:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:



Elements

The Object with states Content OP locally defines the following ontology elements:

ObjectProperty hasState (owl:ObjectProperty) Defines the state of an object.
ArrowRight.gif hasState page
ObjectProperty isStateOf (owl:ObjectProperty) Defines the object that has an state
ArrowRight.gif isStateOf page
Class Object (owl:Class) Objects are entities that have different states and that in each state different restrictions on their properties apply.
ArrowRight.gif Object page
Class 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).
ArrowRight.gif State page
Class StateSet (owl:Class) State sets are sets of states (i.e., collections of non-duplicate states).
ArrowRight.gif StateSet page

Additional information

Scenarios

Scenarios about Object with states

No scenario is added to this Content OP.

Reviews

Reviews about Object with states
There is no review about this proposal.
Some subquery has no valid condition.

This revision (revision ID 11698) 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

Modeling issues

Modeling issues about Object with states
There is no Modeling issue related to this proposal.
Some subquery has no valid condition.

References

Add a reference


Ontology including the content ontology design pattern for modelling objects with states.

Retrieved from "http://ontologydesignpatterns.org/index.php?title=Submissions:Object_with_states&oldid=11698"
The page [[Bootstrap:Footer]] was not found.