Identifying WS-BaseNotification dependencies on WSRF

["Murray, Bryan P." <bryan.murray@hp.com>]

In order to clarify issue WSN2.2 David Hull and myself reviewed
WS-BaseNotification to determine the points at which WS-BN currently
depends upon the WSRF specifications. Some of these points are already
being discussed in other email threads and their discussion should
continue in those threads. Related existing issues are identified where
possible.

Section 3.1: Notify message may follow implied resource pattern. 
Section 4: First sentence implies resource properties must be supported.

Section 4.1: Indicates the required messages of WSRF-RP must be exposed,
the optional messages may be exposed. Defines a property document where
the spec does not indicate whether the properties are writable, but they
appear as if they are read-only. 
Section 4.2: The Subscribe message has 2 fields of type QueryExpression
as defined in WSRF-RP. The fields are Precondition and Selector. It is
not clear that these fields have the same type of expression as the
operation QueryResourceProperties defined in WSRF-RP. There is a
statement that the Subscribe message must follow the implied resource
pattern. 
" ": The description of InitialTerminationTime talks about the property
TerminationTime (presumably from WSRF-RL) implying a dependency. 
" ": Both the request and response talk about a subscription resource.
Also the subscribe response message contains an endpoint reference
specifically having reference properties that include a subscription
identifier. This implies a dependency on WSRF-RP. 
Section 4.3: The GetCurrentMessage message must follow the implied
resource pattern. 
Section 5: SubscriptionManager follows the implied resource pattern. It
must support required WSRF-RP messages and may support optional WSRF-RP
messages. It must support both immediate and scheduled destruction from
WSRF-RL. (issue WSN2.18 is part of this) 
Section 5.1: In addition to the properties defined in WSRF-RL,
additional properties are defined. The properties Precondition and
Selector require the use of QueryExpressionType as defined in WSRF-RP.
Only the property CreationTime is explicitly read-only. (relates to
issue WSN2.7 and WSN2.20 and WSN4.14) 
Section 5.2: Pause message must follow implied resource pattern.
Statements referring to TerminationTime from WSRF-RL. 
Section 5.2: Resume message must follow implied resource pattern. 

In general, it is not clear what is intended in the several places that
indicate an implementation must/may follow the implied resource pattern.
This becomes even more true as the specs move towards standardization as
the current plan is not to publish the state paper as a normative part
of the standards.
David Hull and Bryan Murray