FormalSemanticsCR

From Provenance WG Wiki

(Difference between revisions)
Jump to: navigation, search
(Constraint 56 (membership-empty-collection))
(Constraint 53 (impossible-property-overlap))
Line 858: Line 858:
</math>
</math>
===Constraint 53 (impossible-property-overlap)===
===Constraint 53 (impossible-property-overlap)===
-
For each r  \wedge s in { used, wasGeneratedBy, wasInvalidatedBy, wasStartedBy, wasEndedBy, wasInformedBy, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf} such that r  \wedge s are different relation names, the following constraint holds:
+
For each r  and s in { used, wasGeneratedBy, wasInvalidatedBy, wasStartedBy, wasEndedBy, wasInformedBy, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf} such that r  and s are different relation names, the following constraint holds:
<math>
<math>
-
\forall XYZ .~ r(id; a_1,...,am)  \wedge  s(id; b1,...,bn) \Longrightarrow False
+
\forall id,a_1,\ldots,a_m,b_1,\ldots,b_n .~ r(id; a_1,...,am)  \wedge  s(id; b_1,...,b_n) \Longrightarrow False
</math>
</math>
 +
===Constraint 54 (impossible-object-property-overlap)===
===Constraint 54 (impossible-object-property-overlap)===

Revision as of 12:50, 22 November 2012

Contents

Overview

See also FormalSemantics.

The idea of this document is to sketch what aspects of the provenance model can be formalized and how they can be formalized, as a first step towards establishing a consensus on the (intended) meaning of the components of the model and the consistency constraints or inferences that can be applied to the model to distinguish valid from ivalid provenance records.


The PROV-CONSTRAINTS document contains formal content specifying a notion of validity (approximately, logical consistency) for PROV documents. The formal semantics, PROV-SEM, is planned for release as a W3C Note that will complement the procedural specification in PROV-CONSTRAINTS with a declarative specification formulated in terms of first-order logic. The formal semantics is work in progress. The drafts below are intermediate stages and some of them are out of date.

The current version (editor's draft) of the formal semantics can always be found at: FormalSemanticsED.

Status

This is work in progress. The semantics is being updated to be consistent with the Candidate Recommendation of PROV. The plan is to release the semantics as a Note over the next few months. At that point, the wiki pages containing drafts of the semantics will be superseded.


Idea of the semantics

As a starting point, I will assume that we intend the assertions made in a PROV-DM instance to be intended to describe one, consistent state of the world, much like a logical formula is said to be satisfied in a mathematical model. That is, I propose an approach similar to that taken in model theory, where the PROV-DM instance corresponds to a formula or theory of a logic, and the semantics corresponds to what logicians call a model.

For example, the formula \forall x. x \geq 0 is satisfied in a mathematical model where the individual elements denotable by x are natural numbers, and the ordering relation symbol \geq is interpreted as the usual ordering relation on natural numbers. Here, the goal is to come up with a plausible "intended model" for interpreting PROV-DM instances, where the formulas are assertions in PROV-DM and the individuals are things and agents. This is complicated by the fact that many statements about provenance involve talking about objects that change over time.

The modeling methodology I'm using below is similar to that used in some (old, but still relevant) work on preservation: see [1]

The word "world" is used in PROV-DM to talk about the actual state of affairs that the PROV-DM instance describes, which is what I would usually call a "model". The word "model" is used in PROV-DM mainly in the sense of "data model", that is, to talk about what I would otherwise call the syntax of PROV-DM. To avoid confusion with the uses of terms in PROV-DM, I will use "world model" to describe the mathematical structure that corresponds to actual state of affairs, and will try to avoid ambiguous, unqualified uses of the word "model".

Axiomatization and relationship to PROV-CONSTRAINTS

One goal of the semantics is to link the procedural specification of validity and equivalence with traditional notions of logical consistency and equivalence of theories, for example in first-order logic. A first-order axiomatization that corresponds to the formal constraints and is sound for reasoning about the models described below is in progress at the end of the document.

Basics

I will use syntax for PROV-DM records (which I will usually call formulas) as described in the third working draft of PROV-DM (PROV-DM 3PWD).

A PROV-DM instance consisting of assertions φ1...φn is interpreted as a conjunction, that is, the overall instance is considered to hold if each atomic formula in it holds.

The rest of the document will discuss the structure of the worlds and when an atomic assertion holds in a given world.

Identifiers

A lowercase symbol x,y,... on its own denotes an identifier. Identifiers may or may not be URIs. I view identifiers as being like variables in logic (or blank nodes in RDF): just because we have two different identifiers x and y doesn't tell us that they denote different things, since we could discover that they are actually the same later.

Times and Intervals

We assume an ordered set (T,\leq) of time instants. This could be a total order (i.e. a linear timeline) or a partial order describing events that are not necessarily reconciled to a single global clock.

We also consider a set Intervals of sets of time instants closed under "convexity", that is, such that if t_1 \leq t \leq t_2 and t_1,t_2 \in I then t \in I. Sets of the form {t \mid t_1 \leq t \leq t_2} are called basic intervals - there can also be other intervals.

The common case is that T is a finite, linear order, for example, the set of time instants in a single place/time zone. In this case, we can represent all intervals as basic intervals, giving only the starting and ending time [t1,t2]. (If the order is infinite or dense, like the reals or rational numbers, then we need open intervals and infinite intervals too.)

Example

First consider an ordinary linear order Monday < Tuesday < Wednesday < Thursday < Friday. Then all of the intervals are of the form [Monday,Wednesday] or [Tuesday,Friday].

Now consider the time point set {Monday,Tuesday,Tuesday,WednesdayNY,WednesdayCA}, where Monday < Tuesday < WednesdayNY and Monday < Tuesday < WednesdayCA are two basic intervals. The set of all time points in this example is also an interval, but it cannot be defined by taking just two time points.

Attributes and Values

We assume a set Attributes of attribute labels and a set Values of possible values of attributes.

Formulas

Summary of syntax of formulas from PROV-DM.



\begin{array}{rcl}
  formula &::=& element\_formula\\
          & | & relation\_formula\\
  element\_formula
          &::= &entity(id,attrs) \\
          & |&  activity(id,st,et,attrs)\\
          & |&  agent(id,attrs)\\
  relation\_formula
          &::=& wasGeneratedBy(id,e,a,t,attrs)\\
          & |&  used(id,e,a,t,attrs)\\
          & |&  wasAssociatedWith(id,ag,act,pl,attrs)\\
          & |&  wasStartedBy(id,a,ag,attrs)\\
          & |&  wasEndedBy(id,a,ag,attrs)\\
          & |&  actedOnBehalfOf(if,ag2,ag1,act,attrs)\\
          & |&  wasDerivedFrom(id,e2,e1,act,g,u,attrs)\\
          & |&  wasDerivedFrom(id,e2,e1,t,[prov:steps=single,attrs])\\
          & |&  wasDerivedFrom(id,e2,e1,t,[prov:steps=any,attrs])\\
          & |&  alternateOf(e1,e2)\\
          & |&  specializationOf(e1,e2)
\end{array}

Some additional features defined in PROV-DM 3PWD but not yet handled in the semantics are omitted. We exclude from attention derivation, annotations, accounts, and containers, since these features are in flux and non-obvious how to formalize. Also, we omit identifiers and attributes on alternateOf and specializationOf, anticipating that these features will be removed in future drafts.

World Models

Things

Things are things in the world. Each thing has a lifetime during which it exists and attributes whose values can change over time.

To model this, a world model W includes

  • a set Things of things
  • a function lifetime : Things \to Intervals from objects to time intervals
  • a function value : Things \times Attributes \times Times \to Values

Note that this description does not say what the structure of an object is, only how it may be described in terms of its time interval and attribute values. An object could just be a record of fixed attribute values; it could be a bear; it could be the Royal Society; it could be a transcendental number like π. All that matters from our point of view is that we know how to map the object to its time interval and attribute mapping.

It is possible for two Things to be indistinguishable by their attribute values and lifetime, but have different identity.

Objects

A Object is described by a time interval and attributes with unchanging values. Objects encompass entities, interactions, and activities.

To model this, a world includes

  • a set Objects
  • a function lifetime : Objects \to Intervals from objects to time intervals
  • a function value : Objects \times Attributes \to Values

Intuitively, lifetime(e) is the time interval during which object e exists; and for each t \in lifetime(e), the value value(e,a) is the value of attribute a during the object's lifetime.

As with Things, it is also possible to have two different objects that are indistinguishable by their attributes and time intervals.

Entities

An entity is a kind of object that describes a time-slice of a thing, during which some of the thing's attributes are fixed. We assume:

  • a set Entities \subseteq Objects of entities, disjoint from Activities and Events below.
  • a function thingOf : Entities \to Things that associates each Entity with a Thing, such that for each t \in lifetime(obj), and each attribute defined by obj, we have value(obj,a) = value(thingOf(obj),a,t)

Plans

We identify a specific subset of the entities called plans, Plans \subseteq Entities.

Agents

An agent is an entity that can act, by controlling, starting, ending, or participating in activities. Agents can act on behalf of other agents. We introduce:

  • a set Agents \subseteq Entities of agents, which is disjoint from Plans and also necessarily disjoint from Activities and Events

Interactions

We consider Interactions which are split into Events between entities and activities, Associations between agents and activities, and Derivations that describe chains of generation and usage steps. (The first two sets may overlap.)

Interactions = (Events \cup Associations) \uplus Derivations

Events

An Event is an interaction whose lifetime is a single time instant, and relates an activity to an entity (which could be an agent). Events have types including usage, generation, starting and ending (possibly more may be added such as destruction/invalidation of an entity). Events are instantaneous. We introduce:

  • A set Events \subseteq Interactions of events.
  • A function time : Events \to Times giving the time of each event; i.e. lifetime(evt) = time(t).
  • The derived ordering on events given by evt_1 \leq evt_2 \iff t(evt_1) \leq t(evt_2)
  • A function type: Events \to \{start,end,use,generate\} such that Events have types in {start,end,use,generate}.

Associations

An Association is an interaction relating an agent to an activity. Associations can overlap with events; for example, a start event is also an association. To model associations, we introduce:

  • A set Associations \subseteq Interactions, such that every event evt \in Events that is a start or end event is also an association. That is, type(evt) \in \{start,end\} implies evt \in Associations

Associations are used below in the ActsFor and AssociatedWith relations.

Derivations

A Derivation is an interaction chaining one or more generation and use steps. Derivations can also carry attributes, so we introduce an explicit kind of interaction for them that can carry attributes.

  • A set Derivations \subseteq Interactions, disjoint from Events \cup Associations.

See below for the associated derivation path and DerivedFrom relation.

Actvities

An activity is an object that encompasses a set of events. We introduce

  • a set Activities \subseteq Objects of activities, disjoint from Entities and Events

Relations

(ISSUE-214: Luc suggests replaces Generated,EventActivities with Generated : Events \times Entities \times Activities and similar for Used).

Simple relations

The entities, interactions, and activities in a world model are related in the following ways:

  • A relation Used \subseteq Events \times Entities saying when an event used an entity. An event can use at most one entity, and if (evt,e)\in Used then time(evt) \in lifetime(e) must hold.
  • A relation Generated \subseteq Events \times Entities saying when an event generated an entity. An event can generate at most one entity, and an entity is generated by at most one event, and if (evt,e)\in Generated then min(lifetime(e)) = time(evt) must hold.
  • A relation EventActivity \subseteq Events \times Activities associating activities with events, such that (act,evt) \in EventActivity implies time(evt) \in lifetime(act).
  • A relation AssociatedWith \subseteq Association \times Agents \times Activities \times Plans^? indicating when an agent is associated with an activity, and giving the identity of the association relationship, and an optional plan. This must satisfy the constraint that if (assoc,ag,act,pl) \in AssociatedWith then lifetime(assoc) \subseteq lifetime(ag) \cap lifetime(act), i.e. the duration of the association must be within the lifetime of both the agent and the activity.
  • A relation ActsFor \subseteq Agents \times Agents \times Activities indicating when one agent acts on behalf of another with respect to a given activity. This must satisfy the constraint that if (ag_2,ag_1,act) \in ActsFor then there is an association such that (assoc,ag_1,act),(assoc,ag_2,act) \in AssociatedWith, hence, both agents' lifetimes must overlap with some common time point in the lifetime of the activity.

Derivation paths and DerivedFrom

Recall that above we introduced a subset of interactions called Derivations. These identify paths of the form

ent_n\cdot g_n\cdot  act_n\cdot  u_n\cdot  ent_{n-1}\cdot  ...\cdot  ent_1\cdot  g_1\cdot  act_1\cdot  u_1\cdot  ent_0 where the enti are entities, acti are activities, gi are generations, and ui are usages.

Formally, we consider the (regular) language:

  • DerivationPaths = Entities \cdot (Events \cdot Activities \cdot Events \cdot Entities)^+

and we use this language to give meaning to derivations:

  • A relation derivedFrom : Derivations \to DerivationPaths with the constraints that for each derivation path:
  1. for each substring ent\cdot g \cdot act we have (g,ent) \in Generated (hence, type(g) = generation) and (g,act) \in EventActivities, and
  2. for each substring act \cdot u \cdot ent we have (u,ent) \in Used (hence, type(u) = used) and (u,act) \in EventActivities.

Note: The reason why we need paths and not just individual derivation steps is that imprecise-n wasDerivedFrom edges can represent multiple derivation steps. Without this, we can simplify here.

Putting it all together

A world model W is a structure containing all of the above described data. If we need to talk about the objects or relations of more than one world model then we may write W1.Objects; otherwise, to decrease notational clutter, when we consider a fixed world model then the names of the sets, relations and functions above refer to the components of that model.

Semantics

In what follows, let W be a fixed world model with the associated sets and relations discussed in the previous section, and let I be an interpretation of identifiers as objects in W.

The annotations [WF] refer to well-formedness constraints that could in principle be enforced by requiring a consistent typing of identifiers (i.e. by assuming that each identifier is associated with and can only denote an element of Entity, Agent, Note, Activity, Event, Association or Note). These could be factored out or eliminated for readability.

Interpretations

Note that the above discussion does not mention identifiers. We need to add structure to the world to link identifiers to the objects they denote. We do this using a function which we shall call an interpretation.

The mapping from identifiers to objects may not change over time. Thus, we consider interpretations as follows:

  • An interpretation function I : Identifiers \to Objects describing which object is the target of each identifier. This is time-independent.

Satisfaction

Consider an assertion φ, a world W and an interpretation I. We define notation W,I \models \phi which means that φ is satisfied in W,I. For basic assertions, the definition of the satisfaction relation is given in the next few subsections. For a conjunction of assertions \phi_1,\ldots,\phi_n we write W,I \models \phi_1,\ldots,\phi_n to indicate that W,I \models \phi_1 and ... and W,I \models \phi_n hold.

Attribute validity

Objects have attributes, and many

We say that an object obj has valid attributes [attr1 = val1,...] in world W provided:

  • for each attribute attri, we have W.value(obj,attri) = vali.

This is sometimes abbreviated as: valid(W,obj,attrs)

Semantics of Element Records

Entity Records

PROV-DM refers to entity assertions entity(id,attrs).

Entity assertions entity(id,attrs) can be interpreted as follows:

  • W,I \models entity(id,attrs) if and only if:
  1. [WF] id denotes an entity ent = I(id) \in Entities
  2. the attributes are valid: valid(W,ent,attrs).

Activity Records

An activity record is of the form activity(id,plan,st,et,attrs) where id is a identifier referring to the activity, st is a start time and et is an end time. There is also a set of attribute-value pairs describing additional features of the activity. We don't do anything to interpret the plan here, it is purely an annotation (e.g. pointing to a web page describing the program or service that was executed, to source code, or to some other information that might be useful).

  • We say that W,I \models activity(id,st,et,attrs) if and only if:
  1. [WF] The identifier id maps to an activity act = I(id) \in Activities
  2. If st is specified then it is equal to the start time of the activity, that is: min(lifetime(id)) = st
  3. If et is specified then it is equal to the end time of the activity, that is: max(lifetime(id)) = et
  4. The attributes are valid: valid(W,act,attrs).

Agent Records

For the purpose of the semantics so far, an agent record holds at a time instant or interval if the corresponding entity record holds and the entity denoted by the record identifier is an agent.

Agent assertions agent(id,attrs) can be interpreted as follows:

  • W,I \models agent(id,attrs) if and only if:
  1. [WF] id denotes an agent ag = I(id) \in Agents
  2. The attributes are valid: valid(W,ag,attrs).

Note records

Out of scope of the formalization.

Semantics of Relations

Entity-Activity

Generation

The generation assertion is of the form wasGeneratedBy(id,e,a,t,attrs) where id is an event (identifier), e is an object identifier, a is an activity identifier, attrs is a set of attribute-value pairs, and t is an optional time.

  • W,I \models wasGeneratedBy(id,e,a,t,attrs) if and only if:
  1. [WF] The identifier id denotes an event evt = I(id) \in Events
  2. [WF] The identifier e denotes an object obj = I(e) \in Objects
  3. [WF] The identifier a denotes an activity act = I(a) \in Activities.
  4. The event evt is involved in act, that is, such that (evt,act) \in EventActivities.
  5. The type of evt is generation, i.e. type(evt) = generation
  6. The event evt occurred at time t, i.e. time(evt) = t
  7. [Redundant?] The object obj came into existence at time t, that is, min(lifetime(I(e))) = t.
  8. The event evt generated obj, i.e. (evt,obj) \in Generated.
  9. The attribute values are valid: valid(W,evt,attrs)

Use

The use assertion is of the form used(id,a,e,t,attrs) where id denotes an event, a is an activity identifier, e is an object identifier, attrs is a set of attribute-value pairs, and t is an optional time.

  • W,I \models used(id,a,e,t,attrs) if and only if:
  1. The identifier id denotes an event evt = I(id) 
\in Events.
  2. [WF] The identifier id denotes an event evt = I(id) \in Events
  3. [WF] The identifier a denotes an activity act = I(id) \in Activities
  4. [WF] The identifier e denotes an object obj = I(e) \in Objects
  5. The event evt is part of act, i.e. (evt,act) \in EventActivities.
  6. The type of evt is use, i.e., type(evt) = use.
  7. The event evt occurred at time t, i.e. time(evt) = t
  8. [Redundant?] The entity obj existed at time t, i.e., t \in lifetime(obj).
  9. The event evt used obj, i.e. (evt,obj) \in Used.
  10. The attribute values are valid: valid(W,evt,attrs)

Agent-Activity

Association Records

An association record has the form wasAssociatedWith(id,a,ag,pl,attrs).

  • W,I \models wasAssociatedWith(id,a,ag,pl,attrs) holds if and only if:
  1. [WF] assoc denotes an association assoc = I(id) \in Associations is an association interaction
  2. [WF] a denotes an activity act = I(a) \in Activities is an activity.
  3. [WF] ag denotes an agent agent = I(ag) \in Agents is an agent.
  4. [WF] pl denotes a plan plan=I(pl) \in Plans is a plan.
  5. The association associates the agent with the activity and plan, i.e. (assoc,agent,act,plan) \in AssociatedWith.
  6. The attributes are valid: valid(W,assoc,attrs).

Start Records

A start record wasStartedBy(id,a,ag,attrs) is interpreted as follows:

  • W,I \models wasStartedBy(id,a,ag,attrs) holds if and only if:
  1. [WF] id denotes an event evt = I(id) \in Events that is also an association evt \in Associations
  2. [WF] a denotes an activity act = I(a)
  3. [WF] ag denotes an agent agent = I(ag)
  4. The event evt has type start, i.e. type(evt) = start.
  5. The agent was associated with the activity, i.e. (id,ag,act) \in AssociatedWith
  6. The event was part of the activity, that is, (act,evt) \in ActivitiesEvents, and min(lifetime(act)) = time(evt).
  7. The attributes are valid: valid(W,evt,attrs).

End Records

An activity end record wasEndedBy(id,a,ag,attrs) is interpreted as follows:

  • W,I \models wasEndedBy(id,a,ag,attrs) holds if and only if:
  1. [WF] id denotes an event evt = I(id) that is also an association evt \in Associations
  2. [WF] a denotes an activity act = I(a)
  3. [WF] ag denotes an agent agent = I(ag)
  4. The event evt has type end, i.e. type(evt) = end.
  5. The agent was associated with the activity, i.e. (id,ag,act) \in AssociatedWith
  6. The event was part of the activity, that is, (act,evt) \in ActivitiesEvents, and max(lifetime(act)) = time(evt).
  7. The attributes are valid: valid(W,evt,attrs).

Agent-Agent or Entity-Entity

Responsibility

The actedOnBehalfOf(id,ag2,ag1,act,attrs) relation is interpreted using the ActsFor relation as follows:

  • W,I \models actedOnBehalfOf(id,ag2,ag1,act,attrs) holds if and only if:
  1. [WF] id denotes an association assoc=I(id) \in Associations that is an association interaction, and type(id) = responsibility.
  2. [WF] a denotes an activity act=I(a) \in Activities is an activity.
  3. [WF] ag1,ag2 denote agents agent1=I(ag1), agent2=I(ag2) \in Agents are agents.
  4. The agent agent2 acts for the agent agent1 with respect to the activity act, i.e. (agent2,agent1,act) \in ActsFor.
  5. [Redundant?] The association id associates both agents with the activity, i.e. (assoc,agent1,act),(assoc,agent2,act) \in AssociatedWith.
  6. The attributes are valid: valid(W,assoc,attrs).

Derivation

Precise-1

A precise-1 derivation record has the form wasDerivedFrom(id,e2,e1,a,g,u,attrs).

  • W,I \models wasDerivedFrom(id,e2,e1,act,g,u,attrs) if and only if:
  1. [WF] id denotes a derivation deriv = I(id) \in Derivations
  2. [WF] e1,e2 denote entities ent1 = I(e1), ent2=I(e2)  \in Entities
  3. [WF] a denotes an activity act = I(a) \in Activities
  4. [WF] g denotes a generation event gen = I(g) \in Events and type(I(g)) = generation
  5. [WF] u denotes a use event I(u) \in Events and type(I(u)) = used
  6. The derivation denotes a valid one-step derivation derivedFrom(deriv) = I(e2) \cdot I(g) \cdot I(act) \cdot I(u) \cdot I(e1))
  7. The attribute values are valid: valid(W,deriv,attrs).


Imprecise-1

An imprecise-1 derivation record has the form wasDerivedFrom(id,e2,e1,t,[prov:steps = single,attrs]).

  • W,I \models wasDerivedFrom(id,e2,e1,t,[prov:steps=single,attrs]) if and only if there exist act \in Activities, g \in Events, and u \in Events such that:
  1. [WF] id denotes a derivation deriv = I(id) \in Derivations
  2. [WF] e1,e2 denote entities ent1 = I(e1), ent2=I(e2)  \in Entities
  3. type(u) = used and type(g) = generation and time(g) = t
  4. derivedFrom(deriv) = ent2 \cdot g \cdot act \cdot u \cdot ent1)
  5. The attribute values are valid: valid(W,deriv,attrs).
Imprecise-n

An imprecise-n derivation record has the form wasDerivedFrom(id,e2,e1,t,[prov:steps = any,attrs]).

  • W,I \models wasDerivedFrom(id,e2,e1,t,[prov:steps=any,attrs]) if and only if there exists path \in DerivationPaths such that:
  1. [WF] id denotes a derivation deriv = I(id) \in Derivations
  2. [WF] e1,e2 denote entities ent1 = I(e1), ent2=I(e2)  \in Entities
  3. derivedFrom(deriv)= ent2 \cdot g \cdot w \cdot ent1 and time(g) = t
  4. The attribute values are valid: valid(W,deriv,attrs).


Specialization

The specializationOf(e1,e2) relation indicates when one entity record "provides a more concrete characterization of" another. This concept (like alternateOf) is in flux, but we attempt to provide a formalization to aid discussion.

  • W,I \models specializationOf(a,b) if and only if:
  1. [WF] Both a and b are entity identifiers, denoting obj1 = I(a) and obj2 = I(b).
  2. The two Entities refer to the same Thing, that is, thingOf(obj1) = thingOf(obj2).
  3. The lifetime of obj1 is contained in that of obj2,i.e. lifetime(obj_1) \subseteq lifetime(obj_2).
  4. Every attribute attr of obj2 is also an attribute of obj1, and for each such attribute we have value(obj1,attr) = value(obj2,attr).

The second criterion says that the two Entities are descriptions of the same Things. Note that the third criterion allows obj1 and obj2 to have the same lifetime (or that of obj2 can be larger). The last criterion allows obj1 to define more attributes than obj2, but they must agree on their common attributes.

Question: There has been controversy over whether specializationOf is transitive and/oranti-symmetric:

  • Transitivity: If specializationOf(a,b) and specializationOf(b,c) hold then specializationOf(a,c) hold. This holds for the above definition.
  • Antisymmetry: If specializationOf(a,b) and specializationOf(b,a) hold then a = b. This doesn't follow from the current definition (but it would if we stipulated that two entities that have the same interval, attribute and thing are equal).

Alternate

The alternateOf relation indicates when two entity records "provide different characterizations of the same thing".

  • W,I \models alternateOf(a,b) if and only if:
  1. [WF] Both a and b are entity identifiers, denoting obj1 = I(a) and obj2 = I(b).
  2. The lifetime of obj1 overlaps that of obj2. That is, lifetime(obj_1) \cap lifetime(obj_2) \neq \emptyset.
  3. The two objects refer to the same underlying Thing: thingOf(obj1) = thingOf(obj2)
  4. For every attribute attr common to both obj1 and obj2, we have value(obj1,attr) = value(obj2,attr).

Question: There has been controversy whether alternateOf is symmetric and transitive:

  • Symmetry: If alternateOf(a,b) holds then alternateOf(b,a) holds.
  • Transitivity: If alternateOf(a,b) and alternateOf(b,c) hold then alternateOf(a,c) hold. This does not hold of the above definition because we require the intervals to overlap (a and c do not necessarily have overlapping lifetimes.)

We also consider the following properties which have been suggested:

  • specializationOf(e1,e2) implies alternateOf(e1,e2)? (This holds at the moment.)
  • alternateOf(a,b) if and only if there exists c such that specializationOf(a,c) and specializationOf(b,c)? (This does not necessarily hold without further assumptions about the Entities).

Problem: The above definition is symmetric. However, it is not transitive. Suppose

  • lifetime(obj1) = [1,2]
  • lifetime(obj2) = [2,3]
  • lifetime(obj3) = [3,4]

and suppose alternateOf(obj1,obj2) and alternateOf(obj2,obj3) hold. Then alternateOf(obj1,obj3) cannot hold since the intervals of obj1,obj3 do not overlap.

Annotation records

As with note records, annotation records are considered out of scope of the formal semantics.

Axiomatization

Definitions

The definitions are essentially used to map the compact notation and implicit placeholder notation used n PROV-N with the abstract syntax of PROV-DM used in the rest of this semantics. We can formalize the definitional expansion rules as follows:

Definition 1 (optional-identifiers)

For each  r \in  \{ used, wasGeneratedBy, wasInvalidatedBy, wasInfluencedBy, wasStartedBy, wasEndedBy, wasInformedBy, wasDerivedFrom, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf\} the following axioms hold:

  1. r(a_1,...,a_n) \iff \exists id.~ r(id; a_1,...,a_n)
  2. r(-; a_1,...,a_n) \iff \exists id.~ r(id; a_1,...,a_n)

Definition 2 (optional-attributes)

  1. For each p in {entity, activity, agent}, if an is not an attribute list parameter then the following definitional rule holds:

p(a1,...,an) IF AND ONLY IF p(a1,...,an,[]).

  1. For each r in { used, wasGeneratedBy, wasInvalidated, wasInfluencedBy, wasStartedBy, wasEndedBy, wasInformedBy, wasDerivedFrom, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf}, if an is not an attribute list parameter then the following definition holds:

r(id; a1,...,an) IF AND ONLY IF r(id; a1,...,an,[]).

Definition 3 (definition-short-forms)

  1. \forall id,attrs. ~
activity(id,attrs) \iff activity(id,-,-,attrs)
  2. \forall id, e, attrs. ~
wasGeneratedBy(id; e,attrs) \iff wasGeneratedBy(id; e,-,-,attrs)
  3. \forall id,a,attrs. ~
used(id; a,attrs) \iff used(id; a,-,-,attrs)
  4. \forall id,a,attrs. ~
wasStartedBy(id; a,attrs) \iff wasStartedBy(id; a,-,-,-,attrs)
  5. \forall id,a,attrs. ~
wasEndedBy(id; a,attrs) \iff wasEndedBy(id; a,-,-,-,attrs)
  6. \forall id,e,attrs. ~
wasInvalidatedBy(id; e,attrs) \iff wasInvalidatedBy(id; e,-,-,attrs)
  7. \forall id,e1,e2,attrs. ~
wasDerivedFrom(id; e2,e1,attrs) \iff wasDerivedFrom(id; e2,e1,-,-,-,attrs)
  8. \forall id,e,attrs. ~
wasAssociatedWith(id; e,attrs) \iff wasAssociatedWith(id; e,-,-,attrs)
  9. \forall id,a1,a2,attrs. ~
actedOnBehalfOf(id; a2,a1,attrs) \iff actedOnBehalfOf(id; a2,a1,-,attrs)

Definition 4 (optional-placeholders)

  1. activity(id,-,t2,attrs) IF AND ONLY IF there exists t1 such that activity(id,t1,t2,attrs). Here, t2 may be a placeholder.
  2. activity(id,t1,-,attrs) IF AND ONLY IF there exists t2 such that activity(id,t1,t2,attrs). Here, t1 must not be a placeholder.
  3. For each r in { used, wasGeneratedBy, wasStartedBy, wasEndedBy, wasInvalidatedBy, wasAssociatedWith, actedOnBehalfOf }, if the ith parameter of r is an expandable parameter of r as specified in Table 3 then the following definition holds:

r(a0;...,ai-1, -, ai+1, ...,an) IF AND ONLY IF there exists a' such that r(a0;...,ai-1,a',ai+1,...,an).

  1. If a is not the placeholder -, and u is any term, then the following definition holds:

wasDerivedFrom(id;e2,e1,a,-,u,attrs) IF AND ONLY IF there exists g such that wasDerivedFrom(id; e2,e1,a,g,u,attrs).

  1. If a is not the placeholder -, and g is any term, then the following definition holds:

wasDerivedFrom(id;e2,e1,a,g,-,attrs) IF AND ONLY IF there exists u such that wasDerivedFrom(id; e2,e1,a,g,u,attrs).

Inferences

Inference 5 (communication-generation-use-inference)


\forall id, a_2,a_1,attrs. 
wasInformedBy(id; a_2,a_1,attrs) \Longrightarrow
  \exists e, gen, t_1, use,  t_2. wasGeneratedBy(gen; e,a_1,t_1,[]) \wedge used(use; a_2,e,t_2,[])

Inference 6 (generation-use-communication-inference)


\forall gen, a_1, t_1, attrs_1,id_2,a_2,t_2,attrs_2.~wasGeneratedBy(gen; e,a_1,t_1,attrs_1) \wedge used(id_2; a_2,e,t_2,attrs_2) \Longrightarrow \exists id.~wasInformedBy(id; a_2,a_1,[])

Inference 7 (entity-generation-invalidation-inference)


\forall gen, e, a_1, t_1, attrs_1, id_2, a_2, t_2, attrs_2.
wasGeneratedBy(gen; e,a_1,t_1,attrs_1) \wedge used(id_2; a_2,e,t_2,attrs_2) \Longrightarrow  \exists id.~ wasInformedBy(id; a_2,a_1,[])

Inference 8 (activity-start-end-inference)


\forall a, t_1, t_2, attrs.~ activity(a,t_1,t_2,attrs) \Longrightarrow \exists start, e_1, a_1, end, a_2,  e_2.~ wasStartedBy(start; a,e_1,a_1,t_1,[]) \wedge wasEndedBy(end; a,e_2,a_2,t_2,[]) </math>

Inference 9 (wasStartedBy-inference)

 \forall id, a, e_1, a_1, t, attrs.~ wasStartedBy(id; a,e_1,a_1,t,attrs), \Longrightarrow \exists  gen, t_1.~ wasGeneratedBy(gen; e_1,a_1,t_1,[])


Inference 10 (wasEndedBy-inference)

 \forall id, a, e_1, a_1, t, attrs.~ wasEndedBy(id; a,e_1,a_1,t,attrs), \Longrightarrow \exists  gen, t_1 .~ wasGeneratedBy(gen; e_1,a_1,t_1,[])

Inference 11 (derivation-generation-use-inference)

In this inference, none of a, gen2 or use1 can be placeholders -.

 \forall id, e_2, e_1, a, gen_2, use_1, attrs.~ wasDerivedFrom(id; e_2,e_1,a,gen_2,use_1,attrs), \Longrightarrow \exists s, t_1,t_2 .~ used(use_1; a,e_1,t_1,[]) \wedge wasGeneratedBy(gen_2; e_2,a,t_2,[])

Inference 12 (revision-is-alternate-inference)

In this inference, any of a, g or u may be placeholders.

 \forall id, e_1, e_2, a, g,u.~ wasDerivedFrom(id; e_2,e_1,a,g,u,[prov:type='prov:Revision']), \Longrightarrow alternateOf(e_2,e_1)

Inference 13 (attribution-inference)

 \forall att, e, ag, attrs.~ wasAttributedTo(att; e,ag,attrs) \Longrightarrow \exists  a, t, gen, assoc, pl, .~ wasGeneratedBy(gen; e,a,t,[]) \wedge wasAssociatedWith(assoc; a,ag,pl,[])

Inference 14 (delegation-inference)

 \forall id, ag_1, ag_2, a, attrs.~ actedOnBehalfOf(id; ag_1, ag_2, a, attrs) \Longrightarrow \exists  id_1, pl_1, id_2, pl_2 .~ wasAssociatedWith(id_1; a, ag_1, pl_1, []) \wedge wasAssociatedWith(id_2; a, ag_2, pl_2, [])


Inference 15 (influence-inference)

  1.  \forall id, e, a, t, attrs.~ wasGeneratedBy(id; e,a,t,attrs) \Longrightarrow wasInfluencedBy(id; e, a, attrs)
  2.  \forall id, a, e, t, attrs.~ used(id; a,e,t,attrs) \Longrightarrow wasInfluencedBy(id; a, e, attrs)
  3.  \forall id, a_2, a_1, attrs.~ wasInformedBy(id; a_2,a_1,attrs) \Longrightarrow wasInfluencedBy(id; a_2, a_1, attrs)
  4.  \forall id, a_2, e, a_1, t, attrs.~ wasStartedBy(id; a_2,e,a_1,t,attrs) \Longrightarrow wasInfluencedBy(id; a_2, e, attrs)
  5.  \forall id, a_2, e, a_1, t, attrs.~ wasEndedBy(id; a_2,e,a_1,t,attrs) \Longrightarrow wasInfluencedBy(id; a_2, e, attrs)
  6.  \forall id, e, a, t, attrs.~ wasInvalidatedBy(id; e,a,t,attrs) \Longrightarrow wasInfluencedBy(id; e, a, attrs)
  7.  \forall id, e_2, e_1, a, g, u, attrs.~ wasDerivedFrom(id; e_2, e_1, a, g, u, attrs) \Longrightarrow wasInfluencedBy(id; e_2, e_1, attrs). Here, a, g, u may be placeholders -.
  8.  \forall id, e, ag, attrs.~ wasAttributedTo(id; e,ag,attrs) \Longrightarrow wasInfluencedBy(id; e, ag, attrs)
  9.  \forall id, a, ag, pl, attrs.~ wasAssociatedWith(id; a,ag,pl,attrs) \Longrightarrow wasInfluencedBy(id; a, ag, attrs) Here, pl may be a placeholder -.
  10.  \forall id, ag_2, ag_1, a, attrs.~ actedOnBehalfOf(id; ag_2,ag_1,a,attrs) \Longrightarrow wasInfluencedBy(id; ag_2, ag_1, attrs)

Inference 16 (alternate-reflexive)

 \forall e.~ entity(e) \Longrightarrow alternateOf(e,e)

Inference 17 (alternate-transitive)

 \forall e_1, e_2, e_3.~ alternateOf(e_1,e_2) \wedge alternateOf(e_2,e_3) \Longrightarrow alternateOf(e_1,e_3)

Inference 18 (alternate-symmetric)

 \forall e_1, e_2.~ alternateOf(e_1,e_2) \Longrightarrow alternateOf(e_2,e_1)

Inference 19 (specialization-transitive)

 \forall e_1, e_2, e_3 .~ specializationOf(e_1,e_2) \wedge specializationOf(e_2,e_3) \Longrightarrow specializationOf(e_1,e_3)

Inference 20 (specialization-alternate-inference)

 \forall e_1, e_2.~ specializationOf(e_1,e_2) \Longrightarrow alternateOf(e_1,e_2)

Inference 21 (specialization-attributes-inference)

 \forall e_1, attrs, e_2.~ entity(e_1, attrs) \wedge specializationOf(e_2,e_1), \Longrightarrow entity(e_2, attrs)

Constraints

Constraint 22 (key-object)

  1. The identifier field id is a KEY for the entity(id,attrs) statement.
  2. The identifier field id is a KEY for the activity(id,t1,t2,attrs) statement.
  3. The identifier field id is a KEY for the agent(id,attrs) statement.

Constraint 23 (key-properties)

  1. The identifier field id is a KEY for the wasGeneratedBy(id;e,a,t,attrs) statement.
  2. The identifier field id is a KEY for the used(id;a,e,t,attrs) statement.
  3. The identifier field id is a KEY for the wasInformedBy(id;a2,a1,attrs) statement.
  4. The identifier field id is a KEY for the wasStartedBy(id;a2,e,a1,t,attrs) statement.
  5. The identifier field id is a KEY for the wasEndedBy(id;a2,e,a1,t,attrs) statement.
  6. The identifier field id is a KEY for the wasInvalidatedBy(id;e,a,t,attrs) statement.
  7. The identifier field id is a KEY for the wasDerivedFrom(id;e2,e1,a,g2,u1,attrs) statement.
  8. The identifier field id is a KEY for the wasAttributedTo(id;e,ag,attr) statement.
  9. The identifier field id is a KEY for the wasAssociatedWith(id;a,ag,pl,attrs) statement.
  10. The identifier field id is a KEY for the wasAssociatedWith(id;a,ag, − ,attrs) statement.
  11. The identifier field id is a KEY for the actedOnBehalfOf(id;ag2,ag1,a,attrs) statement.
  12. The identifier field id is a KEY for the wasInfluencedBy(id;o2,o1,attrs) statement.

Constraint 24 (unique-generation)


\forall gen_1,gen_2,e,a,t_1,t_2,attrs_1,attrs_2.~ wasGeneratedBy(gen_1; e,a,t_1,attrs_1)  \wedge  wasGeneratedBy(gen_2; e,a,t_2,attrs_2), \Longrightarrow gen_1 = gen_2.

Constraint 25 (unique-invalidation)


\forall inv_1,inv_2,e,a,t_1,t_2,attrs_1,attrs_2 .~ wasInvalidatedBy(inv_1; e,a,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv_2; e,a,t_2,attrs_2), \Longrightarrow inv_1 = inv_2.

Constraint 26 (unique-wasStartedBy)

 
\forall start_1,start_2,a,e_1,e_2,a_0,t_1,t_2,attrs_1,attrs_2 .~ wasStartedBy(start_1; a,e_1,a_0,t_1,attrs_1)  \wedge  wasStartedBy(start_2; a,e_2,a_0,t_2,attrs_2), \Longrightarrow start_1 = start_2.

Constraint 27 (unique-wasEndedBy)


\forall end_1,end_2,a,e_1,e_2,a_0,t_1,t_2,attrs_1,attrs_2 .~ wasEndedBy(end_1; a,e_1,a0,t_1,attrs_1)  \wedge  wasEndedBy(end2; a,e_2,a0,t_2,attrs_2), \Longrightarrow end_1 = end2.

Constraint 28 (unique-startTime)

 
\forall a_1,a_2,t,t_1,t_2,e,attrs,attrs_1 .~ activity(a_2,t_1,t_2,attrs)  \wedge  wasStartedBy(start; a_2,e,a_1,t,attrs_1) \Longrightarrow t_1=t.

Constraint 29 (unique-endTime)

 
\forall  a_1,a_2,t,t_1,t_2,e,attrs,attrs_1.~ activity(a_2,t_1,t_2,attrs)  \wedge  wasEndedBy(end; a_2,e,a_1,t,attrs_1) \Longrightarrow t_2 = t.

Constraint 30 (start-precedes-end)

 
\forall XYZ .~ wasStartedBy(start; a,e_1,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end; a,e_2,a_2,t_2,attrs_2) \Longrightarrow start  \preceq  end.

Constraint 31 (start-start-ordering)

 
\forall XYZ .~ wasStartedBy(start_1; a,e_1,a_1,t_1,attrs_1)  \wedge  wasStartedBy(start_2; a,e_2,a_2,t_2,attrs_2) \Longrightarrow start_1  \preceq  start_2.

Constraint 32 (end-end-ordering)

 
\forall XYZ .~ wasEndedBy(end_1; a,e_1,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end2; a,e_2,a_2,t_2,attrs_2) \Longrightarrow end_1  \preceq  end2.

Constraint 33 (usage-within-activity)

  1.  
\forall XYZ .~ wasStartedBy(start; a,e_1,a_1,t_1,attrs_1)  \wedge  used(use; a,e_2,t_2,attrs_2) \Longrightarrow start  \preceq  use.
  2.  
\forall XYZ .~ used(use; a,e_1,t_1,attrs_1)  \wedge  wasEndedBy(end; a,e_2,a_2,t_2,attrs_2) \Longrightarrow use  \preceq  end.

Constraint 34 (generation-within-activity)

  1.  
\forall XYZ .~ wasStartedBy(start; a,e_1,a_1,t_1,attrs_1)  \wedge  wasGeneratedBy(gen; e_2,a,t_2,attrs_2) \Longrightarrow start  \preceq  gen.
  2.  
\forall XYZ .~ wasGeneratedBy(gen; e_,a,t_,attrs_)  \wedge  wasEndedBy(end; a,e_1,a_1,t_1,attrs_1) \Longrightarrow gen  \preceq  end.

Constraint 35 (wasInformedBy-ordering)

 
\forall XYZ .~ wasInformedBy(id; a_2,a_1,attrs_)  \wedge  wasStartedBy(start; a_1,e_1,a_1',t_1,attrs_1)  \wedge  wasEndedBy(end; a_2,e_2,a_2',t_2,attrs_2) \Longrightarrow start  \preceq  end.

Constraint 36 (generation-precedes-invalidation)

 
\forall XYZ .~ wasGeneratedBy(gen; e,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv; e,a_2,t_2,attrs_2) \Longrightarrow gen  \preceq  inv.

Constraint 37 (generation-precedes-usage)

 
\forall XYZ .~ wasGeneratedBy(gen; e,a_1,t_1,attrs_1)  \wedge  used(use; a_2,e,t_2,attrs_2) \Longrightarrow gen  \preceq  use.

Constraint 38 (usage-precedes-invalidation)

 
\forall XYZ .~ used(use; a_1,e,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv; e,a_2,t_2,attrs_2) \Longrightarrow use  \preceq  inv.

Constraint 39 (generation-generation-ordering)

 
\forall XYZ .~ wasGeneratedBy(gen_1; e,a_1,t_1,attrs_1)  \wedge  wasGeneratedBy(gen_2; e,a_2,t_2,attrs_2) \Longrightarrow gen_1  \preceq  gen_2.

Constraint 40 (invalidation-invalidation-ordering)

 
\forall XYZ .~ wasInvalidatedBy(inv_1; e,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv_2; e,a_2,t_2,attrs_2) \Longrightarrow inv_1  \preceq  inv_2.

Constraint 41 (derivation-usage-generation-ordering)

In this constraint, a_, gen_2, use_1 must not be placeholders.

 
\forall XYZ .~ wasDerivedFrom(d; e_2,e_1,a_,gen_2,use_1,attrs_) \Longrightarrow use_1  \preceq  gen_2.

Constraint 42 (derivation-generation-generation-ordering)

In this constraint, any of a, g, u may be placeholders.

 
\forall XYZ .~ wasDerivedFrom(d; e_2,e_1,a,g,u,attrs)  \wedge  wasGeneratedBy(gen_1; e_1,a_1,t_1,attrs_1)  \wedge  wasGeneratedBy(gen_2; e_2,a_2,t_2,attrs_2) \Longrightarrow gen_1 \prec gen_2.

Constraint 43 (wasStartedBy-ordering)

  1.  
\forall XYZ .~ wasGeneratedBy(gen; e,a_1,t_1,attrs_1)  \wedge  wasStartedBy(start; a_,e,a_2,t_2,attrs_2) \Longrightarrow gen  \preceq  start.
  2.  
\forall XYZ .~ wasStartedBy(start; a_,e,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv; e,a_2,t_2,attrs_2) \Longrightarrow start  \preceq  inv.

Constraint 44 (wasEndedBy-ordering)

  1.  
\forall XYZ .~ wasGeneratedBy(gen; e,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end; a_,e,a_2,t_2,attrs_2) \Longrightarrow gen  \preceq  end.
  2.  
\forall XYZ .~ wasEndedBy(end; a_,e,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv; e,a_2,t_2,attrs_2) \Longrightarrow end  \preceq  inv.

Constraint 45 (specialization-generation-ordering)


 \forall XYZ .~ specializationOf(e_2,e_1)  \wedge  wasGeneratedBy(gen_1; e_1,a_1,t_1,attrs_1)  \wedge  wasGeneratedBy(gen_2; e_2,a_2,t_2,attrs_2) \Longrightarrow gen_1  \preceq  gen_2.

Constraint 46 (specialization-invalidation-ordering)

 
\forall XYZ .~ specializationOf(e_1,e_2)  \wedge  wasInvalidatedBy(inv_1; e_1,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv_2; e_2,a_2,t_2,attrs_2) \Longrightarrow inv_1  \preceq  inv_2.

Constraint 47 (wasAssociatedWith-ordering)

In the following inferences, pl may be a placeholder -.

  1.  
\forall XYZ .~ wasAssociatedWith(assoc; a,ag,pl,attrs)  \wedge  wasStartedBy(start_1; a,e_1,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv_2; ag,a_2,t_2,attrs_2) \Longrightarrow start_1  \preceq  inv_2.
  2.  
\forall XYZ .~ wasAssociatedWith(assoc; a,ag,pl,attrs)  \wedge  wasGeneratedBy(gen_1; ag,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end2; a,e_2,a_2,t_2,attrs_2) \Longrightarrow gen_1  \preceq  end2.
  3.  
\forall XYZ .~ wasAssociatedWith(assoc; a,ag,pl,attrs)  \wedge  wasStartedBy(start_1; a,e_1,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end2; ag,e_2,a_2,t_2,attrs_2) \Longrightarrow start_1  \preceq  end2.
  4.  
\forall XYZ .~ wasAssociatedWith(assoc; a,ag,pl,attrs)  \wedge  wasStartedBy(start_1; ag,e_1,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end2; a,e_2,a_2,t_2,attrs_2) \Longrightarrow start_1  \preceq  end2.

Constraint 48 (wasAttributedTo-ordering)

  1.  
\forall XYZ .~ wasAttributedTo(a_t; e,ag,attrs)  \wedge  wasGeneratedBy(gen_1; ag,a_1,t_1,attrs_1)  \wedge  wasGeneratedBy(gen_2; e,a_2,t_2,attrs_2) \Longrightarrow gen_1  \preceq  gen_2.
  2.  
\forall XYZ .~ wasAttributedTo(a_t; e,ag,attrs)  \wedge  wasStartedBy(start_1; ag,e_1,a_1,t_1,attrs_1)  \wedge  wasGeneratedBy(gen_2; e,a_2,t_2,attrs_2) \Longrightarrow start_1  \preceq  gen_2.

Constraint 49 (actedOnBehalfOf-ordering)

  1.  
\forall XYZ .~ actedOnBehalfOf(del; ag_2,ag_1,a_,attrs)  \wedge  wasGeneratedBy(gen_1; ag_1,a_1,t_1,attrs_1)  \wedge  wasInvalidatedBy(inv_2; ag_2,a_2,t_2,attrs_2) \Longrightarrow gen_1  \preceq  inv_2.
  2.  
\forall XYZ .~ actedOnBehalfOf(del; ag_2,ag_1,a_,attrs)  \wedge  wasStartedBy(start_1; ag_1,e_1,a_1,t_1,attrs_1)  \wedge  wasEndedBy(end2; ag_2,e_2,a_2,t_2,attrs_2) \Longrightarrow start_1  \preceq  end2.

Constraint 50 (typing)

  1.  
\forall XYZ .~ entity(e,attrs) \Longrightarrow entity \in typeOf(e).
  2.  
\forall XYZ .~ agent(ag,attrs) \Longrightarrow agent \in typeOf(ag).
  3.  
\forall XYZ .~ activity(a,attrs) \Longrightarrow activity \in typeOf(a).
  4.  
\forall XYZ .~ used(u; a,e,t,attrs) \Longrightarrow activity \in typeOf(a)  \wedge  entity \in typeOf(e).
  5.  
\forall XYZ .~ wasGeneratedBy(gen; e,a,t,attrs) \Longrightarrow entity \in typeOf(e)  \wedge  activity \in typeOf(a).
  6.  
\forall XYZ .~ wasInformedBy(id; a_2,a_1,attrs) \Longrightarrow activity \in typeOf(a_2)  \wedge  activity \in typeOf(a_1).
  7.  
\forall XYZ .~ wasStartedBy(id; a_2,e,a_1,t,attrs) \Longrightarrow activity \in typeOf(a_2)  \wedge  entity \in typeOf(e)  \wedge  activity \in typeOf(a_1).
  8.  
\forall XYZ .~ wasEndedBy(id; a_2,e,a_1,t,attrs) \Longrightarrow activity \in typeOf(a_2)  \wedge  entity \in typeOf(e)  \wedge  activity \in typeOf(a_1).
  9.  
\forall XYZ .~ wasInvalidatedBy(id; e,a,t,attrs) \Longrightarrow entity \in typeOf(e)  \wedge  activity \in typeOf(a).
  10. In this constraint, a, g2, and u1 must not be placeholders.

 
\forall XYZ .~ wasDerivedFrom(id; e_2, e_1, a, g2, u1, attrs) \Longrightarrow entity \in typeOf(e_2)  \wedge  entity \in typeOf(e_1)  \wedge  activity \in typeOf(a).

  1.  
\forall XYZ .~ wasDerivedFrom(id; e_2, e_1, -, -, -, attrs) \Longrightarrow entity \in typeOf(e_2)  \wedge  entity \in typeOf(e_1).
  2.  
\forall XYZ .~ wasAttributedTo(id; e,ag,attr) \Longrightarrow entity \in typeOf(e)  \wedge  agent \in typeOf(ag).
  3. In this constraint, pl must not be a placeholder.

 
\forall XYZ .~ wasAssociatedWith(id; a,ag,pl,attrs) \Longrightarrow activity \in typeOf(a)  \wedge  agent \in typeOf(ag)  \wedge  entity \in typeOf(pl).

  1.  
\forall XYZ .~ wasAssociatedWith(id; a,ag,-,attrs) \Longrightarrow activity \in typeOf(a)  \wedge  agent \in typeOf(ag).
  2.  
\forall XYZ .~ actedOnBehalfOf(id; ag_2,ag_1,a,attrs) \Longrightarrow agent \in typeOf(ag_2)  \wedge  agent \in typeOf(ag_1)  \wedge  activity \in typeOf(a).
  3.  
\forall XYZ .~ alternateOf(e_2, e_1) \Longrightarrow entity \in typeOf(e_2)  \wedge  entity \in typeOf(e_1).
  4.  
\forall XYZ .~ specializationOf(e_2, e_1) \Longrightarrow entity \in typeOf(e_2)  \wedge  entity \in typeOf(e_1).
  5.  
\forall XYZ .~ mentionOf(e_2,e_1,b) \Longrightarrow entity \in typeOf(e_2)  \wedge  entity \in typeOf(e_1)  \wedge  entity \in typeOf(b).
  6.  
\forall XYZ .~ hadMember(c,e) \Longrightarrow prov:Collection \in typeOf(c)  \wedge  entity \in typeOf(c)  \wedge  entity \in typeOf(e).
  7.  
\forall XYZ .~ entity(c,[prov:type=prov:EmptyCollection]) \Longrightarrow entity \in typeOf(c)  \wedge  prov:Collection \in typeOf(c) \wedge  prov:EmptyCollection \in typeOf(c).


Constraint 51 (impossible-unspecified-derivation-generation-use)

In the following rules, g \wedge u must not be -.

  1. 
\forall XYZ .~ wasDerivedFrom(id;e_2,e_1,-,g,-,attrs) \Longrightarrow False
  2.  
\forall XYZ .~ wasDerivedFrom(id;e_2,e_1,-,-,u,attrs) \Longrightarrow False
  3. 
\forall XYZ .~ wasDerivedFrom(id;e_2,e_1,-,g,u,attrs) \Longrightarrow False

Constraint 52 (impossible-specialization-reflexive)


\forall XYZ .~ specializationOf(e,e) \Longrightarrow False

Constraint 53 (impossible-property-overlap)

For each r and s in { used, wasGeneratedBy, wasInvalidatedBy, wasStartedBy, wasEndedBy, wasInformedBy, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf} such that r and s are different relation names, the following constraint holds:


\forall id,a_1,\ldots,a_m,b_1,\ldots,b_n .~ r(id; a_1,...,am)  \wedge  s(id; b_1,...,b_n) \Longrightarrow False

Constraint 54 (impossible-object-property-overlap)

For each p \in \{entity, activity, agent\} and for each r \in \{ used, wasGeneratedBy, wasInvalidatedBy, wasInfluencedBy, wasStartedBy, wasEndedBy, wasInformedBy, wasDerivedFrom, wasAttributedTo, wasAssociatedWith, actedOnBehalfOf\}, the following impossibility constraint holds:


\forall id,a_1,\ldots,a_m,b_1,\ldots,b_n.~ p(id,a_1,\ldots,a_m)  \wedge  r(id; b_1,\ldots,b_n) \Longrightarrow False

Constraint 55 (entity-activity-disjoint)


\forall id .~ entity \in typeOf(id)  \wedge  activity \in typeOf(id) \Longrightarrow False

Constraint 56 (membership-empty-collection)


\forall c,e .~ hasMember(c,e)  \wedge prov:EmptyCollection \in typeOf(c) \Longrightarrow False

Personal tools