Submissions:Object with states Revision as of 11:14, 30 August 2013 by {{| (Talk | contribs)}} (Imported from OWL file.) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

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:	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
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:

hasState (owl:ObjectProperty) Defines the state of an object.

hasState page

isStateOf (owl:ObjectProperty) Defines the object that has an state

isStateOf page

Object (owl:Class) Objects are entities that have different states and that in each state different restrictions on their properties apply.

Object 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 page

StateSet (owl:Class) State sets are sets of states (i.e., collections of non-duplicate states).

StateSet page

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.