Web Services Resource Access Working Group Teleconference

28 Sep 2010


See also: IRC log


Alessio Soldano, Red Hat
Bob Freund, Hitachi, Ltd.
David Snelling, Fujitsu, Ltd.
Doug Davis, IBM
Katy Warr, IBM
Vikas Varma, Software AG
Wu Chou, Avaya Communications
Yves Lafon, W3C/ERCIM
Ashok Malhotra, Oracle Corp.
Asir Vedamuthu, Microsoft Corp.
Bob Natale, MITRE Corp.
Fred Maciel, Hitachi, Ltd.
Gilbert Pilz, Oracle Corp.
Jeff Mischkinsky, Oracle Corp.
Li Li, Avaya Communications
Mark Little, Red Hat
Martin Chapman, Oracle Corp.
Nathan Burkhart, Microsoft Corp.
Orit Levin, Microsoft Corp.
Paul Fremantle, WSO2
Paul Nolan, IBM
Prasad Yendluri, Software AG
Ram Jeyaraman, Microsoft Corp.
Tom Rutt, Fujitsu, Ltd.
Wei Jun Kong, CA
Ashok Malhotra, Oracle Corp.
Fred Maciel, Hitachi, Ltd.
Martin Chapman, Oracle Corp.
Ram Jeyaraman, Microsoft Corp.
Bob Freund, Hitachi, Ltd.
Katy Warr, IBM


<trackbot> Date: 28 September 2010

<Bob_> scribenick: Katy


Agenda accepted

Approve minutes from 21st Sept

Minutes approved

Issue-10768 MEX: Optionality of GetWSDL http://www.w3.org/Bugs/Public/show_bug.cgi?id=10768 -Davis

Doug: Explains issue

Issue 10768 Accepted

<Bob_> proposal: Proposal: Modify the GetWSDLResponse: Current text: [Body]/mex:GetWSDLResponse/xs:any When the GetWSDLResponse element contains any child elements, the first element MUST either be the WSDL metadata document, or a reference to the WSDL metadata document, of the endpoint. Any extension elements MUST appear after the WSDL document/reference. The absence of any child elements indicates that the endpoint does not have any WSDL document, or additional m

<Bob_> "Any extension elements..." sentence: While an endpoint MAY choose to return a reference to the WSDL, it is STRONGLY RECOMMENDED that the WSDL metadata document itself be returned. If a requester would like a reference to the WSDL then it can use the GetMetadata operation specifying the appropriate Content URI.

No objections to accepting proposal

RESOLUTION: Issue 10768 resolved with proposal

Issue-10785 MEX: PutMetadata is ambiguous on request with references http://www.w3.org/Bugs/Public/show_bug.cgi?id=10785

Doug: explains

thanks Yves

No objections to opening issue

RESOLUTION: Proposal accepted - Doug to edit approriate text

Feature list

Bob: Eventing, Mex, Transfer and Frag Feature lists out
... remaining expected within next couple of days
... Implementors must take feature template lists and mark up aspects that they are not implementing

Discussion about best format for document editing/sharing

Bob: We will use HTML for these documents

<Bob_> ACTION: Freund will perform conversion on documents [recorded in http://www.w3.org/2010/09/28-ws-ra-minutes.html#action01]

<trackbot> Created ACTION-167 - Will perform conversion on documents [on Bob Freund - due 2010-10-05].

Bob: Will distribute the feature lists in html for discuss next week
... Mex primer under review and should be distributed this week
... Doug will do Mex primer (no timescale yet)
... Gil and Wu to start work on Eventing

Summary of Action Items

[NEW] ACTION: Freund will perform conversion on documents [recorded in http://www.w3.org/2010/09/28-ws-ra-minutes.html#action01]
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/10/06 10:46:17 $