W3C home > Mailing lists > Public > xml-dist-app@w3.org > October 2002

[AF] Proposal for Issue 387

From: Herve Ruellan <ruellan@crf.canon.fr>
Date: Fri, 18 Oct 2002 09:48:31 +0200
Message-ID: <3DAFBCCF.2090600@crf.canon.fr>
To: xml-dist-app@w3.org

Dear all,

The attachment feature defines an URI for referencing it:
"http://www.w3.org/2002/06/soap/features/attachment".

Issue 387 is about the prose describing the purpose of this URI:
" Protocol binding specifications can use this URI to declare their 
support for this feature and its associated semantics. "
The commentator suggest changing "can" to "MAY", or even to "SHOULD" to 
conform to RFC 2119.

This sentence is similar as the one in the main SOAP spec part 2 in 
section 6.2.1, 6.3.1, 6.4.1, which uses "may" (lower case) instead of "can".

As far as my memory is correct, we use "can" in the AF spec instead of 
"may" because there was some reluctance using keywords from RFC 2119. 
However the AF spec modification never made it to the main spec.

As a resolution for this issue, I suggest either reverting to the main 
spec text, but using an upper case "MAY" (I don't think "SHOULD" is 
appropriate here), or change the sentence so that we clearly can not use 
some keyword from RFC 2119 in it.
Note that this resolution propose to change the sentences in both the AF 
spec and the main SOAP spec.

Proposals:
1. Protocol binding specifications MAY use this URI to declare their 
support for this feature/MEP and its associated semantics.

2. Usage of this URI enables protocol binding specifications to declare 
their support for this feature/MEP and its associated semantics.

Best regards,

Hervé.
Received on Friday, 18 October 2002 03:48:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:11 GMT