- From: Luc Moreau <L.Moreau@ecs.soton.ac.uk>
- Date: Mon, 07 Nov 2011 16:28:58 +0000
- To: Satya Sahoo <satya.sahoo@case.edu>
- CC: public-prov-wg@w3.org
- Message-ID: <EMEW3|ab94bcc1c15743519ea7949ad2b46fa1nA6GY108L.Moreau|ecs.soton.ac.uk|4EB8074A>
Hi Satya, You seem to indicate that an agent should be 'running', an instance of a process. Where did we say that an agent should be like this? We just defined agent as an entity capable of activity. I feel that my workflow script in capable of activity. Luc On 11/07/2011 04:24 PM, Satya Sahoo wrote: > Hi Luc, > Comments on your example are interleaved > > > 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 code for the email client is a specification vs. email client > process corresponding to the distinction between a program (in memory > or on disk etc.) and a process (being actively executed). > > A program can have multiple processes, similar to the blueprint of a > welding robot, reconnaissance drone and actual robots, drones etc. > > The same question also applies to a workflow script, controlling > an activity. Is it an agent > or a plan? > > > Workflow script is a "plan" or "recipe" or "specification" etc. and > not an agent. > > Best, > Satya > > Thanks, > Luc > > > 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)? >> >> Best, >> Satya >> >> 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] >> >> http://www.w3.org/2011/prov/track/issues/147 >> >> 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 <tel:%2B44%2023%208059%204487> > University of Southampton fax:+44 23 8059 2865 <tel:%2B44%2023%208059%202865> > Southampton SO17 1BJ email:l.moreau@ecs.soton.ac.uk <mailto:l.moreau@ecs.soton.ac.uk> > United Kingdomhttp://www.ecs.soton.ac.uk/~lavm <http://www.ecs.soton.ac.uk/%7Elavm> > > > -- 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 Monday, 7 November 2011 16:29:31 UTC