RE: [ws-tx] Issue 097 - WS-C: Editorial comments (AI#56)

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

Monica,

Thanks for the comments.

As we discuss this and close this issue, I will add the final resolution to the issues list.

-----Original Message-----
From: Monica.Martin@Sun.COM [mailto:Monica.Martin@Sun.COM]
Sent: Friday, October 27, 2006 1:45 PM
To: Ram Jeyaraman
Cc: ws-tx@lists.oasis-open.org; Joe Fialli
Subject: Re: [ws-tx] Issue 097 - WS-C: Editorial comments (AI#56)


>Ram Jeyaraman wrote: This issue is identified as 097.
>...13.   Section 1.4 Terminology had the usual description of the "MUST", "MAY" etc. but the text repeatedly uses "may" (lower case). Check the use of 'must' and  consider whether this is intentional throughout the doc.
>
>
mm1: Ram, related to #097 and specifically for any recommendations
regarding Action Item #56 for WS-Coordination [1], please accept these
comments to the discussion, in addition to the point submitted against
Action #57 (related to SOAP headers) that affects WS-C, WS-AT and WS-BA.

Section 1.4.
Change from:
58 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD
59 NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described
60 in [RFC2119].

58 The upper case key words "MUST", "MUST NOT", "REQUIRED", "SHALL",
"SHALL NOT", "SHOULD", "SHOULD
59 NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described
60 in [RFC2119].

Reason: As agreed before these action items were logged 19 October 2006.

Section 3.2.
Change from:
329 These Endpoint References may contain (opaque)
wsa:ReferenceParameters to fully qualify the target
330 protocol service endpoint. According to the mapping rules defined in
the WS-Addressing specification, all
331 such reference properties must be copied literally as headers in any
message targeting the endpoint.

Change to:
329 These Endpoint References MAY contain (opaque)
wsa:ReferenceParameters to fully qualify the target
330 protocol service endpoint. According to the mapping rules defined in
the WS-Addressing specification [add link], all
331 such reference properties are copied literally as headers in any
message targeting the endpoint.

Reason: In first sentence, MAY seems consistent with surrounding text in
this section. For second sentence, suggest
to leave out 'must be copied' and change to 'are copied'. A normative
reference exists to WS-A (and the TC
could add a link herein). This is consistent with our goal not to
restate WS-Addressing but reference it when needed.

Section 3.2.1.
Change from:
341 Participants can register for multiple Coordination protocols by
issuing multiple Register operations. WS-
342 Coordination assumes that transport protocols provide for message
batching if required.

Change to:
348 Participants MAY register for multiple Coordination protocols by
issuing multiple Register operations. WS-
349 Coordination assumes that transport protocols provide for message
batching if required.

Reason: The use of MAY seems consistent with surrounding text in this
section and the intent.

[1] Action item #56:
http://www.oasis-open.org/apps/org/workgroup/ws-tx/members/action_item.php?action_item_id=1718