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

Re: PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]

From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
Date: Mon, 7 Nov 2011 17:32:25 +0000
To: Paolo Missier <Paolo.Missier@ncl.ac.uk>
CC: "public-prov-wg@w3.org" <public-prov-wg@w3.org>
Message-ID: <EMEW3|bcc934bfdd8ea1f08ccb60f774d30321nA6HWU08L.Moreau|ecs.soton.ac.uk|69EC54AD-33AE-4E48-AAA7-D5EFBAE3FB0C@ecs.soton.ac.uk>
Hi paolo,

We know that there is always an "interpreter":
Workflow script interpreted by workflow engine, she'll script by shell interpreter, executable by processor, etc

If it's the intention of a plan that it is interpreted some agent interpreter, I am ok, but the specs need to make it clear.

Professor Luc Moreau
Electronics and Computer Science
University of Southampton
Southampton SO17 1BJ
United Kingdom

On 7 Nov 2011, at 17:06, "Paolo Missier" <Paolo.Missier@ncl.ac.uk<mailto:Paolo.Missier@ncl.ac.uk>> wrote:

+1 for plan.

a workflow script is a plan, as other suggested.
The workflow engine would be an agent.


On 11/7/11 5:01 PM, Luc Moreau wrote:
Hi Jim and Satya,

I welcome any proposal that clarifies this concept that I don't understand.
Plan is already a great improvement.

However, take an activity run by my email client. I would argue that my email
client executable is a specification of an activity and is also a plan.
In this specific case, what's the difference between a Plan and a (Software) Agent?

The same question also applies to a workflow script, controlling an activity.  Is it an agent
or a plan?


On 11/07/2011 03:28 PM, Satya Sahoo wrote:
+1 for replacing Recipe.

Plan is a nice alternative - should we make it Activity/Process Plan (corresponds to the Activity/Process Execution)?


On Mon, Nov 7, 2011 at 10:16 AM, Provenance Working Group Issue Tracker <sysbot+tracker@w3.org<mailto:sysbot%2Btracker@w3.org>> wrote:

PROV-ISSUE-147 (Replace recipe): Change the name if "Recipe" [Data Model]


Raised by: James McCusker
On product: Data Model

We chose Recipe to be explicitly clear about the use of a method or plan to guide a ProcessExecution. We should find a broader term that isn't as tied to the cake example. This is what I recommend. We start with the term "Recipe" and replace it with ever more general terms that are unambiguous. We then accept the broadest possible term that cannot be confused with an occurrent.

My first cut is "Plan". It's short, simple, and unambiguous. I think it's sufficiently general to cover the definition of "Recipe" without being confused with "Process".

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<mailto:l.moreau@ecs.soton.ac.uk>
United Kingdom                     http://www.ecs.soton.ac.uk/~lavm<http://www.ecs.soton.ac.uk/%7Elavm>

-----------  ~oo~  --------------
Paolo Missier - Paolo.Missier@newcastle.ac.uk<mailto:Paolo.Missier@newcastle.ac.uk>, pmissier@acm.org<mailto:pmissier@acm.org>
School of Computing Science, Newcastle University,  UK
Received on Monday, 7 November 2011 17:33:16 UTC

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