Link to page: 5.2 Service Discovery and Governance
{toc]
Comment 04 on Section 5.2
Section 5 > caGRID 2.0 Platform and Terminology Integration > Service Discovery November 22 version
The terms orchestration, choreography, and composition seem to be used interchangeably. The dynamic composibility of services, including runtime contract discovery, is a hard if not unsolvable task. The paragraph would benefit from a more careful wording, e.g., emphasizing design-time or semi-automatic composition, where specific services are discovered and composed to solve specific tasks. Note that in a composition of services, current state of the art abstracts services as one input/ one output only. Additionally taking into account more complicated choreographies of 2 services interacting is not feasible.
Resolution:
Comment 03 on Section 5.2
Section 5 > Service Discovery and Governance November 22 version
It states "Service discovery and governance allows service developers to specify rich metadata about services". This should be the other way around: specify rich metadata about services allows service discovery?
Resolution:
Comment 02 on Section 5.2
It states "Service discovery and governance help to accomplish the following:" where the last bullet is "Enable better discovery". This is circular and similar to the above, it is the expressing of rich metadata that enables better discovery.
Resolution:
Comment 01 on Section 5.2
Section 5 > Service Discovery and Governance > Service Discovery Functions November 22 version
The discovery functions are rather implementation-level (involving service endpoints and service interfaces). What about the discovery of services based on a declaratively specified goal or task and the rich metadata of services using semantic reasoning?
Resolution:
