mdld-parse 0.9.3 → 0.9.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,2367 +0,0 @@
1
- <a id="index"></a>
2
-
3
- [mdp] <https://mdld.js.org/prov/>
4
-
5
- # PROV-O MDLD Catalog {=mdp:index .Container label}
6
-
7
- > W3C standard for provenance chains working in MDLD text with SHACL validation {comment}
8
-
9
- > We have authoritative source - the [prov-o.ttl](./prov-o.ttl) {+mdp:ttl ?member}
10
-
11
- ## Overview
12
-
13
- This catalog presents a complete reconstruction of the W3C PROV-O ontology in MDLD format, featuring:
14
-
15
- - **6 Components** - Organized functional modules covering all provenance aspects
16
- - **3 Categories** - Starting Point, Qualified, and Expanded terms for progressive learning
17
- - **11 Examples** - Real-world scenarios demonstrating provenance patterns
18
- - **35 Entities, 16 Activities, 16 Agents** - Rich instance data for validation
19
-
20
- ## Categories
21
-
22
- [3 categories](#categories-index)
23
-
24
- - **[Starting Point Terms](#categories-starting-point-index)** - Core provenance concepts for immediate use
25
- - **[Qualified Terms](#categories-qualified-index)** - Enhanced relationships with contextual detail
26
- - **[Expanded Terms](#categories-expanded-index)** - Advanced patterns for complex scenarios
27
-
28
- ## Components
29
-
30
- [6 components](#components-index)
31
-
32
- - **[Entities and Activities](#components-entities-activities-index)** - Core building blocks and lifecycle management
33
- - **[Agents, Responsibility and Influence](#components-agents-responsibility-index)** - Accountability and authority structures
34
- - **[Derivations](#components-derivations-index)** - Entity transformation and lineage tracking
35
- - **[Collections](#components-collections-index)** - Dynamic membership and provenance of groups
36
- - **[Bundles](#components-bundles-index)** - Nested provenance and provenance-of-provenance
37
- - **[Alternate](#components-alternate-index)** - Multiple perspectives and specialization relationships
38
-
39
- ## Examples
40
-
41
- [11 examples](#examples-index)
42
-
43
- Real-world provenance scenarios including data journalism, scientific workflows, and collaborative authorship demonstrating practical applications of all PROV-O components and patterns.
44
-
45
-
46
-
47
-
48
-
49
-
50
- {=}
51
-
52
-
53
-
54
- <a id="categories-index"></a>
55
-
56
- [mdp] <https://mdld.js.org/prov/>
57
-
58
- ## Categories {=mdp:categories .Container label}
59
-
60
- 3 categories for complexity classification:
61
-
62
- - [Starting point](#categories-starting-point-index) {+mdp:categories#starting-point ?member}
63
- - [Qualified](#categories-qualified-index) {+mdp:categories#qualified ?member}
64
- - [Expanded](#categories-expanded-index) {+mdp:categories#expanded ?member}
65
-
66
-
67
-
68
-
69
-
70
-
71
- {=}
72
-
73
-
74
-
75
- <a id="categories-starting-point-index"></a>
76
-
77
- [mdp] <https://mdld.js.org/prov/>
78
-
79
- # Starting Point Terms {=mdp:categories#starting-point .mdp:Category label}
80
-
81
- ![Figure 1](./categories/starting-point/starting-points.svg)
82
-
83
- The Starting Point category is a small set of classes and properties that can be used to create simple, initial provenance descriptions. Three classes provide a basis for the rest of PROV-O:
84
-
85
- - An **prov:Entity** {+prov:Entity .Class !prov:category} is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary.
86
- - An **prov:Activity** {+prov:Activity .Class !prov:category} is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities.
87
- - An **prov:Agent** {+prov:Agent .Class !prov:category} is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity.
88
-
89
- The three primary classes relate to one another and to themselves using the properties shown in the following figure.
90
-
91
- Activities start and end at particular points in time (described using properties **prov:startedAtTime** {+prov:startedAtTime .rdf:Property !prov:category} and **prov:endedAtTime** {+prov:endedAtTime !prov:category}, respectively) and during their lifespan can use and generate a variety of Entities (described with **prov:used** {+prov:used !prov:category} and **prov:wasGeneratedBy** {+prov:wasGeneratedBy !prov:category}, respectively). For example, a blog writing activity may use a particular dataset and generate a bar chart. By expressing usage and generation, one can construct provenance chains comprising both Activities and Entities.
92
-
93
- In addition, we can say that an Activity **prov:wasInformedBy** {+prov:wasInformedBy !prov:category} another Activity to provide some dependency information without explicitly providing the activities' start and end times. A **prov:wasInformedBy** relation between Activities suggests that the informed Activity used an Entity that was generated by the informing Activity, but the Entity itself is unknown or is not of interest. So, the **prov:wasInformedBy** property allows the construction of provenance chains comprising only Activities.
94
-
95
- Provenance chains comprising only Entities can be formed using the **prov:wasDerivedFrom** {+prov:wasDerivedFrom !prov:category} property. A derivation is a transformation of one entity into another. For example, if the Activity that created the bar chart is not known or is not of interest, then we can say that the bar chart **prov:wasDerivedFrom** the dataset. Arbitrary RDF properties can be used to describe the fixed aspects of an Entity that are interesting within a particular application (for example, the file size and format of the dataset, or the aspect ratio of the bar chart).
96
-
97
- While the properties **prov:used**, **prov:wasGeneratedBy**, **prov:wasInformedBy**, and **prov:wasDerivedFrom** can be used to construct provenance chains among Activities and Entities, Agents may also be ascribed responsibility for any Activity or Entity within a provenance chain. An Agent's responsibility for an Activity or Entity is described using the properties **prov:wasAssociatedWith** {+prov:wasAssociatedWith !prov:category} and **prov:wasAttributedTo** {+prov:wasAttributedTo !prov:category}, respectively. Agents can also be responsible for other Agents' actions. In this case of delegation, the influencing Agent **prov:actedOnBehalfOf** {+prov:actedOnBehalfOf !prov:category} another Agent that also bears responsibility for the influenced Activity or Entity.
98
-
99
- The properties rdf:type and rdfs:label are used to express prov:type and prov:label, respectively.
100
-
101
-
102
- ## Example
103
-
104
- ![example 1](./categories/starting-point/starting-points-example.svg)
105
-
106
- ### TTL
107
-
108
- ![ttl](./examples/example1.ttl)
109
-
110
- ### MDLD
111
-
112
- ![mdld](./categories/starting-point/#examples-example)
113
-
114
-
115
-
116
-
117
-
118
-
119
- {=}
120
-
121
-
122
-
123
- <a id="examples-example"></a>
124
-
125
- [ex] <http://example.org/>
126
- [foaf] <http://xmlns.com/foaf/0.1/>
127
-
128
- # Work report
129
-
130
- ## Entities
131
-
132
- ### Aggregated data {=ex:aggregatedByRegions .prov:Entity}
133
-
134
- Created by [Derek] {+ex:derek ?prov:wasAttributedTo} via the [aggregation] {+ex:aggregationActivity ?prov:wasGeneratedBy}
135
-
136
- ### Bar Chart {=ex:bar_chart .prov:Entity}
137
-
138
- Created by [Derek] {+ex:derek ?prov:wasAttributedTo} based on [aggregatedByRegions] {+ex:aggregatedByRegions ?prov:wasDerivedFrom} via [illustrationActivity] {+ex:illustrationActivity ?prov:wasGeneratedBy}
139
-
140
- ## Activities
141
-
142
- ### Aggregation {=ex:aggregationActivity .prov:Activity}
143
-
144
- Done by [Derek] {+ex:derek ?prov:wasAssociatedWith} using [Crime data] {+ex:crimeData ?prov:used} and the [National Regions List] {+ex:nationalRegionsList ?prov:used} to create the report from [2011-07-14T02:02:02Z] {prov:endedAtTime ^^xsd:dateTime} till [2011-07-14T01:01:01Z] {prov:startedAtTime ^^xsd:dateTime}.
145
-
146
- ### Illustration {=ex:illustrationActivity .prov:Activity}
147
-
148
- Performed by [derek] {+ex:derek ?prov:wasAssociatedWith} using the [Report] {+ex:aggregatedByRegions ?prov:used} after the [Aggregation] {+ex:aggregationActivity ?prov:wasInformedBy}
149
-
150
- ## Sources
151
-
152
- ### Crime Data {=ex:crimeData .prov:Entity}
153
-
154
- Coming from official [Government] {+ex:government ?prov:wasAttributedTo} source.
155
-
156
- ### National Regions List {=ex:nationalRegionsList .prov:Entity}
157
-
158
- Provided by [CAG] {+ex:civil_action_group ?prov:wasAttributedTo}
159
-
160
- ## Agents
161
-
162
- ### Derek {=ex:derek .prov:Agent .prov:Person foaf:givenName}
163
-
164
- [National Newspaper] {+ex:natonal_newspaper_inc ?prov:actedOnBehalfOf}
165
- [<derek@example.org>] {+mailto:<derek@example.org> ?foaf:mbox}
166
-
167
- ### Government {=ex:government .prov:Agent .prov:Organization}
168
-
169
- ### Civil Action Group {=ex:civil_action_group .prov:Agent .prov:Organization foaf:name}
170
-
171
- ### National Newspaper Inc. {=ex:national_newspaper_inc .prov:Agent .prov:Organization foaf:name}
172
-
173
-
174
-
175
-
176
-
177
-
178
- {=}
179
-
180
-
181
-
182
- <a id="categories-qualified-index"></a>
183
-
184
- [mdp] <https://mdld.js.org/prov/>
185
-
186
- # Qualified Terms {=mdp:categories#qualified .mdp:Category label}
187
-
188
- The Qualified Terms category is the result of applying the Qualification Pattern [LD-Patterns-QR] to the simple (unqualified) relations available in the Starting Point and Expanded categories. The terms in this category are for users who wish to provide further details about the provenance-related influence among Entities, Activities, and Agents.
189
-
190
- The Qualification Pattern restates an unqualified influence relation by using an intermediate class that represents the influence between two resources. This new instance, in turn, can be annotated with additional descriptions of the influence that one resource had upon another. The following two tables list the influence relations that can be qualified using the Qualification Pattern, along with the properties used to qualify them. For example, the second row of the first table indicates that to elaborate how an prov:Activity prov:used a particular prov:Entity, one creates an instance of prov:Usage that indicates the influencing entity with the prov:entity property. Meanwhile, the influenced prov:Activity indicates the prov:Usage with the property prov:qualifiedUsage. The resulting structure that qualifies the an Activity's usage of an Entity is illustrated in Figure 4a below.
191
-
192
- ![figure 4](./categories/qualified/qualified-patterns.svg)
193
-
194
-
195
- ## Starting Point Qualification Patterns
196
-
197
- Seven Starting Point relations can be further described using the Qualification Pattern:
198
-
199
- ### Entity Generation Qualification {=mdp:qual:entity-generation .mdp:QualificationPattern}
200
-
201
- When an [Entity] {+prov:Entity ?mdp:influencedClass} is generated by an [Activity] {+prov:Activity ?mdp:influencingClass}, you can qualify this relationship using [wasGeneratedBy] {+prov:wasGeneratedBy ?mdp:unqualifiedInfluence}. The qualification uses [qualifiedGeneration] {+prov:qualifiedGeneration ?mdp:qualificationProperty} to reference a [Generation] {+prov:Generation ?mdp:qualifiedInfluence} instance, which then cites the generating [Activity] {+prov:activity ?mdp:influencerProperty}.
202
-
203
- ### Entity Derivation Qualification {=mdp:qual:entity-derivation .mdp:QualificationPattern}
204
-
205
- When one [Entity] {+prov:Entity ?mdp:influencedClass} is derived from another [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship using [wasDerivedFrom] {+prov:wasDerivedFrom ?mdp:unqualifiedInfluence}. The qualification uses [qualifiedDerivation] {+prov:qualifiedDerivation ?mdp:qualificationProperty} to reference a [Derivation] {+prov:Derivation ?mdp:qualifiedInfluence} instance, which then cites the source [entity] {+prov:entity ?mdp:influencerProperty}.
206
-
207
- ### Entity Attribution Qualification {=mdp:qual:entity-attribution .mdp:QualificationPattern}
208
-
209
- When an [Entity] {+prov:Entity ?mdp:influencedClass} is attributed to an [Agent] {+prov:Agent ?mdp:influencingClass}, you can qualify this relationship using [wasAttributedTo] {+prov:wasAttributedTo ?mdp:unqualifiedInfluence}. The qualification uses [qualifiedAttribution] {+prov:qualifiedAttribution ?mdp:qualificationProperty} to reference an [Attribution] {+prov:Attribution ?mdp:qualifiedInfluence} instance, which then cites the responsible [agent] {+prov:agent ?mdp:influencerProperty}.
210
-
211
- ### Activity Usage Qualification {=mdp:qual:activity-usage .mdp:QualificationPattern}
212
-
213
- When an [Activity] {+prov:Activity ?mdp:influencedClass} [used] {+prov:used ?mdp:unqualifiedInfluence} an [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedUsage] {+prov:qualifiedUsage ?mdp:qualificationProperty} to reference a [Usage] {+prov:Usage ?mdp:qualifiedInfluence} instance, which then cites the used [entity] {+prov:entity ?mdp:influencerProperty}.
214
-
215
- ### Activity Communication Qualification {=mdp:qual:activity-communication .mdp:QualificationPattern}
216
-
217
- When one [Activity] {+prov:Activity ?mdp:influencedClass} [wasInformedBy] {+prov:wasInformedBy ?mdp:unqualifiedInfluence} another [Activity] {+prov:Activity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedCommunication] {+prov:qualifiedCommunication ?mdp:qualificationProperty} to reference a [Communication] {+prov:Communication ?mdp:qualifiedInfluence} instance, which then cites the informing [activity] {+prov:activity ?mdp:influencerProperty}.
218
-
219
- ### Activity Association Qualification {=mdp:qual:activity-association .mdp:QualificationPattern}
220
-
221
- When an [Activity] {+prov:Activity ?mdp:influencedClass} [wasAssociatedWith] {+prov:wasAssociatedWith ?mdp:unqualifiedInfluence} an [Agent] {+prov:Agent ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedAssociation] {+prov:qualifiedAssociation ?mdp:qualificationProperty} to reference an [Association] {+prov:Association ?mdp:qualifiedInfluence} instance, which then cites the associated [agent] {+prov:agent ?mdp:influencerProperty}.
222
-
223
- ### Agent Delegation Qualification {=mdp:qual:agent-delegation .mdp:QualificationPattern}
224
-
225
- When one [Agent] {+prov:Agent ?mdp:influencedClass} [actedOnBehalfOf] {+prov:actedOnBehalfOf ?mdp:unqualifiedInfluence} another [Agent] {+prov:Agent ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedDelegation] {+prov:qualifiedDelegation ?mdp:qualificationProperty} to reference a [Delegation] {+prov:Delegation ?mdp:qualifiedInfluence} instance, which then cites the delegating [agent] {+prov:agent ?mdp:influencerProperty}.
226
-
227
- ## Expanded Qualification Patterns
228
-
229
- Seven Expanded relations can be further described using the Qualification Pattern:
230
-
231
- ### General Influence Qualification {=mdp:qual:general-influence .mdp:QualificationPattern}
232
-
233
- When any [Entity/Activity/Agent] {+prov:Entity ?mdp:influencedClass} [wasInfluencedBy] {+prov:wasInfluencedBy ?mdp:unqualifiedInfluence} another [Entity/Activity/Agent] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedInfluence] {+prov:qualifiedInfluence ?mdp:qualificationProperty} to reference an [Influence] {+prov:Influence ?mdp:qualifiedInfluence} instance, which then cites the [influencer] {+prov:influencer ?mdp:influencerProperty}.
234
-
235
- ### Entity PrimarySource Qualification {=mdp:qual:entity-primary-source .mdp:QualificationPattern}
236
-
237
- When an [Entity] {+prov:Entity ?mdp:influencedClass} [hadPrimarySource] {+prov:hadPrimarySource ?mdp:unqualifiedInfluence} another [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedPrimarySource] {+prov:qualifiedPrimarySource ?mdp:qualificationProperty} to reference a [PrimarySource] {+prov:PrimarySource ?mdp:qualifiedInfluence} instance, which then cites the source [entity] {+prov:entity ?mdp:influencerProperty}.
238
-
239
- ### Entity Quotation Qualification {=mdp:qual:entity-quotation .mdp:QualificationPattern}
240
-
241
- When an [Entity] {+prov:Entity ?mdp:influencedClass} [wasQuotedFrom] {+prov:wasQuotedFrom ?mdp:unqualifiedInfluence} another [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedQuotation] {+prov:qualifiedQuotation ?mdp:qualificationProperty} to reference a [Quotation] {+prov:Quotation ?mdp:qualifiedInfluence} instance, which then cites the quoted [entity] {+prov:entity ?mdp:influencerProperty}.
242
-
243
- ### Entity Revision Qualification {=mdp:qual:entity-revision .mdp:QualificationPattern}
244
-
245
- When an [Entity] {+prov:Entity ?mdp:influencedClass} [wasRevisionOf] {+prov:wasRevisionOf ?mdp:unqualifiedInfluence} another [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedRevision] {+prov:qualifiedRevision ?mdp:qualificationProperty} to reference a [Revision] {+prov:Revision ?mdp:qualifiedInfluence} instance, which then cites the original [entity] {+prov:entity ?mdp:influencerProperty}.
246
-
247
- ### Entity Invalidation Qualification {=mdp:qual:entity-invalidation .mdp:QualificationPattern}
248
-
249
- When an [Entity] {+prov:Entity ?mdp:influencedClass} [wasInvalidatedBy] {+prov:wasInvalidatedBy ?mdp:unqualifiedInfluence} an [Activity] {+prov:Activity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedInvalidation] {+prov:qualifiedInvalidation ?mdp:qualificationProperty} to reference an [Invalidation] {+prov:Invalidation ?mdp:qualifiedInfluence} instance, which then cites the invalidating [activity] {+prov:activity ?mdp:influencerProperty}.
250
-
251
- ### Activity Start Qualification {=mdp:qual:activity-start .mdp:QualificationPattern}
252
-
253
- When an [Activity] {+prov:Activity ?mdp:influencedClass} [wasStartedBy] {+prov:wasStartedBy ?mdp:unqualifiedInfluence} an [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedStart] {+prov:qualifiedStart ?mdp:qualificationProperty} to reference a [Start] {+prov:Start ?mdp:qualifiedInfluence} instance, which then cites the triggering [entity] {+prov:entity ?mdp:influencerProperty}.
254
-
255
- ### Activity End Qualification {=mdp:qual:activity-end .mdp:QualificationPattern}
256
-
257
- When an [Activity] {+prov:Activity ?mdp:influencedClass} [wasEndedBy] {+prov:wasEndedBy ?mdp:unqualifiedInfluence} an [Entity] {+prov:Entity ?mdp:influencingClass}, you can qualify this relationship. The qualification uses [qualifiedEnd] {+prov:qualifiedEnd ?mdp:qualificationProperty} to reference an [End] {+prov:End ?mdp:qualifiedInfluence} instance, which then cites the ending [entity] {+prov:entity ?mdp:influencerProperty}.
258
-
259
- All influence classes (e.g. prov:Association, prov:Usage) are extensions of prov:Influence and either prov:EntityInfluence, prov:ActivityInfluence, or prov:AgentInfluence, which determine the property used to cite the influencing resource (either prov:entity, prov:activity, or prov:agent, respectively). Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable.
260
-
261
-
262
- ![example6](./examples/example6.ttl)
263
-
264
- #### Example 7
265
-
266
- One can find that prov:wasGeneratedBy can be qualified using the qualification property prov:qualifiedGeneration, the class prov:Generation (a subclass of prov:ActivityInfluence), and the property prov:activity. From this, the influence relation above can be restated with the qualification pattern as:
267
-
268
- ![example7](./examples/example7.ttl)
269
-
270
- The asserter can thus attach additional properties to :e1Gen to describe the generation of :e1 by :a1.
271
-
272
- As can be seen in this example, qualifying an influence relation provides a second form (e.g. :e1 prov:qualifiedGeneration :e1Gen) to express an equivalent influence relation (e.g. :e1 prov:wasGeneratedBy :a1). It is correct and acceptable for an implementer to use either qualified or unqualified forms as they choose (or both), and a consuming application should be prepared to recognize either form. Consuming applications should recognize both qualified and unqualified forms, and treat the qualified form as implying the unqualified form. Because the qualification form is more verbose, the unqualified form should be favored in cases where additional properties are not provided. When the qualified form is expressed, including the equivalent unqualified form can facilitate PROV-O consumption, and is thus encouraged.
273
-
274
- In addition to the previous two tables, Figure 4 illustrates the classes and properties needed to apply the qualification pattern to ten of the fourteen qualifiable influence relations. For example, while prov:qualifiedUsage, prov:Usage, and prov:entity are used to qualify prov:used relations, prov:qualifiedAssociation, prov:Association, and prov:agent are used to qualify prov:wasAssociatedWith relations. This pattern applies to the twelve other influence relations that can be qualified.
275
-
276
- In subfigure a the prov:qualifiedUsage property parallels the prov:used property and references an instance of prov:Usage, which in turn provides attributes of the prov:used relation between the Activity and Entity. The prov:entity property is used to cite the Entity that was used by the Activity. In this case, the time that the Activity used the Entity is provided using the prov:atTime property and a literal xsd:dateTime value. The prov:atTime property can be used to describe any prov:InstantaneousEvent (including prov:Start, prov:Generation, prov:Usage, prov:Invalidation, and prov:End).
277
-
278
- Similarly in subfigure j, the prov:qualifiedAssociation property parallels the prov:wasAssociatedWith property and references an instance of prov:Association, which in turn provides attributes of the prov:wasAssociatedWith relation between the Activity and Agent. The prov:agent property is used to cite the Agent that influenced the Activity. In this case, the plan of actions and steps that the Agent used to achieve its goals is provided using the prov:hadPlan property and an instance of prov:Plan. Further, the prov:hadRole property and prov:Role class can be used to describe the function that the agent served with respect to the Activity. Both prov:Plan and prov:Role are left to be extended by applications.
279
- Express association between an activity and an agent using a binary relationship and an alternatie qualified relationship
280
- Figure 4: Illustration of the properties and classes to use (in blue) to qualify the starting point and expanded influence relations (dotted black).
281
- The diagrams in this document depict Entities as ovals, Activities as rectangles, and Agents as pentagons. Quotation, Revision, and PrimarySource are omitted because they are special forms of Derivation and follow the same pattern as subfigure g.
282
-
283
- The following two examples show the result of applying the Usage and Association patterns to the chart-making example from Section 3.1.
284
-
285
- #### Example 8: Qualified Usage
286
-
287
- The prov:qualifiedUsage property parallels the prov:used property to provide an additional description to :illustrationActivity. The instance of prov:Usage cites the data used (:aggregatedByRegions) and the time the activity used it (2011-07-14T03:03:03Z).
288
-
289
-
290
- ![example8](./examples/example8.ttl)
291
-
292
- #### Example 9: Qualified Association
293
-
294
- The prov:qualifiedAssociation property parallels the prov:wasAssociatedWith property to provide an additional description about the :illustrationActivity that Derek influenced. The instance of prov:Association cites the influencing agent (:derek) that followed the instructions (:tutorial_blog). Further, Derek served the role of :illustrationist during the activity.
295
-
296
- ![example9](./examples/example9.ttl)
297
-
298
- This section finishes with two more examples of qualification as applied to the chart-making example from Section 3.1.
299
-
300
- #### Example 10: Qualified Generation
301
-
302
- ![example10](./examples/example10.ttl)
303
-
304
-
305
- ### Example 11: Qualified Derivation
306
-
307
- The prov:qualifiedDerivation property parallels the prov:wasDerivedFrom property to provide an additional description to :bar_chart. The instance of prov:Derivation cites the activity (:illustrationActivity) and the Usages and Generations that the activity conduced to create the :bar_chart.
308
-
309
- ![example11](./examples/example11.ttl)
310
-
311
-
312
-
313
-
314
-
315
-
316
- {=}
317
-
318
-
319
-
320
- <a id="categories-expanded-index"></a>
321
-
322
- [mdp] <https://mdld.js.org/prov/>
323
-
324
- # Expanded Terms {=mdp:categories#expanded .Container .mdp:Category label}
325
-
326
- > The terms introduced in this section provide additional ways to describe the provenance among Entities, Activities, and Agents. The additional terms are illustrated in the following figure and can be separated into five different categories. {comment}
327
-
328
- ![](./categories/expanded/expanded.svg)
329
-
330
- ## First category
331
-
332
- The first category extends the Starting Point terms with subclasses, subproperties, and a superproperty.
333
-
334
- ### 3 Sub-classes of Agent
335
-
336
- Agent types:
337
-
338
- * Person {+prov:Person !prov:category}
339
-
340
- * Organization {+prov:Organization !prov:category}
341
-
342
- * SoftwareAgent {+prov:SoftwareAgent !prov:category}
343
-
344
- ### 3 Sub-classes of Entity
345
-
346
- A **prov:Collection** {+prov:Collection !prov:category} is an Entity that provides a structure (e.g. set, list, etc.) to some constituents (which are themselves Entities). The **prov:Collection** class can be used to express the provenance of the collection itself: e.g. who maintained the collection, which members it contained as it evolved, and how it was assembled. The **prov:hadMember** {+prov:hadMember !prov:category} property is used to assert membership in a collection. **prov:EmptyCollection** {+prov:EmptyCollection !prov:category} is a Collection with no members.
347
-
348
- A **prov:Bundle** {+prov:Bundle !prov:category} is a named set of provenance descriptions, which may itself have provenance. The named set of provenance descriptions may be expressed as PROV-O or any other form. The subclass of Bundle that names a set of PROV-O assertions is not provided by PROV-O, since it is more appropriate to do so using other recommendations, standards, or technologies. In any case, a Bundle of PROV-O assertions is an abstract set of RDF triples, and adding or removing a triple creates a new distinct Bundle of PROV-O assertions.
349
-
350
- A **prov:Plan** {+prov:Plan !prov:category} is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.
351
-
352
- More general and more specific properties are also provided by the expanded terms. More generally, the property **prov:wasInfluencedBy** is a superproperty that relates any **prov:influenced** {+prov:influenced !prov:category} Entity, Activity, or Agent to any other influencing Entity, Activity, or Agent that had an effect on its characteristics. Three subproperties of **prov:wasDerivedFrom** are also provided for certain kinds of derivation among Entities: **prov:wasQuotedFrom** {+prov:wasQuotedFrom !prov:category} cites a potentially larger Entity (such as a book, blog, or image) from which a new Entity was created by repeating some or all of the original, **prov:wasRevisionOf** {+prov:wasRevisionOf !prov:category} indicates that the derived Entity contains substantial content from the original Entity (e.g., two editions of a book), and **prov:hadPrimarySource** {+prov:hadPrimarySource !prov:category} cites a preceding Entity produced by some agent with direct experience and knowledge about the topic (such as a reading from a sensor, or a journal written during an historical event).
353
-
354
- ## Second category
355
-
356
- The second category of expanded terms relates Entities according to their levels of abstraction, where some Entities may present more specific aspects than their more general counterparts. While **prov:specializationOf** {+prov:specializationOf !prov:category} links a more specific Entity to a more general one (e.g., today's BBC news home page versus BBC's news home page on any day), **prov:alternateOf** {+prov:alternateOf !prov:category} links Entities that present aspects of the same thing, but not necessarily the same aspects or at the same time (e.g., the serialization of a document in different formats or a backup copy of a computer file).
357
-
358
- ## Third category
359
-
360
- The third category of expanded terms allows further description of Entities. The property **prov:value** {+prov:value !prov:category} provides a literal value that is a direct representation of an entity. For example, the prov:value of a quote could be a string of the sentences stated, or the prov:value of an Entity involved in a numeric calculation could be the xsd:integer four. The property **prov:atLocation** {+prov:atLocation !prov:category} can be used to describe the **prov:Location** {+prov:Location !prov:category} of any Entity, Activity, Agent, or prov:InstantaneousEvent (i.e., the starting or ending of an activity or the generation, usage, or invalidation of an entity). The properties used to describe instances of **prov:Location** are outside the scope of PROV-O; reuse of other existing vocabulary is encouraged.
361
-
362
- ## Fourth category
363
-
364
- The fourth category of expanded terms describes the lifetime of an Entity beyond being generated by an Activity and used by other Activities. For example, a painting could not have been displayed before it was painted, and it could not be sold after it was destroyed by fire. Similar to how Activities have start and end times, an Entity may be bound by points in time for which it was generated or is no longer usable. The properties **prov:generatedAtTime** {+prov:generatedAtTime !prov:category} and **prov:invalidatedAtTime** {+prov:invalidatedAtTime !prov:category} can be used to bound the starting and ending moments of an Entity's existence. The Activities that led to the generation or invalidation of an Entity can be provided using **prov:wasGeneratedBy** and **prov:wasInvalidatedBy**, respectively. **prov:generated** {+prov:generated !prov:category} and **prov:invalidated** {+prov:invalidated !prov:category} are the inverses of **prov:wasGeneratedBy** and **prov:wasInvalidatedBy** {+prov:wasInvalidatedBy !prov:category}, respectively, and are defined to facilitate Activity-as-subject as well as Entity-as-subject descriptions. For more about inverses, see the Appendix B.
365
-
366
- ## Fifth category
367
-
368
- The fifth category of expanded terms describes the lifetime of an Activity beyond its start and end times and predecessor Activities. Activities may also be started or ended by Entities, which are described using the properties **prov:wasStartedBy** {+prov:wasStartedBy !prov:category} and **prov:wasEndedBy** {+prov:wasEndedBy !prov:category}, respectively. Since Entities may start or end Activities, and Agents may be Entities, then Agents may also start or end Activities.i
369
-
370
- ## Examples
371
-
372
- The following examples illustrate the expanded terms by elaborating the crime chart example from the previous section. After aggregating the dataset and creating the chart, Derek published a post to exhibit his work.
373
-
374
- ### Example 2
375
-
376
- ![example2](./examples/example2.ttl)
377
-
378
- ![example2](./categories/expanded/expanded-terms-example-bundlePost.svg)
379
-
380
- > Figure 4. An illustration of the PROV-O assertions in Example 2, where Derek
381
- published two versions of a blog for the National Newspaper, Inc.
382
- The diagrams in this document depict Entities as yellow ovals, Activities as blue rectangles,
383
- and Agents as orange pentagons. The responsibility properties are shown in pink.
384
-
385
- ![example2](./categories/expanded/#examples-example2)
386
-
387
-
388
- ### Example 3
389
-
390
- ![example3](./categories/expanded/#examples-example3)
391
-
392
- ![example3](./examples/example3.ttl)
393
-
394
- ### Example 4
395
-
396
- ![example4](./categories/expanded/#examples-example4)
397
-
398
- ![example4](./examples/example4.ttl)
399
-
400
- ### Example 5
401
-
402
- ![example5](./categories/expanded/#examples-example5)
403
-
404
- ![example5](./examples/example5.ttl)
405
-
406
-
407
-
408
-
409
-
410
- {=}
411
-
412
-
413
-
414
- <a id="examples-example2"></a>
415
-
416
- [ex] <http://www.example.org#>
417
- [foaf] <http://xmlns.com/foaf/0.1/>
418
- [sioc] <http://rdfs.org/sioc/ns#>
419
-
420
- # More crime happens in cities {=ex:post9821v1 .Entity .Post sioc:title label}
421
-
422
- > I was currius... {prov:value}
423
-
424
- # Provenance
425
-
426
- Agent **Derek** {=ex:derek .Agent .Person foaf:givenName} ([derek@example.org] {+mailto:derek@example.org ?foaf:mbox}), acting again on behalf of the **National Newspaper, Inc.** {+ex:national_newspaper_inc ?prov:actedOnBehalfOf foaf:name} organization, used the **Post Editor 3000** {=ex:postEditor .Agent .SoftwareAgent foaf:name} tool to publish a post about his recent data analysis **Crime aggregated by regions** {=ex:aggregatedByRegions .Entity} stored at **aggr.txt** {+file://Users/aggr.txt .Location ?prov:atLocation} based on **Crime Data** {=ex:crimeData .Entity ?prov:used} coming from *government* {+ex:government .Agent .Organization ?prov:wasAttributedTo}.
427
-
428
- The blog editing *tool* {=ex:postEditor} tracked Derek's actions as PROV-O assertions and published them as a Bundle (the current file **derek-bundle.ttl** {=ex:derek-bundle.ttl .Bundle .Entity ?prov:wasAttributedTo}) at *2011-07-16T02:52:02Z* {prov:generatedAtTime ^^xsd:dateTime}. The tool recorded that **Derek** {=ex:derek} started at *2011-07-16T01:52:02Z* {prov:endedAtTime ^^xsd:dateTime} and ended at *2011-07-16T01:01:01Z* {prov:startedAtTime ^^xsd:dateTime} the **publishing activity** {=ex:publicationActivity1123 !prov:wasEndedBy !prov:wasStartedBy} that used the **aggregation** {+ex:aggregatedByRegions ?prov:wasInfluencedBy} of **crime data** {+ex:crimeData ?prov:hadPrimarySource} to *generate* {+ex:postEditor ?prov:wasAssociatedWith} the post **More crime happens in cities** {=ex:post9821v1 ?prov:generated !prov:wasGeneratedBy} at *2011-07-16T01:52:02Z* {prov:generatedAtTime ^^xsd:dateTime}. Was later invalidated by new version at *2011-07-16T02:02:02Z* {prov:invalidatedAtTime ^^xsd:dateTime}
429
-
430
- The post included a permanent link where the content of the **latest version** {+ex:more-crime-happens-in-cities ?prov:specializationOf !sioc:previous_version} is available in addition to a textual snapshot of the current version (using prov:value). Derek also included additional domain-specific descriptions of the post, such as its title.
431
-
432
- ## Typo update
433
-
434
- Shortly after publishing the post, Derek noticed a typographical error in his narrative. Because the fix would be minimal, he did not record the activity that led to the new version. Instead, he related the **new version** {=ex:post9821v2 .Entity .Post} generated at *2011-07-16T02:02:02Z* {prov:generatedAtTime ^^xsd:dateTime} as a revision of the **previous** {+ex:post9821v1 ?prov:wasRevisionOf ?prov:alternateOf}. Since both versions of the blog are forms of the long-standing blog permalink, the revisions are alternates of one another and each is a prov:specializationOf of **More Crime In Cities** {+ex:more-crime-happens-in-cities ?prov:specializationOf !sioc:latest_version}.
435
-
436
- > I was curious... {prov:value}
437
-
438
-
439
-
440
-
441
-
442
- {=}
443
-
444
-
445
-
446
- <a id="examples-example3"></a>
447
-
448
- [ex] <http://www.example.org#>
449
- [foaf] <http://xmlns.com/foaf/0.1/>
450
- [sioc] <http://rdfs.org/sioc/ns#>
451
-
452
- # More crime happens in cities (for dummies) {=ex:post9822 .Entity .Post sioc:title}
453
-
454
- > A quick overview of Derek's... {prov:value}
455
-
456
- # Provenance
457
-
458
- Shortly after Derek published his blog post, **Monica** {=ex:monica .Agent .Person foaf:givenName} (<monica@example.org> {+mailto:monica@example.org ?foaf:mbox}) adapted the text for a wider audience in a **new post** {=ex:post9822}. This rewrite is an *alternate* {+ex:more-crime-happens-in-cities ?prov:alternateOf}, abbreviated view of the same topic that Derek wrote about and was created from his **original text** {=ex:derek-bundle.ttl}. Since the provenance produced by the activities of Derek and Monica corresponded to different user views, the system automatically published it in a **different prov:Bundle** {=ex:monica-bundle.ttl .Bundle .Entity !prov:wasDerivedFrom} at *2011-07-16T03:03:03Z* {prov:generatedAtTime ^^xsd:dateTime}. The *tool* {=ex:postEditor ?prov:wasAttributedTo} also asserted *provenance* {=ex:post9822 !prov:wasAttributedTo} about the bundle that it produced (e.g., the date of creation, its **creator** {+ex:monica ?prov:wasAttributedTo}, and the fact that it Derek's bundle was *used* {+ex:post9821v2 ?prov:wasRevisionOf}). Because a bundle is a kind of entity, all provenance assertions that can be made about entities can also be made about bundles. The use of bundles enables the creation of provenance of provenance.
459
-
460
-
461
-
462
-
463
-
464
- {=}
465
-
466
-
467
-
468
- <a id="examples-example4"></a>
469
-
470
- [ex] <http://www.example.org#>
471
- [foaf] <http://xmlns.com/foaf/0.1/>
472
- [sioc] <http://rdfs.org/sioc/ns#>
473
-
474
- # Reply to Derek and Monica {=ex:post19201 .Entity .Post}
475
-
476
- > I'm not so sure that... {prov:value}
477
-
478
- # Provenance
479
-
480
- After some time, **John** {=ex:john .Agent .Person foaf:name} *wrote* {+ex:publicationActivity1124 .Activity !prov:wasAttributedTo} his own conclusions in his own **post** {=ex:post19201 !prov:wasAttributedTo} quoting the previous two posts.
481
-
482
- Each quote that John makes (*quote_from_monica* {+ex:quote_from_monica ?prov:wasDerivedFrom} and *quote_from_derek* {+ex:quote_from_derek ?prov:wasDerivedFrom}) is a new entity derived from the previous blogs and is annotated with the time that the quote was taken.
483
-
484
- The provenance of John's blog notes that his post is the result of the quotes that he took from Dereks **report** {=ex:more-crime-happens-in-cities}: *Analysis of the datasets demonstrates that there is more crime.* {=ex:quote_from_derek .Entity prov:value !prov:wasQuotedFrom} at *2012-08-08T01:01:01Z* {prov:generatedAtTime ^^xsd:dateTime} and Monica: *In summary, there are clearly more crimes in the country.* {=ex:quote_from_monica .Entity prov:value} quoted from [her post] {+ex:post9822 ?prov:wasQuotedFrom} at *2012-08-08T02:02:02Z* {prov:generatedAtTime ^^xsd:dateTime}.
485
-
486
- The *blog post* {=ex:post19201} is also derived with the *tool* {+ex:postEditor ?prov:wasAttributedTo} from Derek's *aggregatedByRegions* {+ex:aggregatedByRegions ?prov:wasDerivedFrom} dataset because John *inspected* {+ex:publicationActivity1124 ?prov:wasGeneratedBy !prov:generated } it and found a concern that he discusses in his blog. All the provenance statements related to John's post are grouped in a new **prov:Bundle** {=ex:john-bundle.ttl .Bundle .Entity} by the *software editor* {+ex:postEditor ?prov:wasAttributedTo} at *2012-08-08T08:08:08Z* {prov:generatedAtTime ^^xsd:dateTime} thas is derived from *Derek's Bundle* {+ex:derek-bundle.ttl ?prov:wasDerivedFrom} and *Monica's Bundle* {+ex:monica-bundle.ttl ?prov:wasDerivedFrom}
487
-
488
-
489
-
490
-
491
-
492
-
493
- {=}
494
-
495
-
496
-
497
- <a id="examples-example5"></a>
498
-
499
- [ex] <http://www.example.org#>
500
- [foaf] <http://xmlns.com/foaf/0.1/>
501
- [sioc] <http://rdfs.org/sioc/ns#>
502
-
503
- Unfortunately, there was a **problem** {=ex:hard_disk_failure .Activity} in the servers at [2012-09-02T01:31:00Z] {prov:endedAtTime ^^xsd:dateTime} where **the post** {=ex:post19201 .Entity .Post !prov:wasInvalidatedBy} was being stored, and all the data related to the post was lost permanently. Thus, the system invalidated the entity automatically at [2012-09-02T01:31:00Z] {prov:invalidatedAtTime ^^xsd:dateTime} and notified John about the error.
504
-
505
-
506
-
507
-
508
-
509
-
510
-
511
- {=}
512
-
513
-
514
-
515
- <a id="components-index"></a>
516
-
517
- [mdp] <https://mdld.js.org/prov/>
518
-
519
- ## Components {=mdp:components .Container label}
520
-
521
- > Provenance concepts, expressed as PROV-DM types and relations, are organized according to six components.
522
-
523
- 6 components in layers:
524
-
525
- - [Entities and Activities](#components-entities-activities-index) {+mdp:components#entities-activities ?member}
526
- - [Derivations](#components-derivations-index) {+mdp:components#derivations ?member}
527
- - [Agents, responsibility and influence](#components-agents-responsibility-index) {+mdp:components#agents-responsibility ?member}
528
- - [Bundles](#components-bundles-index) {+mdp:components#bundles ?member}
529
- - [Alternate](#components-alternate-index) {+mdp:components#alternate ?member}
530
- - [Collections](#components-collections-index) {+mdp:components#collections ?member}
531
-
532
-
533
-
534
-
535
-
536
-
537
-
538
- {=}
539
-
540
-
541
-
542
- <a id="components-entities-activities-index"></a>
543
-
544
- [mdp] <https://mdld.js.org/prov/>
545
- [owl] <http://www.w3.org/2002/07/owl#>
546
-
547
- # Entities and Activities {=mdp:components#entities-activities .mdp:Component label}
548
-
549
- The first component of PROV-DM is concerned with entities and activities, and their interrelations.
550
-
551
- ![](./components/entities-activities/component1.png)
552
-
553
- [Core flow](#components-entities-activities-core)
554
- [Entity lifecycle flow](#components-entities-activities-entity-lifecycle)
555
- [Activity lifecycle flow](#components-entities-activities-activity-lifecycle)
556
- [Usage flow](#components-entities-activities-usage)
557
- [Communication flow](#components-entities-activities-communication)
558
-
559
- ## Summary
560
-
561
- The PROV-O Entities and Activities component provides the foundational building blocks of provenance, modeling the "what" and "when" of provenance through entities, activities, and their temporal relationships. The component is organized into clear flows that separate concerns while maintaining consistent patterns.
562
-
563
- **Flow Architecture:**
564
- Each flow follows the provenance pattern of binary relations, qualified forms, and influence classes, with temporal properties providing cross-cutting time annotations.
565
-
566
- **Core Flows:**
567
-
568
- **1. Entities Flow** - Fundamental provenance objects
569
- - **Entity**: Physical, digital, or conceptual things with fixed aspects
570
- - **value**: Direct representation of entity characteristics
571
- - **Location**: Spatial context for entities and activities
572
- - **InstantaneousEvent**: Events marking world transitions
573
- - Establishes the "what" of provenance statements
574
-
575
- **2. Entity Lifecycle Flow** - Entity state transitions
576
- - `wasGeneratedBy` → `qualifiedGeneration` → `Generation`
577
- - `wasInvalidatedBy` → `qualifiedInvalidation` → `Invalidation`
578
- - **Temporal Properties**: `generatedAtTime`, `invalidatedAtTime`
579
- - Models creation, existence, and destruction of entities
580
- - Example: Entity generated by activity, later invalidated
581
-
582
- **3. Activity Lifecycle Flow** - Activity state management
583
- - `wasStartedBy` → `qualifiedStart` → `Start`
584
- - `wasEndedBy` → `qualifiedEnd` → `End`
585
- - **Temporal Properties**: `startedAtTime`, `endedAtTime`
586
- - Models initiation and termination of activities
587
- - Example: Activity started by trigger entity, ended by terminator entity
588
-
589
- **4. Usage of Entities by Activities Flow** - Core interaction pattern
590
- - `used` → `qualifiedUsage` → `Usage`
591
- - Models consumption, processing, transformation of entities by activities
592
- - Fundamental provenance relationship (activities act upon entities)
593
- - Example: Baking activity uses spoon, egg, oven
594
-
595
- **5. Inter-Activity Communication Flow** - Activity coordination
596
- - `wasInformedBy` → `qualifiedCommunication` → `Communication`
597
- - Models exchange of entities between activities
598
- - Supports activity dependency and information flow
599
- - Example: Activity A2 informed by Activity A1 via shared entity
600
-
601
- **6. Temporal Properties Flow** - Cross-cutting time framework
602
- - `atTime`: For instantaneous events (generation, usage, start, end, invalidation)
603
- - **Activity Timing**: `startedAtTime`, `endedAtTime`
604
- - **Entity Timing**: `generatedAtTime`, `invalidatedAtTime`
605
- - Provides temporal context for all provenance elements
606
- - Supports property chains for qualified temporal access
607
-
608
- **Key Relationships:**
609
- ```
610
- Entity (disjoint from Activity)
611
- ├── Entity Lifecycle
612
- │ ├── Generation (creates entities)
613
- │ └── Invalidation (destroys entities)
614
- └── Activity Lifecycle
615
- ├── Start (initiates activities)
616
- └── End (terminates activities)
617
-
618
- Activity-Entity Interactions
619
- ├── Usage (activities use entities)
620
- └── Communication (activities coordinate via entities)
621
-
622
- Temporal Framework
623
- ├── atTime (instantaneous events)
624
- ├── Entity Timing (generatedAtTime, invalidatedAtTime)
625
- └── Activity Timing (startedAtTime, endedAtTime)
626
- ```
627
-
628
- **Benefits of Flow Organization:**
629
- - Clear separation of entity vs activity concerns
630
- - Consistent binary→qualified→influence patterns
631
- - Explicit temporal modeling across all flows
632
- - Logical lifecycle progression modeling
633
- - Cross-cutting spatial and temporal context
634
- - Foundation for all other PROV-O components
635
-
636
-
637
-
638
-
639
-
640
-
641
- {=}
642
-
643
-
644
-
645
- <a id="components-entities-activities-core"></a>
646
-
647
- [mdp] <https://mdld.js.org/prov/>
648
- [owl] <http://www.w3.org/2002/07/owl#>
649
-
650
- # Core flow
651
-
652
- ## Entity {=prov:Entity .Class label}
653
-
654
- > An entity is a physical, digital, conceptual, or other kind of thing with some fixed aspects; entities may be real or imaginary. {prov:definition @en}
655
-
656
- **Disjoint with:** [InstantaneousEvent] {+prov:InstantaneousEvent ?owl:disjointWith}
657
-
658
- ## value {=prov:value .owl:DatatypeProperty label}
659
-
660
- > Provides a value that is a direct representation of an entity. {comment @en}
661
-
662
- Attaches a value to an [entity] {+prov:Entity ?domain}.
663
-
664
- > This property serves the same purpose as rdf:value, but has been reintroduced to avoid some of the definitional ambiguity in the RDF specification (specifically, 'may be used in describing structured values')." {prov:editorialNote}
665
-
666
- ## Activity {=prov:Activity .Class label}
667
-
668
- > An activity is something that occurs over a period of time and acts upon or with entities; it may include consuming, processing, transforming, modifying, relocating, using, or generating entities. {prov:definition @en}
669
-
670
- > An activity is not an entity. This distinction is similar to the distinction between 'continuant' and 'occurrent' in logic. {comment @en}
671
-
672
- Disjoint with [Entity] {+prov:Entity ?owl:disjointWith}
673
-
674
- ## InstantaneousEvent {=prov:InstantaneousEvent .Class label}
675
-
676
- > The PROV data model is implicitly based on a notion of instantaneous events (or just events), that mark transitions in the world. Events include generation, usage, or invalidation of entities, as well as starting or ending of activities. This notion of event is not first-class in the data model, but it is useful for explaining its other concepts and its semantics. {prov:definition}
677
-
678
- > An instantaneous event, or event for short, happens in the world and marks a change in the world, in its activities and in its entities. The term 'event' is commonly used in process algebra with a similar meaning. Events represent communications or interactions; they are assumed to be atomic and instantaneous. {comment}
679
-
680
- ## atTime {=prov:atTime .owl:DatatypeProperty label}
681
-
682
- > The time at which an InstantaneousEvent occurred, in the form of xsd:dateTime. {comment @en}
683
-
684
- Sets [dateTime] {+xsd:dateTime ?range} for an [InstantaneousEvent] {+prov:InstantaneousEvent ?sharesDefinitionsWith ?domain}.
685
-
686
- Inverse: [timeOf] {+prov:timeOf ?inverse}
687
-
688
- > This property is not functional because the many values could be at a variety of granularities (In this building, in this room, in that chair). {prov:editorialNote}
689
-
690
- ## atLocation {=prov:atLocation .owl:ObjectProperty label}
691
-
692
- > The Location of any resource. {comment @en}
693
-
694
- Points to a [Location] {+prov:Location ?range ?prov:sharesDefinitionWith} from [Activity] {+prov:Activity ?domain}, [Agent] {+prov:Agent ?domain}, [Entity] {+prov:Entity ?domain}, or [InstantaneousEvent] {+prov:InstantaneousEvent ?domain}.
695
-
696
- Inverse: [locationOf] {prov:inverse}.
697
-
698
- > The naming of prov:atLocation parallels prov:atTime, and is not named prov:hadLocation to avoid conflicting with the convention that prov:had* properties are used on prov:Influence classes. {prov:editorialNote}
699
-
700
- ## Location {=prov:Location .Class label}
701
-
702
- > A location can be an identifiable geographic place (ISO 19112), but it can also be a non-geographic place such as a directory, row, or column. As such, there are numerous ways in which location can be expressed, such as by a coordinate, address, landmark, and so forth. {prov:definition @en}
703
-
704
- See also [atLocation] {+prov:atLocation ?seeAlso}.
705
-
706
-
707
- ==============
708
-
709
- ## Summary
710
-
711
- The core flow establishes the fundamental vocabulary of provenance by introducing three essential concepts that form the bedrock of all provenance modeling. This flow answers the most basic questions in any provenance investigation: "What exists?", "What happens?", and "When and where does it occur?"
712
-
713
- At the heart of this flow lies a fundamental distinction between entities and activities. Entities represent the stable, enduring "things" in our world - documents that persist, datasets that maintain their structure, physical objects that exist over time, or even conceptual ideas that remain fixed. These are the nouns of provenance, the subjects and objects that we track, analyze, and reason about. In contrast, activities represent the dynamic processes - the verbs of provenance that transform, analyze, modify, relocate, or otherwise act upon entities. This clear separation between stable continuants and dynamic occurrents provides the conceptual clarity needed to model complex real-world scenarios.
714
-
715
- Bridging these two concepts are instantaneous events, which mark the precise moments when the world changes. These events capture the transitions - the exact moment an entity comes into being, the instant it gets used, the point when it becomes invalid, or the moments when activities begin or end. By treating these transitions as first-class concepts, PROV-O enables precise temporal reasoning about when and how state changes occur.
716
-
717
- This conceptual framework enables powerful real-world applications across diverse domains. In document management, it provides the language to track versions, transformations, and processing steps through the document lifecycle. For data processing pipelines, it models the computational processes and analytical workflows that turn raw data into insights. Physical asset tracking uses these concepts to monitor manufacturing processes, supply chain movements, and equipment lifecycles from deployment to retirement. Software development teams capture build processes, deployment activities, and code transformations with the same vocabulary.
718
-
719
- The flow's essential properties provide the contextual depth needed for meaningful provenance. The value property allows direct representation of entity characteristics, bridging the gap between abstract provenance tracking and concrete data representation. Time properties anchor all events to precise moments using xsd:dateTime, enabling temporal analysis and chronological reasoning. Location properties provide spatial context, supporting both geographic positioning and non-geographic contexts like directories, containers, or logical positions.
720
-
721
- The design benefits of this core flow extend far beyond simple bookkeeping. The clear separation between entities and activities prevents conceptual confusion and enables clean modeling patterns. Temporal precision through instantaneous events provides exact timing for all state changes, supporting sophisticated temporal queries. Spatial context through location properties enables geographic and logical positioning. Most importantly, this extensible foundation supports all advanced PROV-O patterns, from simple linear chains to complex networks of influence and responsibility.
722
-
723
- By providing this essential vocabulary for describing what exists, what happens, and when/where it occurs, the core flow forms the backbone of complex provenance scenarios. It establishes the conceptual foundation upon which all specialized components and advanced provenance patterns are built, enabling organizations to capture, analyze, and reason about their processes with clarity and precision.
724
-
725
-
726
-
727
-
728
-
729
- {=}
730
-
731
-
732
-
733
- <a id="components-entities-activities-entity-lifecycle"></a>
734
-
735
- [mdp] <https://mdld.js.org/prov/>
736
- [owl] <http://www.w3.org/2002/07/owl#>
737
-
738
- # Entity lifecycle flow
739
-
740
- ## generatedAtTime {=prov:generatedAtTime .owl:DatatypeProperty label}
741
-
742
- > The time at which an entity was completely created and is available for use. {comment @en}
743
-
744
- Sets [dateTime] {+xsd:dateTime ?range} literal for an [entity] {+prov:Entity ?domain}.
745
-
746
- May be qualified by [atTime] {+prov:atTime ?prov:qualifiedForm} in a [Generation] {+prov:Generation ?prov:qualifiedForm} attached to the entity.
747
-
748
- > It is the intent that the property chain holds: (prov:qualifiedGeneration o prov:atTime) rdfs:subPropertyOf prov:generatedAtTime. {prov:editorialNote @en}
749
-
750
- ## wasGeneratedBy {=prov:wasGeneratedBy .owl:ObjectProperty label}
751
-
752
- Records that one [entity] {+prov:Entity ?domain} was generated by an [activity] {+prov:Activity ?range}.
753
-
754
- May be qualified by [qualifiedGeneration] {+prov:qualifiedGeneration ?prov:qualifiedForm} with [Generation] {+prov:Generation ?prov:qualifiedForm} attached.
755
-
756
- Sub-property: [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}
757
-
758
- Inverse: [generated] {prov:inverse}
759
-
760
- ## generated {=prov:generated .owl:ObjectProperty}
761
-
762
- Connects [activities] {+prov:Activity ?domain} to [entities] {+prov:Entity ?range} with a [generation] {+prov:Generation ?prov:sharedDefinitionWith} relation as a sub-property of [influenced] {+prov:influenced ?subPropertyOf}.
763
-
764
- Inverse: [wasGeneratedBy] {prov:inverse} - one of few defined inverse properties - it's the inverse of [wasGeneratedBy] {+prov:wasGeneratedBy ?owl:inverseOf}.
765
-
766
- > prov:generated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions. {comment @en}
767
-
768
-
769
- ## qualifiedGeneration {=prov:qualifiedGeneration owl:ObjectProperty label}
770
-
771
- > If this Activity prov:generated Entity :e, then it can qualify how it performed the Generation using prov:qualifiedGeneration [ a prov:Generation; prov:entity :e; :foo :bar ]. {comment @en}
772
-
773
- Informs that an [entity] {+prov:Entity ?domain} was [generated] {+prov:Generation ?range ?prov:sharesDefinitionWith} by an [activity] {+prov:Activity ?domain}.
774
-
775
- A qualified version of [wasGeneratedBy] {+prov:wasGeneratedBy ?prov:unqualifiedForm}.
776
-
777
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
778
-
779
- Inverse: [qualifiedGenerationOf] {prov:inverse}
780
-
781
-
782
- ## Generation {=prov:Generation .Class label}
783
-
784
- > Generation is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. {prov:definition @en}
785
-
786
- Sub-class of [ActivityInfluence] {+prov:ActivityInfluence ?subClassOf} and [InstantaneousEvent] {+prov:InstantaneousEvent ?subClassOf}.
787
-
788
- > An instance of prov:Generation provides additional descriptions about the binary prov:wasGeneratedBy relation from a generated prov:Entity to the prov:Activity that generated it. For example, :cake prov:wasGeneratedBy :baking; prov:qualifiedGeneration [ a prov:Generation; prov:activity :baking; :foo :bar ]. {comment @en}
789
-
790
- ## invalidatedAtTime {=prov:invalidatedAtTime .owl:DatatypeProperty label}
791
-
792
- > The time at which an entity was invalidated (i.e., no longer usable). {comment @en}
793
-
794
- Sets [dateTime] {+xsd:dateTime ?range} literal for an [entity] {+prov:Entity ?domain}.
795
-
796
- May be qualified by [atTime] {+prov:atTime ?prov:qualifiedForm} in an [Invalidation] {+prov:Invalidation ?prov:qualifiedForm} attached to the entity.
797
-
798
- > It is the intent that the property chain holds: (prov:qualifiedInvalidation o prov:atTime) rdfs:subPropertyOf prov:invalidatedAtTime. {prov:editorialNote @en}
799
-
800
- ## wasInvalidatedBy {=prov:wasInvalidatedBy .owl:ObjectProperty label}
801
-
802
- Connects an [entity] {+prov:Entity ?domain} to an [activity] {+prov:Activity ?range} that terminated it.
803
-
804
- May be qualified by a [qualifiedInvalidation] {+prov:qualifiedInvalidation ?prov:qualifiedForm} with [Invalidation] {+prov:Invalidation ?prov:qualifiedForm} attached.
805
-
806
- Sub-property of [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}.
807
-
808
- Inverse: [invalidated] {prov:inverse}
809
-
810
- ## invalidated {=prov:invalidated .owl:ObjectProperty label}
811
-
812
- > prov:invalidated is one of few inverse property defined, to allow Activity-oriented assertions in addition to Entity-oriented assertions. {prov:editorialNote @en}
813
-
814
- Connects an [Activity] {+prov:Activity ?domain} with an [Entity] {+prov:Entity ?range} that was [invalidated] {+prov:Invalidation ?prov:sharesDefinitionWith} by it.
815
-
816
- A sub-property of [influenced] {+prov:influenced ?subPropertyOf}.
817
-
818
- Inverse: [wasInvalidatedBy] {prov:inverse}.
819
-
820
- ## qualifiedInvalidation {=prov:qualifiedInvalidation owl:ObjectProperty label}
821
-
822
- > If this Entity prov:wasInvalidatedBy Activity :a, then it can qualify how it was invalidated using prov:qualifiedInvalidation [ a prov:Invalidation; prov:activity :a; :foo :bar ]. {comment @en}
823
-
824
- Records the [invalidation] {+prov:Invalidation ?range ?prov:sharesDefinitionWith} of an [entity] {+prov:Entity ?domain} by an [activity] {+prov:Activity ?domain}.
825
-
826
- A qualified version of [wasInvalidatedBy] {+prov:wasInvalidatedBy ?prov:unqualifiedForm}.
827
-
828
- Inverse: [qualifiedInvalidationOf] {prov:inverse}
829
-
830
- ## Invalidation {=prov:Invalidation .Class label}
831
-
832
- Sub-class of [ActivityInfluence] {+prov:ActivityInfluence ?subClassOf} and [InstantaneousEvent] {+prov:InstantaneousEvent ?subClassOf}.
833
-
834
- > Invalidation is the start of the destruction, cessation, or expiry of an existing entity by an activity. The entity is no longer available for use (or further invalidation) after invalidation. Any generation or usage of an entity precedes its invalidation. {prov:definition}
835
-
836
- > Given that an invalidation is the start of destruction, cessation, or expiry, it is instantaneous. {comment}
837
-
838
- Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end.
839
-
840
- ==============
841
-
842
- ## Summary
843
-
844
- The entity lifecycle flow captures the fundamental story of how entities come into existence, persist through time, and eventually cease to be. This flow provides the temporal backbone of provenance by modeling the complete journey of entities from their birth through their active life to their eventual death.
845
-
846
- At its core, this flow addresses a critical question in provenance: "When did this thing exist, and what brought it into or out of existence?" The answer unfolds through a clear pattern of generation and invalidation events, each precisely timed and causally linked to specific activities. Every entity begins with a generation moment - a discrete point in time when an activity completes the creation of something new and makes it available for use. This entity then exists stably until its invalidation moment, when another activity terminates its existence and renders it unavailable.
847
-
848
- This temporal framing enables powerful real-world applications. In document management, it tracks when reports are created, published, and eventually deprecated, providing clear audit trails for compliance and governance. For data systems, it monitors freshness windows and expiration schedules, ensuring consumers know exactly when datasets become valid or obsolete. In physical asset tracking, it follows equipment from deployment through maintenance cycles to retirement, supporting lifecycle management and resource planning.
849
-
850
- The flow's strength lies in its precise temporal precision. The generatedAtTime and invalidatedAtTime properties establish exact boundaries for entity existence, while the atTime property in qualified forms provides event-level granularity. This temporal accuracy supports sophisticated queries about entity overlap, validity periods, and temporal relationships between different entities.
851
-
852
- Crucially, the flow maintains clear activity relationships through bidirectional properties. The wasGeneratedBy and wasInvalidatedBy relations link entities to their responsible activities, while their inverse properties (generated, invalidated) enable activity-centric queries. This dual perspective allows analysts to ask both "What did this activity create?" and "What created this entity?" depending on their investigative needs.
853
-
854
- The qualified forms through Generation and Invalidation classes enrich these basic relationships with contextual depth. They capture not just that an entity was generated, but how, where, by whom, and under what circumstances. Similarly, invalidation events can include details about termination reasons, processes, and environmental conditions. This contextual richness transforms simple temporal bookkeeping into meaningful provenance narratives.
855
-
856
- By providing complete lifecycle coverage with temporal accuracy and activity integration, this flow becomes the foundation for temporal analysis, compliance reporting, and resource management. It enables organizations to answer critical questions about entity evolution, maintain audit trails for regulatory requirements, and optimize resource usage through precise lifecycle understanding.
857
-
858
-
859
-
860
-
861
-
862
-
863
- {=}
864
-
865
-
866
-
867
- <a id="components-entities-activities-activity-lifecycle"></a>
868
-
869
- [mdp] <https://mdld.js.org/prov/>
870
- [owl] <http://www.w3.org/2002/07/owl#>
871
-
872
- # Activity lifecycle flow
873
-
874
- ## startedAtTime {=prov:startedAtTime .owl:DatatypeProperty label}
875
-
876
- > The time at which an activity started. See also prov:endedAtTime. {comment @en}
877
-
878
- Sets starting [dateTime] {+xsd:dateTime ?range} literal for an [activity] {+prov:Activity ?sharesDefinitionsWith ?domain}.
879
-
880
- May be qualified by [atTime] {+prov:atTime ?prov:qualifiedForm} in a [Start] {+prov:Start ?prov:qualifiedForm} attached to the activity.
881
-
882
- > It is the intent that the property chain holds: (prov:qualifiedStart o prov:atTime) rdfs:subPropertyOf prov:startedAtTime. {prov:editorialNote @en}
883
-
884
- ## wasStartedBy {=prov:wasStartedBy .owl:ObjectProperty label}
885
-
886
- > Start is when an activity is deemed to have started. A start may refer to an entity, known as trigger, that initiated the activity. {comment @en}
887
-
888
- Connects an [activity] {+prov:Activity ?domain} to an [entity] {+prov:Entity ?range} that initiated it.
889
-
890
- May be qualified by a [qualifiedStart] {+prov:qualifiedStart ?prov:qualifiedForm} with [Start] {+prov:Start ?prov:qualifiedForm} attached.
891
-
892
- Sub-property of [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}.
893
-
894
- Inverse: [started] {prov:inverse}
895
-
896
- ## qualifiedStart {=prov:qualifiedStart owl:ObjectProperty label}
897
-
898
- > If this Activity prov:wasStartedBy Entity :e1, then it can qualify how it was started using prov:qualifiedStart [ a prov:Start; prov:entity :e1; :foo :bar ]. {comment @en}
899
-
900
- Adds a [Start] {+prov:Start ?range ?prov:sharesDefinitionWith} to an [activity] {+prov:Activity ?domain}.
901
-
902
- A qualified version of [wasStartedBy] {+prov:wasStartedBy ?prov:unqualifiedForm}.
903
-
904
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
905
-
906
- Inverse: [qualifiedStartOf] {prov:inverse}
907
-
908
- ## Start {=prov:Start .Class label}
909
-
910
- > Start is when an activity is deemed to have been started by an entity, known as trigger. The activity did not exist before its start. Any usage, generation, or invalidation involving an activity follows the activity's start. A start may refer to a trigger entity that set off the activity, or to an activity, known as starter ◊, that generated the trigger. {prov:definition @en}
911
-
912
- > An instance of prov:Start provides additional descriptions about the binary prov:wasStartedBy relation from some started prov:Activity to an prov:Entity that started it. For example, :foot_race prov:wasStartedBy :bang; prov:qualifiedStart [ a prov:Start; prov:entity :bang; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ] . {comment @en}
913
-
914
-
915
- ## endedAtTime {=prov:endedAtTime .owl:DatatypeProperty label}
916
-
917
- > The time at which an activity ended. See also prov:startedAtTime. {comment @en}
918
-
919
- Sets ending [dateTime] {+xsd:dateTime ?range} literal for an [activity] {+prov:Activity ?sharesDefinitionsWith ?domain}.
920
-
921
- May be qualified by [atTime] {+prov:atTime ?prov:qualifiedForm} in an [End] {+prov:End ?prov:qualifiedForm} attached to the activity.
922
-
923
- > It is the intent that the property chain holds: (prov:qualifiedEnd o prov:atTime) rdfs:subPropertyOf prov:endedAtTime. {prov:editorialNote @en}
924
-
925
-
926
- ## wasEndedBy {=prov:wasEndedBy .owl:ObjectProperty label}
927
-
928
- > End is when an activity is deemed to have ended. An end may refer to an entity, known as trigger, that terminated the activity. {comment @en}
929
-
930
- Records that one [activity] {+prov:Activity ?domain} was ended by a [trigger] {+prov:Entity ?range} that terminated it.
931
-
932
- May be qualified by [qualifiedEnd] {+prov:qualifiedEnd ?prov:qualifiedForm} with [End] {+prov:End ?prov:qualifiedForm} attached.
933
-
934
- Sub-property: [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}
935
-
936
- Inverse: [ended] {prov:inverse}
937
-
938
- ## qualifiedEnd {=prov:qualifiedEnd owl:ObjectProperty label}
939
-
940
- > If this Activity prov:wasEndedBy Entity :e1, then it can qualify how it was ended using prov:qualifiedEnd [ a prov:End; prov:entity :e1; :foo :bar ]. {comment @en}
941
-
942
- Informs that an [activity] {+prov:Activity ?domain} was [ended] {+prov:End ?range ?prov:sharesDefinitionWith} by an [entity] {+prov:Entity ?domain}.
943
-
944
- A qualified version of [wasEndedBy] {+prov:wasEndedBy ?prov:unqualifiedForm}.
945
-
946
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
947
-
948
- Inverse: [qualifiedEndOf] {prov:inverse}
949
-
950
- ## End {=prov:End .Class label}
951
-
952
- Sub-class of [EntityInfluence] {+prov:EntityInfluence ?subClassOf} and [InstantaneousEvent] {+prov:InstantaneousEvent ?subClassOf}.
953
-
954
- > End is when an activity is deemed to have been ended by an entity, known as trigger. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to a trigger entity that terminated the activity, or to an activity, known as ender ◊ that generated the trigger. {prov:definition @en}
955
-
956
- > An instance of prov:End provides additional descriptions about the binary prov:wasEndedBy relation from some ended prov:Activity to an prov:Entity that ended it. For example, :ball_game prov:wasEndedBy :buzzer; prov:qualifiedEnd [ a prov:End; prov:entity :buzzer; :foo :bar; prov:atTime '2012-03-09T08:05:08-05:00'^^xsd:dateTime ]. {comment @en}
957
-
958
- ==============
959
-
960
- ## Summary
961
-
962
- The activity lifecycle flow captures the temporal boundaries and triggering mechanisms of activities, modeling how dynamic processes begin, execute, and eventually conclude. This flow provides the essential framework for understanding the temporal dimension of processes - when they start, what initiates them, when they end, and what terminates them.
963
-
964
- At its core, this flow addresses a fundamental question in process provenance: "When did this activity occur, and what brought it into or out of existence?" The answer emerges through a clear pattern of start and end events, each precisely timed and causally linked to triggering entities. Every activity begins with a start moment - a discrete point when the activity transitions from non-existence to active execution. This start may be triggered by an entity that serves as the catalyst, such as a timer event, a command signal, or a prerequisite condition being met. The activity then executes through its duration until its end moment, when another entity triggers its termination and the activity ceases to exist.
965
-
966
- This temporal framework enables sophisticated process management across diverse domains. In workflow orchestration, it tracks when automated processes begin based on schedule triggers or input availability, and when they complete successfully or terminate due to error conditions. For computational pipelines, it monitors job initiation from queue systems and completion through success or failure signals. In manufacturing processes, it captures production line activation from start buttons and shutdown through safety triggers or completion sensors. Project management uses these concepts to track task initiation from authorization and completion through deliverable submission.
967
-
968
- The flow's temporal precision provides the foundation for process analysis and optimization. The startedAtTime and endedAtTime properties establish exact boundaries for activity execution, enabling duration calculations, overlap detection, and performance metrics. The atTime property in qualified forms offers event-level granularity, capturing the precise moments when triggers occur and when activities transition between states.
969
-
970
- Crucially, the flow maintains clear trigger relationships through bidirectional properties. The wasStartedBy and wasEndedBy relations link activities to their triggering entities, while their inverse properties (started, ended) enable entity-centric queries. This dual perspective allows analysts to ask both "What activities did this trigger start?" and "What triggered this activity?" depending on their investigative needs.
971
-
972
- The qualified forms through Start and End classes enrich these basic relationships with contextual depth. They capture not just that an activity started, but how, where, by whom, and under what environmental conditions. Similarly, end events can include details about termination reasons, completion status, and contextual factors. This contextual richness transforms simple temporal bookkeeping into meaningful process narratives that support root cause analysis and process improvement.
973
-
974
- By providing complete temporal coverage with trigger integration and contextual enhancement, this flow becomes the foundation for process monitoring, performance analysis, and operational intelligence. It enables organizations to answer critical questions about process efficiency, maintain audit trails for operational compliance, and optimize workflows through precise temporal understanding and trigger analysis.
975
-
976
-
977
-
978
-
979
-
980
-
981
-
982
- {=}
983
-
984
-
985
-
986
- <a id="components-entities-activities-usage"></a>
987
-
988
- [mdp] <https://mdld.js.org/prov/>
989
- [owl] <http://www.w3.org/2002/07/owl#>
990
-
991
- # Usage of entities by activities flow
992
-
993
- ## used {=prov:used .owl:ObjectProperty label}
994
-
995
- > A prov:Entity that was used by this prov:Activity. For example, :baking prov:used :spoon, :egg, :oven . {comment @en}
996
-
997
- Adds an [entity] {+prov:Entity ?range} to an [activity] {+prov:Activity ?domain}.
998
-
999
- May be qualified by [qualifiedUsage] {+prov:qualifiedUsage ?prov:qualifiedForm} with [Usage] {+prov:Usage ?prov:qualifiedForm} attached.
1000
-
1001
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1002
-
1003
- Inverse: [qualifiedUsage] {prov:inverse}
1004
-
1005
- ## qualifiedUsage {=prov:qualifiedUsage owl:ObjectProperty label}
1006
-
1007
- > If this Activity prov:used Entity :e, then it can qualify how it used it using prov:qualifiedUsage [ a prov:Usage; prov:entity :e; :foo :bar ]. {comment @en}
1008
-
1009
- Adds a [Usage] {+prov:Usage ?range ?prov:sharesDefinitionWith} to an [activity] {+prov:Activity ?domain}.
1010
-
1011
- A qualified version of [used] {+prov:used ?prov:unqualifiedForm}.
1012
-
1013
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1014
-
1015
- Inverse: [qualifiedUsingActivity] {prov:inverse}
1016
-
1017
- ## Usage {=prov:Usage .Class label}
1018
-
1019
- > Usage is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.) {prov:definition @en}
1020
-
1021
- Sub-class of [EntityInfluence] {+prov:EntityInfluence ?subClassOf} and [InstantaneousEvent] {+prov:InstantaneousEvent ?subClassOf}.
1022
-
1023
- > Given that a usage is the beginning of utilizing an entity, it is instantaneous. {comment @en}
1024
-
1025
- ==============
1026
-
1027
- ## Summary
1028
-
1029
- The usage flow captures the precise moment when activities begin consuming entities, establishing the fundamental input relationships that drive all transformations. This flow answers the critical question: "What resources did this activity use, and when did that consumption begin?"
1030
-
1031
- Usage marks the instantaneous transition when entities move from being passive resources to active inputs that influence activity behavior. This temporal precision enables powerful dependency tracking across computational workflows, manufacturing processes, and research pipelines. By capturing the exact moment resources become available to activities, the flow supports sophisticated analysis of resource consumption patterns, process optimization, and audit trail maintenance.
1032
-
1033
- The bidirectional used relationship provides flexible querying - both "What did this activity consume?" and "Which activities used this resource?" - while qualified Usage classes enrich these relationships with contextual depth about how, where, and under what conditions resources were applied. This combination of precise timing and contextual richness transforms simple resource tracking into meaningful provenance narratives that support optimization, debugging, and compliance reporting.
1034
-
1035
-
1036
-
1037
-
1038
-
1039
-
1040
- {=}
1041
-
1042
-
1043
-
1044
- <a id="components-entities-activities-communication"></a>
1045
-
1046
- [mdp] <https://mdld.js.org/prov/>
1047
- [owl] <http://www.w3.org/2002/07/owl#>
1048
-
1049
- # Inter-activity communication flow
1050
-
1051
- ## wasInformedBy {=prov:wasInformedBy .owl:ObjectProperty label}
1052
-
1053
- > An activity a2 is dependent on or informed by another activity a1, by way of some unspecified entity that is generated by a1 and used by a2. {comment @en}
1054
-
1055
- Connects one [activity] {+prov:Activity ?domain} to another [activity] {+prov:Activity ?range}.
1056
-
1057
- May be qualified by [qualifiedCommunication] {+prov:qualifiedCommunication ?prov:qualifiedForm} with [Communication] {+prov:Communication ?prov:qualifiedForm} attached.
1058
-
1059
- Sub-property of [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}.
1060
-
1061
- Inverse: [informed] {prov:inverse}.
1062
-
1063
- ## qualifiedCommunication {=prov:qualifiedCommunication .owl:ObjectProperty label}
1064
-
1065
- > If this Activity prov:wasInformedBy Activity :a, then it can qualify how it was influenced using prov:qualifiedCommunication [ a prov:Communication; prov:activity :a; :foo :bar ]. {comment @en}
1066
-
1067
- Clarifies if an [activity] {+prov:Activity ?domain} was [communicated] {+prov:Communication ?range ?prov:sharesDefinitionWith ?prov:qualifiedForm} by another one.
1068
-
1069
- Sub-property of [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}.
1070
-
1071
- Inverse: [qualifiedCommunicationOf] {prov:inverse}.
1072
-
1073
- ## Communication {=prov:Communication .Class label}
1074
-
1075
- Sub-class of [ActivityInfluence] {+prov:ActivityInfluence ?subClassOf}.
1076
-
1077
- Qualifies the [wasInformedBy] {+prov:wasInformedBy ?prov:unqualifiedForm}.
1078
-
1079
- > Communication is the exchange of some unspecified entity by two activities, one activity using some entity generated by the other. {prov:definition}
1080
-
1081
- > A communication implies that activity a2 is dependent on another a1, by way of some unspecified entity that is generated by a1 and used by a2. {comment}
1082
-
1083
- ==============
1084
-
1085
- ## Summary
1086
-
1087
- The communication flow captures the essential dependency relationships between activities, modeling how processes inform and influence each other through the exchange of entities. This flow answers the fundamental question: "Which activities influenced this activity, and through what communication channels?"
1088
-
1089
- Communication represents the exchange of entities between activities - where one activity generates something that another activity subsequently uses. This creates a dependency chain where the informed activity relies on the informing activity's output, establishing clear causal relationships in complex workflows. The flow provides the backbone for understanding process orchestration, pipeline dependencies, and workflow coordination across diverse domains.
1090
-
1091
- The wasInformedBy relationship connects activities in a directed dependency graph, enabling sophisticated analysis of process chains, bottleneck identification, and impact assessment. The bidirectional properties support flexible querying - both "What influenced this activity?" and "Which activities did this influence?" - while qualified Communication classes enrich these relationships with contextual detail about the nature and circumstances of the communication.
1092
-
1093
- By capturing these inter-activity dependencies, the flow becomes essential for workflow optimization, root cause analysis, and process improvement initiatives. It enables organizations to understand how processes connect, identify critical paths, and maintain comprehensive audit trails of process coordination and information flow.
1094
-
1095
-
1096
-
1097
-
1098
-
1099
-
1100
- {=}
1101
-
1102
-
1103
-
1104
- <a id="components-derivations-index"></a>
1105
-
1106
- [mdp] <https://mdld.js.org/prov/>
1107
- [owl] <http://www.w3.org/2002/07/owl#>
1108
-
1109
- # Derivations {=mdp:components#derivations .mdp:Component label}
1110
-
1111
- The second component of PROV-DM is concerned with: derivations of entities from other entities and derivation subtypes WasRevisionOf (Revision), WasQuotedFrom (Quotation), and HasPrimarySource (Primary Source). Figure 6 depicts the third component with PROV core structures in the yellow area, including two classes (Entity, Activity) and binary association WasDerivedFrom (Derivation). PROV extended structures are found outside this area. UML association classes express expanded n-ary relations. The subclasses are marked by the UML stereotype "prov:type" to indicate that the corresponding types are valid values for the attribute prov:type.
1112
-
1113
- ![](./components/derivations/component2.png)
1114
-
1115
- [Derivation flow](#components-derivations-derivation)
1116
- [Revision flow](#components-derivations-revision)
1117
- [Quotation flow](#components-derivations-quotation)
1118
- [Primary Source flow](#components-derivations-source)
1119
- [Influence flow](#components-derivations-influence)
1120
-
1121
- ## Summary
1122
-
1123
- The PROV-O Derivations component is organized into clear flows that model how entities are transformed, updated, or constructed from other entities. Each flow follows a consistent pattern of binary relations, qualified forms, and influence classes.
1124
-
1125
- **Flow Architecture:**
1126
- Each derivation type follows the same three-part pattern:
1127
- 1. **Binary Relation** (e.g., `wasDerivedFrom`, `wasRevisionOf`)
1128
- 2. **Qualified Form** (e.g., `qualifiedDerivation`, `qualifiedRevision`)
1129
- 3. **Influence Class** (e.g., `Derivation`, `Revision`)
1130
-
1131
- **Core Flows:**
1132
-
1133
- **1. Derivation Flow** - Foundation for all entity transformations
1134
- - `wasDerivedFrom` → `qualifiedDerivation` → `Derivation`
1135
- - Base relation for all entity-to-entity transformations
1136
- - Enhanced with `hadGeneration` and `hadUsage` properties
1137
-
1138
- **2. Revision Flow** - Versioning and content updates
1139
- - `wasRevisionOf` → `qualifiedRevision` → `Revision`
1140
- - Specializes derivation for versioned entities with substantial original content
1141
- - Sub-property of `wasDerivedFrom`
1142
-
1143
- **3. Quotation Flow** - Copying and attribution
1144
- - `wasQuotedFrom` → `qualifiedQuotation` → `Quotation`
1145
- - Handles copying/quoting of entity content
1146
- - Sub-property of `wasDerivedFrom`
1147
-
1148
- **4. Primary Source Flow** - Source citation and authority
1149
- - `hadPrimarySource` → `qualifiedPrimarySource` → `PrimarySource`
1150
- - Connects secondary entities to authoritative primary sources
1151
- - Sub-property of `wasDerivedFrom`
1152
-
1153
- **5. Influence Flow** - Cross-cutting enhancement mechanisms
1154
- - `hadActivity` → `qualifiedInfluence` → `Influence`
1155
- - Connects all influence types to activities and provides broad influence modeling
1156
- - Supports delegation, derivation, end, and start processes
1157
-
1158
- **Hierarchy and Relationships:**
1159
- ```
1160
- Influence (broadest)
1161
- ├── EntityInfluence
1162
- │ └── Derivation
1163
- │ ├── Revision
1164
- │ ├── Quotation
1165
- │ └── PrimarySource
1166
- └── qualifiedInfluence (supports all qualified forms)
1167
- ```
1168
-
1169
- **Benefits of Flow Organization:**
1170
- - Clear separation of derivation types
1171
- - Consistent patterns across all flows
1172
- - Easy navigation between related concepts
1173
- - Direct mapping from simple to complex provenance descriptions
1174
- - Modular understanding of derivation mechanisms
1175
-
1176
-
1177
-
1178
-
1179
-
1180
-
1181
- {=}
1182
-
1183
-
1184
-
1185
- <a id="components-derivations-derivation"></a>
1186
-
1187
- [mdp] <https://mdld.js.org/prov/>
1188
- [owl] <http://www.w3.org/2002/07/owl#>
1189
-
1190
- # Derivation flow
1191
- ==================
1192
-
1193
- ## wasDerivedFrom {=prov:wasDerivedFrom .owl:ObjectProperty label}
1194
-
1195
- > The more specific subproperties of prov:wasDerivedFrom (i.e., prov:wasQuotedFrom, prov:wasRevisionOf, prov:hadPrimarySource) should be used when applicable. {comment @en}
1196
-
1197
- > A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity. {comment @en}
1198
-
1199
- Records that one [entity] {+prov:Entity ?domain} was derived from [another] {+prov:Entity ?range}.
1200
-
1201
- May be qualified by [qualifiedDerivation] {+prov:qualifiedDerivation ?prov:qualifiedForm} with [Derivation] {+prov:Derivation ?prov:qualifiedForm} attached.
1202
-
1203
- Sub-property: [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}
1204
-
1205
- Inverse: [hadDerivation] {prov:inverse}
1206
-
1207
- ## qualifiedDerivation {=prov:qualifiedDerivation owl:ObjectProperty label}
1208
-
1209
- > If this Entity prov:wasDerivedFrom Entity :e, then it can qualify how it was derived using prov:qualifiedDerivation [ a prov:Derivation; prov:entity :e; :foo :bar ]. {comment @en}
1210
-
1211
- Informs that an [entity] {+prov:Entity ?domain} was [derived] {+prov:Derivation ?range ?prov:sharesDefinitionWith} from another entity.
1212
-
1213
- A qualified version of [wasDerivedFrom] {+prov:wasDerivedFrom ?prov:unqualifiedForm}.
1214
-
1215
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1216
-
1217
- Inverse: [qualifiedDerivationOf] {prov:inverse}
1218
-
1219
- ## Derivation {=prov:Derivation .Class label}
1220
-
1221
- Sub-class of [EntityInfluence] {+prov:EntityInfluence ?subClassOf}.
1222
-
1223
- > A derivation is a transformation of an entity into another, an update of an entity resulting in a new one, or the construction of a new entity based on a pre-existing entity. {prov:definition @en}
1224
-
1225
- > An instance of prov:Derivation provides additional descriptions about the binary prov:wasDerivedFrom relation from some derived prov:Entity to another prov:Entity from which it was derived. For example, :chewed_bubble_gum prov:wasDerivedFrom :unwrapped_bubble_gum; prov:qualifiedDerivation [ a prov:Derivation; prov:entity :unwrapped_bubble_gum; :foo :bar ]. {comment @en}
1226
-
1227
- > The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation, prov:PrimarySource) should be asserted if they apply. {comment @en}
1228
-
1229
- Has 3 sub-classes: [PrimarySource] {+prov:PrimarySource !subClassOf}, [Quotation] {+prov:Quotation !subClassOf} and [Revision] {+prov:Revision !subClassOf}.
1230
-
1231
- ## hadGeneration {=prov:hadGeneration .owl:ObjectProperty label}
1232
-
1233
- > The _optional_ Generation involved in an Entity's Derivation. {comment @en}
1234
-
1235
- Points to an optional explicit [generation] {+prov:Generation ?prov:sharesDefinitionWith ?range} that influenced [derivation] {+prov:Derivation ?domain} of an entity.
1236
-
1237
- Inverse: [generatedAsDerivation] {prov:inverse}.
1238
-
1239
- ### hadUsage {=prov:hadUsage .owl:ObjectProperty label}
1240
-
1241
- > The _optional_ Usage involved in an Entity's Derivation. {comment @en}
1242
-
1243
- It describes that an entity was [used] {+prov:Usage ?range ?prov:sharesDefinitionWith} during a [Derivation] {+prov:Derivation ?domain}.
1244
-
1245
- Inverse: [wasUsedInDerivation] {prov:inverse}.
1246
-
1247
- ==============
1248
-
1249
- ## Summary
1250
-
1251
- The derivation flow captures the fundamental transformation relationship between entities, modeling how one entity is created, updated, or constructed from another. This flow answers the essential question: "What was this entity derived from, and through what transformation process?"
1252
-
1253
- Derivation represents the core concept of entity transformation - whether through direct modification, computational processing, or creative construction. It establishes the foundational lineage that enables tracking how entities evolve, combine, or are repurposed across complex workflows. This flow provides the backbone for understanding data provenance, document evolution, and material transformation across diverse domains.
1254
-
1255
- The wasDerivedFrom relationship creates clear transformation chains that support sophisticated analysis of entity evolution, impact assessment, and dependency tracking. The bidirectional properties enable flexible querying - both "What was this derived from?" and "What was derived from this?" - while qualified Derivation classes enrich these relationships with contextual detail about generation and usage processes involved in transformation.
1256
-
1257
- By capturing the essential transformation relationships with contextual enhancement, the flow becomes the foundation for provenance analysis, audit trail maintenance, and process understanding. It enables organizations to answer critical questions about entity evolution, maintain comprehensive transformation histories, and support compliance requirements through detailed derivation tracking.
1258
-
1259
-
1260
-
1261
-
1262
-
1263
-
1264
-
1265
- {=}
1266
-
1267
-
1268
-
1269
- <a id="components-derivations-revision"></a>
1270
-
1271
- [mdp] <https://mdld.js.org/prov/>
1272
- [owl] <http://www.w3.org/2002/07/owl#>
1273
-
1274
- # Revision flow
1275
- ================
1276
-
1277
- ## wasRevisionOf {=prov:wasRevisionOf .owl:ObjectProperty label}
1278
-
1279
- > A revision is a derivation that revises an entity into a revised version. {comment @en}
1280
-
1281
- Connects one [entity] {+prov:Entity ?domain} to [another] {+prov:Entity ?range} that is a revised version of it.
1282
-
1283
- May be qualified by [qualifiedRevision] {+prov:qualifiedRevision ?prov:qualifiedForm} with a [Revision] {+prov:Revision ?prov:qualifiedForm}.
1284
-
1285
- Sub-property of [wasDerivedFrom] {+prov:wasDerivedFrom ?subPropertyOf}.
1286
-
1287
- Inverse: [hadRevision] {prov:inverse}
1288
-
1289
- ## qualifiedRevision {=prov:qualifiedRevision owl:ObjectProperty label}
1290
-
1291
- > If this Entity prov:wasRevisionOf Entity :e, then it can qualify how it was revised using prov:qualifiedRevision [ a prov:Revision; prov:entity :e; :foo :bar ]. {comment @en}
1292
-
1293
- Adds a [Revision] {+prov:Revision ?range ?prov:sharesDefinitionWith} to an [entity] {+prov:Entity ?domain}.
1294
-
1295
- A qualified version of [wasRevisionOf] {+prov:wasRevisionOf ?prov:unqualifiedForm}.
1296
-
1297
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1298
-
1299
- Inverse: [revisedEntity] {prov:inverse}
1300
-
1301
- ## Revision {=prov:Revision .Class label}
1302
-
1303
- Sub-class of [Derivation] {+prov:Derivation ?subClassOf}.
1304
-
1305
- > A revision is a derivation for which the resulting entity is a revised version of some original. The implication here is that the resulting entity contains substantial content from the original. Revision is a particular case of derivation. {prov:definition @en}
1306
-
1307
- > An instance of prov:Revision provides additional descriptions about the binary prov:wasRevisionOf relation from some newer prov:Entity to an earlier prov:Entity. For example, :draft_2 prov:wasRevisionOf :draft_1; prov:qualifiedRevision [ a prov:Revision; prov:entity :draft_1; :foo :bar ]. {comment @en}
1308
-
1309
- ==============
1310
-
1311
- ## Summary
1312
-
1313
- The revision flow captures the versioning relationship between entities, modeling how one entity becomes an updated version of another. This flow answers the essential question: "What is this entity a revision of, and what original content does it preserve?"
1314
-
1315
- Revision represents a specialized derivation where the new entity contains substantial content from its original while incorporating updates or corrections. This creates clear version chains that enable tracking document evolution, software releases, and content refinement across diverse workflows. The flow provides the backbone for understanding how entities evolve through controlled updates rather than complete transformations.
1316
-
1317
- The wasRevisionOf relationship establishes precise version lineage that supports sophisticated analysis of content evolution, change tracking, and version management. The bidirectional properties enable flexible querying - both "What is this a revision of?" and "What revisions exist for this entity?" - while qualified Revision classes enrich these relationships with contextual detail about the revision process and circumstances.
1318
-
1319
- By capturing structured version relationships with contextual enhancement, the flow becomes essential for document management, software versioning, and content governance. It enables organizations to maintain clear audit trails, support rollback capabilities, and understand content evolution through precise revision tracking.
1320
-
1321
-
1322
-
1323
-
1324
-
1325
-
1326
-
1327
- {=}
1328
-
1329
-
1330
-
1331
- <a id="components-derivations-quotation"></a>
1332
-
1333
- [mdp] <https://mdld.js.org/prov/>
1334
- [owl] <http://www.w3.org/2002/07/owl#>
1335
-
1336
- # Quotation flow
1337
- =================
1338
-
1339
- ## wasQuotedFrom {=prov:wasQuotedFrom .owl:ObjectProperty label}
1340
-
1341
- > An entity is derived from an original entity by copying, or 'quoting', some or all of it. {comment @en}
1342
-
1343
- Connects an [entity] {+prov:Entity ?domain} to another [entity] {+prov:Entity ?range} that is quoted from it.
1344
-
1345
- May be qualified by a [qualifiedQuotation] {+prov:qualifiedQuotation ?prov:qualifiedForm} with [Quotation] {+prov:Quotation ?prov:qualifiedForm} attached.
1346
-
1347
- Sub-property of [wasDerivedFrom] {+prov:wasDerivedFrom ?subPropertyOf}.
1348
-
1349
- Inverse: [quotedAs] {prov:inverse}
1350
-
1351
- ## qualifiedQuotation {=prov:qualifiedQuotation owl:ObjectProperty label}
1352
-
1353
- > If this Entity prov:wasQuotedFrom Entity :e, then it can qualify how using prov:qualifiedQuotation [ a prov:Quotation; prov:entity :e; :foo :bar ]. {comment @en}
1354
-
1355
- Adds a [Quotation] {+prov:Quotation ?range ?prov:sharesDefinitionWith} to an [entity] {+prov:Entity ?domain}.
1356
-
1357
- A qualified version of [wasQuotedFrom] {+prov:wasQuotedFrom ?prov:unqualifiedForm}.
1358
-
1359
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1360
-
1361
- Inverse: [qualifiedQuotationOf] {prov:inverse}
1362
-
1363
- ## Quotation {=prov:Quotation .Class label}
1364
-
1365
- Sub-class of [Derivation] {+prov:Derivation ?subClassOf}.
1366
-
1367
- > A quotation is the repeat of (some or all of) an entity, such as text or image, by someone who may or may not be its original author. Quotation is a particular case of derivation. {prov:definition @en}
1368
-
1369
- > An instance of prov:Quotation provides additional descriptions about the binary prov:wasQuotedFrom relation from some taken prov:Entity from an earlier, larger prov:Entity. For example, :here_is_looking_at_you_kid prov:wasQuotedFrom :casablanca_script; prov:qualifiedQuotation [ a prov:Quotation; prov:entity :casablanca_script; :foo :bar ]. {comment @en}
1370
-
1371
- ==============
1372
-
1373
- ## Summary
1374
-
1375
- The quotation flow captures the referencing relationship between entities, modeling how one entity incorporates content from another through direct copying or citation. This flow answers the essential question: "What does this entity quote, and from what source material?"
1376
-
1377
- Quotation represents a specialized derivation where content is extracted from an original entity and incorporated into a new one, whether by the original author or another party. This creates clear attribution chains that enable tracking intellectual property, academic citations, and content reuse across diverse workflows. The flow provides the backbone for understanding how knowledge and creative works build upon existing sources.
1378
-
1379
- The wasQuotedFrom relationship establishes precise citation lineage that supports sophisticated analysis of content provenance, intellectual property tracking, and source attribution. The bidirectional properties enable flexible querying - both "What does this quote?" and "What quotes this source?" - while qualified Quotation classes enrich these relationships with contextual detail about the quoting process and circumstances.
1380
-
1381
- By capturing structured quotation relationships with contextual enhancement, the flow becomes essential for academic publishing, content management, and intellectual property governance. It enables organizations to maintain clear attribution trails, support citation analysis, and understand content reuse through precise quotation tracking.
1382
-
1383
-
1384
-
1385
-
1386
-
1387
- {=}
1388
-
1389
-
1390
-
1391
- <a id="components-derivations-source"></a>
1392
-
1393
- [mdp] <https://mdld.js.org/prov/>
1394
- [owl] <http://www.w3.org/2002/07/owl#>
1395
-
1396
- # Primary Source flow
1397
- =======================
1398
-
1399
- ## hadPrimarySource {=prov:hadPrimarySource .owl:ObjectProperty label}
1400
-
1401
- Connects two [entities] {+prov:Entity ?domain ?range} with a source relation that is a sub-property of [wasDerivedFrom] {+prov:wasDerivedFrom ?subPropertyOf}.
1402
-
1403
- Has a qualified form - [qualifiedPrimarySource] {+prov:qualifiedPrimarySource ?prov:qualifiedForm} that creates an explicit [PrimarySource] {+prov:PrimarySource ?prov:qualifiedForm} relation.
1404
-
1405
- Inverse: [wasPrimarySourceOf] {prov:inverse}
1406
-
1407
- ## qualifiedPrimarySource {=prov:qualifiedPrimarySource owl:ObjectProperty label}
1408
-
1409
- > If this Entity prov:hadPrimarySource Entity :e, then it can qualify how using prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :e; :foo :bar ]. {comment @en}
1410
-
1411
- Adds a [PrimarySource] {+prov:PrimarySource ?range ?prov:sharesDefinitionWith} to an [entity] {+prov:Entity ?domain}.
1412
-
1413
- A qualified version of [hadPrimarySource] {+prov:hadPrimarySource ?prov:unqualifiedForm}.
1414
-
1415
- Sub-property: [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1416
-
1417
- Inverse: [qualifiedSourceOf] {prov:inverse}
1418
-
1419
- ## PrimarySource {=prov:PrimarySource .Class label}
1420
-
1421
- Sub-class of [Derivation] {+prov:Derivation ?subClassOf}.
1422
-
1423
- > An instance of prov:PrimarySource provides additional descriptions about the binary prov:hadPrimarySource relation from some secondary prov:Entity to an earlier, primary prov:Entity. For example, :blog prov:hadPrimarySource :newsArticle; prov:qualifiedPrimarySource [ a prov:PrimarySource; prov:entity :newsArticle; :foo :bar ] . {comment @en}
1424
-
1425
- ``` {prov:definition @en}
1426
- A primary source for a topic refers to something produced by some agent with direct experience and knowledge about the topic, at the time of the topic's study, without benefit from hindsight.
1427
-
1428
- Because of the directness of primary sources, they 'speak for themselves' in ways that cannot be captured through the filter of secondary sources. As such, it is important for secondary sources to reference those primary sources from which they were derived, so that their reliability can be investigated.
1429
-
1430
- A primary source relation is a particular case of derivation of secondary materials from their primary sources. It is recognized that the determination of primary sources can be up to interpretation, and should be done according to conventions accepted within the application's domain.
1431
- ```
1432
-
1433
- ==============
1434
-
1435
- ## Summary
1436
-
1437
- The primary source flow captures the authoritative relationship between entities, modeling how secondary works derive from original, firsthand sources. This flow answers the essential question: "What is the primary source for this entity, and what direct experience does it represent?"
1438
-
1439
- Primary source represents a specialized derivation where the source entity was created by someone with direct experience and knowledge of the topic, without benefit from hindsight. This creates clear authority chains that enable tracking research provenance, journalistic sourcing, and academic evidence across diverse workflows. The flow provides the backbone for understanding how knowledge flows from original observations to derived works.
1440
-
1441
- The hadPrimarySource relationship establishes precise authority lineage that supports sophisticated analysis of source reliability, evidence tracking, and research validation. The bidirectional properties enable flexible querying - both "What is the primary source for this?" and "What works derive from this source?" - while qualified PrimarySource classes enrich these relationships with contextual detail about the source determination process.
1442
-
1443
- By capturing structured authority relationships with contextual enhancement, the flow becomes essential for research integrity, journalistic standards, and academic rigor. It enables organizations to maintain clear evidence trails, support source validation, and understand knowledge provenance through precise primary source tracking.
1444
-
1445
-
1446
-
1447
-
1448
-
1449
-
1450
-
1451
- {=}
1452
-
1453
-
1454
-
1455
- <a id="components-derivations-influence"></a>
1456
-
1457
- [mdp] <https://mdld.js.org/prov/>
1458
- [owl] <http://www.w3.org/2002/07/owl#>
1459
-
1460
- # Influence flow
1461
- =================
1462
-
1463
- ## hadActivity {+prov:hadActivity .owl:ObjectProperty label}
1464
-
1465
- > The _optional_ Activity of an Influence, which used, generated, invalidated, or was the responsibility of some Entity. This property is _not_ used by ActivityInfluence (use prov:activity instead). {comment}
1466
-
1467
- Multidomain extension to an [influence] {+prov:Influence ?domain} with an [activity] {+prov:Activity ?prov:sharesDefinitionWith ?range} that influenced these processes:
1468
-
1469
- - Delegation {+prov:Delegation ?domain},
1470
- - Derivation {+prov:Derivation ?domain},
1471
- - End {+prov:End ?domain},
1472
- - Start {+prov:Start ?domain}.
1473
-
1474
- Inverse: [wasActivityOfInfluence] {prov:inverse}
1475
-
1476
-
1477
- ## qualifiedInfluence {=prov:qualifiedInfluence owl:ObjectProperty label}
1478
-
1479
- > Because prov:qualifiedInfluence is a broad relation, the more specific relations (qualifiedCommunication, qualifiedDelegation, qualifiedEnd, etc.) should be used when applicable. {comment @en}
1480
-
1481
- Attaches a broad term [influence] {+prov:Influence ?range ?prov:sharesDefinitionWith} to an [entity] {+prov:Entity ?domain}, [activity] {+prov:Activity ?domain} or [agent] {+prov:Agent ?domain}.
1482
-
1483
- Inverse: [qualifiedInfluenceOf] {prov:inverse}
1484
-
1485
- ## Influence {=prov:Influence .Class label}
1486
-
1487
- > Influence is the capacity of an entity, activity, or agent to have an effect on the character, development, or behavior of another by means of usage, start, end, generation, invalidation, communication, derivation, attribution, association, or delegation. {prov:definition @en}
1488
-
1489
- > An instance of prov:Influence provides additional descriptions about the binary prov:wasInfluencedBy relation from some influenced Activity, Entity, or Agent to the influencing Activity, Entity, or Agent. For example, :stomach_ache prov:wasInfluencedBy :spoon; prov:qualifiedInfluence [ a prov:Influence; prov:entity :spoon; :foo :bar ] . Because prov:Influence is a broad relation, the more specific relations (Communication, Delegation, End, etc.) should be used when applicable. {comment @en}
1490
-
1491
- > Because prov:Influence is a broad relation, its most specific subclasses (e.g. prov:Communication, prov:Delegation, prov:End, prov:Revision, etc.) should be used when applicable. {comment @en}
1492
-
1493
-
1494
-
1495
- ==============
1496
-
1497
- ## Summary
1498
-
1499
- The influence flow captures the broadest relationship in PROV-O, modeling how any entity, activity, or agent can affect another through diverse mechanisms. This flow answers the fundamental question: "What influenced this, and through what means of effect?"
1500
-
1501
- Influence represents the overarching capacity for one element to impact another through any provenance mechanism - whether direct usage, generation, communication, delegation, or other forms of interaction. This provides the most flexible framework for understanding complex causal relationships and effect propagation across diverse systems. The flow serves as the universal connector that unifies all other provenance patterns under a common conceptual umbrella.
1502
-
1503
- The qualifiedInfluence relationship establishes comprehensive effect tracking that supports sophisticated analysis of impact propagation, causal chains, and system-wide influence patterns. The broad applicability enables flexible querying across all provenance domains - both "What influenced this?" and "What does this influence?" - while the Influence class provides contextual detail about the nature and circumstances of the effect.
1504
-
1505
- By capturing the full spectrum of influence relationships with contextual enhancement, this flow becomes the foundation for comprehensive provenance analysis, system understanding, and impact assessment. It enables organizations to answer the most fundamental questions about causal relationships, maintain complete effect histories, and support advanced provenance reasoning across all domains.
1506
-
1507
-
1508
-
1509
-
1510
-
1511
-
1512
- {=}
1513
-
1514
-
1515
-
1516
- <a id="components-agents-responsibility-index"></a>
1517
-
1518
- [mdp] <https://mdld.js.org/prov/>
1519
- [owl] <http://www.w3.org/2002/07/owl#>
1520
-
1521
- # Agents, responsibility and influence {=mdp:components#agents-responsibility .mdp:Component label}
1522
-
1523
- ![](./components/agents-responsibility/component3.png)
1524
-
1525
- ![](./components/agents-responsibility/Component3b.png)
1526
-
1527
- [Agent flow](#components-agents-responsibility-agent)
1528
- [Association flow](#components-agents-responsibility-association)
1529
- [Responsibility flow](#components-agents-responsibility-responsibility)
1530
- [Attribution flow](#components-agents-responsibility-attribution)
1531
- [Influence flow](#components-agents-responsibility-influence)
1532
-
1533
- ## Summary
1534
-
1535
- The PROV-O Agents, Responsibility and Influence component models the "who" and "why" of provenance through a comprehensive framework of agent types, responsibility relationships, and influence mechanisms. The component is organized into clear flows that establish agent hierarchies and their various modes of influence.
1536
-
1537
- **Flow Architecture:**
1538
- Each agent-related flow follows the provenance pattern of binary relations, qualified forms, and influence classes, creating consistent and predictable modeling approaches.
1539
-
1540
- **Core Flows:**
1541
-
1542
- **1. Agent Flow** - Foundation of all provenance actors
1543
- - **Agent Hierarchy**: `Agent` → `Person`, `Organization`, `SoftwareAgent`
1544
- - Establishes the fundamental types of provenance actors
1545
- - Provides the "who" for all provenance statements
1546
- - Disjoint from `InstantaneousEvent` to maintain clear semantic boundaries
1547
-
1548
- **2. Association Flow** - Agent participation in activities
1549
- - `wasAssociatedWith` → `qualifiedAssociation` → `Association`
1550
- - **Enhancement Properties**: `hadPlan` → `Plan`, `hadRole` → `Role`
1551
- - Models how agents participate in and take responsibility for activities
1552
- - Supports plan-based activity execution and role-based participation
1553
- - Example: Baker associated with baking activity using recipe plan
1554
-
1555
- **3. Responsibility Flow** - Hierarchical accountability
1556
- - `actedOnBehalfOf` → `qualifiedDelegation` → `Delegation`
1557
- - Models chains of responsibility and authority delegation
1558
- - Supports multi-level accountability (student → supervisor → department → university)
1559
- - Maintains responsibility while allowing task delegation
1560
- - Sub-property of `wasInfluencedBy` for influence framework integration
1561
-
1562
- **4. Attribution Flow** - Entity-to-agent responsibility
1563
- - `wasAttributedTo` → `qualifiedAttribution` → `Attribution`
1564
- - Ascribes entities to agents when the specific activity is unknown or irrelevant
1565
- - Provides direct entity-agent responsibility links
1566
- - Useful for authorship and ownership attribution
1567
- - Sub-property of `qualifiedInfluence`
1568
-
1569
- **5. Influence Flow** - Cross-cutting influence framework
1570
- - `wasInfluencedBy` → `qualifiedInfluence` → `Influence`
1571
- - **Specialized Influence Types**: `ActivityInfluence`, `AgentInfluence`, `EntityInfluence`
1572
- - **Supporting Properties**: `influencer`, `influenced`, `activity`, `agent`, `entity`
1573
- - Provides the foundational influence mechanism for all other flows
1574
- - Connects agents, entities, and activities in flexible influence relationships
1575
-
1576
- **Key Relationships:**
1577
- ```
1578
- Influence (broadest)
1579
- ├── ActivityInfluence (activity-based influence)
1580
- ├── AgentInfluence (agent-based influence)
1581
- │ ├── Association (activity participation)
1582
- │ ├── Delegation (responsibility chains)
1583
- │ └── Attribution (entity responsibility)
1584
- └── EntityInfluence (entity-based influence)
1585
- ```
1586
-
1587
- **Benefits of Flow Organization:**
1588
- - Clear separation of agent responsibility concepts
1589
- - Consistent binary→qualified→influence patterns
1590
- - Hierarchical responsibility modeling
1591
- - Cross-cutting influence framework
1592
- - Comprehensive agent type support
1593
- - Flexible role and plan integration
1594
-
1595
-
1596
-
1597
-
1598
-
1599
-
1600
-
1601
- {=}
1602
-
1603
-
1604
-
1605
- <a id="components-agents-responsibility-agent"></a>
1606
-
1607
- [mdp] <https://mdld.js.org/prov/>
1608
- [owl] <http://www.w3.org/2002/07/owl#>
1609
-
1610
- # Agent flow
1611
- =============
1612
-
1613
- ## Agent {=prov:Agent .Class label}
1614
-
1615
- > An agent is something that bears some form of responsibility for an activity taking place, for the existence of an entity, or for another agent's activity. {prov:definition @en}
1616
-
1617
- **Disjoint with:** [InstantaneousEvent] {+prov:InstantaneousEvent !owl:disjointWith}
1618
-
1619
- ## Person {=prov:Person .Class label}
1620
-
1621
- Subclass of [Agent] {+prov:Agent ?subClassOf}
1622
-
1623
- > Person agents are people. {prov:definition}
1624
-
1625
- ## Organization {=prov:Organization .Class label}
1626
-
1627
- Subclass of [Agent] {+prov:Agent ?subClassOf}
1628
-
1629
- > An organization is a social or legal institution such as a company, society, etc. {prov:definition}
1630
-
1631
- ## SoftwareAgent {=prov:SoftwareAgent .Class label}
1632
-
1633
- Subclass of [Agent] {+prov:Agent ?subClassOf}
1634
-
1635
- > A software agent is running software. {prov:definition}
1636
-
1637
- ==============
1638
-
1639
- ## Summary
1640
-
1641
- The agent flow establishes the fundamental concept of responsibility in provenance by modeling entities that bear accountability for activities, entities, or other agents' actions. This flow answers the essential question: "Who or what is responsible for this provenance element?"
1642
-
1643
- Agents represent the active participants in provenance systems - the entities that can be held responsible for actions, decisions, and outcomes. This concept provides the human and organizational dimension that transforms provenance from mere technical tracking into meaningful accountability frameworks. By defining agents as responsible entities, PROV-O enables organizations to establish clear lines of authority, accountability, and attribution across complex systems.
1644
-
1645
- The three specialized agent types provide comprehensive coverage of responsibility scenarios. Person agents capture individual human accountability, enabling personal attribution for actions and decisions. Organization agents model institutional responsibility, supporting corporate governance and organizational accountability. SoftwareAgent agents represent computational responsibility, enabling attribution to automated systems, algorithms, and software processes.
1646
-
1647
- Together, these agent types enable sophisticated provenance scenarios across diverse domains. Research workflows can attribute data processing to individual researchers, research groups, and analysis software. Business processes can track responsibility across employees, departments, and automated systems. Regulatory compliance can establish clear accountability chains from individual actions up to organizational policies and automated enforcement mechanisms.
1648
-
1649
- By providing a comprehensive framework for modeling responsibility, the agent flow becomes the foundation for accountability, auditability, and trust in provenance systems. It enables organizations to answer not just what happened, but who was responsible, supporting governance, compliance, and transparency initiatives across all operational contexts.
1650
-
1651
-
1652
-
1653
-
1654
-
1655
-
1656
-
1657
-
1658
- {=}
1659
-
1660
-
1661
-
1662
- <a id="components-agents-responsibility-association"></a>
1663
-
1664
- [mdp] <https://mdld.js.org/prov/>
1665
- [owl] <http://www.w3.org/2002/07/owl#>
1666
-
1667
- # Association flow
1668
- ======================
1669
-
1670
- ## wasAssociatedWith {=prov:wasAssociatedWith .owl:ObjectProperty label}
1671
-
1672
- > An prov:Agent that had some (unspecified) responsibility for the occurrence of this prov:Activity. {comment @en}
1673
-
1674
- Adds an [agent] {+prov:Agent ?range} to an [activity] {+prov:Activity ?domain}.
1675
-
1676
- May be qualified by [qualifiedAssociation] {+prov:qualifiedAssociation ?prov:qualifiedForm} with [Association] {+prov:Association ?prov:qualifiedForm} attached.
1677
-
1678
- Sub-property: [wasAssociateFor] {+prov:wasAssociateFor ?subPropertyOf}
1679
-
1680
- Inverse: [wasAssociateFor] {prov:inverse}
1681
-
1682
- ## qualifiedAssociation {=prov:qualifiedAssociation .owl:ObjectProperty label}
1683
-
1684
- > If this Activity prov:wasAssociatedWith Agent :ag, then it can qualify the Association using prov:qualifiedAssociation [ a prov:Association; prov:agent :ag; :foo :bar ]. {comment @en}
1685
-
1686
- As a qualified form of [wasAssociatedWith] {+prov:wasAssociatedWith ?prov:unqualifiedForm} it describes that an activity was [associated] {+prov:Association ?range ?prov:sharesDefinitionWith} with an [activity] {+prov:Activity ?domain}.
1687
-
1688
- Sub-property of [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}.
1689
-
1690
- Inverse: [qualifiedAssociationOf] {prov:inverse}.
1691
-
1692
- ## Association {=prov:Association .Class label}
1693
-
1694
- Sub-class of [AgentInfluence] {+prov:AgentInfluence ?subClassOf}
1695
-
1696
- > An activity association is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. {prov:definition}
1697
-
1698
- > An instance of prov:Association provides additional descriptions about the binary prov:wasAssociatedWith relation from an prov:Activity to some prov:Agent that had some responsiblity for it. For example, :baking prov:wasAssociatedWith :baker; prov:qualifiedAssociation [ a prov:Association; prov:agent :baker; :foo :bar ]. {comment @en}
1699
-
1700
- ## hadPlan {=prov:hadPlan .owl:ObjectProperty label}
1701
-
1702
- > The _optional_ Plan adopted by an Agent in Association with some Activity. Plan specifications are out of the scope of this specification. {comment @en}
1703
-
1704
- Is used to connect [Association] {+prov:Association ?domain} to a [Plan] {+prov:Plan ?range ?prov:sharesDefinitionWith}.
1705
-
1706
- Inverse: [wasPlanOf] {prov:inverse}
1707
-
1708
- ## Plan {=prov:Plan .Class label}
1709
-
1710
- Sub-class of [Entity] {+prov:Entity ?subClassOf}
1711
-
1712
- > A plan is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals. {prov:definition @en}
1713
-
1714
- > There exist no prescriptive requirement on the nature of plans, their representation, the actions or steps they consist of, or their intended goals. Since plans may evolve over time, it may become necessary to track their provenance, so plans themselves are entities. Representing the plan explicitly in the provenance can be useful for various tasks: for example, to validate the execution as represented in the provenance record, to manage expectation failures, or to provide explanations. {comment @en}
1715
-
1716
- ## hadRole {=prov:hadRole .owl:ObjectProperty label}
1717
-
1718
- > The _optional_ Role that an Entity assumed in the context of an Activity. For example, :baking prov:used :spoon; prov:qualified [ a prov:Usage; prov:entity :spoon; prov:hadRole roles:mixing_implement ]. {comment @en}
1719
-
1720
- It describes that an entity assumed a [Role] {+prov:Role ?range ?prov:sharesDefinitionWith} during an [Influence] {+prov:Influence ?domain} or [Association] {+prov:Association ?domain} or [InstantaneousEvent] {+prov:InstantaneousEvent ?domain} in general.
1721
-
1722
- Inverse: [wasRoleIn] {prov:inverse}.
1723
-
1724
- ## Role {=prov:Role .Class label}
1725
-
1726
- > A role is the function of an entity or agent with respect to an activity, in the context of a usage, generation, invalidation, association, start, and end. {prov:definition}
1727
-
1728
- See also [hadRole] {+prov:hadRole ?seeAlso}.
1729
-
1730
- ==============
1731
-
1732
- ## Summary
1733
-
1734
- The association flow captures the responsibility relationship between agents and activities, modeling how agents are assigned responsibility for specific actions and the plans they follow. This flow answers the essential question: "Which agents are responsible for this activity, and what plans and roles guided their involvement?"
1735
-
1736
- Association represents the fundamental mechanism for assigning responsibility where agents have specific roles in activities and operate according to intended plans. This concept provides the structured framework for understanding not just that an agent was involved, but how they were involved - what capacity they served, what procedures they followed, and what goals they intended to achieve. By modeling associations with plans and roles, PROV-O enables sophisticated accountability frameworks that capture both responsibility and intent.
1737
-
1738
- The hadPlan relationship enables organizations to track the procedures and methodologies that guided activities, supporting compliance validation and process improvement. Plans can represent standard operating procedures, research methodologies, or automated algorithms, allowing organizations to validate that activities followed intended processes and manage expectation failures when deviations occur.
1739
-
1740
- The hadRole relationship provides contextual depth by specifying the function or capacity in which agents participated. Roles can represent job functions, system capacities, or contextual positions that clarify the nature of agent involvement. This enables precise attribution where multiple agents participate in the same activity with different responsibilities.
1741
-
1742
- Together, these association elements enable sophisticated provenance scenarios across diverse domains. Research workflows can track which researchers conducted analyses following specific protocols. Business processes can attribute activities to employees following standard operating procedures. Automated systems can record which software processes executed according to predefined algorithms.
1743
-
1744
- By providing comprehensive responsibility tracking with plans and roles, the association flow becomes essential for governance, compliance, and process improvement. It enables organizations to establish clear accountability chains, validate process adherence, and understand not just what happened, but how and why it happened according to established frameworks.
1745
-
1746
-
1747
-
1748
-
1749
-
1750
-
1751
-
1752
- {=}
1753
-
1754
-
1755
-
1756
- <a id="components-agents-responsibility-responsibility"></a>
1757
-
1758
- [mdp] <https://mdld.js.org/prov/>
1759
- [owl] <http://www.w3.org/2002/07/owl#>
1760
-
1761
- # Responsibility flow
1762
- ======================
1763
-
1764
- ## actedOnBehalfOf {=prov:actedOnBehalfOf .owl:ObjectProperty label}
1765
-
1766
- > An object property to express the accountability of an agent towards another agent. The subordinate agent acted on behalf of the responsible agent in an actual activity {comment @en}
1767
-
1768
- Connects one [Agent] {+prov:Agent ?domain} to another [Agent] {+prov:Agent ?range} with a [delegation] {+prov:Delegation ?qualifiedForm} relation that is a sub-property of the [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf} property.
1769
-
1770
- It's qualified form is the [qualifiedDelegation] {+prov:qualifiedDelegation ?qualifiedForm} property.
1771
-
1772
- Inverse: not defined explicitly, rather a recommended name for use in additional ontologies if necessary - [hadDelegate] {prov:inverse}.
1773
-
1774
- ## qualifiedDelegation {=prov:qualifiedDelegation .owl:ObjectProperty label}
1775
-
1776
- > If this Agent prov:actedOnBehalfOf Agent :ag, then it can qualify how with prov:qualifiedResponsibility [ a prov:Responsibility; prov:agent :ag; :foo :bar ]. {comment @en}
1777
-
1778
- Connects an [agent] {+prov:Agent ?domain} to a [delegation] {+prov:Delegation ?range ?prov:sharesDefinitionWith}.
1779
-
1780
- Sub-property of [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}.
1781
-
1782
- Inverse: [qualifiedDelegationOf] {prov:inverse}
1783
-
1784
- ## Delegation {=prov:Delegation .Class label}
1785
-
1786
- Sub-class of [AgentInfluence] {+prov:AgentInfluence ?subClassOf}
1787
-
1788
- > An instance of prov:Delegation provides additional descriptions about the binary prov:actedOnBehalfOf relation from a performing prov:Agent to some prov:Agent for whom it was performed. For example, :mixing prov:wasAssociatedWith :toddler . :toddler prov:actedOnBehalfOf :mother; prov:qualifiedDelegation [ a prov:Delegation; prov:entity :mother; :foo :bar ]. {comment @en}
1789
-
1790
- ``` {prov:definition @en}
1791
- Delegation is the assignment of authority and responsibility to an agent (by itself or by another agent) to carry out a specific activity as a delegate or representative, while the agent it acts on behalf of retains some responsibility for the outcome of the delegated work.
1792
-
1793
- For example, a student acted on behalf of his supervisor, who acted on behalf of the department chair, who acted on behalf of the university; all those agents are responsible in some way for the activity that took place but we do not say explicitly who bears responsibility and to what degree.
1794
- ```
1795
-
1796
- ==============
1797
-
1798
- ## Summary
1799
-
1800
- The responsibility flow captures the hierarchical accountability relationship between agents, modeling how subordinate agents act on behalf of responsible agents within organizational or authority structures. This flow answers the essential question: "On whose behalf did this agent act, and what authority structures guided their actions?"
1801
-
1802
- Responsibility represents the fundamental mechanism for modeling delegation and authority chains where agents operate within hierarchical relationships. This concept provides the essential framework for understanding how responsibility flows through organizational structures, from individual actions up through management chains to institutional accountability. By enabling agent-to-agent accountability relationships, PROV-O supports sophisticated governance frameworks that capture both direct responsibility and delegated authority.
1803
-
1804
- The actedOnBehalfOf relationship creates clear delegation chains that support sophisticated analysis of organizational accountability, authority structures, and responsibility flow. The bidirectional properties enable flexible querying - both "On whose behalf did this agent act?" and "Which agents acted on this agent's behalf?" - while qualified Delegation classes enrich these relationships with contextual detail about the delegation circumstances and authority frameworks.
1805
-
1806
- By providing hierarchical responsibility tracking, the flow becomes essential for organizational governance, regulatory compliance, and accountability frameworks. It enables organizations to maintain clear authority chains, support audit trails that follow responsibility through complex organizational structures, and understand how individual actions relate to broader institutional responsibilities.
1807
-
1808
- This hierarchical approach complements direct attribution and activity-based association by providing the mechanism for understanding how responsibility flows through multi-level organizational structures, making responsibility the essential component for modeling complex accountability scenarios where authority is delegated and actions are performed on behalf of others.
1809
-
1810
-
1811
-
1812
-
1813
-
1814
-
1815
-
1816
-
1817
-
1818
-
1819
- {=}
1820
-
1821
-
1822
-
1823
- <a id="components-agents-responsibility-attribution"></a>
1824
-
1825
- [mdp] <https://mdld.js.org/prov/>
1826
- [owl] <http://www.w3.org/2002/07/owl#>
1827
-
1828
- # Attribution flow
1829
- ===================
1830
-
1831
- ## wasAttributedTo {=prov:wasAttributedTo .owl:ObjectProperty label}
1832
-
1833
- Sub-property of [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}
1834
-
1835
- > Attribution is the ascribing of an entity to an agent. {comment @en}
1836
-
1837
- Adds an [agent] {+prov:Agent ?range} to an [entity] {+prov:Entity ?domain}.
1838
-
1839
- May be qualified by [qualifiedAttribution] {+prov:qualifiedAttribution ?prov:qualifiedForm} with [Attribution] {+prov:Attribution ?prov:qualifiedForm} attached.
1840
-
1841
- Inverse: [qualifiedAttribution] {prov:inverse}
1842
-
1843
- ## qualifiedAttribution {=prov:qualifiedAttribution .owl:ObjectProperty label}
1844
-
1845
- > If this Entity prov:wasAttributedTo Agent :ag, then it can qualify how it was influenced using prov:qualifiedAttribution [ a prov:Attribution; prov:agent :ag; :foo :bar ]. {comment @en}
1846
-
1847
- As a qualified form of [wasAttributedTo] {+prov:wasAttributedTo ?prov:unqualifiedForm} it describes that an entity was [attributed] {+prov:Attribution ?range ?prov:sharesDefinitionWith} to an [entity] {+prov:Entity ?domain}.
1848
-
1849
- Sub-property of [qualifiedInfluence] {+prov:qualifiedInfluence ?subPropertyOf}.
1850
-
1851
- Inverse: [qualifiedAttributionOf] {prov:inverse}.
1852
-
1853
- ## Attribution {=prov:Attribution .Class label}
1854
-
1855
- Sub-class of [AgentInfluence] {+prov:AgentInfluence ?subClassOf}
1856
-
1857
- > Attribution is the ascribing of an entity to an agent.
1858
-
1859
- > When an entity e is attributed to agent ag, entity e was generated by some unspecified activity that in turn was associated to agent ag. Thus, this relation is useful when the activity is not known, or irrelevant. {prov:definition @en}
1860
-
1861
-
1862
- > An instance of prov:Attribution provides additional descriptions about the binary prov:wasAttributedTo relation from an prov:Entity to some prov:Agent that had some responsible for it. For example, :cake prov:wasAttributedTo :baker; prov:qualifiedAttribution [ a prov:Attribution; prov:entity :baker; :foo :bar ]. {comment @en}
1863
-
1864
- ==============
1865
-
1866
- ## Summary
1867
-
1868
- The attribution flow captures the direct responsibility relationship between entities and agents, modeling how entities are ascribed to their creators or responsible parties without requiring explicit activity details. This flow answers the essential question: "Who is responsible for this entity's existence?"
1869
-
1870
- Attribution represents a streamlined approach to responsibility assignment where the focus is on entity ownership rather than the specific activities that created them. This concept provides the essential mechanism for establishing intellectual property, authorship, and ownership relationships that form the foundation of creative and academic attribution systems. By enabling direct entity-to-agent relationships, PROV-O supports scenarios where activity tracking is unnecessary, unknown, or irrelevant to the accountability framework.
1871
-
1872
- The wasAttributedTo relationship creates clear ownership chains that support sophisticated analysis of intellectual property, creative works, and data provenance. The bidirectional properties enable flexible querying - both "Who created this entity?" and "What entities did this agent create?" - while qualified Attribution classes enrich these relationships with contextual detail about the attribution circumstances and processes.
1873
-
1874
- By providing direct entity attribution without requiring activity specification, the flow becomes essential for academic publishing, creative works management, and data governance. It enables organizations to maintain clear authorship records, support intellectual property tracking, and establish responsibility for entities even when the creation processes are unknown or irrelevant to the accountability requirements.
1875
-
1876
- This streamlined approach complements more detailed activity-based provenance by providing a lightweight mechanism for establishing responsibility when the full activity context is not needed or available, making attribution the most direct path from entity to responsible agent.
1877
-
1878
-
1879
-
1880
-
1881
-
1882
-
1883
-
1884
-
1885
- {=}
1886
-
1887
-
1888
-
1889
- <a id="components-agents-responsibility-influence"></a>
1890
-
1891
- [mdp] <https://mdld.js.org/prov/>
1892
- [owl] <http://www.w3.org/2002/07/owl#>
1893
-
1894
- # Influence flow
1895
- =================
1896
-
1897
- ## wasInfluencedBy {=prov:wasInfluencedBy .owl:ObjectProperty label}
1898
-
1899
- > Because prov:wasInfluencedBy is a broad relation, its more specific subproperties (e.g. prov:wasInformedBy, prov:actedOnBehalfOf, prov:wasEndedBy, etc.) should be used when applicable. {comment @en}
1900
-
1901
- It describes that an entity was influenced by another entity.
1902
-
1903
- This is a broad relation of [Influence] {+prov:Influence ?prov:qualifiedForm ?prov:sharesDefinitionWith} that can connect any of [agents] {+prov:Agent ?domain ?range}, [entities] {+prov:Entity ?domain ?range} or [activities] {+prov:Activity ?domain ?range} to each other.
1904
-
1905
- Can be qualified with [qualifiedInfluence] {+prov:qualifiedInfluence ?prov:qualifiedForm}.
1906
-
1907
- Inverse: [influenced] {prov:inverse} is one of few that are [defined] {+prov:influenced ?prov:inverse}.
1908
-
1909
- ``` {prov:editorialNote @en}
1910
- The sub-properties of prov:wasInfluencedBy can be elaborated in more detail using the Qualification Pattern. For example, the binary relation :baking prov:used :spoon can be qualified by asserting :baking prov:qualifiedUsage [ a prov:Usage; prov:entity :spoon; prov:atLocation :kitchen ] .
1911
-
1912
- Subproperties of prov:wasInfluencedBy may also be asserted directly without being qualified.
1913
-
1914
- prov:wasInfluencedBy should not be used without also using one of its subproperties.
1915
- ```
1916
-
1917
- ## ActivityInfluence** {=prov:ActivityInfluence.Class label}
1918
-
1919
- Sub-class of [Influence] {+prov:Influence ?subClassOf}
1920
-
1921
- > ActivityInfluence provides additional descriptions of an Activity's binary influence upon any other kind of resource. Instances of ActivityInfluence use the prov:activity property to cite the influencing Activity. {comment @en}
1922
-
1923
- > It is not recommended that the type ActivityInfluence be asserted without also asserting one of its more specific subclasses. {comment @en}
1924
-
1925
- Disjoint with [EntityInfluence] {+prov:EntityInfluence ?owl:disjointWith}.
1926
-
1927
- See also: [activity] {+prov:activity ?seeAlso}
1928
-
1929
- > ActivitiyInfluence is the capacity of an activity to have an effect on the character, development, or behavior of another by means of generation, invalidation, communication, or other. {prov:editorsDefinition @en}
1930
-
1931
- ## AgentInfluence {=prov:AgentInfluence .Class label}
1932
-
1933
- Sub-class of [Influence] {+prov:Influence ?subClassOf}
1934
-
1935
- > AgentInfluence provides additional descriptions of an Agent's binary influence upon any other kind of resource. Instances of AgentInfluence use the prov:agent property to cite the influencing Agent. {comment @en}
1936
-
1937
- > AgentInfluence is the capacity of an agent to have an effect on the character, development, or behavior of another by means of attribution, association, delegation, or other. {prov:editorsDefinition @en}
1938
-
1939
- ## EntityInfluence {=prov:EntityInfluence .Class label}
1940
-
1941
- Sub-class of [Influence] {+prov:Influence ?subClassOf}.
1942
-
1943
- > EntityInfluence is the capacity of an entity to have an effect on the character, development, or behavior of another by means of usage, start, end, derivation, or other. {prov:editorsDefinition @en}
1944
-
1945
- > EntityInfluence provides additional descriptions of an Entity's binary influence upon any other kind of resource. Instances of EntityInfluence use the prov:entity property to cite the influencing Entity. {comment @en}
1946
-
1947
- > It is not recommended that the type EntityInfluence be asserted without also asserting one of its more specific subclasses. {comment @en}
1948
-
1949
-
1950
- ## influenced {=prov:influenced .owl:ObjectProperty label}
1951
-
1952
- Inverse: [wasInfluencedBy] {prov:inverse} with a defined [inverse] {+prov:wasInfluencedBy ?owl:inverseOf}.
1953
-
1954
- See [Influence] {+prov:Influence ?prov:sharesDefinitionWith}
1955
-
1956
- ## influencer {=prov:influencer .owl:ObjectProperty label}
1957
-
1958
- > Subproperties of prov:influencer are used to cite the object of an unqualified PROV-O triple whose predicate is a subproperty of prov:wasInfluencedBy (e.g. prov:used, prov:wasGeneratedBy). prov:influencer is used much like rdf:object is used. {comment @en}
1959
-
1960
- Clarifies an [Influence] {+prov:Influence ?domain} with what was that [thing] {+owl:Thing ?range} that made the influence.
1961
-
1962
- Inverse: [hadInfluence] {prov:inverse}.
1963
-
1964
- > This property and its subproperties are used in the same way as the rdf:object property, i.e. to reference the object of an unqualified prov:wasInfluencedBy or prov:influenced triple. {prov:editorialNote @en}
1965
-
1966
- > This property is used as part of the qualified influence pattern. Subclasses of prov:Influence use these subproperties to reference the resource (Entity, Agent, or Activity) whose influence is being qualified. {prov:editorialNote @en}
1967
-
1968
-
1969
- ## activity {=prov:activity .owl:ObjectProperty label}
1970
-
1971
- Applies to [Activities] {+prov:Activity ?range} as a sub-property of [influencer] {+prov:influencer ?subPropertyOf} - it references an [Activity] that influenced a resource.
1972
-
1973
- > This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple. {prov:editorialNote @en}
1974
-
1975
- > The prov:activity property references an prov:Activity which influenced a resource. This property applies to an prov:ActivityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent. {prov:editorsDefinition @en}
1976
-
1977
- Inverse: [activityOfInfluence] {prov:inverse}
1978
-
1979
- ## agent {=prov:agent .owl:ObjectProperty label}
1980
-
1981
- Points to [Agents] {+prov:Agent ?range} from the [AgentInfluence] {+prov:AgentInfluence ?domain} qualified relations that are sub-properties of the [influencer] {+prov:influencer ?subPropertyOf} property.
1982
-
1983
- > This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple. {prov:editorialNote @en}
1984
-
1985
- > The prov:agent property references an prov:Agent which influenced a resource. This property applies to an prov:AgentInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent. {prov:editorsDefinition @en}
1986
-
1987
- Inverse: [agentOfInfluence] {prov:inverse}
1988
-
1989
-
1990
- ## entity {=prov:entity .owl:ObjectProperty label}
1991
-
1992
- A qualified [EntityInfluence] {+prov:EntityInfluence ?domain} uses this relation to point to an [entity] {+prov:Entity} that influences an entity/agent/activity with some [influence] {+prov:influencer ?subPropertyOf}.
1993
-
1994
- Inverse: [entityOfInfluence] {prov:inverse}
1995
-
1996
- > This property behaves in spirit like rdf:object; it references the object of a prov:wasInfluencedBy triple. {prov:editorialNote @en}
1997
-
1998
- > The prov:entity property references an prov:Entity which influenced a resource. This property applies to an prov:EntityInfluence, which is given by a subproperty of prov:qualifiedInfluence from the influenced prov:Entity, prov:Activity or prov:Agent. {prov:editorsDefinition @en}
1999
-
2000
- ==============
2001
-
2002
- ## Summary
2003
-
2004
- The influence flow captures the most fundamental and universal relationship in PROV-O, modeling how any entity, activity, or agent can affect another through any mechanism. This flow answers the essential question: "What influenced this, and through what capacity?"
2005
-
2006
- Influence represents the broadest concept in provenance - the capacity for one element to have an effect on another through any means, whether direct or indirect, specific or general. This universal relationship serves as the conceptual umbrella that unifies all other provenance patterns under a common framework. While specific relations like usage, generation, or delegation capture precise mechanisms, influence provides the flexible foundation for modeling complex, multi-faceted relationships that may not fit neatly into specialized categories.
2007
-
2008
- The specialized influence classes provide structured mechanisms for different influence types. ActivityInfluence captures how activities affect resources through generation, invalidation, or communication. AgentInfluence models how agents exert influence through attribution, association, or delegation. EntityInfluence represents how entities influence others through usage, derivation, or other entity-based mechanisms. This specialization enables precise modeling while maintaining the conceptual unity of influence as the fundamental relationship.
2009
-
2010
- The wasInfluencedBy relationship creates comprehensive effect chains that support sophisticated analysis of system-wide impact, causal propagation, and complex interdependencies. The bidirectional properties enable flexible querying across all provenance domains - both "What influenced this?" and "What does this influence?" - while the specialized influence classes provide contextual detail about the nature and mechanisms of influence.
2011
-
2012
- By providing the most universal relationship with specialized subtypes, the influence flow becomes the foundation for comprehensive provenance analysis, system understanding, and impact assessment. It enables organizations to capture the full spectrum of relationships in complex systems while maintaining the ability to specialize when needed, making influence both the most generic and most specific mechanism for provenance modeling.
2013
-
2014
-
2015
-
2016
-
2017
-
2018
-
2019
- {=}
2020
-
2021
-
2022
-
2023
- <a id="components-bundles-index"></a>
2024
-
2025
- [mdp] <https://mdld.js.org/prov/>
2026
- [owl] <http://www.w3.org/2002/07/owl#>
2027
-
2028
- # Bundles {=mdp:components#bundles .mdp:Component label}
2029
-
2030
- The fourth component of PROV-DM is concerned with bundles, a mechanism to support provenance of provenance. Figure 9 depicts a UML class diagram for the fourth component. It comprises a Bundle class defined as a subclass of Entity.
2031
-
2032
- ![](./components/bundles/component4.png)
2033
-
2034
- ## Bundle {=prov:Bundle .Class label}
2035
-
2036
- > A bundle is a named set of provenance descriptions, and is itself an Entity, so allowing provenance of provenance to be expressed. {prov:definition @en}
2037
-
2038
- > Note that there are kinds of bundles (e.g. handwritten letters, audio recordings, etc.) that are not expressed in PROV-O, but can be still be described by PROV-O. {comment @en}
2039
-
2040
- A bundle's identifier id identifies a unique set of descriptions.
2041
-
2042
- A bundle is a named set of descriptions, but it is also an [entity] {+prov:Entity ?subClassOf} so that its provenance can be described.
2043
-
2044
- A prov:Bundle is a named set of provenance descriptions, which may itself have provenance. The named set of provenance descriptions may be expressed as PROV-O or any other form. The subclass of Bundle that names a set of PROV-O assertions is not provided by PROV-O, since it is more appropriate to do so using other recommendations, standards, or technologies. In any case, a Bundle of PROV-O assertions is an abstract set of RDF triples, and adding or removing a triple creates a new distinct Bundle of PROV-O assertions.
2045
-
2046
- ## Summary
2047
-
2048
- The PROV-O Bundles component enables "provenance of provenance" by treating collections of provenance descriptions as entities themselves. This powerful concept allows recursive provenance tracking where provenance records can have their own provenance, creating multi-layered documentation of documentation processes.
2049
-
2050
- At its core, bundles represent a sophisticated approach to provenance management where sets of provenance descriptions become first-class entities. This enables organizations to track not just what happened to their data and processes, but also track how their provenance records themselves evolve over time. Each bundle identifier represents a unique, immutable set of descriptions that can be referenced, versioned, and managed as distinct units of provenance information.
2051
-
2052
- The recursive nature of bundles provides the foundation for complex provenance scenarios. A bundle might contain provenance about data processing workflows, which itself could be part of a larger bundle describing organizational provenance policies. This creates hierarchical provenance structures that support sophisticated audit trails, compliance documentation, and multi-level accountability frameworks.
2053
-
2054
- By enabling provenance of provenance, the component becomes essential for organizations that need to track how their provenance systems change, evolve, and are governed. It supports complex scenarios like regulatory reporting where organizations must demonstrate not just data lineage, but also the evolution of their tracking and documentation practices. This recursive capability makes bundles uniquely powerful for establishing trust, maintaining auditability, and supporting sophisticated provenance analysis across multiple organizational and temporal dimensions.
2055
- - Provenance collection provenance
2056
-
2057
-
2058
-
2059
-
2060
-
2061
- {=}
2062
-
2063
-
2064
-
2065
- <a id="components-alternate-index"></a>
2066
-
2067
- [mdp] <https://mdld.js.org/prov/>
2068
- [owl] <http://www.w3.org/2002/07/owl#>
2069
-
2070
- # Alternate {=mdp:components#alternate .mdp:Component label}
2071
-
2072
- ![](./components/alternate/component5.png)
2073
-
2074
-
2075
- ## alternateOf {=prov:alternateOf .owl:ObjectProperty label}
2076
-
2077
- Connects two [entities] {+prov:Entity ?domain ?range} as describing the same thing from multiple perspectives - a sub-property of the [alternate] {+prov:alternate ?subPropertyOf} property - it's a [symmetrical] {+prov:alternateOf ?prov:inverse} relation.
2078
-
2079
- > Two alternate entities present aspects of the same thing. These aspects may be the same or different, and the alternate entities may or may not overlap in time. {comment @en}
2080
-
2081
- Related: [specializationOf] {+prov:specializationOf ?seeAlso}
2082
-
2083
- ## specializationOf {=prov:specializationOf .owl:ObjectProperty label}
2084
-
2085
- > An entity that is a specialization of another shares all aspects of the latter, and additionally presents more specific aspects of the same thing as the latter. In particular, the lifetime of the entity being specialized contains that of any specialization. Examples of aspects include a time period, an abstraction, and a context associated with the entity. {comment @en}
2086
-
2087
- Connects two [entities] {+prov:Entity ?range ?domain} where one is a more specific version of the other.
2088
-
2089
- Sub-property: [alternateOf] {+prov:alternateOf ?subPropertyOf ?seeAlso}
2090
-
2091
- Inverse: [generalizationOf] {prov:inverse}
2092
-
2093
- ## Summary
2094
-
2095
- The PROV-O Alternate component provides sophisticated mechanisms for expressing relationships between entities that represent the same underlying thing in different ways. This component answers the essential question: "How do these entities relate to the same reality, and what perspectives do they represent?"
2096
-
2097
- At its heart, this component addresses the fundamental challenge of modeling how multiple entities can simultaneously represent the same concept while differing in format, perspective, or specificity. The alternateOf relation captures symmetric relationships where entities describe the same thing from different viewpoints - such as the same document in PDF and Word formats, or the same dataset in raw and processed states. This enables organizations to track how information flows through different representations while maintaining clear understanding of their underlying unity.
2098
-
2099
- The specializationOf relation provides hierarchical modeling where one entity represents a more refined or specific version of another. This creates clear lineage chains where entities evolve through addition of specific aspects, contexts, or temporal boundaries. For example, a research paper might specialize into a conference presentation by adding presentation-specific context while maintaining the core research content. This supports sophisticated understanding of how concepts are refined and adapted for different purposes.
2100
-
2101
- Together, these relations enable powerful provenance scenarios across diverse domains. Document management systems can track format conversions and version evolution while maintaining clear understanding of content continuity. Data platforms can model how raw data transforms into processed formats while preserving the relationship to the same underlying information. Research workflows can capture how studies evolve into publications while maintaining clear attribution to original findings.
2102
-
2103
- By providing both symmetric alternation and asymmetric specialization relationships, the component becomes essential for managing complex information ecosystems where entities exist in multiple forms and evolve through hierarchical refinement. It enables organizations to maintain semantic clarity while supporting the flexibility needed for real-world provenance scenarios.
2104
-
2105
-
2106
-
2107
-
2108
-
2109
- {=}
2110
-
2111
-
2112
-
2113
- <a id="components-collections-index"></a>
2114
-
2115
- [mdp] <https://mdld.js.org/prov/>
2116
- [owl] <http://www.w3.org/2002/07/owl#>
2117
-
2118
- # Collections {=mdp:components#collections .mdp:Component label}
2119
-
2120
- The sixth component of PROV-DM is concerned with the notion of collections. A collection is an entity that has some members. The members are themselves entities, and therefore their provenance can be expressed. Some applications need to be able to express the provenance of the collection itself: e.g. who maintains the collection (attribution), which members it contains as it evolves, and how it was assembled. The purpose of Component 6 is to define the types and relations that are useful to express the provenance of collections.
2121
-
2122
- ![](./components/collections/component6.png)
2123
-
2124
- ## Collection {=prov:Collection .Class label}
2125
-
2126
- Sub-class of [Entity] {+prov:Entity ?subClassOf}
2127
-
2128
- > A collection is an entity that provides a structure to some constituents, which are themselves entities. These constituents are said to be member of the collections. {prov:definition @en}
2129
-
2130
- The prov:Collection [entity] {+prov:Entity ?subClassOf} class can be used to express the provenance of the collection itself: e.g. who maintained the collection, which members it contained as it evolved, and how it was assembled. The prov:hadMember property is used to assert membership in a collection.
2131
-
2132
- Has a subclass - **Empty Collection** {=prov:EmptyCollection .Class label !subClassOf} - *An empty collection is a collection without members.* {prov:definition @en}
2133
-
2134
- ## hadMember {=prov:hadMember .owl:ObjectProperty label}
2135
-
2136
- Connects a [Collection] {+prov:Collection ?domain ?prov:sharesDefinitionWith} to its [member] {+prov:Entity ?range} with a relation that is a sub-property of [wasInfluencedBy] {+prov:wasInfluencedBy ?subPropertyOf}.
2137
-
2138
- Inverse: [wasMemberOf] {prov:inverse}
2139
-
2140
- ## Summary
2141
-
2142
- The PROV-O Collections component enables provenance tracking for collections as first-class entities, modeling how groups of items maintain their own evolution while tracking membership relationships. This component answers the essential question: "How do collections evolve, and what entities do they contain?"
2143
-
2144
- Collections represent a powerful concept where entities themselves become members of larger, structured entities. This creates hierarchical provenance where collections can be tracked through their own lifecycle - creation, modification, and evolution - while simultaneously maintaining precise membership information about their constituent entities. The component provides the foundation for understanding complex systems where items are grouped, organized, and managed as coherent units.
2145
-
2146
- The hadMember relationship establishes clear membership chains that support sophisticated analysis of collection evolution, item tracking, and organizational structure. The bidirectional properties enable flexible querying - both "What items does this collection contain?" and "What collections include this item?" - while the entity nature of collections ensures they inherit all provenance capabilities of individual entities, from attribution to derivation relationships.
2147
-
2148
- By treating collections as entities with their own provenance, the component becomes essential for dataset management, repository systems, and research aggregation. It enables organizations to maintain complete audit trails for both individual items and their groupings, support complex organizational structures, and understand how collections evolve through addition, removal, and reorganization of their constituent entities.
2149
-
2150
-
2151
-
2152
-
2153
-
2154
- {=}
2155
-
2156
-
2157
-
2158
- <a id="examples-index"></a>
2159
-
2160
- [mdp] <https://mdld.js.org/prov/>
2161
-
2162
- # Examples {=mdp:examples .Container label}
2163
-
2164
- > Examples in both TTL and MDLD.
2165
-
2166
- ## Example 1
2167
-
2168
- ![example1](./examples/example1.ttl) {+mdp:examples#ttl1 ?member}
2169
-
2170
- [example1](./example1.md) {+mdp:examples#md1 ?member}
2171
-
2172
- ## Example 2
2173
-
2174
- ![example2](./examples/example2.ttl) {+mdp:examples#ttl2 ?member}
2175
-
2176
- [example2](#examples-example2) {+mdp:examples#md2 ?member}
2177
-
2178
- ## Example 3
2179
-
2180
- ![example3](./examples/example3.ttl) {+mdp:examples#ttl3 ?member}
2181
-
2182
- [example3](#examples-example3) {+mdp:examples#md3 ?member}
2183
-
2184
- ## Example 4
2185
-
2186
- ![example4](./examples/example4.ttl) {+mdp:examples#ttl4 ?member}
2187
-
2188
- [example4](#examples-example4) {+mdp:examples#md4 ?member}
2189
-
2190
-
2191
- ## Example 5
2192
-
2193
- ![example5](./examples/example5.ttl) {+mdp:examples#ttl5 ?member}
2194
-
2195
- [example5](#examples-example5) {+mdp:examples#md5 ?member}
2196
-
2197
- ## Example 6
2198
-
2199
- ![example6](./examples/example6.ttl) {+mdp:examples#ttl6 ?member}
2200
-
2201
- [example6](#examples-example6) {+mdp:examples#md6 ?member}
2202
-
2203
- ## Example 7
2204
-
2205
- ![example7](./examples/example7.ttl) {+mdp:examples#ttl7 ?member}
2206
-
2207
- [example7](#examples-example7) {+mdp:examples#md7 ?member}
2208
-
2209
- ## Example 8
2210
-
2211
- ![example8](./examples/example8.ttl) {+mdp:examples#ttl8 ?member}
2212
-
2213
- [example8](#examples-example8) {+mdp:examples#md8 ?member}
2214
-
2215
- ## Example 9
2216
-
2217
- ![example9](./examples/example9.ttl) {+mdp:examples#ttl9 ?member}
2218
-
2219
- [example9](#examples-example9) {+mdp:examples#md9 ?member}
2220
-
2221
- ## Example 10
2222
-
2223
- ![example10](./examples/example10.ttl) {+mdp:examples#ttl10 ?member}
2224
-
2225
- [example10](#examples-example10) {+mdp:examples#md10 ?member}
2226
-
2227
-
2228
- ## Example 11
2229
-
2230
- ![example11](./examples/example11.ttl) {+mdp:examples#ttl11 ?member}
2231
-
2232
- [example11](#examples-example11) {+mdp:examples#md11 ?member}
2233
-
2234
-
2235
-
2236
-
2237
-
2238
-
2239
-
2240
-
2241
-
2242
-
2243
- {=}
2244
-
2245
-
2246
-
2247
- <a id="examples-example6"></a>
2248
-
2249
- [ex] <http://example.org#>
2250
-
2251
- An **entity** {=ex:e1 .prov:Entity} appeared as a result of some [activity] {+ex:a1 .prov:Activity ?prov:wasGeneratedBy}.
2252
-
2253
-
2254
-
2255
-
2256
-
2257
-
2258
-
2259
- {=}
2260
-
2261
-
2262
-
2263
- <a id="examples-example7"></a>
2264
-
2265
- [ex] <http://example.org#>
2266
-
2267
- # Some entity {=ex:e1 .prov:Entity}
2268
-
2269
- Created by the [activity] {+ex:a1 .prov:Activity ?prov:wasGeneratedBy}.
2270
-
2271
- # Activity has generated an entity {=ex:e1Gen .prov:Generation}
2272
-
2273
- Qualifies creation of the [entity] {+ex:e1 !prov:qualifiedGeneration} by that [activity] {+ex:a1 ?prov:activity} with this additional [influence] {+ex:bar ?ex:foo}.
2274
-
2275
-
2276
-
2277
-
2278
-
2279
-
2280
-
2281
-
2282
- {=}
2283
-
2284
-
2285
-
2286
- <a id="examples-example8"></a>
2287
-
2288
- [ex] <http://example.org#>
2289
-
2290
- # Statistics used for illustration {=ex:usage .prov:Usage}
2291
-
2292
- We have used the [statistics] {+ex:aggregatedByRegions .prov:Entity ?prov:entity} during the [illustration] {+ex:illustrationActivity .prov:Activity !prov:used} at [2011-07-14T03:03:03Z] {prov:atTime ^^xsd:dateTime}.
2293
-
2294
-
2295
-
2296
-
2297
-
2298
- {=}
2299
-
2300
-
2301
-
2302
- <a id="examples-example9"></a>
2303
-
2304
- [ex] <http://example.org#>
2305
-
2306
- # Tutorial blog {=ex:tutorial_blog .prov:Entity .prov:Plan}
2307
-
2308
- ## Agents
2309
-
2310
- [Derek] {=ex:derek .prov:Agent}
2311
-
2312
- ## Roles
2313
-
2314
- [Illustrationist] {=ex:illustrationist .prov:Role}
2315
-
2316
- ## Activities
2317
-
2318
- ### Illustration activity {=ex:illustrationActivity .prov:Activity}
2319
-
2320
- Performed by [Derek] {+ex:derek ?prov:wasAssociatedWith}.
2321
-
2322
- #### Association {=ex:illustration_association .prov:Association}
2323
-
2324
- The [illustration] {+ex:illustrationActivity !prov:qualifiedAssociation} performed by [Derek] {+ex:derek ?prov:agent} acting as an [illustrationist] {+ex:illustrationist ?prov:hadRole} for the [blog] {+ex:tutorial_blog ?prov:hadPlan}.
2325
-
2326
-
2327
-
2328
-
2329
-
2330
-
2331
-
2332
- {=}
2333
-
2334
-
2335
-
2336
- <a id="examples-example10"></a>
2337
-
2338
- [ex] <http://example.org#>
2339
-
2340
- # Bar Chart {=ex:bar_chart .prov:Entity}
2341
-
2342
- ## Generation {=ex:generation .prov:Generation}
2343
-
2344
- Created the [chart] {+ex:bar_chart !prov:wasGeneratedBy} by performing the [illustration] {+ex:illustrationActivity .prov:Activity ?prov:activity} at [2011-07-14T15:52:14Z] {prov:atTime ^^xsd:dateTime}.
2345
-
2346
-
2347
-
2348
-
2349
-
2350
-
2351
-
2352
- {=}
2353
-
2354
-
2355
-
2356
- <a id="examples-example11"></a>
2357
-
2358
- [ex] <http://example.org#>
2359
-
2360
- # Bar chart {=ex:bar_chart .prov:Entity}
2361
-
2362
- Was derived from [regional aggregation] {+ex:aggregatedByRegions .prov:Entity ?prov:wasDerivedFrom}.
2363
-
2364
- # Derivation {=ex:bar_chart_derivation .prov:Derivation}
2365
-
2366
- Used [stats] {+ex:aggregatedByRegions ?prov:entity} during the [aggregation] {+ex:aggregating_activity ?prov:hadActivity} to [create] {+ex:generation_of_bar_chart ?prov:hadGeneration} the [chart] {+ex:bar_chart !prov:qualifiedDerivation} with a recorded [usage] {+ex:use_of_aggregatedData ?prov:hadUsage}.
2367
-