Based on IRC log http://www.w3.org/2003/07/02-xmlprotocol-irc
======== Roll call Present 13/10 AT&T, Mark Jones BEA Systems, Mark Nottingham Canon, Herve Ruellan IBM, John Ibbotson IBM, Noah Mendelsohn IBM, David Fallside Microsoft Corporation, Martin Gudgin Oracle, Anish Karmarkar SAP AG, Volker Wiechers SeeBeyond, Pete Wenzel Sun Microsystems, Tony Graham W3C, Yves Lafon W3C, Carine Bournez Excused AT&T, Michah Lerner BEA Systems, David Orchard Canon, Jean-Jacques Moreau Microsoft Corporation, Jeff Schlimmer Oracle, Jeff Mischkinsky SAP AG, Gerd Hoelzing Sun Microsystems, Marc Hadley Regrets DaimlerChrysler R. & Tech, Mario Jeckle Fujitsu Limited, Kazunori Iwasa Fujitsu Limited, Masahiko Narita IONA Technologies, Oisin Hurley Matsushita Electric, Ryuji Inoue Systinet (IDOOX), Jacek Kopecky Absent DaimlerChrysler R. & Tech, Andreas Riegg Ericsson, Nilo Mitra IONA Technologies, Eric Newcomer Macromedia, Glen Daniels Software AG, Dietmar Gaertner Software AG, Michael Champion Systinet (IDOOX), Miroslav qSimek ======== [Scribe] Review of agenda [Scribe] No AOB, agenda accepted as is ======== [Scribe] Approval of telcon minutes: [Scribe] One correction: Oracle\Anish sent regrets for last weeks telcon [Scribe] Minutes approved without objection ======== [Scribe] Review of action items: [Scribe] ACTION: W3C staff to add boiler plate to requirements and usage scenarios and then publish in 'member accessible/unadvertised place' as a WG note [Scribe] Above action supercedes previous action to Chair, JJM, JohnI, W3C Staff [Scribe] MNot: Pending [Scribe] DaveO: Done [Scribe] Jacek: Done [Scribe] TonyG: Done [Scribe] Noah: Done ======== [Scribe] Status reports: [Scribe] FTF registration open until July 17th [Scribe] Media-Type registration [Scribe] We are now at the stage where we can request an RFC [Scribe] Once the document has been published as an RFC it will be entered in the IANA registry [Scribe] That said, it could be a while before it is published [Scribe] ACTION: MNot to ask IETF to publish the SOAP Media-Type registration as an RFC [Scribe] Above action replaces existing action for MNOT ======== [Scribe] Attachments: [Scribe] There were a number of edits/revisions proposed/requested last week [Scribe] Various edits have been made to the draft [Scribe] Document is at http://www.w3.org/2000/xp/Group/3/06/Attachments/OptimizationMechanism.html [Scribe] Hervé summarizes the changes he has made... [Scribe] xbinc:Include is still the name of the inclusion element [Scribe] other changes have been incorporated [Scribe] text incorporated into Section 1.2 regarding reconciliation of req doc and MTOM doc ( or lack thereof ) [davidF] This document represents the transmission optimization mechanism which [davidF] is a part of the original PASWA document [link]. The WG plans to work [davidF] later on the other parts of that documents (assigning media types to [davidF] binary data in XML infosets and including representations of Web [davidF] resources in SOAP messages) and to publish other drafts which will [davidF] include such mechanisms. [davidF] This document represents the transmission optimization mechanism which [davidF] is a part of the original PASWA document [link]. The WG plans to work [davidF] later on the other parts of that documents (assigning media types to [davidF] binary data in XML infosets and including representations of Web [davidF] resources in SOAP messages) and to publish other drafts which will [davidF] include such mechanisms. [davidF] This document represents the transmission optimization mechanism which [davidF] was inspired by the description in the PASWA document [link]. The WG plans to work later on the other parts of that documents (assigning media types to [davidF] binary data in XML infosets and including representations of Web [davidF] resources in SOAP messages) and to publish other drafts which will [davidF] include such mechanisms. [Scribe] Noah suggestes amended text [davidF] This document represents the transmission optimization mechanism which [davidF] was inspired by a similar mechanism in the PASWA document [link]. The WG plans to work later on the other parts of that documents (assigning media types to [davidF] binary data in XML infosets and including representations of Web [davidF] resources in SOAP messages) and to publish other drafts which will [davidF] include such mechanisms. [noah] Looks fine to me [noah] Agree with Gudge the transmission -> a transmission [davidF] This document represents a transmission optimization mechanism which [davidF] was inspired by a similar mechanism in the PASWA document [link]. The WG plans to work later on the other parts of that document (assigning media types to [davidF] binary data in XML infosets and including representations of Web [davidF] resources in SOAP messages) and to publish other drafts which will [davidF] include such mechanisms. [Scribe] Above text accepted without objection [Scribe] ACTION: Hervé to add above text. [Scribe] ACTION: DavidF to e-mail above text to Hervé [davidF] ACTION: herve to add Gudge's 1st change from his emial this morning [Scribe] Gudges' e-mail is at http://lists.w3.org/Archives/Public/xml-dist-app/2003Jul/0003.html [davidF] The first part of this document (2. Abstract Transmission Optimization [davidF] Feature) describes an abstract feature for optimizing the transmission [davidF] and/or wire format of a SOAP message by selectively re-encoding portions of [davidF] the message, while still presenting an XML Infoset to the SOAP application. [davidF] This Abstract Transmission Optimization Feature is intended to be [davidF] implemented by SOAP bindings, however nothing precludes implementing it as [davidF] a SOAP module. [davidF] The usage of the Abstract Transmission Optimization Feature is a hop-by-hop [davidF] contract between a SOAP node and the next SOAP node in the SOAP message [davidF] path, providing no normative convention for optimization of SOAP [davidF] transmission through intermediaries. Additional specifications could in [davidF] principle be written to provide for optimized multi-hop transmission, [davidF] either through repeated use of the single-hop facilities provided herein, [davidF] or in other ways that build on this specification (e.g. by providing for [davidF] transparent passthrough of optimized messags.) [davidF] The second part (3. Inclusion Mechanism) describes an Inclusion Mechanism [davidF] implementing part of the Abstract Transmission Optimization Feature in a [davidF] binding-independant way. The third part (4. HTTP Transmission Optimization [davidF] Feature) uses this Inclusion Mechanism for implementing the Abstract [davidF] Transmission Optimization Feature for an HTTP binding. [mnot] http://www.w3.org/mid/OF660E4603.05E30836-ON85256D56.006B3454@lotus.com [Yves] http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2003Jul/0002.html [davidF] http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2003Jul/0002.html [Scribe] MNot, OK with above text. Question about packing of deliverables. [Scribe] DavidF: we make reference to the fact that this is not necessariliy the final delivery mechanism. e.g. Section 1.2 [davidF] ACTION: herve incorporate Noah's new intro (July msg #2 as above) [Scribe] No objection to proceeding with publication after Hervé incorporates above changes [Scribe] Changes should be done by EOW ( July 4th ) [Scribe] Hervé will try to do the edits tomorrow, Gudge will help if needed [Scribe] PASWA and XQuery Data Model, discussion deferred until FTF [Scribe] Discussion of Issue 431 [Scribe] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x431 [Scribe] Some discussion of the 'receiver side' property [Scribe] Some discussion of whether intermediaries can change the set of things that are optimized [Scribe] Gudge says Yes, Hervé agrees [Scribe] ACTION: Gudge to write up a summary of where we are up to regarding Issue 431/432. Include discussion of 'receiver side' property. [mnot] +1 ;) [Scribe] Adjourned ( agenda exhausted ) [RRSAgent] ACTION: W3C staff to add boiler plate to requirements and usage scenarios and then publish in 'member accessible/unadvertised place' as a WG note [1] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-13-09 [RRSAgent] ACTION: MNot to ask IETF to publish the SOAP Media-Type registration as an RFC [2] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-17-14 [RRSAgent] ACTION: Hervé to add above text. [3] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-32-28 [RRSAgent] ACTION: DavidF to e-mail above text to Hervé [4] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-32-36 [RRSAgent] ACTION: herve to add Gudge's 1st change from his emial this morning [5] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-35-48 [RRSAgent] ACTION: herve incorporate Noah's new intro (July msg #2 as above) [6] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-44-04 [RRSAgent] ACTION: Gudge to write up a summary of where we are up to regarding Issue 431/432. Include discussion of 'receiver side' property. [7] [RRSAgent] recorded in http://www.w3.org/2003/07/02-xmlprotocol-irc#T18-57-51