W3C

- DRAFT -

Web Services Resource Access Working Group Teleconference

28 Jul 2009

Agenda

See also: IRC log

Attendees

Present
+1.908.696.aaaa, +1.571.262.aabb, Bob_Freund, +91.98.49.99.aacc, [Microsoft], +984999aadd, +25625660aaee, Wu_Chou, Ashok_Malhotra, Dug, +1.408.642.aaff, Mark_Little, Tom_Rutt, +1.408.642.aagg, +984999aahh, +1.408.642.aaii
Regrets
Chair
Bob Freund
Scribe
Sreedhara Narayanaswamy

Contents


 

 

<trackbot> Date: 28 July 2009

<dug> echo echo echo

<gpilz> I'll drown myself tonight, in sangrehia / made with sliced up fruit and cheap marsala

<Bob> http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0060.html

<Bob> Scribe: Sreedhara Narayanaswamy

<Bob> scribenick: Sreed

Bob: Agenda accepted

Action Items

<Bob> http://www.w3.org/2002/ws/ra/tracker/actions/open

Bob: Issue 6917
... Need to address this issue
... Discussion of 6917 in F2F

Li: Discuss the agenda of publication

Geoff: Working on it will send it over the week

Bob: Need by Thursday
... Any other item for the F2F

<dug> chair slaps Geoff for not getting the wine list

Bob: New issue http://www.w3.org/Bugs/Public/show_bug.cgi?id=7127

Tom Rutt: Notification defintion discussing about the mechanism would be required

Tom Rutt: Proposed solution require Notification defintion which is the application content of the defintion, need discussion on this

Bob: Accepting New issue 7127 & Tom Rutt will be taking the ownership

gpilz: 6401 reference parameters information trying to work which is specific - the way description

Bob: http://www.w3.org/Bugs/Public/show_bug.cgi?id=6692

Geoff: Joint proposal - discussion IBM & Microsoft had which is based on the last F2F
... push mode is not currently specified in the spec, delivery element is still exists - original spec when push mode is undefined. Wording changes push/make connections which will be handled 6432

Dug: Notifications can be delivered

gpliz: It is not clear

<gpilz> hello?

Bob: Asynchronous with specific to

<dug> I can live w/o "async" - same end result

<Bob> proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/att-0057/wseventing-6692-10.doc

Bob: Any objection accepting the proposal

<dug> "This specification defines only an asynchronous method of delivery for notifications from the event source to event sink. "

<dug> "The absence of any extensions to the wse:Delivery or wse:NotifyTo elements indicates that notifications should be asynchronously sent as SOAP messages to the endpoint described in lines (21-28). "

<dug> "When present this element indicates that notifications MUST be asynchronously sent to the EndpointReference identified by this element."

<dug> This specification defines only one method of delivery for notifications from the event source to event sink.

<dug> ??

<dug> This specification a method of delivery for notifications from the event source to the event sink.

<dug> This specification defines a method of delivery for notifications from the event source to the event sink.

<gpilz> This specification defines a method for delivering notifications from the event source to the event sink.

li: define is reference to the event - async some kind of i/p

Bob: Eventing with message cause to flow back

<gpilz> This specification defines a method for transmitting notifications from the event source to the event sink.

<dug> maybe we should delete this sentence??

<dug> :-)

<Wu> This specification defines a subscribe/notify method ...

Bob: Wu what text you propose

<dug> "This specification defines a method for transmitting notifications from the event source to the event sink through the inclusion of the wse:NotifyTo EPR."

<Wu> This specification defines a subscribe/notify method for transmitting notifications from the event source to the event sink.

<gpilz> hello?

<gpilz> my mic isn't working

<dug> "This specification defines a method for transmitting notifications from the event source to the event sink through the use of the wse:NotifyTo element."

dug: how we actually do it

<Geoff> +1 for doug

<Bob> "This specification defines a method for transmitting notifications from the event source to the event sink through the use of thewse:NotifyTo element."

<Bob> no objections

Bob: any objectiosn to other two sentenses

<Bob> no objections to the removal of asynchronously in the other two places

<asir> Vow!!

<asir> Certainly progress!

RESOLUTION: 6692 Modification in bugzilla

<Bob> comment: chair to add modifications to bugzilla reflecting the thre agreements above

<dug> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6432#c5

Bob: new poposal

<Bob> s/prposal/proposal in the bugzilla

<gpilz> +1

Wu: suggest wording changes

<Ram> Proposal for 6432: "When the wse:NotifyTo element is used within the Delivery element it specifies the endpoint to which Notifications are sent. For delivery to addressable endpoints this is sufficient. However, for non-addressable endpoints some additional mechanisms are needed. A subscriber can choose to leverage the WS-MakeConnection] specification to enable delivery of Notifications to non-addressable endpoints."

Bob: Ram are suggesting specific changes to the text in the proposal
... Wu Are you supporting Ram's text
... we might have to discuss and close this in F2F

<Ram> Bob says: There needs to be two implementations for optional features. If not, those features may need to be marked at risk.

Asir: might not to test anything at all

Bob: We can discuss this next week

<gpilz> http://www.w3.org/Bugs/Public/show_bug.cgi?id=7136

<li> geoff: where is the link to the proposal?

Geoff: Information with the subscription currently in the spec. Complexity of having two models how we can differentiate it.

Geoff

<dug> http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0079.html

dug: might be re-inventing transfer in this

<Geoff> +q

<Bob> N.B. both Oracle and IBM mentioned that they would be able to demonstrate implementations of eventing composed with MC during CR

<dug> +1 gil

<Bob> trackbot, end telecon

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/07/28 21:13:12 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

FAILED: s/prposal/proposal in the bugzilla/
Found Scribe: Sreedhara Narayanaswamy
Found ScribeNick: Sreed
Default Present: +1.908.696.aaaa, +1.571.262.aabb, Bob_Freund, +91.98.49.99.aacc, [Microsoft], +984999aadd, +25625660aaee, Wu_Chou, Ashok_Malhotra, Dug, +1.408.642.aaff, Mark_Little, Tom_Rutt, +1.408.642.aagg, +984999aahh, +1.408.642.aaii
Present: +1.908.696.aaaa +1.571.262.aabb Bob_Freund +91.98.49.99.aacc [Microsoft] +984999aadd +25625660aaee Wu_Chou Ashok_Malhotra Dug +1.408.642.aaff Mark_Little Tom_Rutt +1.408.642.aagg +984999aahh +1.408.642.aaii
Agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0060.html
Found Date: 28 Jul 2009
Guessing minutes URL: http://www.w3.org/2009/07/28-ws-ra-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


[End of scribe.perl diagnostic output]