An address may be contained in the message envelope.
A message may have a delivery policy associated with it (2.3.1.3.2)
A message transport is constrained by various delivery policies
Delivery policy constrains message transport - 2.3.1.2.2
A message body is contained by the message envelope
a message envelope may contain address information about the intended recipients of its associated message
A message envelope contains the body of the message
A message body is the application-specific content intended for the message recipient.
Message correlation may be realized by including message identifiers to enable messages to be identified
A message exchange pattern may describe a service invocation
a message may be described using a service description language. There is no concept that represents service description language.
a message may have an identifier (2.3.1.3.2)
A message envelope contains the message headers
A message header is contained in a message envelope
A message exchange parttern should have a unique identifier
a message has a message body (2.3.1.3.2)
A message has a message envelope (2.3.1.3.2)
a message has zero or more message headers (2.3.1.3.2)
a message has one or more message recipients We assume that Message Recipient is the same of Message Receiver
A message is delivered by a message transport system (2.3.1.3.2) I assume that "transport system" is actually Message Transport
A message sender is the originator of a message
message may be part of a message sequence
A message exchange pattern may realize a message correlation
A message sequence may realize a documented message exchange pattern
Message reliability may be realized by a transport mechanism We assume that "transport mechanism" is equivalent to message transport
A message receiver is the recipient of the message
message reliability may be realized by a combination of message acknowledgement and correlation.
a message header may identify a service role, which denotes the kind of processing expected for the header.
a policy is a constraint on the allowable actions or states of an agent or person or organization (interpreted as: a policy constraints the actions performed by an agent)
A permission guard controls one or more resources
a permission may enable one or more actions
a permission may enable one or more allowable states
A permission guard is a mechanism that enforces permissive policies
A policy guard has an owner responsible for establishing the guard.
A person or organization belongs to a domain.
An audit guard may monitor one or more resources (2.3.4.1.2)
A person or organization may be the owner of an agent.
A domain defines the scope of application of zero or more policies.
Discovery may be realized using a discovery service
a resource may be governed by zero or more policies
an identifier identifies a resource that is relevant to the architecture
a resource is owned by a person or an organization
Discovery may be performed by an agent, or by an end-user
A discovery service is used to publish descriptions
a resource may have zero or more representations
a resource may have zero or more resource description
A discovery service is used to search for resources
A discovery service may be used by an agent
a capability can be advertised by an agent that supports it
a service role is a set of service tasks
a capability has a description of its semantics
A service interface defines the message relevant to the service
a goal state is desired by some person or organization which has an interest in defining it.
A choreography may be expressed in a choreography description language
a capability may be @@referenced@@ by a service description
a capability has a identifier which is a URI
An agent has an owner that is a person or organization
A service intermediary adopts a specific service role.
A service is owned by a person or an organization
a provider agent acts on behalf of a provider entity
A service performs one or more tasks Here I assume that "task" is infact "service task"
A service may have one or more policies applied to it
A service intermediary preserves the semantics of messages it receives and sends.
A service is provided by a person or an organization
a requester agent acts on behalf of a requester entity
An agent may realize zer or more services
a service is realized by a provider agent.
An agent may request zer or more services
a capability can be required by agent that wishes to use it
An action may result in a desired goal state
a service description may include a description of the service's semantics
a service description is a machine-processable description of the service's interface
a service semantics should be identified in a service description
a service description is a machine-processable description of a service
A service has a service identifier Here I assume that "service identifier" is the same of the resource model "identifier"
a service has one or more service roles in relation to the service's owner
Approximation of the following statement: a service semantics describes the intended effects of using a service
a service role may be established by a service owner
a service semantics may be described in a formal, machine-processable language
A choreography uses one or more service interfaces
a goal state is a state of the real world, which includes the state of relevant resources
A service has A (ONE) service description
a service has one or more service roles in relation to the
a message sender may be an intermediary I represent this with a subclass so that some message senders are intermediaries, and others are not. Though I also assume that all intermediaries are message receivers, which sounds quite reasonable.
a message receiver may be an intermediary We represent this with a subclass so that some message recipients are intermediaries, and others are not. Though we also assume that all intermediaries are message receivers, which sounds quite reasonable.
A place holder for content of a message body.
A place holder for Choreography Description Language
A place holder class for Computational Resource
A place holder for languages described in the architecture specification.
An Network address is that information required by a message transport mechanism in order to deliver a message appropriately.
A place holder for Policy Description Language
A place holder for Service Description Language
A place holder for Service Semantics Description Language
An address is that information required by a message transport mechanism in order to deliver a message appropriately.
A delivery policy is a policy that constrains the methods by which messages are delivered by the message transport.
A message is the basic unit of data sent from one Web services agent to another in the context of Web services.
A message body is the structure that represents the primary content that the message sender intends to deliver to the message recipient.
Message correlation is the association of a message with a context. Message correlation ensures that a requester agent can match the reply with the request, especially when multiple replies may be possible.
A message envelope is the structure that encapsulates the component parts of a message: the message body and the message headers.
A Message Exchange Pattern (MEP) is a template, devoid of application semantics, that describes a generic pattern for the exchange of messages between agents. It describes the temporal and causal relationships, if any, of multiple messages exchanged in conformance with the pattern, as well as the normal and abnormal termination of any message exchange conforming to the pattern.
A message header is the part of the message that contains information about a specific aspect of the message. Message headers may be available to potential intermediaries that also process the message.
A message Receiver is an agent that receives a message
Message reliability is the degree of certainty that a message will be delivered and that sender and receiver will both have the same understanding of the delivery status. Message reliability is a property of message delivery.
A message sender is the agent that transmits a message
A message sequence is a sequence of related messages
A message transport is a mechanism that may be used by agents to delivers messages
An audit guard is a mechanism used on behalf of an owner that monitors actions and agents to verify the satisfaction of obligations
A domain is a set of agents and/or resources that is subject to constrains of one or more policies.
An obligation is a kind of policy that prescribes actions and/or states of an agent and/or resource.
A permission is a kind of policy that relates to the allowed actions and states of an agent and/or resource. (2.3.4.5.1)
An obligation of a type of policy (2.3.4.5.2)
A permission guard is a mechanism deployed on behalf of an owner that enforces permission policies.
A person or organization may be the owner or agents that provide or request Web services.
A policy is a constraint on the behavior of agents.
A policy description is a machine-processable description of a policy or set of policies
A policy guard is a mechanism deployed on behalf of an owner that enforces a policy (or set of policies). A policy guard is a mechanism that enforces policies. (2.3.4.9.2)
Discovery is the act of locating a machine-processable description of a Web service-related resource that may have been previously unknown and that meets certain functional criteria. It involves matching a set of functional and other criteria with a set of resource descriptions. The goal is to find an appropriate Web service-related resource
A discovery service is a service that enables agents to retrieve Web service-related resource descriptions
An identifier is an opaque string of bits that may be used to associate with a resource.
A representation is a piece of data that describes a resource state.
A resource is defined by [RFC 2396] to be anything that can have an identifier. Although resources in general can be anything, this architecture is only concerned with those resources that are relevant to Web services and therefore have some additional characteristics. In particular, they incorporate the concepts of ownership and control: a resource that appears in this architecture is a thing that has a name, may have reasonable representations and which can be said to be owned. The ownership of a resource is critically connected with the right to set policy on the resource.
A resource description is any machine readable structure that may permit resources to be discovered. Resource descriptions may be of many different forms, tailored for specific purposes, but all resource descriptions must contain the resource's identifier. (2.3.3.6.1)
An action, for the purposes of this architecture, is any action that may be performed by an agent, possibly as a result of receiving a message, or which results in sending a message or other observable state change.
And agent is a program acting on behalf of another person, entity, or process
A capability is a named piece of functionality (or feature) that is declared as supported or requested by an agent.
A choreography defines the sequence and conditions under which multiple cooperating independent agents exchange information in order to achieve some useful function.
A goal state is a state of some service or resource that is desireable from some person or organization's point of view.
An action may be the processing of a received message
A provider agent is an agent that is capable of and empowered to perform the actions associated with a service on behalf of its owner the provider entity.
The provider entity is the person or organization that is providing a Web service.
A requester agent is a software agent that wishes to interact with a provider agent in order to request that a task be performed on behalf of its owner the requester entity
The requester entity is the person or organization that wishes to use a provider entity's Web service.
An action may be the sending of a message
A service is an abstract resource that represents a capability of performing tasks that represents a coherent functionality from the point of view of provider entities and requester entities. To be used, a service must be realized by a concrete provider agent.
A service description is a set of documents that describe the interface to and semantics of a service.
A service interface is the abstract boundary that a service exposes. It defines the types of messages and the message exchange patterns that are involved in interacting with the service, together with any conditions implied by those messages.
A service intermediary is a Web service whose main role is to transform messages in a value-added way. (From a messaging point of view, an intermediary processes messages en route from one agent to another.) Specifically, we say that a service intermediary is a service whose outgoing messages are equivalent to its incoming messages in some application-defined sense.
A service role is an abstract set of tasks which is identified to be relevant by a person or organization offering a service. Service roles are also associated with particular aspects of messages exchanged with a service.
The semantics of a service is the behavior expected when interacting with the service. The semantics expresses a contract (not necessarily a legal contract) between the provider entity and the requester entity. It expresses the intended real-world effect of invoking the service. A service semantics may be formally described in a machine readable form, identified but not formally defined, or informally defined via an `out of band' agreement between the provider entity and the requester entity.
A service task is an action or combination of actions that is associated with a desired goal state. Performing the task involves executing the actions, and is intended to achieve a particular goal state.