| (3 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
|Name=EventCore | |Name=EventCore | ||
|Intent=The purpose of this pattern is to provide a minimalistic model of event where it is not always possible to separate its spatial and the temporal aspects, thus can model events that move or possess discontinuous temporal extent. Events according to this model has at least one participant, attached via a participant-role, and may have additional descriptive information through its information object. | |Intent=The purpose of this pattern is to provide a minimalistic model of event where it is not always possible to separate its spatial and the temporal aspects, thus can model events that move or possess discontinuous temporal extent. Events according to this model has at least one participant, attached via a participant-role, and may have additional descriptive information through its information object. | ||
| + | |Domain=General, Event Processing, | ||
|CompetencyQuestion=Where and when did the 1990 World Chess Championship Match take place?, | |CompetencyQuestion=Where and when did the 1990 World Chess Championship Match take place?, | ||
Who were involved in the 1990 World Chess Championship Match? | Who were involved in the 1990 World Chess Championship Match? | ||
| Line 14: | Line 15: | ||
|Consequences=This pattern can model moving events and events with discontinuous temporal extents, provided an appropriate spatiotemporal extent model is used. This pattern, however, does not facilitate modeling complex relationships between events, such as causality, provenance, or correlation | |Consequences=This pattern can model moving events and events with discontinuous temporal extents, provided an appropriate spatiotemporal extent model is used. This pattern, however, does not facilitate modeling complex relationships between events, such as causality, provenance, or correlation | ||
|Scenario=The 1990 World Chess Championship Match takes place in New York from October 8 to November 7, 1990, and in Lyons, France, from November 26 to December 30, 1990. | |Scenario=The 1990 World Chess Championship Match takes place in New York from October 8 to November 7, 1990, and in Lyons, France, from November 26 to December 30, 1990. | ||
| − | |RelatedCP=SpatioTemporalExtent, ParticipantRole, AgentRole, Objectrole, Information realization | + | |RelatedCP=SpatioTemporalExtent, ParticipantRole, AgentRole, Objectrole, Information realization, InformationObjectsAndRepresentationLanguages, InformationObject, EventProcessing, |
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 59: | Line 60: | ||
{{Modeling issues about me}} | {{Modeling issues about me}} | ||
{{My references}} | {{My references}} | ||
| + | {{Submission to event | ||
| + | |Event=WOP:2016 | ||
| + | }} | ||
|
Last modified date is: 2016-07-17 |
Diagram
| Name: | EventCore |
|---|---|
| Submitted by: | AdilaKrisnadhi |
| Also Known As: | |
| Intent: | The purpose of this pattern is to provide a minimalistic model of event where it is not always possible to separate its spatial and the temporal aspects, thus can model events that move or possess discontinuous temporal extent. Events according to this model has at least one participant, attached via a participant-role, and may have additional descriptive information through its information object. |
| Domains: | |
| Competency Questions: | |
| Solution description: | See Adila Krisnadhi; Pascal Hitzler : A Core Pattern for Events. Under review at WOP 2016 |
| Reusable OWL Building Block: | 1 (467) |
| Consequences: | This pattern can model moving events and events with discontinuous temporal extents, provided an appropriate spatiotemporal extent model is used. This pattern, however, does not facilitate modeling complex relationships between events, such as causality, provenance, or correlation |
| Scenarios: | The 1990 World Chess Championship Match takes place in New York from October 8 to November 7, 1990, and in Lyons, France, from November 26 to December 30, 1990. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The EventCore Content OP locally defines the following ontology elements:
DASE_RULE page
freshProp1 (owl:ObjectProperty) This property is artificially generated in order to express the following rule in OWL: :Event(?x) ^ :providesParticipantRole(?x,?p) ^ :subEventOf(?x,?y) -> :providesParticipantRole(?y,?p).
The rule is translated into two axioms:
1. :Event SubClassOf: :freshProp1 some Self
2. inverse (:subEventOf) o :freshProp1 o :providesParticipantRole SubPropertyOf: : :providesParticipantRole
freshProp1 page freshProp2 (owl:ObjectProperty) This property is artificially generated in order to express the following rule in OWL: :Event(?x) ^ :hasSpatioTemporalExtent(?x,?w) ^ :subEventOf(?x,?y) ^ :Event(?y) ^ :hasSpatioTemporalExtent(?y,?z) -> :subSpatioTemporalExtentOf(?w,?z).
The rule is translated into two axioms:
1. :Event SubClassOf: :freshProp2 some Self
2. inverse (:hasSpatioTemporalExtent) o :freshProp2 o :subEventOf o :freshProp2 o :hasSpatioTemporalExtent SubPropertyOf: :subSpatioTemporalExtentOf
freshProp2 page hasInformationObject (owl:ObjectProperty) Property relating Event to InformationObject in this pattern. The domain of this property is not restricted to Event since it is possible that non-event to have an information object. The range is always InformationObject since it makes no sense to have a property named hasInformationObject to point to anything other than information object.
hasInformationObject page hasSpatioTemporalExtent (owl:ObjectProperty) Property relating Event to SpatioTemporalExtent in this pattern. The range is always SpatioTemporalExtent (globally) since it makes no sense to have a property named hasSpatioTemporalExtent to point to anything other than spatiotemporal extent. Tthe domain is not set to Event as non-Event may also have spatiotemporal extent.
hasSpatioTemporalExtent page providesParticipantRole (owl:ObjectProperty) Property relating Event to ParticipantRole in this pattern. The range is always ParticipantRole since it makes no sense to have a property named as providesParticipantRole not to point to a participant role. The domain is not set to Event as non-Event may also provide a participant role.
providesParticipantRole page subEventOf (owl:ObjectProperty) Property expressing partonomic relation between two events. Domain and range are always Event.
subEventOf page subSpatioTemporalExtentOf (owl:ObjectProperty) Property indicating partonomic relation between two spatiotemporal extents. The Event pattern only assumes that this is given by the spatiotemporal extent pattern actually used. Thus, domain and range are not explicitly stated and this property is included in axioms resulted by OWL translation of the following rule: :Event(?x) ^ :hasSpatioTemporalExtent(?x,?w) ^ :subEventOf(?x,?y) ^ :Event(?y) ^ :hasSpatioTemporalExtent(?y,?z) -> :subSpatioTemporalExtentOf(?w,?z)
subSpatioTemporalExtentOf page
Event (owl:Class) Represents any kind of events. An event possesses a spatiotemporal extent, provides at least one participant-role, which is performed by some entity (agents or otherwise), and may be a sub-event of another event. An event may also have additional descriptive information, which is consolidated through an information object.
Event page InformationObject (owl:Class) An entity that encapsulates all descriptive or non-defining information of the corresponding event, e.g., names, additional identifiers, textual descriptions, etc. Should normally be aligned to a separate Information Object pattern.
InformationObject page ParticipantRole (owl:Class) Every ParticipantRole represents a reified relationship between an event and one of its participants. Should normally be aligend to a separate Participant-Role pattern.
ParticipantRole page SpatioTemporalExtent (owl:Class) Hook to a complex notion representing a unified spatial and temporal extent. Intended to cover non-static or discontinuous spatiotemporal extent. Should be aligned to a separate Spatiotemporal Extent pattern.
SpatioTemporalExtent pageNo scenario is added to this Content OP.
This revision (revision ID 12751) takes in account the reviews: none
Other info at evaluation tab
|
Submission to event |
|---|
'Ontology Design Patterns'
