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

Issue 6403: Enumertion Policy - some things for us to consider

From: Katy Warr <katy_warr@uk.ibm.com>
Date: Tue, 21 Apr 2009 15:10:34 +0100
To: public-ws-resource-access@w3.org
Message-ID: <OFE9C8A895.3640E61C-ON8025759F.004BAAC3-8025759F.004DDFBE@uk.ibm.com>
Just wondering whether we need to consider the following in the context of 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6403 proposal?:

1) The wsenp:WSEnumeration policy indicates that WS-Enumeration MUST be 
used when communicating with this endpoint. I think this is shorthand for 
defining the data source enumeration operations at the endpoint (i.e. 
enumerate, pull, renew, getstatus and release). 
Because of the 'MUST', would it therefore be an error to attach 
wsenp:Ennumeration policy wsp:Optional=FALSE to an endpoint if that 
endpoint also supported other (non-enum) operations?

2) We should consider whether an endpoint must advertise all the filter 
dialects that it supports using:
  <x:FilterDialect xmlns:x="xs:anyURI" wsp:Optional="true"/> 
If we don't mandate that all supported filter dialects are advertised in 
the policy, do we need a mechanism for an enumeration endpoint to indicate 
that it does not support filtering at all (i.e. including a filter on the 
enumerate verb will return wesn:FilteringNotSupported)?


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Received on Tuesday, 21 April 2009 14:11:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:48 UTC