W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > February 2009

issue 6403: ws-enum policy proposal

From: Doug Davis <dug@us.ibm.com>
Date: Mon, 2 Feb 2009 20:47:19 -0500
To: public-ws-resource-access@w3.org
Message-ID: <OFE7BDF3AB.3C4CAD46-ON85257551.007648CE-85257552.0009D5AA@us.ibm.com>
Following the pattern being proposed for WS-Eventing's policy,
define a new section of WS-Enum that has the following:

- - - - - - - - - - - - - - - - - - -

WS-Policy Framework and WS-Policy Attachment [WS-PolicyAttachment] 
collectively define a framework, model and grammar for expressing 
the requirements, and general characteristics of entities in an XML 
Web services-based system. To enable a Data Source to describe its
requirements, this specification defines a single policy assertion
that leverages the WS-Policy framework.  This assertion has Endpoint
Policy Subject.

The normative outline of this assertion is:

<wsenp:WSEnumeration [wsp:Optional="true"]? ...>
    <x:FilterDialect xmlns:x="xs:anyURI" wsp:Optional="true"/> *

  A policy assertion that specifies that WS-Enumeration protocol 
  MUST be used when communicating with this endpoint. This assertion 
  has Endpoint Policy Subject.

  Per WS-Policy, this is compact notation for two policy alternatives,
  one with and one without the assertion. The intuition is that the 
  behavior indicated by the assertion is optional, or in this case, 
  that WS-Enumeration MAY be used.

  This required element allows for the inclusion of nested policy 

  When present, this assertion defines the requirement that the 
  consumer, if it chooses to include a filter in the wsen:Enumerate 
  request, MUST use the filter dialect associated with the namespace 
  URI of this element. Note: the namespace of this element is 
  application defined, but the Local Name MUST be  "FilterDialect".

  This attribute specifies that the assertion is optional per 
  WS-Policy. This attribute MUST be present since the inclusion of 
  a Filter dialect in a Enumerate request is optional.

- - - - - - - - - - - - - - - - - - -

Its not clear to me which other features of WS-Enum are optional
(for example, Renew) and should therefore have a policy assertion
associated with it.  But we can add more to the above as we
decide if they are optional.

Also, once we agree on the format of the policy assertion we can
then define the exact policy assertions for the pre-defined
filter dialects.

STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
Received on Tuesday, 3 February 2009 01:47:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:34:31 UTC