- From: <bugzilla@jessica.w3.org>
- Date: Fri, 01 Oct 2010 15:54:24 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10960 Summary: Eventing: MaxExpires assertion needs a min value Product: WS-Resource Access Version: PR Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Eventing AssignedTo: public-ws-resource-access-notifications@w3.org ReportedBy: dug@us.ibm.com QAContact: public-ws-resource-access-notifications@w3.org Right now Eventing (and Enum) define policy with: <wse:MaxExpires ...> xs:duration </wse:MaxExpires> ? This is fine for defining the max value but it seems like we should also allow people to say what the minimum value is. For example, what if someone only support subscriptions for exactly one year. Using the above they can only say that the max is one year but the client will never know that they can't specify something less than a year either. This becomes even more important with an endpoint that only support indefinite expirations - meaning just PT0s (explicitly or implicitly). Putting PT0S in the above doesn't tell the client that any value other than PT0S will be rejected. Proposal: Change it to: <wse:ExpiresRange min="xs:duration" max="xs:duration" ... /> And mandate that min <= max. Do this for both enum and eventing. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. You are the assignee for the bug.
Received on Friday, 1 October 2010 15:54:25 UTC