Cal it proposed-01, this is
the only one I’ve seen.
From: Christopher B
Ferris [mailto:chrisfer@us.ibm.com]
Sent: Friday, May 26, 2006 6:51 AM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] new issue: unclear text regarding wsa:Action
Title: unclear
text regarding wsa:Action
Description:
Line 120
currently reads:
If an action
IRI is used, and one is not already defined per the rules of the WS-Addressing
specification
[WS-Addressing],
then the action IRI MUST consist of the WS-RM namespace URI concatenated with a
'/', followed
by the message element name. For example:
http://docs.oasis-open.org/ws-rx/wsrm/200602/SequenceAcknowledgement
This text is,
IMO, ambiguous, if not confusing, at best. The intent was to define the pattern
of defining
a wsa:Action
IRI value when the intent of a message is exclusive to RM, such as in the case
of
RM lifecycle
messages (CreateSequence, TerminateSequence, etc.) or in the case where either
an RM fault or
SequenceAcknowledgement are sent standalone.
Even Gil's
proposed revisions (for i093) don't resolve the ambiguity:
If an action
IRI is used by a system that uses the elements defined within this
specification, and one is not
already defined
per the rules of the WS-Addressing specification [WS-Addressing], then said
system
MUST use an the
action IRI that MUST consists of the WS-RM namespace URI concatenated with a
'/',
followed by the
message element name. For example:
http://docs.oasis-open.org/ws-rx/wsrm/200604/SequenceAcknowledgement
What is needed
is simply a clear prescription for the designation of the wsa:Action IRIs that
are specific
to the
specification.
Target: core
spec
Type: editorial
Proposal:
replace text at
line 120-123 with the following:
When the RM
protocol, defined in this specification, is composed with the WS-Addressing
specification
[WS-Addressing],
the following rules prescribe the constraints on the value of the wsa:Action
header:
1. When an
endpoint generates a message that carries an RM protocol element, that is
defined in section 3 below, in the body of a SOAP envelope
that endpoint
MUST include in that envelope a wsa:Action SOAP header block whose value is an
IRI that is a concatenation of the WS-RM namespace URI, followed by a
'/', followed
by the value of the local name of the child element of the SOAP body . For
example, for a Sequence creation request message
as described in
section 3.1 below, the value of the wsa:Action IRI would be:
http://docs.oasis-open.org/ws-rx/wsrm/200602/CreateSequence
2. When an
endpoint generates a SequenceAcknowledgement message that has no element
content in the SOAP body, then
the value of
the wsa:Action IRI MUST be:
http://docs.oasis-open.org/ws-rx/wsrm/200602/SequenceAcknowledgement
3. When an
endpoint generates an AckRequested message that has no element content in the
SOAP body, then the value
of the
wsa:Action IRI MUST be:
http://docs.oasis-open.org/ws-rx/wsrm/200602/AckRequested
4. When an
endpoint generates an RM fault as defined in section 4 below, the value of the
wsa:Action IRI MUST be as
defined in
section 4 below.
Cheers,
Christopher
Ferris
STSM, Software Group Standards Strategy
email: chrisfer@us.ibm.com
blog: http://www.ibm.com/developerworks/blogs/dw_blog.jspa?blog=440
phone: +1 508 377 9295