Distributed trust management for validating sla choreographies

16 Feb

Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.] A Web service is an abstract notion that must be implemented by a concrete agent.

(See Figure 1-1) The agent is the concrete piece of software or hardware that sends and receives messages, while the service is the resource characterized by the abstract set of functionality that is provided.

Nonetheless, for consistency we still use the term "requester agent" for the agent that interacts with the provider agent, even in cases when the provider agent actually initiates the exchange.) Note: A word on terminology: Many documents use the term service provider to refer to the provider entity and/or provider agent.

While the concepts and relationships represent an enumeration of the architecture, the stakeholders' perspectives approaches from a different viewpoint: how the architecture meets the goals and requirements.

In this section we elucidate the more global properties of the architecture and demonstrate how the concepts actually achieve important objectives.

Using this assertion as a basis, we can assess conformance to the architecture of a particular resource by looking for its identifier.

If, in a given instance of this architecture, a resource has no identifier, then it is not a valid instance of the architecture.