ISSUE-105: 5.3.1 Generation (current version of the conceptual model document)

5.3.1 Generation (current version of the conceptual model document)

State:

CLOSED

Product:

prov-dm

Raised by:

Satya Sahoo

Opened on:

2011-09-28

Description:

Hi,
My review comments for 5.3.1 Generation in the current version of the conceptual model document:

5.3.1 Generation
=====
1. In PROV-DM, a generation expression is a representation of a world event, the creation of a new characterized thing by an activity. This characterized thing did not exist before creation.

Issue: The "characterized thing" in the above statements is Entity or some other resource?

2. contains a generationQualifier q that describes the modalities of generation of this thing by this activity

Issue: How is this qualifier distinct from specialization of the generation property?

3. The first one is available as the first value on port p1, whereas the other is the second value on port p1.

Issue: As we discussed during the telcon on Sept 15 [1] and in email thread (Subject: Roles, initiated by Paolo on Sept 15), the "qualifier" if any are on the entity and PE and not on the relation. In the above statement, port p1 is qualifier for either the entities e1, e2 (they were generated on that particular port) or the PE pe1 (it was using that port for listening/responding). Hence, the qualifiers are on the "class" and not the "relation".

[1] http://www.w3.org/2011/prov/meeting/2011-09-15

4. If two process executions sequentially set different values to some attribute by means of two different generate events, then they generate distinct entities.

Issue: This is an incorrect statement. Setting values of an entity at different points of time cannot be equated to generating new entities. For example, we don't generate a new human being everytime a PE changes the value of their age. pe1 sets Person X age = 5 years in 2005 and pe2 sets Person X age = 10 years in 2010 then they are not generating new person (within an account or across accounts).

5. Alternatively, for two process executions to generate an entity simultaneously, they would require some synchronization by which they agree the entity is released for use; the end of this synchronization would constitute the actual generation of the entity, but is performed by a single process execution.Given an entity expression denoted by e, two process execution expressions denoted by pe1 and pe2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then pe1=pe2 and q1=q2.

Issue: If two sculptors collaborate on creating a human figurine statue entity e1: sculptor A by PE pe1 creates the arms and legs of e1 and sculptor B by PE pe2 creates the head and upper-body part of e1 then both pe1 and pe2 create e1. They may or may not be synchronized. How can we infer that pe1 = pe2 (whether in one account or across accounts)?

6. Given an identifier pe for a process execution expression, an identifier e for an entity expression, qualifier q, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, then the values of some of e's attributes are determined by the activity represented by process execution expression identified by pe and the entity expressions used by pe. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entity expressions may have been asserted. [PROV:0002]

Issue: This constraint is confusing (maybe even contradictory) - some or none attributes may be determined? Further, there is no specification or mechanism defined to identify which attributes were determined by the PE? the constraint does not provide any new information (even as a constraint) regarding generation.

7. If an assertion wasGeneratedBy(x,pe,r) or wasGeneratedBy(x,pe,r,t), then generation of the thing denoted by x precedes the end of pe and follows the beginning of pe.

Issue: Suggest rewording this: given the assertion that "an Entity e1 was generated by a PE pe1" then "the Entity e1 did not exist before start of PE pe1".

Related Actions Items:

No related actions

Related emails:

1. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from satya.sahoo@case.edu on 2012-02-16)
2. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from L.Moreau@ecs.soton.ac.uk on 2012-01-17)
3. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from soiland-reyes@cs.manchester.ac.uk on 2012-01-17)
4. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from L.Moreau@ecs.soton.ac.uk on 2012-01-17)
5. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from soiland-reyes@cs.manchester.ac.uk on 2012-01-17)
6. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from L.Moreau@ecs.soton.ac.uk on 2012-01-16)
7. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from satya.sahoo@case.edu on 2011-12-07)
8. Re: PROV-ISSUE-190: Section 5.3.1.1 (PROV-DM as on Nov 28) [prov-dm] (from L.Moreau@ecs.soton.ac.uk on 2011-12-07)
9. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from L.Moreau@ecs.soton.ac.uk on 2011-11-30)
10. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from lebot@rpi.edu on 2011-11-16)
11. Re: PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from L.Moreau@ecs.soton.ac.uk on 2011-11-07)
12. PROV-ISSUE-105: 5.3.1 Generation (current version of the conceptual model document) [Conceptual Model] (from sysbot+tracker@w3.org on 2011-09-28)

Related notes:

No additional notes.

Display change log