This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10960 - Eventing: MaxExpires assertion needs a min value
Summary: Eventing: MaxExpires assertion needs a min value
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2010-10-01 15:54 UTC by Doug Davis
Modified: 2011-02-01 18:26 UTC (History)
0 users

See Also:


Description Doug Davis 2010-10-01 15:54:23 UTC
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.


Change it to:

  <wse:ExpiresRange min="xs:duration" max="xs:duration" ... />

And mandate that min <= max.

Do this for both enum and eventing.
Comment 1 Doug Davis 2010-10-04 16:59:47 UTC
To expand proposal:
default min=0
default max=PT0S