10960 2010-10-01 15:54:23 +0000 Eventing: MaxExpires assertion needs a min value 2011-02-01 18:26:45 +0000 1 1 1 Unclassified WS-Resource Access Eventing LC PC Windows XP CLOSED REMIND P2 normal --- 1 dug dug public-ws-resource-access-notifications oldest_to_newest 40451 0 dug 2010-10-01 15:54:23 +0000 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. 40563 1 dug 2010-10-04 16:59:47 +0000 To expand proposal: default min=0 default max=PT0S