Hi Olegario, thanks for your comments!  See my responses below...

- Jem

1) Too much "See..." (33/148) 

JT>> No change made; this is a normal way to minimize repetition (and maintenance).

2) Some acronyms are explained with 1st letter in uppercase (EMS - Execution Management Service) and others in lower 
case or mixed (DoS - Denial of service; DRM - Distributed resource management/manager) 

JT>> DoS and QoS are the only mixed-case acronyms I see, and I think this is common practice for these terms.  With DoS 
in particular it helps to distinguish it from DOS, which is another well-known acronym in the industry.

3) Not in the Glossary some key words/concepts like: 
� Architecture (related to OGSA and OGSI) 
� Bind (or binding) 
� Broker 
� Business process (used to define Orchestration and Workflow) 
� Consumer (to differentiate it from a requestor and to explain why this term 
 is introduced) 
� Heterogeneity or heterogeneous 
� Infrastructure 
� Node 
� Openness (just to explain how open is the Grid Architecture) 
� Producer (to differentiate it from a provider and to explain why this term is introduced) 
� Provider 
� Requestor 
� Schema 
� URL (because URI is included) 

JT>> We considered several of these for the V1 document, but decided only to add URL. However, the remainder have been 
added to the tracker at https://forge.gridforum.org/tracker/index.php?aid=957 (http://tinyurl.com/472lv), for 
consideration for V2.

4) Comments regarding specific terms: 

� Choreography, orchestration and workflow: Add under Orchestration the relation to the "Orchestrator", and to be 
orchestrated (be the "orchestratee") 

JT>> We felt that these forms of the words were intuitive, and don't need explanation.

� Denial of service (DoS): I would say: An action of refuses the provision of a service due to a form of attack on a 
computer system... 

JT>> We didn't see any reason to change the original definition.

� Entity: Because further definitions (Manageable entity and Manageable resource), I would define this like: Any 
nameable thing like a resource. 

JT>> We added an example in line with your suggestion.

� Event consumer/producer: Not clear. Here, Event seems to be a service what is not deducible from the definition of 
Event, which explicitly should define it as a Service. 

JT>> We felt that the definitions as they stand are clear and correct.

� Interface: In general (for the first given definition), interface is a piece of software/hardware used to inter-
relate two different pieces (service and client?). In particular (for the second paragraph),  WSDL2.0 or WSDL 1.1?

JT>> We narrowed the focus to refer to interfaces in an SOA, and clarified the definition somewhat.
 
� Port type. (or PortType?) Same as Interface: WSDL 1.1 or WSDL 2.0 defs.?

JT>> We changed the spelling to portType, but didn't see a need for any further change. 

� Manageability: I would say: Is the capacity for managing a resource or service with related information. 

JT>> We simplified this definition, and revised many of the management-related terms.

� Resource: ...manageable resource (or simply resource) is synonymous with manageable entities (note that one is 
singular and the second one is plural). Resource should be explicitly and clearly defined and not in terms of a third 
term. 

JT>> We reviewed and changed the definition of resource, and related terms.  We feel that being able to reference other 
terms in a definition is important to minimize duplication and inconsistency.

� Resource deployment (and all terms associated to resource): Why the exclusive for programs and data?  for example, 
storage space is not a resource? 

JT>> Agreed, and we've made changes in this area.

� Resource management: Please define DRM. 

JT>> We removed DRM, as it is not used in the OGSA document.

� Service: I would say: A service is a software module deployed on network-accessible platforms...