Re: [wsn] Issue Verification BaseN 1.0j Issue 2.46: Should UseNotifybe a policy utterance

[David Hull <dmh@tibco.com>]

The current schema has SubscriptionPolicy as xsd:Any and defines a
UseRaw element.  This seems compatible with the text.  We could put
together a content model for SubscriptionPolicy that explicitly says
"UseRaw or anything else", but this doesn't seem useful as it doesn't
change what contents are valid.

Have I missed the obvious (this is quite possible)?

Tom Maguire wrote:

>Remove the <UseNotify> property from the SubscribeRequest message and
>define a new  subscription policy  <UseRaw>  as an optional child of the
><SubscriptionPolicy> element.  The baseline behavior (in absence of the
><UseRaw> policy element in the SubscribeRequest message) is to use the
>Notify wrapper.
>
>
>Normative prose correct
>
>Issue schema line 1705 does not match the choice of wsnt:UseRaw or xsd:any
>as child sequence of SubscriptionPolicy
>
>
>
>Frey’s Law: “Every 5 years the number of architecture components double and
>the ability to comprehend them halves”
>
>
>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
>