W3C home > Mailing lists > Public > public-prov-wg@w3.org > December 2011

Re: PROV-ISSUE-187: Section 5.2.2 (PROV-DM as on Nov 28) [prov-dm]

From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
Date: Wed, 07 Dec 2011 11:28:57 +0000
Message-ID: <EMEW3|dde68be23e27467e2dfffddff119f851nB6BY008L.Moreau|ecs.soton.ac.uk|4EDF4DF9.1070002@ecs.soton.ac.uk>
To: public-prov-wg@w3.org
Hi Satya

It's frustrating to see that you are raising new issues, when you dont' 
emails regarding previous issues you have raised.

This issue is mostly the same as PROV-ISSUE-101.

On Nov 7th, I responded to your initial comment

followed by a reminder on Nov 30th

To address this specific example, I am not sure what you are trying to 
express, since the attribute status
is application specific. But for example, you could write

activity(a1, [status="composing text", status="uploading attachment", 
status="sending", status="sent"])

meaning that the activity a1 had a status with one of the possible 
values "composing ...", "uploading", ..." sent".

The duration is given by the interval between start and event.

To some extent, an entity interval or an activity interval are opaque, 
we just know that some attributes
hold for the duration.

If you want to describe that something changes in an activity. Say it 
was on hostA, and then on hostB,
then, you need to express this as two separate activities. Likewise, if 
you want to say running, paused, running,
you also have to have separate activities.

What definition would you like to see for type? Intentionally, it's open 
ended, so that we don't constraint
application to using specific typing approaches.
Further information is also available in the type attribute in


On 12/07/2011 01:53 AM, Provenance Working Group Issue Tracker wrote:
> PROV-ISSUE-187: Section 5.2.2 (PROV-DM as on Nov 28) [prov-dm]
> http://www.w3.org/2011/prov/track/issues/187
> Raised by: Satya Sahoo
> On product: prov-dm
> Hi,
> The following are my comments on Section 5.2.2 of the PROV-DM as on Nov 28th 2011.
> Section 5.2.2:
> 1. "attributes: a set of attribute-value pairs [ attr1=val1, ...], representing other attributes of this activity that hold for its whole duration."
> "an activity record's attribute remains constant for the duration of the activity it represents."
> Comment: I have raised this issue before - why does the attribute values of an activity have to hold for its whole duration? Why is this constraint necessary or enforceable?
> If emailing is an activity a0 with attribute "status", then how do we represent [status="composing text"], [status="uploading attachment"], [status="sending"], and [status="sent"]?
> In addition, what does "duration" of activity mean - the time when it is "active" or between its "start event" and "end event"? What about "paused event"?
> 2. "The attribute type is a reserved attribute of PROV-DM, allowing for subtyping to be expressed."
> Comment: Exact definition of "type" is absent?
> Thanks.
> Best,
> Satya

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
Received on Wednesday, 7 December 2011 11:29:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:51:04 UTC