EnricoDaga (Talk | contribs) m (Text replace - 'PatternAlsoKnownAs' to 'ContentODPAlsoKnownAs') |
AldoGangemi (Talk | contribs) (Imported from OWL file.) |
||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
| − | {{Include Image}} | + | {{Include Image |
| + | |ImageName= | ||
| + | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| − | | | + | |AlsoKnownAs=precedence, sequence, ordering |
| − | + | ||
| − | + | ||
|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. | ||
| − | | | + | |SubmittedBy=AldoGangemi |
| − | | | + | |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 |
| + | |CompetencyQuestion=What is before what?,What's next?,What's immediately following this? | ||
| + | |ReusableOWLBuildingBlock=http://ontologydesignpatterns.org/cp/owl/sequence.owl | ||
| + | |Name=Sequence | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 16: | Line 19: | ||
}} | }} | ||
{{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 | ||
}} | }} | ||
| − | |||
| − | |||
{{Scenarios about me}} | {{Scenarios about me}} | ||
{{Reviews about me}} | {{Reviews about me}} | ||
|
Last modified date is: 2010-02-21 |
| 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: | |
| 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: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
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
No scenario is added to this Content OP.
This revision (revision ID 7044) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
