Diane, Peter,
I am raising this issue based on the discussion during the TC ch9
review call today. Please see the full specification of the issue
below.
Regards,
Prasad
Description: This issue addresses two problems. (1) Chapter 9,
currently has normative descriptions pertinent to the Correlation Set
description interspersed with the description of the examples. (2)
Details of implications of the "initiate" attribute values are
described in (pp 3 of) section 9.2 while the attribute is not
introduced or defined prior to its first use (in terms of its
implications with respect to correlation set consistency).
Proposed Resolution: Move specification text out of the example
area and recast it appropriately at the location above the area that
talks about the implications of different values of the "initiate"
attribute on the correlation set consistency.
Specifically make the following modifications:
(1) Add the following text just above the paragraph that starts with
"After a correlationSet is initiated, the values of the properties for
correlation set MUST be identical ......"
The <correlationSet> specifications are used in <invoke>, <receive>, and <reply>
activities (see 10.3. Invoking Web
Service Operations and 10.4. Providing
Web Service
Operations); in the <onMessage> branches of <pick>
activities, and in the <onEvent> variant of <eventHandlers> (see 11.5. Pick and 12.5.1. Message Events). These <correlationSet> specifications identify the correlation sets are identified by name and are used to
indicate which correlationSet's
(i.e., the corresponding property sets) occur in the messages being
sent and
received. The initiate attribute
on a <correlationSet> specification is
used to indicate whether the correlation set is being initiated.
(2) Add the following text just above the
paragraph that starts with "Following
is an extended example of correlation.
It begins by defining ..."
In the case of <invoke>, when the operation invoked is a request/response
operation, a pattern attribute on the <correlationSet> specification is
used to indicate whether the correlation applies to the outbound
message (“request”), the inbound message (“response”),
or both (“request-response”). The pattern
attribute of <invoke> is only allowed for request-response operations,
and disallowed when a one-way operation is invoked. Any violation of
this rule
MUST be detected during static analysis.
<correlations>
<correlation set="NCName" initiate="yes | no"/? pattern="request | response | request-response"?>+
</correlations>
(3) Delete the following paragraph whose contents are now recast
elsewhere, completely.
The<correlationSet> names are used in <invoke>, <receive>, and <reply>
activities (see 10.3. Invoking Web
Service Operations and 10.4. Providing
Web Service
Operations); in the <onMessage> branches of <pick>
activities, and in the <onEvent> variant of <eventHandlers> (see 11.5. Pick and 12.5.1. Message Events). These sets are used to indicate which
correlationSet's
(i.e., the corresponding property sets) occur in the messages being
sent and
received. The initiate attribute
is used to indicate whether the set is being initiated (see the beginning of this section for
details of initiate attribute). Finally, in the case of <invoke>, when the operation invoked is a request/response
operation, a pattern attribute is
used to indicate whether the correlation applies to the outbound
message (“request”), the inbound message (“response”),
or both (“request-response”). These concepts are explained in more detail in
the context of the use of correlation in the rest of this example. The pattern attribute of <invoke>is only allowed for request-response
operations,
and disallowed when a one-way operation is invoked. Any violation of
this rule
MUST be detected during static analysis.