Re: [wsn] Proposed Issue Text: Should UseNotify be a policy utterance?

[David Snelling <David.Snelling@UK.Fujitsu.com>]

Folks,

This might be OK, but only if there was ALWAYS a clear default 
behavior. In other words, UseNotify is the default unless something 
else is put in an optional policy element. I believe we want to enable 
interoperability without requiring a profile to be developed.


On 14 Apr 2005, at 20:40, David Hull wrote:

> 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:
>
>  
>
-- 

Take care:

     Dr. David Snelling < David . Snelling . UK . Fujitsu . com >
     Fujitsu Laboratories of Europe
     Hayes Park Central
     Hayes End Road
     Hayes, Middlesex  UB4 8FE

     +44-208-606-4649 (Office)
     +44-208-606-4539 (Fax)
     +44-7768-807526  (Mobile)