- From: Doug Davis <dug@us.ibm.com>
- Date: Tue, 11 Jan 2011 13:55:41 -0500
- To: "Li, Li (Li)" <lli5@avaya.com>
- Cc: "Gilbert Pilz" <gilbert.pilz@oracle.com>, public-ws-resource-access@w3.org, "Chou, Wu (Wu)" <wuchou@avaya.com>
- Message-ID: <OFDAC78104.4C62D539-ON85257815.0067D3F4-85257815.0067FC36@us.ibm.com>
Li, if you look at the latest draft: http://www.w3.org/2002/ws/ra/edcopies/wseventing.html that fault is not defined. Expires itself is a required feature but xs:dateTime is optional. thanks -Doug ______________________________________________________ STSM | Standards Architect | IBM Software Group (919) 254-6905 | IBM 444-6905 | dug@us.ibm.com The more I'm around some people, the more I like my dog. "Li, Li (Li)" <lli5@avaya.com> Sent by: public-ws-resource-access-request@w3.org 01/11/2011 01:40 PM To "Gilbert Pilz" <gilbert.pilz@oracle.com> cc <public-ws-resource-access@w3.org>, "Chou, Wu (Wu)" <wuchou@avaya.com> Subject questions on ws-e interop tests Gil, In your test scenario document [1], section 3.3 Duration Expiration Test, the conformance clause states that: Note that, because wse:Expires is sender-optional and support for xs:duration is required, there are no valid reasons for a conforming Event Source/Subscription Manager implementation to either be unable to implement this test or to fail to meet one of the defined success criteria. However, the ws-e last call [2] section 4.1 says this: If the event source does not support the wse:Expires element being present in a Subscribe request message then a wse:ExpiresNotSupported fault MUST be generated. According to this, it seems that an conforming event source can send wse:ExpiresNotSupported to the subscriber in this test, but this fault was not included in the test success criteria. Could you clarify this? Thanks, Li [1] http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Dec/00 14.html [2] http://www.w3.org/TR/2010/WD-ws-eventing-20100805/
Received on Tuesday, 11 January 2011 18:56:49 UTC