Re: [sca-bindings] Groups - sca-binding-ws-1.1-spec-cd02-issue61.docuploaded

[Simon Nash <oasis@cjnash.com>]

Here are my comments:

  1. Section 1, third paragaph: Change [WSDL] reference to [WSDL11].
     As this stands, it is ambiguous because the [WSDL] reference
     includes both WSDL 1.1 and WSDL 2.0.

  2. Section 1.2: Remove WSDL 1.1 spec from the [WSDL] reference and
     change the name of this reference to [WSDL20].

  3. Section 2: In bullet describing wsdlElement, first paragraph,
     replace the sentence "This attribute points to the specified
     element in an existing WSDL document." by the following
     normative statement: "This attribute MUST point to an element
     in an existing WSDL document [WSDL11]. [BWSxxxxx]"

  4. Section 2: In bullet describing wsdli:wsdlLocation, replace
     the sentence "The use of this attribute indicates that the
     WSDL binding points to an existing WSDL document." by the
     following normative statement: "If this attribute is used, the
     @wsdlElement attribute MUST also be specified. [BWSxxxxx]"

  5. Section 2: In bullet describing wsdli:wsdlLocation, replace
     the [WSDL] reference in the final sentence by [WSDL20].

  6. Section 2.2: Replace the first sentence by the following
     normative statement: "When binding.ws is used on a service or
     reference that is not defined by interface.wsdl, the SCA runtime
     MUST derive a WSDL portType for the service or reference from
     the interface using the rules defined for that SCA interface
     type. [BWSxxxxx]"

  7. Section 2.3, last sentence: Replace "rules that SHOULD be used"
     by "rules that are used", as suggested by Simon's comment.

  8. Section 4: The second last sentence contains a non-RFC2119
     "optional".  Remove the whole sentence, as the paragraph is
     complete and clear without it.

  9. Section 4.1: Reword BWS40001, BWS40002 and BWS40003 so that
     they use the active sense and name the SCA runtime as the
     conformance target:
      When the SOAP intent is required, the SCA runtime MUST transmit
      messages using SOAP.  One or more versions of SOAP can be used.
      [BWS40001]
      When the SOAP.1_1 intent is required, the SCA runtime MUST transmit
      messages using only SOAP 1.1. [BWS40002]
      When the SOAP.1_2 intent is required, the SCA runtime MUST transmit
      messages using only SOAP 1.2. [BWS40003]

10. Suggested rewording/reordering of section 4.2.2:

     The default transport binding rules for the Web Service binding are
     defined as follows:
     • HTTP-based transfer protocol
     • Bindings for SOAP 1.1 are provided
     • "literal" format as described in section 3.5 of [WSDL11]
     • For document-literal pattern, each message uses "document" style,
       as per section 3.5 of [WSDL11]
     • For rpc-literal pattern, each message uses "rpc" style, as per
       section 3.5 of [WSDL11]
     • For rpc-literal pattern, the child elements of the SOAP Body element
       are namespace qualified with a non-empty namespace name
     • For SOAP 1.1 messages, the SOAPAction HTTP header described in
       section 6.1.1 of "Simple Object Access Protocol (SOAP) 1.1" [SOAP]
       represents the empty string, in quotes ("")
     • For SOAP 1.2 messages, the SOAP Action feature described in
       section 6.5 of [SOAP12Adjuncts] does not appear
     • All WSDL message parts are carried in the SOAP body

     In the event that the transport details are not otherwise determined,
     the SCA runtime MUST use the default transport binding rules. [BWS40005]

     When using the default transport binding rules, the SCA runtime MAY
     provide additional bindings, unless policy is applied that explicitly
     restricts this. [BWS40007]

     When using the default transport binding rules with the rpc-literal
     pattern, the SCA runtime SHOULD use the structural URI associated
     with the binding as the namespace of the child elements of the
     SOAP body element. [BWS40009]

   Simon

Eric Johnson wrote:
> Minor nits:
> 
> BWS40004 - "For a service element..." --> (clarifying) "For an SCA 
> service element..", and "MUST the rpc-literal..." --> (typo) "MUST be 
> either the rpc-literal..."
> 
> BWS40005 - "MUST enable the default transport binding rules" --> 
> (indicating context in the text) "MUST enable the default transport 
> binding rules that follow"
> 
> BWS40007 - "Additional bindings MAY ..." --> (clarifying) "Additional 
> WSDL bindings MAY..."
> 
> -Eric.
> 
> simon_holdsworth@uk.ibm.com wrote:
>> The document named sca-binding-ws-1.1-spec-cd02-issue61.doc has been
>> submitted by Mr. Simon Holdsworth to the OASIS Service Component
>> Architecture / Bindings (SCA-Bindings) TC document repository.
>>
>> Document Description:
>> Updated revision of the WS binding specification including conformance
>> statement numbering.
>>
>> View Document Details:
>> http://www.oasis-open.org/committees/document.php?document_id=31957
>>
>> Download Document:  
>> http://www.oasis-open.org/committees/download.php/31957/sca-binding-ws-1.1-spec-cd02-issue61.doc
>>
>>
>> PLEASE NOTE:  If the above links do not work for you, your email application
>> may be breaking the link into two pieces.  You may be able to copy and paste
>> the entire link address into the address field of your web browser.
>>
>> -OASIS Open Administration
>>   
> --------------------------------------------------------------------- To 
> unsubscribe from this mail list, you must leave the OASIS TC that 
> generates this mail. Follow this link to all your TCs in OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php