W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > September 2009

RE: [Bug 7586] New: wse:Expires multiple data types creates interop issue

From: Asir Vedamuthu <asirveda@microsoft.com>
Date: Sun, 27 Sep 2009 06:35:41 +0000
To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <4F4942E980BD7147AE7F7D3DCB9CBA9F043D530F@TK5EX14MBXC138.redmond.corp.microsoft.com>
To better address the concern quoted in issue 7586, may we request a discussion of the underlying interop issue? What is the interop issue?

For convenience, here is the Expires tag element declaration:

<xs:element name="Expires" type="tns:ExpirationType" .../>

<xs:simpleType name="ExpirationType">
 <xs:union memberTypes="xs:dateTime tns:NonNegativeDurationType" /> 
</xs:simpleType>

<xs:simpleType name="NonNegativeDurationType">
 <xs:restriction base="xs:duration">
  <xs:minInclusive value="P0Y0M0DT0H0M0S" /> 
 </xs:restriction>
</xs:simpleType>

Same question applies to issue 7588.

Regards,

Asir S Vedamuthu
Microsoft Corporation

-----Original Message-----
From: public-ws-resource-access-notifications-request@w3.org [mailto:public-ws-resource-access-notifications-request@w3.org] On Behalf Of bugzilla@wiggum.w3.org
Sent: Friday, September 11, 2009 5:03 PM
To: public-ws-resource-access-notifications@w3.org
Subject: [Bug 7586] New: wse:Expires multiple data types creates interop issue

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 Sunday, 27 September 2009 06:36:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:18:13 GMT