NEW ISSUE: BWS20016 should not be normative

[Simon Nash <oasis@cjnash.com>]

TARGET: Web Services Binding Specification

DESCRIPTION: BWS20016 should not be normative

The normative statement BWS20016 reads as follows:

  The @wsdli:wsdlLocation attribute MAY be specified by the binding in
  the event that the <WSDL-namespace-URI> in the ‘endpoint’ attribute
  is not dereferencable, or when the intended WSDL document is to be
  found at a different location than the one pointed to by the
  <WSDL-namespace-URI>. [BWS20016]

The use of MAY in this statement does not conform to RFC2119, which
states that MAY represents an optional feature that implementations
are free to either support or not support.  In this case, the
@wsdli:wsdlLocation attribute is required to be supported by all
implementations (as stated in BWS20021), and the MAY is attempting
to convey the fact that users can choose whether or not to use
this feature of SCA.

PROPOSAL:

Convert the normative statement BWS20016 into a non-normative
statement, and also fold the first sentence from BWS20018 into this
paragraph.  The resulting text for the /binding.ws/@wsdli:wsdlLocation
bullet would be:

  /binding.ws/@wsdli:wsdlLocation – when present this attribute
  specifies the location(s) of the WSDL document(s) associated with
  specific namespace(s).

  The @wsdli:wsdlLocation attribute can be used in the event that
  the <WSDL-namespace-URI> is not dereferenceable, or when the intended
  WSDL document is found at a different location than the one pointed to
  by the <WSDL-namespace-URI>.  The semantics of this attribute are
  specified in Section 7.1 of WSDL 2.0 [WSDL20].

  If the @wsdli:wsdlLocation attribute is used, the @wsdlElement
  attribute MUST also be specified. [BWS20017]

  The value of the @wsdli:wsdlLocation attribute MUST identify an
  existing WSDL 1.1 document. [BWS20018]

***Note that I have made some minor wording and spelling updates to
the above, including removing the incorrect reference to the
‘endpoint’ attribute***

   Simon