14
12
@prefix nie: <http://www.semanticdesktop.org/ontologies/2007/01/19/nie#>.
15
13
@prefix zg: <http://www.zeitgeist-project.com/ontologies/2010/01/27/zg#>.
21
zg:EventInterpretation
23
rdfs:comment "Base class for event interpretations. Please do no instantiate directly, but use one of the sub classes. The interpretation of an event describes 'what happened' - fx. 'something was created' or 'something was accessed'" ;
24
rdfs:subClassOf nie:InformationElement .
28
rdfs:comment "Event type triggered when an item is created" ;
29
rdfs:subClassOf zg:EventInterpretation .
33
rdfs:comment "Event triggered by opening, accessing, or starting a resource. Most zg:AccessEvents will have an accompanying zg:LeaveEvent, but this need not always be the case" ;
34
rdfs:subClassOf zg:EventInterpretation .
38
rdfs:comment "Event triggered by closing, leaving, or stopping a resource. Most zg:LeaveEvents will be following a zg:Access event, but this need not always be the case" ;
39
rdfs:subClassOf zg:EventInterpretation .
43
rdfs:comment "Event triggered by modifying an existing resources. Fx. when editing and saving a file on disk or correcting a typo in the name of a contact" ;
44
rdfs:subClassOf zg:EventInterpretation .
48
rdfs:comment "Event triggered because a resource has been deleted or otherwise made permanently unavailable. Fx. when deleting a file. FIXME: How about when moving to trash?" ;
49
rdfs:subClassOf zg:EventInterpretation .
53
rdfs:comment "Event triggered when something is received from an external party. The event manifestation must be set according to the world view of the receiving party. Most often the item that is being received will be some sort of message - an email, instant message, or broadcasted media such as micro blogging" ;
54
rdfs:subClassOf zg:EventInterpretation .
58
rdfs:comment "Event triggered when something is send to an external party. The event manifestation must be set according to the world view of the sending party. Most often the item that is being send will be some sort of message - an email, instant message, or broadcasted media such as micro blogging" ;
59
rdfs:subClassOf zg:EventInterpretation .
63
rdfs:comment "Event triggered when the user accepts a request of some sort. Examples could be answering a phone call, accepting a file transfer, or accepting a friendship request over an IM protocol. See also DenyEvent for when the user denies a similar request" ;
64
rdfs:subClassOf zg:EventInterpretation .
68
rdfs:comment "Event triggered when the user denies a request of some sort. Examples could be rejecting a phone call, rejecting a file transfer, or denying a friendship request over an IM protocol. See also AcceptEvent for the converse event type" ;
69
rdfs:subClassOf zg:EventInterpretation .
73
rdfs:comment "Event triggered when something expires or times out. These types of events are normally not triggered by the user, but by the operating system or some external party. Examples are a recurring calendar item or task deadline that expires or a when the user fails to respond to an external request such as a phone call" ;
74
rdfs:subClassOf zg:EventInterpretation .
78
rdfs:comment "Event triggered when a resource has been moved from a location to another. Fx. moving a file from a folder to another.";
79
rdfs:subClassOf zg:EventInterpretation.
17
zg:EventInterpretation
19
rdfs:comment "Base class for event interpretations. Please do no instantiate directly, but use one of the sub classes. The interpretation of an event describes 'what happened' - fx. 'something was created' or 'something was accessed'" ;
20
rdfs:subClassOf nie:InformationElement .
24
rdfs:comment "Event type triggered when an item is created" ;
25
rdfs:subClassOf zg:EventInterpretation .
29
rdfs:comment "Event triggered by opening, accessing, or starting a resource. Most zg:AccessEvents will have an accompanying zg:LeaveEvent, but this need not always be the case" ;
30
rdfs:subClassOf zg:EventInterpretation .
34
rdfs:comment "Event triggered by closing, leaving, or stopping a resource. Most zg:LeaveEvents will be following a zg:Access event, but this need not always be the case" ;
35
rdfs:subClassOf zg:EventInterpretation .
39
rdfs:comment "Event triggered by modifying an existing resources. Fx. when editing and saving a file on disk or correcting a typo in the name of a contact" ;
40
rdfs:subClassOf zg:EventInterpretation .
44
rdfs:comment "Event triggered because a resource has been deleted or otherwise made permanently unavailable. Fx. when deleting a file. FIXME: How about when moving to trash?" ;
45
rdfs:subClassOf zg:EventInterpretation .
49
rdfs:comment "Event triggered when something is received from an external party. The event manifestation must be set according to the world view of the receiving party. Most often the item that is being received will be some sort of message - an email, instant message, or broadcasted media such as micro blogging" ;
50
rdfs:subClassOf zg:EventInterpretation .
54
rdfs:comment "Event triggered when something is send to an external party. The event manifestation must be set according to the world view of the sending party. Most often the item that is being send will be some sort of message - an email, instant message, or broadcasted media such as micro blogging" ;
55
rdfs:subClassOf zg:EventInterpretation .
59
rdfs:comment "Event triggered when the user accepts a request of some sort. Examples could be answering a phone call, accepting a file transfer, or accepting a friendship request over an IM protocol. See also DenyEvent for when the user denies a similar request" ;
60
rdfs:subClassOf zg:EventInterpretation .
64
rdfs:comment "Event triggered when the user denies a request of some sort. Examples could be rejecting a phone call, rejecting a file transfer, or denying a friendship request over an IM protocol. See also AcceptEvent for the converse event type" ;
65
rdfs:subClassOf zg:EventInterpretation .
69
rdfs:comment "Event triggered when something expires or times out. These types of events are normally not triggered by the user, but by the operating system or some external party. Examples are a recurring calendar item or task deadline that expires or a when the user fails to respond to an external request such as a phone call" ;
70
rdfs:subClassOf zg:EventInterpretation .
74
rdfs:comment "Event triggered when a resource has been moved from a location to another. Fx. moving a file from a folder to another.";
75
rdfs:subClassOf zg:EventInterpretation.
86
rdfs:comment "Base class for event manifestation types. Please do no instantiate directly, but use one of the sub classes. The manifestation of an event describes 'how it happened'. Fx. 'the user did this' or 'the system notified the user'" ;
87
rdfs:subClassOf nie:DataObject .
91
rdfs:comment "An event that was actively performed by the user. For example saving or opening a file by clicking on it in the file manager" ;
92
rdfs:subClassOf zg:EventManifestation .
96
rdfs:comment "An event that is caused indirectly from user activity or deducted via analysis of other events. Fx. if an algorithm divides a user workflow into disjoint 'projects' based on temporal analysis it could insert heuristic events when the user changed project" ;
97
rdfs:subClassOf zg:EventManifestation .
101
rdfs:comment "An event that was directly triggered by some user initiated sequence of actions. For example a music player automatically changing to the next song in a playlist" ;
102
rdfs:subClassOf zg:EventManifestation .
106
rdfs:comment "An event that was performed by an entity, usually human or organization, other than the user. An example could be logging the activities of other people in a team" ;
107
rdfs:subClassOf zg:EventManifestation .
109
zg:SystemNotification
111
rdfs:comment "An event send to the user by the operating system. Examples could include when the user inserts a USB stick or when the system warns that the hard disk is full" ;
112
rdfs:subClassOf zg:EventManifestation .
82
rdfs:comment "Base class for event manifestation types. Please do no instantiate directly, but use one of the sub classes. The manifestation of an event describes 'how it happened'. Fx. 'the user did this' or 'the system notified the user'" ;
83
rdfs:subClassOf nie:DataObject .
87
rdfs:comment "An event that was actively performed by the user. For example saving or opening a file by clicking on it in the file manager" ;
88
rdfs:subClassOf zg:EventManifestation .
92
rdfs:comment "An event that is caused indirectly from user activity or deducted via analysis of other events. Fx. if an algorithm divides a user workflow into disjoint 'projects' based on temporal analysis it could insert heuristic events when the user changed project" ;
93
rdfs:subClassOf zg:EventManifestation .
97
rdfs:comment "An event that was directly triggered by some user initiated sequence of actions. For example a music player automatically changing to the next song in a playlist" ;
98
rdfs:subClassOf zg:EventManifestation .
102
rdfs:comment "An event that was performed by an entity, usually human or organization, other than the user. An example could be logging the activities of other people in a team" ;
103
rdfs:subClassOf zg:EventManifestation .
105
zg:SystemNotification
107
rdfs:comment "An event send to the user by the operating system. Examples could include when the user inserts a USB stick or when the system warns that the hard disk is full" ;
108
rdfs:subClassOf zg:EventManifestation .
114
110
# event datastructure
118
rdfs:comment "Something that happened at a point in time. Events are categorized by two primary factors 'what happened' - called the interpretation and 'how did it happen' - called the manifestation. Aside from a timestamp, events can also carry a reference to the entity responsible for instantiating it - called the actor. Normally the event actor is an application, but it need not be. Events happen to zero or more subjects. The subjects are described using the Nepomuk ontologies." ;
119
rdfs:subClassOf rdfs:Resource .
123
rdfs:comment "A unique integer id assigned to an event by the logging framework when the event is first logged" ;
124
rdfs:domain zg:Event ;
125
rdfs:range xsd:nonNegativeInteger ;
127
nrl:maxCardinality "1"^^xsd:nonNegativeInteger .
131
rdfs:comment "Timestamp in milliseconds since the Unix Epoch" ;
132
rdfs:domain zg:Event ;
133
rdfs:range xsd:long ;
134
rdfs:label "timestamp" ;
135
nrl:maxCardinality "1"^^xsd:nonNegativeInteger .
139
rdfs:comment "The application or entity responsible for emitting the event. For applications the format of this field is the base filename of the corresponding .desktop file with an app:// URI scheme. For example /usr/share/applications/firefox.desktop is encoded as app://firefox.desktop" ;
140
rdfs:domain zg:Event ;
141
rdfs:range rdfs:Resource ;
143
nrl:maxCardinality "1"^^xsd:nonNegativeInteger .
145
zg:hasEventInterpretation
147
rdfs:domain zg:Event ;
148
rdfs:range zg:EventInterpretation ;
149
nrl:maxCardinality "1"^^xsd:nonNegativeInteger ;
150
rdfs:label "interpretation" ;
151
rdfs:subPropertyOf nie:interpretedAs .
153
zg:hasEventManifestation
155
rdfs:domain zg:Event ;
156
rdfs:range zg:EventManifestation ;
157
nrl:maxCardinality "1"^^xsd:nonNegativeInteger ;
158
rdfs:label "manifestation" ;
159
rdfs:subPropertyOf rdfs:type .
163
rdfs:domain zg:Event ;
164
rdfs:range rdfs:Resource ;
165
rdfs:label "subject" .
114
rdfs:comment "Something that happened at a point in time. Events are categorized by two primary factors 'what happened' - called the interpretation and 'how did it happen' - called the manifestation. Aside from a timestamp, events can also carry a reference to the entity responsible for instantiating it - called the actor. Normally the event actor is an application, but it need not be. Events happen to zero or more subjects. The subjects are described using the Nepomuk ontologies." ;
115
rdfs:subClassOf rdfs:Resource .
119
rdfs:comment "A unique integer id assigned to an event by the logging framework when the event is first logged" ;
120
rdfs:domain zg:Event ;
121
rdfs:range xsd:nonNegativeInteger ;
123
nrl:maxCardinality "1"^^xsd:nonNegativeInteger .
127
rdfs:comment "Timestamp in milliseconds since the Unix Epoch" ;
128
rdfs:domain zg:Event ;
129
rdfs:range xsd:long ;
130
rdfs:label "timestamp" ;
131
nrl:maxCardinality "1"^^xsd:nonNegativeInteger .
135
rdfs:comment "The application or entity responsible for emitting the event. For applications the format of this field is the base filename of the corresponding .desktop file with an app:// URI scheme. For example /usr/share/applications/firefox.desktop is encoded as app://firefox.desktop" ;
136
rdfs:domain zg:Event ;
137
rdfs:range rdfs:Resource ;
139
nrl:maxCardinality "1"^^xsd:nonNegativeInteger .
141
zg:hasEventInterpretation
143
rdfs:domain zg:Event ;
144
rdfs:range zg:EventInterpretation ;
145
nrl:maxCardinality "1"^^xsd:nonNegativeInteger ;
146
rdfs:label "interpretation" ;
147
rdfs:subPropertyOf nie:interpretedAs .
149
zg:hasEventManifestation
151
rdfs:domain zg:Event ;
152
rdfs:range zg:EventManifestation ;
153
nrl:maxCardinality "1"^^xsd:nonNegativeInteger ;
154
rdfs:label "manifestation" ;
155
rdfs:subPropertyOf rdfs:type .
159
rdfs:domain zg:Event ;
160
rdfs:range rdfs:Resource ;
161
rdfs:label "subject" .