Submissions:Sequence
From Odp
Current revision (13:49, 8 March 2010) (view source) m |
|||
| (9 intermediate revisions not shown.) | |||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
| - | {{ | + | {{Graphical representation header}} |
| + | {{Graphical representation | ||
| + | |ImageName=Sequence.png | ||
| + | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| - | |SubmittedBy= | + | |SubmittedBy=AldoGangemi |
|Name=Sequence | |Name=Sequence | ||
| - | |||
|Intent=To represent sequence schemas. It defines the notion of transitive and intransitive precedence and their inverses. | |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. | It can then be used between tasks, processes, time intervals, spatially locate objects, situations, etc. | ||
| - | |ReusableOWLBuildingBlock=http:// | + | |Domain=General, Organization, Workflow, Time, |
| - | |ExtractedFrom=http://www. | + | |CompetencyQuestion=What is before what?,What's next?,What's immediately following this? |
| + | |ContentODPDescription=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 [[Submissions:TransitiveReduction|Transitive reduction]], in order to represent both transitive and non-transitive precedence relations. | ||
| + | |ReusableOWLBuildingBlock=http://ontologydesignpatterns.org/cp/owl/sequence.owl | ||
| + | |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. | ||
| + | |ExtractedFrom=http://www.ontologydesignpatterns.org/ont/dul/DUL.owl | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 15: | Line 22: | ||
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
| - | |HasElement= | + | |HasElement=directlyPrecedes |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
| - | |HasElement= | + | |HasElement=follows |
}} | }} | ||
{{Has Element Template | {{Has Element Template | ||
|HasElement=precedes | |HasElement=precedes | ||
}} | }} | ||
| - | + | {{Additional information header}} | |
| - | |||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
Current revision
| 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: 9120 |
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: | |
| Competency Questions: |
|
| 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: | http://ontologydesignpatterns.org/cp/owl/sequence.owl (1135) |
| 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: | |
| 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 pageAdditional information
Scenarios
No scenario is added to this Content OP.
Reviews
There is no review about this proposal. This revision (revision ID 9120) takes in account the reviews: none
Other info at evaluation tab
Modeling issues
There is no Modeling issue related to this proposal.
References
