After a reread I think my -1 was not clearly expressed. If we continue to
specify default behavior,
wrt the Notify message, in the absence of 'UseNotify' then I think this
would be an appropriate
factorization. I believe that moving a flag for 'raw' message to the
policy section
(perhaps 'DoNotUseNotify') would be ok, the implication being that default
behavior is
normatively described.
Tom
Tom Maguire/Hawthorne/IBM@IBMUS wrote on 04/14/2005 05:16:18 PM:
-1
One of the premises of the WS-N set of specifications is to provide a set
of protocols and wire formats for Web Services. Removing the default of
'true' for the UseNotify flag and relegating it to a policy utterance
seems
contrary to the aforementioned premise.
Tom
Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away. – Antoine de Saint-Exupery
T o m M a g u i r e
STSM, On Demand Architecture
Poughkeepsie, NY 12601
David Hull
<dmh@tibco.com>
To
04/14/2005 03:40 wsn@lists.oasis-open.org
PM
cc
Subject
[wsn] Proposed Issue Text: Should
UseNotify be a policy utterance?
WSN2.XX: Should UseNotify be a policy utterance?
The SubscribeRequest message currently contains a specialized <UseNotify>
element indicating whether the producer should use the Notify message
format described in section 3.1. The Notify message is essentially a
convenience and is not fundamental to the basic Subscribe/Notify pattern.
If it were not already in the base specification, it could clearly be
added
via policy. As such, it should be treated as a pre-defined policy rather
than a built-in feature of notification, just as topic, selector and
precondition are now treated as pre-defined filters.
Making this change would bring WSN more closely in line with WSE and
would
also strengthen the extensibility story concerning policy.
Specifications
WS-BaseNotification
Proposed Recommendations
Remove the <UseNotify> property from the SubscribeRequest message
proper and make it an optional child of the <SubscriptionPolicy>
element (and so the first complete entry in the policy
document(s)).
The element would retain its current semantics.
Notes
Status:
Contact:
David Hull, Steve Graham
Cross Reference:
Perfection is achieved, not when there is nothing more to add, but when
there is nothing left to take away. – Antoine de Saint-Exupery
T o m M a g u i r e
STSM, On Demand Architecture
Poughkeepsie, NY 12601