FormalSemanticsCR
From Provenance WG Wiki
(→Constraint 27 (unique-wasEndedBy)) |
(→Constraint 28 (unique-startTime)) |
||
| Line 633: | Line 633: | ||
===Constraint 28 (unique-startTime)=== | ===Constraint 28 (unique-startTime)=== | ||
<math> | <math> | ||
| - | \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. | + | \forall start,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. |
</math> | </math> | ||
Revision as of 16:22, 22 November 2012
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
is satisfied in a mathematical model where the individual elements denotable by x are natural numbers, and the ordering relation symbol
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
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
and
then
. Sets of the form
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.
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
from objects to time intervals
- a function
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
from objects to time intervals
- a function
Intuitively, lifetime(e) is the time interval during which object e exists; and for each
, 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
of entities, disjoint from Activities and Events below.
- a function
that associates each Entity with a Thing, such that for each
, 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,
.
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
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.)
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
of events.
- A function
giving the time of each event; i.e. lifetime(evt) = time(t).
- The derived ordering on events given by
- A function
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
, such that every event
that is a start or end event is also an association. That is,
implies
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
, disjoint from
.
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
of activities, disjoint from Entities and Events
Relations
(ISSUE-214: Luc suggests replaces Generated,EventActivities with
and similar for Used).
Simple relations
The entities, interactions, and activities in a world model are related in the following ways:
- A relation
saying when an event used an entity. An event can use at most one entity, and if
then
must hold.
- A relation
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
then min(lifetime(e)) = time(evt) must hold.
- A relation
associating activities with events, such that
implies
.
- A relation
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
then
, i.e. the duration of the association must be within the lifetime of both the agent and the activity.
- A relation
indicating when one agent acts on behalf of another with respect to a given activity. This must satisfy the constraint that if
then there is an association such that
, 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
where the enti are entities, acti are activities, gi are generations, and ui are usages.
Formally, we consider the (regular) language:
and we use this language to give meaning to derivations:
- A relation
with the constraints that for each derivation path:
- for each substring
we have
(hence, type(g) = generation) and
, and
- for each substring
we have
(hence, type(u) = used) and
.
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
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
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
we write
to indicate that
and ... and
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:
-
if and only if:
- [WF] id denotes an entity
- 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
if and only if:
- [WF] The identifier id maps to an activity
- If st is specified then it is equal to the start time of the activity, that is: min(lifetime(id)) = st
- If et is specified then it is equal to the end time of the activity, that is: max(lifetime(id)) = et
- 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:
-
if and only if:
- [WF] id denotes an agent
- 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.
-
if and only if:
- [WF] The identifier id denotes an event
- [WF] The identifier e denotes an object
- [WF] The identifier a denotes an activity
.
- The event evt is involved in act, that is, such that
.
- The type of evt is generation, i.e. type(evt) = generation
- The event evt occurred at time t, i.e. time(evt) = t
- [Redundant?] The object obj came into existence at time t, that is, min(lifetime(I(e))) = t.
- The event evt generated obj, i.e.
.
- 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.
-
if and only if:
- The identifier id denotes an event
.
- [WF] The identifier id denotes an event
- [WF] The identifier a denotes an activity
- [WF] The identifier e denotes an object
- The event evt is part of act, i.e.
.
- The type of evt is use, i.e., type(evt) = use.
- The event evt occurred at time t, i.e. time(evt) = t
- [Redundant?] The entity obj existed at time t, i.e.,
.
- The event evt used obj, i.e.
.
- 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).
-
holds if and only if:
- [WF] assoc denotes an association
is an association interaction
- [WF] a denotes an activity
is an activity.
- [WF] ag denotes an agent
is an agent.
- [WF] pl denotes a plan
is a plan.
- The association associates the agent with the activity and plan, i.e.
.
- The attributes are valid: valid(W,assoc,attrs).
Start Records
A start record wasStartedBy(id,a,ag,attrs) is interpreted as follows:
-
holds if and only if:
- [WF] id denotes an event
that is also an association
- [WF] a denotes an activity act = I(a)
- [WF] ag denotes an agent agent = I(ag)
- The event evt has type start, i.e. type(evt) = start.
- The agent was associated with the activity, i.e.
- The event was part of the activity, that is,
, and min(lifetime(act)) = time(evt).
- The attributes are valid: valid(W,evt,attrs).
End Records
An activity end record wasEndedBy(id,a,ag,attrs) is interpreted as follows:
-
holds if and only if:
- [WF] id denotes an event evt = I(id) that is also an association
- [WF] a denotes an activity act = I(a)
- [WF] ag denotes an agent agent = I(ag)
- The event evt has type end, i.e. type(evt) = end.
- The agent was associated with the activity, i.e.
- The event was part of the activity, that is,
, and max(lifetime(act)) = time(evt).
- 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:
-
holds if and only if:
- [WF] id denotes an association
that is an association interaction, and type(id) = responsibility.
- [WF] a denotes an activity
is an activity.
- [WF] ag1,ag2 denote agents
are agents.
- The agent agent2 acts for the agent agent1 with respect to the activity act, i.e.
.
- [Redundant?] The association id associates both agents with the activity, i.e.
.
- 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).
-
if and only if:
- [WF] id denotes a derivation
- [WF] e1,e2 denote entities
- [WF] a denotes an activity
- [WF] g denotes a generation event
and type(I(g)) = generation
- [WF] u denotes a use event
and type(I(u)) = used
- The derivation denotes a valid one-step derivation
- 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]).
-
if and only if there exist
,
, and
such that:
- [WF] id denotes a derivation
- [WF] e1,e2 denote entities
- type(u) = used and type(g) = generation and time(g) = t
-
- 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]).
-
if and only if there exists
such that:
- [WF] id denotes a derivation
- [WF] e1,e2 denote entities
-
and time(g) = t
- 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.
-
if and only if:
- [WF] Both a and b are entity identifiers, denoting obj1 = I(a) and obj2 = I(b).
- The two Entities refer to the same Thing, that is, thingOf(obj1) = thingOf(obj2).
- The lifetime of obj1 is contained in that of obj2,i.e.
.
- 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".
-
if and only if:
- [WF] Both a and b are entity identifiers, denoting obj1 = I(a) and obj2 = I(b).
- The lifetime of obj1 overlaps that of obj2. That is,
.
- The two objects refer to the same underlying Thing: thingOf(obj1) = thingOf(obj2)
- 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
the following axioms hold:
Definition 2 (optional-attributes)
- 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,[]).
- 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)
Definition 4 (optional-placeholders)
- activity(id,-,t2,attrs) IF AND ONLY IF there exists t1 such that activity(id,t1,t2,attrs). Here, t2 may be a placeholder.
- 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.
- 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).
- 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).
- 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)
Inference 6 (generation-use-communication-inference)
Inference 7 (entity-generation-invalidation-inference)
Inference 8 (activity-start-end-inference)
</math>
Inference 9 (wasStartedBy-inference)
Inference 10 (wasEndedBy-inference)
Inference 11 (derivation-generation-use-inference)
In this inference, none of a, gen2 or use1 can be placeholders -.
Inference 12 (revision-is-alternate-inference)
In this inference, any of a, g or u may be placeholders.
Inference 13 (attribution-inference)
Inference 14 (delegation-inference)
Inference 15 (influence-inference)
Here, a, g, u may be placeholders -.
Here, pl may be a placeholder -.
Inference 16 (alternate-reflexive)
Inference 17 (alternate-transitive)
Inference 18 (alternate-symmetric)
Inference 19 (specialization-transitive)
Inference 20 (specialization-alternate-inference)
Inference 21 (specialization-attributes-inference)
Constraints
Constraint 22 (key-object)
- The identifier field id is a KEY for the entity(id,attrs) statement.
- The identifier field id is a KEY for the activity(id,t1,t2,attrs) statement.
- The identifier field id is a KEY for the agent(id,attrs) statement.
Constraint 23 (key-properties)
- The identifier field id is a KEY for the wasGeneratedBy(id;e,a,t,attrs) statement.
- The identifier field id is a KEY for the used(id;a,e,t,attrs) statement.
- The identifier field id is a KEY for the wasInformedBy(id;a2,a1,attrs) statement.
- The identifier field id is a KEY for the wasStartedBy(id;a2,e,a1,t,attrs) statement.
- The identifier field id is a KEY for the wasEndedBy(id;a2,e,a1,t,attrs) statement.
- The identifier field id is a KEY for the wasInvalidatedBy(id;e,a,t,attrs) statement.
- The identifier field id is a KEY for the wasDerivedFrom(id;e2,e1,a,g2,u1,attrs) statement.
- The identifier field id is a KEY for the wasAttributedTo(id;e,ag,attr) statement.
- The identifier field id is a KEY for the wasAssociatedWith(id;a,ag,pl,attrs) statement.
- The identifier field id is a KEY for the wasAssociatedWith(id;a,ag, − ,attrs) statement.
- The identifier field id is a KEY for the actedOnBehalfOf(id;ag2,ag1,a,attrs) statement.
- The identifier field id is a KEY for the wasInfluencedBy(id;o2,o1,attrs) statement.
Constraint 24 (unique-generation)
Constraint 25 (unique-invalidation)
Constraint 26 (unique-wasStartedBy)
Constraint 27 (unique-wasEndedBy)
Constraint 28 (unique-startTime)
Constraint 29 (unique-endTime)
Constraint 30 (start-precedes-end)
Constraint 31 (start-start-ordering)
Constraint 32 (end-end-ordering)
Constraint 33 (usage-within-activity)
Constraint 34 (generation-within-activity)
Constraint 35 (wasInformedBy-ordering)
Constraint 36 (generation-precedes-invalidation)
Constraint 37 (generation-precedes-usage)
Constraint 38 (usage-precedes-invalidation)
Constraint 39 (generation-generation-ordering)
Constraint 40 (invalidation-invalidation-ordering)
Constraint 41 (derivation-usage-generation-ordering)
In this constraint, a_, gen_2, use_1 must not be placeholders.
Constraint 42 (derivation-generation-generation-ordering)
In this constraint, any of a, g, u may be placeholders.
Constraint 43 (wasStartedBy-ordering)
Constraint 44 (wasEndedBy-ordering)
Constraint 45 (specialization-generation-ordering)
Constraint 46 (specialization-invalidation-ordering)
Constraint 47 (wasAssociatedWith-ordering)
In the following inferences, pl may be a placeholder -.
Constraint 48 (wasAttributedTo-ordering)
Constraint 49 (actedOnBehalfOf-ordering)
Constraint 50 (typing)
- In this constraint, a, g2, and u1 must not be placeholders.
- In this constraint, pl must not be a placeholder.
Constraint 51 (impossible-unspecified-derivation-generation-use)
In the following rules, g and u must not be -.
Constraint 52 (impossible-specialization-reflexive)
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:
Constraint 54 (impossible-object-property-overlap)
For each
and for each
, the following impossibility constraint holds:
Constraint 55 (entity-activity-disjoint)
Constraint 56 (membership-empty-collection)
