Hi Etienne,
New title of the GES document ----------------------------- I propose 'PGI Execution Service'. I would be very nervous about, it would possibly give out the wrong impression, we are profiling, not totally new specs.
States and Transitions Model ---------------------------- A software service can easily publish the list of its states and the authorized transitions between states. A software client can easily read them.
But beyond the syntax, the transitions contain SEMANTICS : - Human software engineers can describe (with some work and review) these semantics for understanding by human software engineers, - But I am afraid that it is very difficult to describe these semantics for understanding by a computer software. Therefore, I am afraid that a software client can NOT guess how to adequately USE the listed authorized transitions.
So, I advise that we agree on the largest possible list of states and transitions, with the semantics of their transitions. - That will define PGI-compliance. - Any further refinement of states will be accepted ONLY for logging purposes, but any further transition will be completely optional and NOT supported by PGI.
Agreed. David
Please study this issue, make your own mind, and express your position.
Best regards.
----------------------------------------------------- Etienne URBAH LAL, Univ Paris-Sud, IN2P3/CNRS Bat 200 91898 ORSAY France Tel: +33 1 64 46 84 87 Skype: etienne.urbah Mob: +33 6 22 30 53 27 mailto:urbah@lal.in2p3.fr -----------------------------------------------------
On Tue, 05 May 2009, Moreno Marzolla wrote:
Dear all,
the next PGI teleconference will be held tomorrow, wednesday may 6th at 16:00 CET (duration: 1 hour).
Call-in details as follow: via Skype call +9900827049931906 (free of charge) ordinary phone numbers (local rates) with the 9931906 conference number:
Austria 0820 401 15470 Belgium 0703 57 134 France 0826 109 071 Germany +49 (0) 180 500 9527 Switzerland 0848 560 397
Agenda (please feel free to suggest additional items):
1) Whether http://forge.ogf.org/sf/go/doc15615?nav=1 contains information which should be included in the requirements documents, as suggested by Etienne;
2) Any final issues with the requirements document, especially with the state model as discussed last time; hopefully this item will be discussed very quickly;
3) How the requirements can be mapped into an actual implementation
Moreno.
_______________________________________________ Pgi-wg mailing list Pgi-wg@ogf.org http://www.ogf.org/mailman/listinfo/pgi-wg