Re: PROV-ISSUE-178 (TLebo): wasStartedBy constraint between started and generated entity [prov-dm]

Luc,

Thanks for your response.

The diagrams are very helpful for gaining an intuition for the constraints.
(I think a little more could be said than "The ordering constraints are represented by triangles."  How does one read a triangle? 
The event of the line to the triangle's immediate left must precede the event of the line to the triangle's immediate right?
Giving an example reading, such as "start of a" must precede "end of a" from the subfigure a, may help.)

After inspecting the subfigures, I think that my original concern is addressed by combining:

* constraint: wasInformedBy-Definition (which creates event e), 
* interpretation: wasInformedBy-ordering (which places the second start event after the first)
* interpretation : generation-activity-ordering (which places the entity between the first activity's start and end)
* interpretation : usage-activity-ordering (which does the same thing for the entity and the using activity)

If that covers my original concern, please feel free to close this issue.

Regards,
Tim


On Dec 19, 2011, at 4:10 AM, Luc Moreau wrote:

> Hi Tim,
> 
> All interpretation constraints have now been illustrated and presented
> in section 
> http://dvcs.w3.org/hg/prov/raw-file/default/model/ProvenanceModel.html#interpretation
> 
> 
> I think the constraint is correctly expressed, since the record wasStartedBy(a2,a1) does not
> identify the entity e, and its generation event. If we had made it explicit, then yes, what
> you suggest is probably right.
> 
> I don't think any further change is required, and I propose
> to close the issue, pending review.
> 
> Regards,
> Luc
> 
> On 12/02/2011 04:19 PM, Provenance Working Group Issue Tracker wrote:
>> 
>> PROV-ISSUE-178 (TLebo): wasStartedBy constraint between started and generated entity [prov-dm]
>> 
>> http://www.w3.org/2011/prov/track/issues/178
>> 
>> Raised by: Timothy Lebo
>> On product: prov-dm
>> 
>> Should an additional constraint be added to wasStartedBy-ordering's interpretation constraint? It currently reads:
>> 
>> "Given two activity records denoted by a1 and a2, if the record wasStartedBy(a2,a1) holds, then the following temporal constraint holds: the start event of the activity record denoted by a1 precedes the start event of the activity record denoted by a2."
>> 
>> but says nothing about the start event of a2 following the generation event of e.
>> 
>> A diagram of the constraint is available at http://dvcs.w3.org/hg/prov/raw-file/e0d6f1a69062/diagrams/activity-ordering-records-control-ordering-record.png 
>> 
>> Thanks,
>> Tim
>> 
>> 
>> 
>>   
> 
> -- 
> Professor Luc Moreau               
> Electronics and Computer Science   tel:   +44 23 8059 4487         
> University of Southampton          fax:   +44 23 8059 2865         
> Southampton SO17 1BJ               email: l.moreau@ecs.soton.ac.uk  
> United Kingdom                     http://www.ecs.soton.ac.uk/~lavm