- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 12 Sep 2009 00:03:28 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7586
Summary: wse:Expires multiple data types creates interop issue
Product: WS-Resource Access
Version: PR
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Eventing
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: gilbert.pilz@oracle.com
QAContact: public-ws-resource-access-notifications@w3.org
WS-Eventing allows the Subscriber to use either an xs:duration or an
xs:dateTime for the /wse:Subscribe/wse:Expires value. However, it also allows
Event Sources to fault on the use of xs:dateTime. It hints, but doesn't
directly say, that all Event Sources MUST support xs:duration, but some Event
Sources MAY also support xs:dateTime.
Note: a proposal for this already exists in the proposal for 7478. In hindsight
I realize I should have opened this issue first and addressed it separately.
--
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 Saturday, 12 September 2009 00:03:37 UTC