Submissions:Object with states
From Odp
(Updated the pattern description.) |
(Imported from OWL file.) |
||
Line 2: | Line 2: | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
{{Graphical representation | {{Graphical representation | ||
- | |ImageName= | + | |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 | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
Line 23: | Line 19: | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
- | |HasElement= | + | |HasElement=isStateOf |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=Object | |HasElement=Object | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
Line 47: | Line 28: | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
- | |HasElement= | + | |HasElement=StateSet |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
}} | }} | ||
+ | |||
{{Additional information header}} | {{Additional information header}} | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
{{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}} | + | |
- | + | ||
- | + | ||
- | + |
Revision as of 11:14, 30 August 2013
If you are a member of quality committee please visit the
If you are author of this proposal or you want to contribute to this pattern's review, you can: specify if this revision takes in account any of the review(s) In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal Current revision ID: 11698 |
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: | http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl (882) |
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:
Additional information
Scenarios
No scenario is added to this Content OP.
Reviews
Review article | Posted on | About revision (current is 11698) |
---|---|---|
AlessandroAdamou about Object with states | 24565127 August 2013 | 1165011,650 |
BenedictoRodriguezCastro about Object with states 2 | 24565138 August 2013 | 1166711,667 |
BenedictoRodriguezCastro about Object with states | 24565138 August 2013 | 1166711,667 |
RinkeHoekstra about Object with states | 245651712 August 2013 | 1166711,667 |
This revision (revision ID 11698) takes in account the reviews: 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
There is no Modeling issue related to this proposal.
References
Ontology including the content ontology design pattern for modelling objects with states.