Web Services Resource Access Working Group Teleconference

<trackbot> Date: 05 October 2010

<scribe> SCRIBE: gpilz

Agenda

RESOLUTION: Agenda approved with no changes

Approval of minutes of 2010-09-28

RESOLUTION: minutes of 2010-09-28 approved

LCWD Comments

-Issue-10960 MEX: Eventing: MaxExpires assertion needs a min value http://www.w3.org/Bugs/Public/show_bug.cgi?id=10960

Bob: Doug has not joined the call yet

RESOLUTION: new issue opened http://www.w3.org/Bugs/Public/show_bug.cgi?id=10960

Bob: should we wait for Doug to discuss?

Dave: yeah

Feature Lists

Bob: ODT is easy to convert to HTML
... ODT can also be saved in .doc form
... let's use tool-neutral formats just to keep the peace

<scribe> ACTION: gpilz to open issue on WS-Eventing and the "expiration feature" [recorded in http://www.w3.org/2010/10/05-ws-ra-minutes.html#action01]

<trackbot> Created ACTION-168 - Open issue on WS-Eventing and the "expiration feature" [on Gilbert Pilz - due 2010-10-12].

Schedule for Primers

<scribe> ACTION: Doug - primers for MEX, Transfer, Frag due on the 19th [recorded in http://www.w3.org/2010/10/05-ws-ra-minutes.html#action02]

<trackbot> Created ACTION-169 - - primers for MEX, Transfer, Frag due on the 19th [on Doug Davis - due 2010-10-12].

Yves: primers should be W3C "Notes"

<scribe> ACTION: gpilz - primer for Eventing due on 2010-10-19 [recorded in http://www.w3.org/2010/10/05-ws-ra-minutes.html#action03]

<trackbot> Created ACTION-170 - - primer for Eventing due on 2010-10-19 [on Gilbert Pilz - due 2010-10-12].

<W3C> what is doug's issue number

<Bob_> 10960

<W3C> thx

Note, a subscription expiring as expected is not considered to be an unexpected termination, therefore a SubscriptionEnd message MUST NOT be sent in this case.

<Tom_Rutt> If pt0s means "as long as possible", then it is a valid return value. However, as Wu said, any killing of that subscription should have the end message, since it is ending at less than infinity.

If the event source terminates a subscription unexpectedly, and it supports the use of the EndTo EPR, and the EndTo EPR was present in the Subscribe message for that subscription (see 4.1 Subscribe), the SubscriptionEnd message MUST be sent to the endpoint reference indicated by that EPR, if possible.

<Tom_Rutt> I think it is important to distinguish "do not care how long the subscription is alive" vs "keep it alive as long as possible"

+1

<Bob_> shall we keep the subscription alive even if it is in a vegatative state?

freeze its head

Ram: typo in the WS-Enumeration spec
... Doug said he would treat it as an editorial issue

<Bob_> http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Oct/0015.html

Bob: any objections to editors making this correction?

RESOLUTION: editorial issue resolved

Next Meetings

Bob: next telecon will be October 26th
... we should start planning a F2F for testing
... In Jan we've picked up most of the implementations
... nearly the full set in January

Ram: would like end of January

Bob: week of Jan 24th?

Ram: I'm available. I'll confirm my product teams availability.

Bob: does anybody see any major conflicts?

Doug: I won't be able to tell until I get to my hotel

Bob: declaring Boston out of bounds

Dave: that week is out for me

Bob: somewhere in the U.S., somewhere south central or west coast

Gil: I might be able to host in Redwood Shores (or maybe S.F.)