prov:asInBundle is used to specify which bundle the general entity of a prov:mentionOf
property is described. When :x prov:mentionOf :y and :y is described in Bundle
:b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in
which :y was described.

Classify prov-o terms into three categories, including 'starting-point', 'qualifed',
and 'extended'. This classification is used by the prov-o html document to
gently introduce prov-o terms to its users.

Classify prov-o terms into six components according to prov-dm, including
'agents-responsibility', 'alternate', 'annotations', 'collections', 'derivations',
and 'entities-activities'. This classification is used so that readers of
prov-o specification can find its correspondence with the prov-dm specification.

This property has multiple RDFS domains to suit multiple OWL Profiles. See
<a href="#owl-profile">PROV-O OWL Profile</a>.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).

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.

PROV-O does not define all property inverses. The directionalities defined
in PROV-O should be given preference over those not defined. However, if users
wish to name the inverse of a PROV-O property, the local name given by prov:inverse
should be used.

prov:mentionOf is used to specialize an entity as described in another bundle.
It is to be used in conjuction with prov:asInBundle. prov:asInBundle is used
to cite the Bundle in which the generalization was mentioned.

This annotation property links a subproperty of prov:wasInfluencedBy with
the subclass of prov:Influence and the qualifying property that are used to
qualify it. Example annotation: prov:wasGeneratedBy prov:qualifiedForm prov:qualifiedGeneration,
prov:Generation . Then this unqualified assertion: :entity1 prov:wasGeneratedBy
:activity1 . can be qualified by adding: :entity1 prov:qualifiedGeneration
:entity1Gen . :entity1Gen a prov:Generation, prov:Influence; prov:activity
:activity1; :customValue 1337 . Note how the value of the unqualified influence
(prov:wasGeneratedBy :activity1) is mirrored as the value of the prov:activity
(or prov:entity, or prov:agent) property on the influence class.

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.This property has multiple RDFS domains to suit multiple
OWL Profiles. See <a href="#owl-profile">PROV-O OWL Profile</a>.

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.It is not
recommended that the type ActivityInfluence be asserted without also asserting
one of its more specific subclasses.

It is not recommended that the type AgentInfluence be asserted without also
asserting one of its more specific subclasses.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.

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 ].

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 ].

The more specific forms of prov:Derivation (i.e., prov:Revision, prov:Quotation,
prov:PrimarySource) should be asserted if they apply.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 ].

This concept allows for the provenance of the dictionary, but also of its
constituents to be expressed. Such a notion of dictionary corresponds to a
wide variety of concrete data structures, such as a maps or associative arrays.A
given dictionary forms a given structure for its members. A different structure
(obtained either by insertion or removal of members) constitutes a different
dictionary.

It is not recommended that the type EntityInfluence be asserted without also
asserting one of its more specific subclasses.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.

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.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.

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.

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.

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
] .

An instance of prov:Usage provides additional descriptions about the binary
prov:used relation from some prov:Activity to an prov:Entity that it used.
For example, :keynote prov:used :podium; prov:qualifiedUsage [ a prov:Usage;
prov:entity :podium; :foo :bar ].

This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to
public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org,
archives http://lists.w3.org/ Archives/Public/public-prov-comments/). All
feedback is welcome.

0.2This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to
public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org,
archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback
is welcome.

This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to
public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org,
archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback
is welcome.

This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to
public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org,
archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback
is welcome.

This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to
public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org,
archives http://lists.w3.org/Archives/Public/public-prov-comments/ ). All
feedback is welcome.

This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page).
If you wish to make comments regarding this document, please send them to
public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org,
archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback
is welcome.