]> $Id$ Action 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. result An action may result in a desired goal state part_of_task An action is part of a task Here I assume that "task" here is "service task" Agent And agent is a program acting on behalf of another person, entity, or process has_owner An agent has an owner that is a person or organization realize_service An agent may realize zer or more services request_service An agent may request zer or more services Choreography A choreography defines the sequence and conditions under which multiple cooperating independent agents exchange information in order to achieve some useful function. expressed A choreography may be expressed in a choreography description language Intermediary An intermediary is a specific kind of service whose main role is to modify messages. Specifically, we say that an intermediary is a service whose outgoing messages are equivalent to its incoming messages. has_role An intermediary adopts a specific service role Service A service is an abstract resource that represents a capability of performing tasks that represents a coherent functional role from the point of view of provider entities and requester entities. A service must be realized by a concrete provider agent. A service is a resource perform_task A service performs one or more tasks Here I assume that "task" is infact "service task" A service performs ONE OR MORE TASKS 1 service_description A service has a service description A service has A (ONE) service description 1 service_interface A service has a service interface service_semantics A service has a service semantics service_identifier A service has a service identifier Here I assume that "service identifier" is the same of the resource model "identifier" service_role a service has one or more service roles in relation to the service's owner policies A service may have one or more policies applied to it owned_by A service is owned by a person or an organization provided_by A service is provided by a person or an organization realized_by A service is realized by a software agent requested_by A service is requested by a software agent Service_Description A service description is a set of documents that describe the interface to and semantics of a service. description_service_interface A service description is a description of the service interface Service_Interface A service interface is the abstract boundary that a service exposes. It is comprised of the messages that are involved in interacting with the service, together with any conditions implied by those messages. (2.3.2.7.1) service_task A service interface has one or more service tasks (2.3.2.7.2) define A service interface defines the message relevant to the service (2.3.2.7.2) Provider_Agent 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. provide a provider agent provides one or more tasks (2.3.2.8.2) Requester_Agent 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. request a requester agent requests one or more tasks Service_Role A service role is an abstract set of tasks which is identified to be relevant by a person or organization deploying a service. Service roles are also associated with particular aspects of messages exchanged with a service. a service role is a set of service tasks Service_Semantics The semantics of a service is the behavior expected when interacting with the service. Where this is well defined, it may be expressed as a contract between the provider entity and the requester entity that expresses the 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. (2.3.2.11) about Approximation of the following statement: (2.3.2.11.2) a service semantics describes the intended effects of using a service Service_Task A 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. associated_with a service task is associated with one or more intended goal states. (2.3.2.12.2)