[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Relation to other specs
In the draft I just sent, I've added a small section on relation to
other specs. Regardless of what decisions we make in this regard, I
believe it's a good idea to have such a section. Here is the version
as it stands in the draft:1.1
Relation to Other Specifications
This specification makes extensive use of endpoint
references. An endpoint reference,
as defined in WS-Addressing, consists of a transport-specific physical
address
together with an arbitrary reference properties element - typically an
opaque
ID unique to the service. Taken as a
whole, these may designate a particular stateful object, or resource,
managed
by the Web Service at the given physical address. For
example, different subscriptions' endpoint references may
share the same physical address but have different reference properties. This allows multiple objects to be managed
through a single physical address. In the non-normative SOAP message exchanges, the
components
of endpoint references appear as SOAP headers.
This is a direct result of the SOAP binding of WS-Addressing. WS-BaseNotification relies on WS-Policy to
negotiate various
parameters such as security, quality of delivery service, continuity of
messaging in the face of changes to an existing subscription, implicit
termination of subscriptions, transport-level options and any other
parameters
not explicitly defined here. WS-Notification objects MAY present themselves as
resources
in the sense of WS-ResourceFramework in addition to supporting the
direct
messages described here. That is, they
may provide a resource properties document and support the various get,
set and
query methods defined in that specification.
This is true of any service representing stateful objects. However, this specification gives explicit
mappings to the WS-ResourceFramework interfaces. Subscriptions made via WS-BaseNotification MAY be
subject to
scheduled termination as defined in WS-ResourceLifetime.
This behavior is negotiable by policy. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]