Based on IRC log
1. Roll Present 12/9 BEA Systems, Mark Nottingham IBM, David Fallside IBM, Noah Mendelsohn IBM, John Ibbotson Microsoft Corporation, Martin Gudgin Nokia, Michael Mahan Oracle, Anish Karmarkar SAP AG, Volker Wiechers SAP AG, Gerd Hoelzing SeeBeyond, Pete Wenzel Sun Microsystems, Marc Hadley (scribe) W3C, Yves Lafon Excused BEA Systems, David Orchard Microsoft Corporation, Jeff Schlimmer Oracle, Jeff Mischkinsky Sun Microsystems, Tony Graham Regrets Canon, Jean-Jacques Moreau Canon, Herve Ruellan Absent IONA Technologies, Suresh Kodichath 2. Agenda review No AOB 3. Approval of minutes 9 June minutes approved without objection. 4. Action items [Scribe] last four action items DONE [Scribe] first action item partly done [Scribe] updated primer due end of week, will discuss on next call 5. Status [Scribe] Media types registrations: in rfc editors publication queue, media type registered [Scribe] XMLP/WSD task force: no update [Scribe] WSD requested changes via email - will create an issue and consider next week 6. Attachment [Scribe] Agreement that 6 "editorial" issues are indeed editorial and that they will be left for editors to handle [Scribe] 480, 476, 478, 468, 469, 471 [Scribe] ACTION: editors to resolve issues 480, 476, 478, 468, 469, 471 and send email to XMLP comments [Scribe] Issue 418 [Scribe] Gudge: thought this was just being parked [Scribe] DF: proposal to close by noting that AF doc is now deprecated, close without action [Scribe] Agreed to close as proposed [Scribe] Issue 470 [Scribe] Gudge: dupe of 469 ? [Scribe] Gudge: First part is dupe, second part is not [Scribe] ACTION: Gudge? to send email to xmlp comment to close issue 418 [Scribe] Second part was considered but alternate approach adopted [Scribe] ACTION: MarkN to write up rationale as closing for issue 470 [Gudge] ACTION: MNot to send e-mail to xmlp-comment and commentator closing issue 470 [Yves] ACTION -4 [Gudge] ACTION 3 = MarkN to write up rationale as closing for issue 470 and send e-mail to xmlp-comments and commentator [Scribe] Issue 472 [Scribe] Marc: editorial ? [Scribe] Use optimized instead of extracted, asign to editors to fix [Scribe] Issue 473 [Gudge] ACTION: Editors to resolve 472 by using the term Optimized Content instead of Extracted Content. [Scribe] Example doesn't correspond to our rules for canonical base64 [Scribe] noah: add note to explain ? [Scribe] MarkN can content of optimized element include other non-base64 chars: e.g. XXXX b ase64 XXXX -> XXXX <xop:Include .../> XXXX ? [Scribe] Gudge: spec is clear, this isn't allowed [Scribe] MarkN: creative editing should fix this [Scribe] Noah: chars not allowed, what about elements - i.e. mixed content [Scribe] DF: (i) clarify that only CIIs allowed in elements to be optimized, (ii) editors to clean up example [Scribe] Update XOP 3.1 bullet 3 as MUST only include CIIs [Scribe] Update example in section 1.2 to remove offending whitespace [Scribe] No objection to closing 473 with above proposal [Gudge] ACTION: Gudge to send mail to xmlp-comments and commentator closing issue 473 [Scribe] Issue 474 [Scribe] MarkN: disagrees with suggestion, last bullet describes package construction [Scribe] MarkN, on lcoser reading agrees that last sentence shoudl be changed [Scribe] 474 closed with originators suggestion [Gudge] ACTION: Gudge to send closing e-mail to xmlp-comment and commentator for issue 474 [Scribe] Issue 475 [Scribe] MarkN: agrees with issue propose to add text in line with suggestion [Scribe] Add to last sentence of first para of section 4 [Noah] Such packaging mechanisms MUST be able to represent, with full fidelity all the parts created according to 3 XOP's Processing Model (see 3.1 Creating XOP Packages), and must be capable of designating a distinguished root part. [Noah] Such packaging mechanisms MUST be able to represent, with full fidelity all the parts created according to 3 XOP's Processing Model (see 3.1 Creating XOP Packages), and must provide a means of designating a distinguished root part. [Noah] Such packaging mechanisms MUST be able to represent, with full fidelity all the parts created according to 3 XOP's Processing Model (see 3.1 Creating XOP Packages), and MUST provide a means of designating a distinguished root part. [Scribe] Marc: concern that this implies that the packaging mechanism would need to have a first class notion of a root part [Noah] Such packaging mechanisms MUST be able to represent, with full fidelity all the parts created according to 3 XOP's Processing Model (see 3.1 Creating XOP Packages), and MUST be used in a manner that provides a means of designating a distinguished root part. [Scribe] 475 closed with text above [Scribe] Issue 477 [Scribe] Marc: suggests chnaging receiver to intermediaries [Scribe] Gudge: drop the sentence [Scribe] Gudge: previous sentence cover the requirement [Scribe] Noah: agrees to drop sentence [Scribe] Proposal: remove last sentence of para 2 in MTOM 2.3.2 [Scribe] 477 closed with this proposal [Scribe] Issue 479 [Scribe] comment 1 [Scribe] TBD in spec section 1.2 [Gudge] ACTION: Gudge to send closing e-mail to commentator and xmlp-commands for Issue 477 [Gudge] ACTION: MikeM to send closing e-mail to commentator and xmlp-comments for Issue 475 [Gudge] ACTION 8 = Gudge to send closing e-mail to commentator and xmlp-comments for Issue 477 [Gudge] ACTION: Anish to produce text for section 1.2 of Representation Header document. [Scribe] 479, pt 2 [Scribe] extracted content to optimized content, editorial fix [Yves] The representation header is also required when multiple references to the same extracted content are required but duplication of extracted content is undesirable. [Scribe] gudge: chnage extracted content to resource [Scribe] noah: note that rep header is designed to work with MTOM/XOP but can be used independently [Gudge] ACTION: Yves to amend paragraph 1 section 2.1 to use 'resource' instead of 'extracted content' [Scribe] 479, pt 3 [Gudge] ACTION 11 = Yves to amend paragraph 1 section 2.1 of Representation header to use 'resource' instead of 'extracted content' and check the rest of the spec for XOP/MTOM specific language. ( Issue 479 Part 3 ) [Scribe] Marc agrees it would be a good idea to make rep header into a SOAP module [Scribe] Noah: low cost to make it a module, might be useful later [Scribe] Anish: from WSDL perspective this would be convenient. [Scribe] Discussion of feature vs module [Scribe] DF: any objection to identifying rep header as a module ? [Scribe] Anish: simpler to define feature rather than module ? [Scribe] Noah: need to do both [Scribe] Will deal with pt3 by adding feature/module stuff to rep header spec [Gudge] ACTION: Anish to draft text for making Representation header a module and a feature. [Scribe] 479, pt 4 [Scribe] gudge: section 2.1 already says this for elements [Yves] ttp://www.w3.org/2004/02/representation is the schema [Scribe] gudge: 2.2.1, bullet 3 sub bullet 3 ans 2.2.4 bullet 3 - add ns qual AII whose ns name is not ... [Scribe] Schema and spec are not completely in line wrt to data element [Gudge] ACTION: Gudge to sweep Rep spec and propose a consistent resolution for namespace qualfication of additional attributes and elements. related to issue 479 bullet 4. [Scribe] wg agrees with sentiment of comment [Scribe] 479, pt 5 [Scribe] Need proposal to address normative vs non-normative in rep header spec [Gudge] ACTION: Yves to make a proposal for addressing normative/non-normative status in Rep header spec. [Scribe] 479, pt 6 [Scribe] WG agrees with comment [Scribe] 479 [Gudge] ACTION: Yves to fix example in section 2.3.3 per issue 479 pt 6 [Scribe] in priciple have resolved all parts of this issue [Scribe] awaiting some proposals and will then bundle these up to close the issue [Zakim] leaving. As of this point the attendees were John_Ibbotson, Gudge, Marc, Yves, Mark_Nottingham, +1.603.827.aaaa, Noah, Anish, M.Mahan [RRSAgent] I see 14 open action items: [RRSAgent] ACTION: editors to resolve issues 480, 476, 478, 468, 469, 471 and send email to XMLP comments [1] [RRSAgent] ACTION: Gudge? to send email to xmlp comment to close issue 418 [2] [RRSAgent] ACTION: MarkN to write up rationale as closing for issue 470 and send e-mail to xmlp-comments and commentator [3] [RRSAgent] ACTION: Editors to resolve 472 by using the term Optimized Content instead of Extracted Content. [5] [RRSAgent] ACTION: Gudge to send mail to xmlp-comments and commentator closing issue 473 [6] [RRSAgent] ACTION: Gudge to send closing e-mail to xmlp-comment and commentator for issue 474 [7] [RRSAgent] ACTION: Gudge to send closing e-mail to commentator and xmlp-comments for Issue 477 [8] [RRSAgent] ACTION: MikeM to send closing e-mail to commentator and xmlp-comments for Issue 475 [9] [RRSAgent] ACTION: Anish to produce text for section 1.2 of Representation Header document. [10] [RRSAgent] ACTION: Yves to amend paragraph 1 section 2.1 of Representation header to use 'resource' instead of 'extracted content' and check the rest of the spec for XOP/MTOM specific language. ( Issue 479 Part 3 ) [11] [RRSAgent] ACTION: Anish to draft text for making Representation header a module and a feature. [12] [RRSAgent] ACTION: Gudge to sweep Rep spec and propose a consistent resolution for namespace qualfication of additional attributes and elements. related to issue 479 bullet 4. [13] [RRSAgent] ACTION: Yves to make a proposal for addressing normative/non-normative status in Rep header spec. [14] [RRSAgent] ACTION: Yves to fix example in section 2.3.3 per issue 479 pt 6 [15]