Johannes, Morris, and all, Concerning the 'EMI Execution Service Specification' version 1.0 dated 20 December 2010 available at http://forge.gridforum.org/sf/go/doc16254?nav=1 here are my first remarks : General structure ----------------- Exactly like the the 'PGI Execution Service Specification' (doc15839), this document is built upside down, beginning with SOAP specific port-types and operations. Best practices of Software Engineering are to : - begin with use cases and requirements (or with documents or web pages detailing these use cases and requirements), - continue with the description of the managed and used entities, the security context, the relationships between the entities, the state model, the sequence of interactions, ... - only then describe the abstract (NOT SOAP-specific) dialog protocol with exchanged records, requests, responses, subscriptions, notifications, ... - describe SOAP specific port-types and operations in a separate RENDERING document referencing the SPECIFICATION document. So, at least, the SPECIFICATION document must have following structure : 1) Introduction 2) Use Cases and Requirements In particular for : - long term traceability, - Resource matching, - Data staging. 3) Managed and Used entities 3.1) Reference = GLUE 2.0 3.2) Entities = User, Policy, Activity, Endpoint, Data file, JSDL document 3.3) Security context = IGTF + VOMS + Delegation, X509 or SAML 3.4) UML Collaboration diagram(s) with comments 3.5) UML State Diagram(s) with comments 3.6) UML Sequence Diagrams with comments 4) Abstract dialog protocol 4.1) Exchanged records (representing entity attributes) 4.2) Operations (requests, responses, subscriptions, notifications) SOAP specific port-types and operations must be described in a separate RENDERING document referencing the SPECIFICATION document. 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 -----------------------------------------------------