RE: Definitions

Hi,

	I would like to reiterate my earlier suggestion : Let us use the
definitions from the WS-Arch group and not redefine them. We should, of
course, add more definitions as needed.

cheers

 | -----Original Message-----
 | From: www-ws-arch-request@w3.org 
 | [mailto:www-ws-arch-request@w3.org] On Behalf Of David Booth
 | Sent: Tuesday, March 19, 2002 6:25 AM
 | To: www-ws-desc@w3.org; www-ws-arch@w3.org
 | Subject: Re: Definitions
 | 
 | 
 | I should clarify that the definitions below are intended for the WS 
 | Description WG.  The Architecture group may need broader definitions 
 | because its charter is much broader.  However, we obviously want to 
 | coordinate definitions between the groups as much as possible.
 | 
 | At 06:21 PM 3/18/2002 -0500, David Booth wrote:
 | >Here is a new draft of definitions, incorporating a number 
 | of people's 
 | >suggestions and concerns.  I am cross posting this to both 
 | the WS-Arch WG 
 | >and the WS-Desc WG because it is clearly relevant to both 
 | groups.  Again, 
 | >please comment.
 | >
 | >
 | >Non-Normative Definitions
 | >=========================
 | >
 | >Web Service
 | >"A web service is is a software application or component 
 | that can be 
 | >accessed over the Internet using a 
 | vendor/platform/language-neutral data 
 | >interchange format to invoke the service and supply the 
 | response, using a 
 | >rigorously defined message exchange pattern, and producing 
 | a result that 
 | >is sufficiently well-defined to be processed by a software 
 | application." [1]
 | >
 | >[The above definition was lifted verbatim from a WS Arch WG 
 | >draft.[1]  Note that this definition does not specifically 
 | mention "URI" 
 | >or "XML".  If the definition of "Web Service" does not specifically 
 | >mention URI or XML, then I would suggest that we 
 | specifically mention 
 | >"URI" and "XML" elsewhere in our requirements, if desired.  
 | -- David Booth]
 | >
 | >Client
 | >Software that makes use of a Web Service, acting as its 
 | "user" or "customer".
 | >
 | >Normative Definitions
 | >=====================
 | >
 | >Message
 | >The basic unit of communication between a Web Service and a 
 | Client: data 
 | >to be communicated to or from a Web Service as a single 
 | logical transmission.
 | >
 | >Operation
 | >A set of messages related to a single Web Service action.
 | >
 | >Interface (a/k/a "Port Type")
 | >A logical grouping of operations.   An Interface represents an 
 | >abstract  Service type, independent of transmission 
 | protocol and data format.
 | >
 | >Binding
 | >An association between an Interface, a concrete protocol and a data 
 | >format.  A Binding specifies the protocol and data format 
 | to be used in 
 | >transmitting messages defined by the associated Interface.
 | >
 | >Port
 | >An association between a Binding and a network address, 
 | specified by a 
 | >URI, that may be used to communicate with an instance of a 
 | Service.  A 
 | >Port indicates a specific location for accessing a Service using a 
 | >specific protocol and data format.
 | >
 | >Service
 | >A collection of Ports.
 | >
 | >References
 | >==========
 | >
 | >[1] http://www.w3.org/2002/ws/arch/2/wd-wsawg-reqs-03042002
 | >
 | >
 | >David Booth
 | >W3C Fellow / Hewlett-Packard
 | >Telephone: +1.617.253.1273
 | 
 | David Booth
 | W3C Fellow / Hewlett-Packard
 | Telephone: +1.617.253.1273
 | 
 |

Received on Tuesday, 19 March 2002 10:03:06 UTC