W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > May 2010

[Bug 9702] New: Add a wse:ExpirationTimeConstraintsNotSupported fault

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 May 2010 20:36:58 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-9702-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9702

           Summary: Add a wse:ExpirationTimeConstraintsNotSupported fault
           Product: WS-Resource Access
           Version: LC
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: antoine.mensch@odonata.fr
         QAContact: public-ws-resource-access-notifications@w3.org


Supporting the min, max and exact constraints on requested expiration time may
be too complicated for small devices (especially since the semantics of
comparison for xsd:duration is not particularly well defined  e.g. is 1 month
greater than 30 days?). In addition, when using scarce resources, it is
important to leave the responsibility of the subscription life cycle to the
event source(as was the case in the Submission version of the spec). If this
feature is profiled out by DPWS (OASIS Devices Profile for Web Services), DPWS
may have to introduce a DPWS-specific fault, thus creating interop issues with
standard WS-Eventing subscribers. Therefore, a standard fault for handling this
case could be useful.

-- 
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 Monday, 10 May 2010 20:37:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 10 May 2010 20:37:01 GMT