RE: Draft of Definitions

 I second this concern.
 I propose simplifying the definition to something like

Operation - A set of messages that correlate to a single action.  

 Otherwise we'll have to define input, output and error messages 
as well.

                   Jacek Kopecky

                   Senior Architect, Systinet (formerly Idoox)
                   http://www.systinet.com/



On Wed, 13 Mar 2002, Steve Graham wrote:

 > With regards the definition of operation:
 > If an operation associates an input message with...
 > does this imply that we are not supporting the notification operation style
 > described in WSDL 1.1?
 > 
 > sgg
 > 
 > ++++++++
 > Steve Graham
 > sggraham@us.ibm.com
 > (919)254-0615 (T/L 444)
 > Emerging Technologies
 > ++++++++
 > 
 > 
 > 
 >                                                                                                                                        
 >                       "Keith Ballinger"                                                                                                
 >                       <keithba@microsof        To:       "David Booth" <dbooth@w3.org>, "Keith Ballinger" <KeithBa@msn.com>            
 >                       t.com>                   cc:       <www-ws-desc@w3.org>                                                          
 >                       Sent by:                 Subject:  RE: Draft of Definitions                                                      
 >                       www-ws-desc-reque                                                                                                
 >                       st@w3.org                                                                                                        
 >                                                                                                                                        
 >                                                                                                                                        
 >                       03/13/2002 02:06                                                                                                 
 >                       AM                                                                                                               
 >                                                                                                                                        
 >                                                                                                                                        
 > 
 > 
 > 
 > Some minor edits:
 > 
 > Message
 > Application specific data to be communicated as a single logical
 > transmission.
 > 
 > Operation
 > A set of messages that correlate to a single action. An operation
 > associates an input message with zero or more output and error messages.
 > 
 > OperationSet (a/k/a "Port Type")
 > A logical grouping of operations.
 > 
 > Binding
 > An association between an OperationSet and the specific wire format,
 > application protocol, and transport protocol to be used to transmit the
 > messages. <Keith>I don't like this wording much. This is a difficult
 > concept, and seems to be really about three separate but related ideas.
 > </Keith>
 > 
 > Port
 > An association between a binding and a network address that may be used to
 > communicate with the Service. <Keith>This feels uneeded as a normative
 > definition. </Keith>
 > 
 > Service
 > A logical grouping of bindings.
 > 
 >              -----Original Message-----
 >              From: David Booth [mailto:dbooth@w3.org]
 >              Sent: Tue 3/12/2002 2:28 PM
 >              To: Keith Ballinger
 >              Cc: www-ws-desc@w3.org
 >              Subject: Draft of Definitions
 > 
 > 
 > 
 >              Keith,
 > 
 >              Here is an initial draft of definitions.  What do you think?
 > 
 >              David Booth
 > 
 >                ---------------------------------- cut here
 >              ------------------------------------
 > 
 >              Non-Normative Definitions
 >              =========================
 > 
 >              Web Service
 >              Software that performs a task on behalf of one or more
 > Clients, typically
 >              over a network, using protocols defined in this document.
 > [This definition
 >              may change, subject to guidance from the Web Services
 > Architecture Working
 >              Group.]
 > 
 >              Client
 >              Software that makes use of a Web Service, acting as its "user"
 > or "customer".
 > 
 >              Normative Definitions
 >              =====================
 > 
 >              Message
 >              Data to be communicated to or from a Web Service as a single
 > logical
 >              transmission.
 > 
 >              Operation
 >              A single logical action supported by the Service. An operation
 > associates
 >              an input message with one or more output or error messages.
 > 
 >              OperationSet (a/k/a "Port Type")
 >              A logical grouping of operations supported by the Service.
 > 
 >              Binding
 >              An association between an OperationSet, a concrete protocol
 > and a data
 >              format that specifies the protocol and data format that may be
 > used to
 >              communicate with the Service.
 > 
 >              Port
 >              An association between a Binding and a network address that
 > may be used to
 >              communicate with the Service.
 > 
 >              Service
 >              A collection of Ports.
 > 
 >              [End]
 > 
 > 
 > 
 > 
 > 
 > 

Received on Wednesday, 13 March 2002 08:07:59 UTC