W3C

XMLP minutes

10 Aug 2005

Agenda

See also: IRC log

1. Roll Call

Present
BEA Systems, Mark Nottingham
BEA Systems, David Orchard
Iona Technologies, Suresh Kodichath
Microsoft Corporation, Martin Gudgin
Nokia, Mike Mahan
Oracle, Anish Karmarkar
SeeBeyond, Pete Wenzel
Sun Microsystems, Marc Hadley
W3C, Yves Lafon
Regrets
Canon, Herve Ruellan
IBM, Chris Ferris
IBM, Noah Mendelsohn
Absent
Microsoft Corporation, Doug Purdy
SAP AG, Volker Wiechers
Excused
Canon, Jean-Jacques Moreau
Microsoft Corporation, Jeff Schlimmer
Oracle, Jeff Mischkinsky
Sun Microsystems, Tony Graham
Chair
Mike Mahan
Scribe
Marc with a c


2. Agenda Review and call for AOB

Will discuss ATF Issue 1 also

3. Approval of Minutes

July 27: http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2005Aug/0001.html APPROVED
Aug 3: http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2005Aug/0016.html PENDING


4. Action items

Mike: Send notification to the WS CG about the upcoming work on the one way MEP. DONE
See: http://lists.w3.org/Archives/Member/w3c-ws-cg/2005Jul/0014.html

Anish: Write a draft message on the ATF's issue 1 and send to list. DONE
aka AsyncTF Issue1 or Does the SOAP/HTTP binding require a SOAP env in the response
See: http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2005Aug/0015.html

DaveO: Draft charter revision language based on this < http://www.w3.org/2005/08/03-xmlprotocol-irc.html > discussion. DONE
See: http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2005Aug/0006.html

Mike: Communicate charter revisions to WSD chair. DONE
See: http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2005Aug/0011.html

Mike: Lets take the agenda out of order and do the new XMLP work item last

6. SOAP 1.2 PER specs

WS-A transition results
mnot: discussed on Monday, directors decision will be announced next Monday

Issue 33rec
http://www.w3.org/2000/xp/Group/xmlp-rec-issues.html#x33
anish reviews the issue
email discussion: noah unsure about what to do, might be too big a change for errata; anish, yves believe that binding defers to HTTP so might be OK
yves: options are to either restrict 3xx to exclude 303 or add specific 303 treatment in table
mike: what would second alternative entail wrt test assertions
what do we lose if we don't support 303
marc: would lose a neat way of doing async in a HTTP-centric way
<anish> +1 to marc
gudge: +1
yves: add new line for 303 and a test case
mike: how much work to change the state machine ?
anish: need to add a line to 303 that changes the method and destination
mike: do we need to provide a test case for this
yves: would be desirable
yves also need to look at the text in init state since that talks about sending the message but after 303 the message is already sent
ACTION: yves to propose text changes to solve 33rec [recorded in http://www.w3.org/2005/08/10-xmlprotocol-minutes.html#action01]
mike: anish will help yves

7. AOB: ATF's issue 1

<anish> http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2005Aug/0015.html
anish reviews the issue, reviews his proposed changes
dorchard: need to look at real world implementations. e.g. WS-I BP on one-way. May be that strict binding as described is not what has been implemented. change the spec to match reality
anish: would be comfortable changing the binding as suggested but recollection from previous discussion is that we didn't want to go there
mike: need more discussion on mailing list
ACTION: dorchard to respond to anish email to get discussion started [recorded in http://www.w3.org/2005/08/10-xmlprotocol-minutes.html#action02]
anish: third solution is to not change binding but have SOAP binding of WS-addr make the modification to the existing SOAP binding
Mike: anish please take that 3rd way to ML also.


5. New SOAP MEP/Binding work item

mike: how narrowly should we scope the work and participation ?
markn: leave it loose appeals more to me since atf is only a task force and may or may not produce what's required by addr wg
dorchard: xmlp wg needs to decide what work it wants to take on and what problems it wants to address
anish: thinks scoping the work before starting on a draft is the right way to go
dorchard: has alternatives already in xmlspec format, WG can review and decide
mike: seems that there is a minimum amount of work (as requested by wsd wg), would it make sense to start on the one-way ?
anish: work on one-way may be superceded by decision we make down the line, e.g. optional out covers one-way
... have requirements from wsd, use-cases from atf - xmlp can discuss these and propose a direction
dorchard: implicit use-case not mentioned - how to author meps and bindings and how difficult is it
mike: not ready to create an action on this yet
ACTION: mike to open discussion on mailing list re options [recorded in http://www.w3.org/2005/08/10-xmlprotocol-minutes.html#action03]

Postlude, Meeting Notes

Ran out of time, might have to consider returning to 90min calls. I will guage next weeks call productivity and act accordingly
No call 24th and 31st!
There will be a call next week – Aug 17.

Summary of Action Items

[NEW] ACTION: dorchard to respond to anish email to get discussion started [recorded in http://www.w3.org/2005/08/10-xmlprotocol-minutes.html#action02]
[NEW] ACTION: mike to open discussion on mailing list re options [recorded in http://www.w3.org/2005/08/10-xmlprotocol-minutes.html#action03]
[NEW] ACTION: yves to propose text changes to solve 33rec [recorded in http://www.w3.org/2005/08/10-xmlprotocol-minutes.html#action01]