Last modified date is: 2010-03-08

Graphical representation

Diagram

General description

Name:	Sequence
Submitted by:	AldoGangemi
Also Known As:
Intent:	To represent sequence schemas. It defines the notion of transitive and intransitive precedence and their inverses. It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc.
Domains:	General, Organization, Workflow, Time
Competency Questions:	What is before what? What's next? What's immediately following this?
Solution description:	This pattern is a basic one; it represents the 'path' cognitive schema, which underlies many different conceptualizations: spatial paths, time lines, event sequences, organizational hierarchies, graph paths, etc. Sequence pattern reuses the logical pattern Transitive reduction, in order to represent both transitive and non-transitive precedence relations.
Reusable OWL Building Block:	1 (659)
Consequences:	We can represent and reason over transitive or intransitive sequences of any kind. However, since coreference cannot be expressed in OWL, it is not possible to represent and reason over loops and other sequences involving coreference.
Scenarios:
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:	http://www.ontologydesignpatterns.org/ont/dul/DUL.owl
Reengineered From:
Has Components:
Specialization Of:
Related CPs:

Elements

The Sequence Content OP locally defines the following ontology elements:

directlyFollows (owl:ObjectProperty) The intransitive follows relation. For example, Wednesday directly precedes Thursday. Directness of precedence depends on the designer conceptualization.

directlyFollows page

directlyPrecedes (owl:ObjectProperty) The intransitive precedes relation. For example, Monday directly precedes Tuesday. Directness of precedence depends on the designer conceptualization.

directlyPrecedes page

follows (owl:ObjectProperty) A relation between entities, expressing a 'sequence' schema.

E.g. 'year 2000 follows 1999', 'preparing coffee' follows 'deciding what coffee to use', 'II World War follows I World War', etc.

It can be used between tasks, processes or time intervals, and subproperties would fit best in order to distinguish the different uses.

follows page

precedes (owl:ObjectProperty) A relation between entities, expressing a 'sequence' schema.

E.g. 'year 1999 precedes 2000', 'deciding what coffee to use' precedes 'preparing coffee', 'World War II follows World War I', 'in the Milan to Rome autoroute, Bologna precedes Florence', etc.

It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc.

Subproperties can be defined in order to distinguish the different uses.

precedes page

Additional information

Scenarios

Scenarios about Sequence

No scenario is added to this Content OP.

Reviews

Reviews about Sequence

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 9120) takes in account the reviews: none

Other info at evaluation tab

Modeling issues

Modeling issues about Sequence

There is no Modeling issue related to this proposal.