Submissions:Object with states

From Odp

Jump to: navigation, search


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 11558

Graphical representation

Diagram

Image:ObjectWithStatesODP.png

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:

General

Competency Questions:
  • 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
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: http://delicias.dia.fi.upm.es/ontologies/ObjectWithStates.owl (878)
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.
hasState page
ObjectProperty 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
ObjectProperty 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
ObjectProperty 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
Class Object (owl:Class) Objects are entities that have different states and that in each state different restrictions on their properties apply.
Object page
Class 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
Class 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
Class 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
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).
State page
StateA (owl:NamedIndividual) This instance represents a certain state of an object.

This is a sample instance, when instantiating the pattern it must be renamed with a meaningful name.

StateA page
StateB (owl:NamedIndividual) This instance represents a certain state of an object.

This is a sample instance, when instantiating the pattern it must be renamed with a meaningful name.

StateB page
StateC (owl:NamedIndividual) This instance represents a certain state of an object.

This is a sample instance, when instantiating the pattern it must be renamed with a meaningful name.

StateC page

Additional information

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

Scenarios

Scenarios about Object with states

No scenario is added to this Content OP.

Reviews

Reviews about Object with states
Review article Posted on About revision (current is 11558)
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 11558) 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

Modeling issues about Object with states

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers