SEE Execution Semantics - set of tasks

[Maciej Zaremba <maciej.zaremba@deri.org>]

Hi all,

I prepared a set of tasks for SEE Execution Semantics deliverable as we
agreed during last phone conference. I would like to ask people 
interested in getting involved in this deliverable to indicate
tasks/sections they would like to contribute to. It has to be emphasized
that this list of items can be *extended/modified* and people are more
then welcome to provide their suggestions. Here is the initial list of
tasks:

1. Section 1.3 Relationships to Other Specifications

2. Section 2 Motivation - it would be worthwhile to elaborate on this
section, to outline more clearly methods that can be applied to model
system behaviors, advantages of formal methods over informal ones. In
general these informations are already there but it would be good to do
it in collaboration with someone who could bring a fresh view on this
section.

3. Section 3 Proposed Description Formalism - IMO it would be good to
revise presented three methods (Activity Diagrams, workflow, Abstract
State Machines) that are already described there in more abstract way
(avoiding references to particular platforms - WSMX of IRS-3).
Additionally, a subsection 3.4 could be added where semantics of chosen
method (preferably Activity Diagrams due to its readability) would be
provided in the detail to guide reader in the notation used throughout
the document to model SEE Execution Semantics.

4. Section 4 Overall Approach - introduction

4.1 Capability based service execution - a complete execution of Web
service on behalf and according to requestor's  Goal. It includes
following components\services: Web service discovery, Web service
selection, Data and Process Mediation, Communication Manager, Resource
Manager.

4.2 Goal centric Web Service discovery - according to the specified
goal a set of Web services is returned. It is up to the requester to
choose of them and to register communication with it using ES described
in section 4.4. It includes: Discovery, Data Mediation, Comm. Manager,
Resource Manager.

4.3 The invocation of Web Services - once conversation between
requester and WS is registered this ES can be used to coordinate the
communication and to pass/mediate messages between interacting parties.
It includes: Data and Process Mediation, Comm. Manager, Choreography,
Resource Manager.

4.4 Register communication with SEE - allows requester to register
communication context with selected WS. Includes: Resource Manager.

   more ... (any suggestions from Open University ?)

5. Proofreading of the document.


I am looking forward to the proposals of your contribution.

Best,
Maciej

-- 
Maciej Zaremba    maciej.zaremba@deri.org
Digital Enterprise Research Institute (DERI)
National University of Ireland, Galway
Galway, Ireland   http://www.deri.ie