Hi Greg, thanks for your comments!  Responses are inserted below...  - Jem

- DRM: I believe that there ought to be a statement that DRM is also commonly used to indicate Digital Rights Management
 and that the current context should make this clear. 

JT>> Agreed, but we removed the definition as it's not used in the OGSA document.
 
- Failure recovery: It seems a bit "strong" by not allowing the notion of an alternate service or entity to fill the gap
 for a failed service or entity. 

JT>> We amended the definition in line with your comment.
 
- IPC: More words to group HTTP and SOAP as alternate communication means or protocols.  It leaves the feeling that IPC 
and clusters or HPC are all there is.

JT>> We amended the wording to include TCP as one of the example transports. 

- MPI: Explicitly mention that MPI is really for single application, cluster-based environments. "Parallel processing" 
mostly covers this but I'd like to see it made more explicit. 

JT>> We changed to the description to include the words "MPI libraries are generally used to coordinate activity within 
parallel applications."
 
- Resource determination: "The process estimating..." to "The  process of estimating..." 
 
JT>> Thanks!

- Service-oriented architecture: Need to explicitly state that SOAs can be heterogeneous. 

JT>> We decided not to change this definition, but references are provided for discussion about the benefits of SOA, 
including platform-neutrality.

- Web service: Stating it as "machine to machine" interaction is too restrictive.  I'd prefer a more liberal view, say, 
allowing machine or application. 

JT>> Done.