Based on IRC logs for 1 August, 2 August
Present: Asir Vedamuthu, WebMethods Yves Lafon, W3C (scribe, a.m.) Martin Gudgin, Microsoft Colleen Evans, Progress Carine Bournez, W3C Noah Mendelsohn, IBM David Fallside, IBM (chair) Volker Wiechers, SAP Anish Karmarkar, Oracle Herve Ruellan, Canon Gerd Hoelzing, SAP Ryuji Inoue, Matsushita Kazunori Iwasa, Fujitsu Mark Jones, ATT (scribe, p.m.) Present by Phone (Partial): Mark Baker, Idokorro Excused: Camilo Arbelaez, webMethods John Ibbotson, IBM Henrik Nielsen, Microsoft Jeff Mischkinsky, Oracle Jean-Jacques Moreau, CanonResearchCentreFrance Paul Cotton, Microsoft Michah Lerner, ATT Masahiko Narita, Fujitsu Regrets: Highland Mountain, Intel Pete Wenzel, SeeBeyond David Orchard, BEASystems Paul Denning, MITRE Oisin Hurley, IONA [Mark Baker, IdokorroMobile, Inc.] Stuart Williams, Hewlett-PackardLabs Marc Hadley, SunMicrosystems Amr Yassin, Philips Jacek Kopecky, Systinet Nilo Mitra, Ericsson Glen Daniels, Macromedia Murali Janakiraman, RogueWaveSoftware Don Mullen, TIBCOExtensibility Michael Champion, SoftwareAG Yin-Leng Husband, Hewlett-Packard Bob Lojek, Intalio Ray Whitmer, Netscape Absent: Jin Yu, MArtsoft Mario Jeckle, Daimler Chrysler Andreas Riegg, Daimler Chrysler Brad Lund, Intel Eric Newcomer, IONA Simeon Simeonov, Macromedia Marwan Sabbouh, MITRE Vidur Apparao, Netscape Yasser alSafadi, Philips Patrick Thompson, Rogue Wave Dietmar Gaertner, Software AG Miroslav Simek, Systinet Frank DeRose, TIBCO Lynne Thompson, Unisys Nick Smilonich, Unisys [RRSAgent] RRSAgent has joined #xmlprotocol [Yves] zakim, this will probably be XMLP [Zakim] I don't understand 'this will probably be XMLP', Yves. Try /msg Zakim help [Yves] zakim, this will be XMLP [Zakim] ok, Yves [Mark_J] Mark_J has joined #xmlprotocol [carine] carine has joined #xmlprotocol [colleen] colleen has joined #xmlprotocol [herve] herve has joined #xmlprotocol [scribe_yl] ==== issue 339 ======= [anish_ca] anish_ca has joined #xmlprotocol [scribe_yl] herve is summarizing the interpretation of the tables [scribe_yl] proposal is at http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Aug/0001.html [scribe_yl] so basically, talbes are correct, and only clarifications will be made [noah] noah has joined #XMLProtocol [noah] noah has left #XMLProtocol [Noah] Noah has joined #XMLProtocol [scribe_yl] proposal is to respond with commentator that tables are ok, and changes done to calrify the meaning ot the tables [scribe_yl] also, the table 23 have a new line for errorcode ErrorEncodingUnknown [scribe_yl] (error 500) [scribe_yl] this will close issue 340 with that one [MarkB] 500? I would have thought 400. [carine] http://lists.w3.org/Archives/Public/xml-dist-app/2002Aug/0000.html [carine] Anish sent an email about this one [scribe_yl] markB: it's like version mismatch, that has 500 [carine] http://lists.w3.org/Archives/Public/xml-dist-app/2002Aug/0001.html [carine] Chris says 400 [Zakim] WS_XMLP(f2f)12:00PM has now started [Zakim] WS_XMLP(f2f)12:00PM has ended [MarkB] Henrik seems to have the magic touch for making those calls. Can we defer to him? [scribe_yl] can't read envelope -> 500, can't understand encoding -> 500 [MarkB] true [Mark_J] we're live on the conference bridge now [MarkB] yah, no phone lines are avaialble right now, so I can't call out [scribe_yl] consensus in the room is 500 [MarkB] ok [scribe_yl] we may revisit that when Henrik come back from holidays [scribe_yl] ACTION: Editors to make the changes per Herve's email, and add the line in table 23 [scribe_yl] ACTION: Herve to send email to xmlp-comments and commentator about closing issue 339 [scribe_yl] ACTION 1= Editors to make the changes per Herve's email wrt 339 [scribe_yl] ACTION Editors to add a line to table 23 per issue 340 [scribe_yl] ACTION Herve to send email to xmlp-comments and commentator about closing issue 340 [scribe_yl] ACTION: Editors to add a line to table 23 per issue 340 [scribe_yl] ACTION: Herve to send email to xmlp-comments and commentator about closing issue 340 [scribe_yl] more on editorial comment in 7.5.1.2 [scribe_yl] herve suggested to have 2 lines in 400 [scribe_yl] 1/ contains no fault [scribe_yl] 2/ contains a fault [scribe_yl] Gudge: content-type is here to figure out in which case you are [scribe_yl] resolution on this is to postpone with a complete proposal (on dist-app) [scribe_yl] ACTION: Herve to take "editorial note" on table 17 (7.5.1.2) and come up with a proposal on dist-app [scribe_yl] <issue number="314"> [Gudge] ACTION: Herve to take "editorial note" on properties that are URIs and come up witha proposal on dist-app [scribe_yl] comment divided as following: [scribe_yl] 1/ use URI for edges [scribe_yl] noah: do we label nodes or serialization? [scribe_yl] gudge: nodes [scribe_yl] 2/ URIs to identify nodes [scribe_yl] noah: why datamodel has IDs (optional id)? [scribe_yl] noah: in the case of edges, we don't require them to be unique, we can have a recursive datastruct, everything will have the same qname, what is the use case here? [asir] asir has joined #xmlprotocol [asir] I have some info on LC 314 [asir] http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Aug/0002.html [scribe_yl] gudge: arcs in rdf may have the same URI. [asir] asir has left #xmlprotocol [scribe_yl] ??P6 is probably F2Froom [scribe_yl] zakim, ??P6 is probably F2Froom [Zakim] +F2Froom?; got it [MarkB] zakim, ??P7 might be me [Zakim] I don't understand '??P7 might be me', MarkB. Try /msg Zakim help [MarkB] zakim, ??P7 may be me [Zakim] +MarkB?; got it [scribe_yl] noah: coherent thing to do is either status quo, or switch to URI, not having the two [scribe_yl] looking at Asir's email [scribe_yl] noah: adding uri may need to check inconsitencies [scribe_yl] 3.1.1, 1 and 2 [scribe_yl] it says we are not using id in the node but in the serialization [scribe_yl] identifying a variable in java is done by navigating in a reference tree [Noah] Why object identity is relative, not absolute: [Noah] object label1 = new Foo(); [Noah] object label2 = label1; [Noah] label1 = null; [Noah] **** [Noah] object label1 = new Foo(); [Noah] * //Object known as label1 [Noah] object label2 = label1; [Noah] * //Object known as label1 and label2 [Noah] label1 = null; [Noah] * //Object known as label2 [scribe_yl] http://www.w3.org/2000/03/rdf-tracking/#rdfms-qname-uri-mapping [scribe_yl] http://lists.w3.org/Archives/Public/www-tag/2002Jan/0221.html [scribe_yl] suggestion: tag will resolve this by having the URI derived from Qname [scribe_yl] noah: ID is there by mistake, it has never been set (unlike value, type...) [scribe_yl] fidning is done by navigation, not direct reference [scribe_yl] * We traverse from the node at the beginning at the encoding, rather than identify [scribe_yl] proposal, close 314, by removing the id on the node, and write back to DanB, that it is a traversal model rather than identity model [scribe_yl] sub proposal, 1/ purity in the model by removing ID [scribe_yl] 2/ status qui [scribe_yl] straw poll 5/0 [scribe_yl] ACTION: Editors Remove the ID property from the nodes of the data model. [scribe_yl] ACTION: Gudge to send email back to xmlp-comments and rdf group to close issue 314 [scribe_yl] </issue> [scribe_yl] <issue number="315"> [scribe_yl] proposal, we have tests in test collection, endpoints are available, and there is a community of people that tokk care of that issue in soap/1.1 ad we expect they will do the same for 1.2. [scribe_yl] s/too.*/are actively engaged into testing.../ [scribe_yl] 315 is closed with that resolution [scribe_yl] ACTION: Yves to send email back to xmlp-comments to close issue 315 with proposed resolution [scribe_yl] </issue> [scribe_yl] <issue number="316"> [scribe_yl] noah, gudge: we are a wire format, we are not defining langage binding [scribe_yl] 1/ how do application describe what they send/receive [scribe_yl] -> we don't say [scribe_yl] 2/ when should I use the encoding? [scribe_yl] 3/ clarification questions of graph edges [scribe_yl] gudge: it is not necessary that sender/receiver have the same view [scribe_yl] 1/ -> they create soap encodings :) [scribe_yl] 2/ [scribe_yl] DavidF: is there something in the primer about that? [scribe_yl] 2/ -> it's not our place to compare/contrast [scribe_yl] 3/ -> yes, yes, yes, yes [scribe_yl] proposal is to wait for Jacek's issue on generics. need to see if we can still determine what is a struct and what is an array [scribe_yl] <pause> [carine] Issues on generics: 297 and 365 (opposite positions ;) ) [Zakim] -MarkB? [scribe_yl] zakim, f2froom is really f2froom [Zakim] +F2froom; got it [scribe_yl] </pause> [scribe_yl] points 4 and 5 deferred [scribe_yl] 5 (how do we know something is a generic) [carine] issues about generics : 297 and 365 [scribe_yl] proposal, is to close 316 by responding to the first 3 question and considering the last 2 parts about generic as being dupes of 297/365 [scribe_yl] Proposal... [scribe_yl] 1/ it's out of scope for us. [scribe_yl] 2/ it's not our job (so out of scope) [scribe_yl] 3/ Y,Y,Y,Y [scribe_yl] 316 is closed [scribe_yl] ACTION: Gudge to send email to xmlp-comments to close issue 316 (see minutes) [scribe_yl] </issue> [scribe_yl] <issue number="317"> [scribe_yl] 1/ xslt/pi -> out of scope (not an use case) [scribe_yl] 2/ out of scope and no (as envelope is missing) [scribe_yl] 3/ out of scope also [scribe_yl] no objection, 317 is then closed [scribe_yl] ACTION: Gerd to send email to xmlp-comments to close issue 317 (see minutes) [scribe_yl] </issue> [scribe_yl] <issue number="318"> [scribe_yl] proposal, change the note in 3.1.4 from SOAP to SOAP-Encoding [scribe_yl] to clarify the paragraph [scribe_yl] proposal for 2/ SOAP processing model have a mechanism such as mU to provide support for what you describe [Zakim] +MarkB [scribe_yl] 318 is closed with that resolution [scribe_yl] </issue> [Noah] Note: we have received a note from Susan Lesch indicating that in the spec, the corporate name Mitre should be spelled MITRE [scribe_yl] ACTION: Editors to make the changes to 3.1.4 per issue 318 resolution (done) [scribe_yl] ACTION: MarkJ to send email to xmlp-comments to close issue 318 [mnot] mnot has joined #xmlprotocol [mnot] Yves? [scribe_yl] discussion on Davidf's proposal (http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Aug/0000.html) [scribe_yl] hi mark [scribe_yl] new draft on its way [MarkB] hey mnot. are you back on xmlp? [scribe_yl] review on proposal for 263 [scribe_yl] minor changes, will be sent to Martin and xmlp-comments [scribe_yl] <issue number="232"> [scribe_yl] issue 232 is closed by keeping status quo (mainly for backward compatibility reasons) [scribe_yl] ACTION: markJ to send email to xmlp-comments to close issue 232 [colleen] colleen has joined #xmlprotocol [scribe_yl] <issue number="233"> [scribe_yl] </issue></issue><issue number="233"> [scribe_yl] (for compliance of the log) [Gudge] http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#soaprole [scribe_yl] close issue 233 by accepting proposed resolution [scribe_yl] ACTION: Editors to remove the sentence per 233 [scribe_yl] ACTION: Carine to send email to xmlp-comments to close 233 [scribe_yl] </issue> [scribe_yl] <issue number="291"> [scribe_yl] proposal : stick it in the Upgrade namespace [scribe_yl] anish: for consistency, why have it lowercase? [scribe_yl] original reason was to have it different from the main one [scribe_yl] proposal to close 291 is uppercase E in Env, and be it part of upgrade namespace [scribe_yl] issue close by this proposal [scribe_yl] ACTION: Editors, make the proposed change wrt issue 192 resolution [scribe_yl] ACTION: DavidF to send email to xmlp-comments to close 291 [scribe_yl] </issue> [scribe_yl] <issue number="307"> [scribe_yl] should be amended to say "elephants allowed" [scribe_yl] (those who did not attend will have hard time understanding this one) [scribe_yl] discussion about handling of comments [scribe_yl] wrt to issue 307, we will add in 5.2.1 and 5.3.1 that child elements are allowed [scribe_yl] issue 307 closed with that resolution [Noah] Possible new issue: should 5.2, 5.2.1 etc. list other properties of element info items such as [namespace attributes]? [scribe_yl] ACTION: Editors: add the proposed change [scribe_yl] ACTION 19= Editors: add the proposed change for issue 307 [scribe_yl] ACTION 19= Editors: add the proposed change for issue 307 per minutes [Noah] ACTION 19= Editors: add the proposed change for issue 307 per minutes of Aug 1 Palo Alto FTF [Noah] :-) [scribe_yl] ACTION: Gudge to research infoset properties of header and body children, and suggest appropriate changes [scribe_yl] ACTION: Gudge Send email to xmlp-comments to close issue 307 (see minutes) [scribe_yl] </issue> [scribe_yl] <issue number="320"> [Gudge] http://www.w3.org/TR/2002/WD-soap12-part1-20020626/#faultcodes [scribe_yl] text proposed is a replacement for what's at the URI above [scribe_yl] noah: there is an asymetry, code/subcode/subcode/subcode [Zakim] -MarkB [scribe_yl] noah: change the example to show this (clarification) [MarkB] MarkB has left #xmlprotocol [scribe_yl] resolution is to mark this as editorial [scribe_yl] editors to clarify the relations between code, subcode and details element [scribe_yl] shorter than the proposed resolution [scribe_yl] ACTION: Editors to clarify the relations between code, subcode and detail element, but at least 1/3 of the size of the proposed solution for issue 320 resolution [scribe_yl] <lunch> [DavidF2F] adjourn until 1.15p [DavidF2F] PDT [DaveO] DaveO has joined #xmlprotocol [herve] herve has joined #xmlprotocol [scribemjg] =========== Afternoon session =================== [scribemjg] Number of items to discuss...AF doc [scribemjg] how to deal with issues we won't cover today [scribemjg] Chair speaking BTW [scribemjg] Approval of minutes from last telcon [scribemjg] rechartering discussion [scribemjg] so, 4 critical things [scribemjg] DavidF posted regarding AF doc [scribemjg] http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0164.html [scribemjg] proposal: publish AF doc as WD [scribemjg] no objection [scribemjg] ACTION: Yves/Herve to publish AF doc as WD [scribemjg] Regarding issues we will not close... [scribemjg] Proposal: Hand issues marked 'Editorial' over to editors to fix [Mark_J] Mark_J has joined #xmlprotocol [scribemjg] Editors to use discretion about bringing more substantive issues back to the WG for dicussion [scribemjg] s/dicussion/discussion [scribemjg] ACTION: Editors to fix all issues marked 'Editorial' in the issues list. Bring more substantive issues back to the WG. Deal with substantive closed issues first. Keep detailed change log. [scribemjg] Mark, you're up [scribemjg] ;-) [scribe_mj] WG will resume telcons on Sept 3 and continue working through the issue list. [scribe_mj] Suggestions for resolving issues are welcome to dist-app. [scribe_mj] The bar will be set high for new issues, which will be flagged as 'late'. [scribe_mj] There will be a set of 'gate people' who will examine the late issues for criticality. [scribe_mj] The minutes for July 24 were approved. [scribe_mj] <rechartering> [scribe_mj] Possible topics -- concrete attachment std, std appl-independent headers, etc. [DavidF2F] headers for example ..... mustHappen, sequencing headers [scribe_mj] Other possible topics are things like RDF and I18N vs. SOAP data model reconciliation. [scribe_mj] Also, re-thinking the SOAP fault reporting mechanism to make it easier for intermediaries to observe. [DavidF2F] zakim, who is here? [Zakim] On the phone I see F2froom [Zakim] On IRC I see scribe_mj, herve, colleen, Noah, anish_ca, carine, RRSAgent, Zakim, Gudge, DavidF2F, Yves, Loggy, HFN_away [scribe_mj] Noah: worried about isolated proposals for new features, might need to coordinate with other standards groups on new features [Noah] Noah also expresses strong feeling that SOAP 1.2 should be a stable spec. We should NOT set out to do a SOAP 1.3. [scribe_mj] ACTION: THe W3C staff to investigate what more is allowed under the existing charter with a temporal extension (post-Rec). [Noah] We should specifically not do a protocol that requires upgrade negotiation across implementations... [Noah] ...unless user feedback suggests that 1.2 really needs changing. This is like XML 1.0...it should be ubiquitiously deployed and should serve us for a long time. [scribe_mj] </rechartering> [Yves] so it rules out the "we will see that un possible next version" resolution ;) [Noah] I do think there is the possibility of creating headers and features, but we should go slow there too. I think most such features should be based on concrete feedback from users and from other organizations using our spec. We don't have that yet, I think. [anish_ca] anish_ca has joined #xmlprotocol [scribe_mj] <resume-issues/> [scribe_mj] <issue321> [scribe_mj] editorial -- eliminate DTDNotSupported [scribe_mj] from the faultcodeEnum in the schema [scribe_mj] ACTION: Editors: remove the DTDNotSupported from the schema [DavidF2F] DavidF2F has joined #xmlprotocol [herve] herve has joined #xmlprotocol [DavidF2F] http://www.w3.org/2000/xp/Group/xmlp-lc-issues#x322 [DavidF2F] dataEncodingUnknown [colleen] colleen has joined #xmlprotocol [scribe_mj] ACTION: Colleen: send msg to xmlp-comments saying we will maintain the status quo on the top-level status of DataEncodingUnknown. Table 23 in part 2 has been fixed. [scribe_mj] </issue321> [scribe_mj] <issue322> [scribe_mj] option 1 -- no change unless we go to a new LC [scribe_mj] option 2 -- status quo [scribe_mj] option 3 -- change the fault-handling mechanism to fix this and other problems [scribe_mj] option 3 -- is actually a minimal change just to 'detail' [scribe_mj] option 4 -- 1 and 3 [scribe_mj] Preponderance want 4. [scribe_mj] ACTIO: Editors: Make the change as in the proposal and ensure consistency elsewhere. [anish_ca] anish_ca has joined #xmlprotocol [scribe_mj] ACTION: Editors: Issue 322 -- Make the change as in the proposal and ensure consistency elsewhere. [DavidF2F] ACTION: Gudge to respond to HFN and xmlp-cmment re issue 322 [scribe_mj] </issue322> [DavidF2F] ========= mtg adjourn, return 3.30p pdt ================= [Gudge] Gudge has joined #xmlprotocol [DavidF2F] =========== mtg restart ============ [colleen] colleen has joined #xmlprotocol [scribe_mj] <issue323> [scribe_mj] ACTION: Editors: Issue 323 -- Make the change as in the proposal (the .../none URI) [scribe_mj] ACTION: Volker: Respond to xmlp-comment re issue 323 [scribe_mj] </issue323> [scribe_mj] <issue324> [scribe_mj] GUdge and Noah: like the way it is [scribe_mj] ACTION: DavidF: Respond to xmlp-comment and commentator re issue 324 [scribe_mj] </issue324> [scribe_mj] <issue292> [Gudge] Gudge has left #xmlprotocol [scribe_mj] ACTION: Noah: Issue 292 -- propose a resolution that the processor may elect to report any fault it chooses (when multiple faults exist) [scribe_mj] </issue292> [scribe_mj] <issue303> [Noah] Noah has joined #XMLProtocol [scribe_mj] general direction is to create an enc:invalidAttributeValue subcode of env:Sender (in the sense of doesn't match its schema type) [scribe_mj] the second point is to create an enc:ArraySizeMismatch subcode of env:Sender to capture incompatibilities between (legal) array sizes and the actual array members present [scribe_mj] general direction is to create an enc:InvalidAttributeValue subcode of env:Sender (in the sense of doesn't match its schema type) [DavidF2F] http://www.w3.org/TR/2002/WD-soap12-part2-20020626/#soapenc [scribe_mj] ACTION: Noah: Send XML Schema a note to clarify whether the validity rules for the IDREF data type require match of an ID. [scribe_mj] ACTION: XMLP WG: Restart the discussion of issue 303 regarding more encoding faults in section 3.2, part 2. [scribe_mj] </issue303> [DavidF2F] http://www.w3.org/2000/xp/Group/xmlp-lc-issues#x234 [scribe_mj] <issue234> [Yves] zakim, excuse us [Zakim] Zakim has left #xmlprotocol [scribe_mj] <adjourn/> ======== SUMMARY OF DAY'S ACTION ITEMS ================ [RRSAgent] I see 35 open action items: [RRSAgent] ACTION: Editors to make the changes per Herve's email wrt 339 [1] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T16-12-36 [RRSAgent] ACTION: Herve to send email to xmlp-comments and commentator about closing issue 339 [2] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T16-13-09 [RRSAgent] ACTION: Editors to add a line to table 23 per issue 340 [3] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T16-15-42 [RRSAgent] ACTION: Herve to send email to xmlp-comments and commentator about closing issue 340 [4] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T16-15-46 [RRSAgent] ACTION: Herve to take "editorial note" on table 17 (7.5.1.2) and come up with a proposal on dist-app [5] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T16-21-16 [RRSAgent] ACTION: Herve to take "editorial note" on properties that are URIs and come up witha proposal on dist-app [6] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T16-23-11-1 [RRSAgent] ACTION: Editors Remove the ID property from the nodes of the data model. [7] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T17-08-20 [RRSAgent] ACTION: Gudge to send email back to xmlp-comments and rdf group to close issue 314 [8] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T17-09-21 [RRSAgent] ACTION: Yves to send email back to xmlp-comments to close issue 315 with proposed resolution [9] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T17-15-43 [RRSAgent] ACTION: Gudge to send email to xmlp-comments to close issue 316 (see minutes) [10] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-19-27 [RRSAgent] ACTION: Gerd to send email to xmlp-comments to close issue 317 (see minutes) [11] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-25-55 [RRSAgent] ACTION: Editors to make the changes to 3.1.4 per issue 318 resolution (done) [12] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-35-13 [RRSAgent] ACTION: MarkJ to send email to xmlp-comments to close issue 318 [13] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-35-26 [RRSAgent] ACTION: markJ to send email to xmlp-comments to close issue 232 [14] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-51-49 [RRSAgent] ACTION: Editors to remove the sentence per 233 [15] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-55-28 [RRSAgent] ACTION: Carine to send email to xmlp-comments to close 233 [16] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T18-55-38 [RRSAgent] ACTION: Editors, make the proposed change wrt issue 192 resolution [17] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T19-00-15 [RRSAgent] ACTION: DavidF to send email to xmlp-comments to close 291 [18] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T19-01-31 [RRSAgent] ACTION: Editors: add the proposed change for issue 307 per minutes of Aug 1 Palo Alto FTF [19] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T19-16-25 [RRSAgent] ACTION: Gudge to research infoset properties of header and body children, and suggest appropriate changes [20] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T19-21-18 [RRSAgent] ACTION: Gudge Send email to xmlp-comments to close issue 307 (see minutes) [21] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T19-22-19 [RRSAgent] ACTION: Editors to clarify the relations between code, subcode and detail element, but at least 1/3 of the size of the proposed solution for issue 320 resolution [22] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T19-31-10 [RRSAgent] ACTION: Yves/Herve to publish AF doc as WD [23] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T20-25-56 [RRSAgent] ACTION: Editors to fix all issues marked 'Editorial' in the issues list. Bring more substantive issues back to the WG. Deal with substantive closed issues first. Keep detailed change log. [24] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T20-31-50 [RRSAgent] ACTION: THe W3C staff to investigate what more is allowed under the existing charter with a temporal extension (post-Rec). [25] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T21-10-44 [RRSAgent] ACTION: Editors: remove the DTDNotSupported from the schema [26] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T21-25-07 [RRSAgent] ACTION: Colleen: send msg to xmlp-comments saying we will maintain the status quo on the top-level status of DataEncodingUnknown. Table 23 in part 2 has been fixed. [27] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T21-27-07 [RRSAgent] ACTION: Editors: Issue 322 -- Make the change as in the proposal and ensure consistency elsewhere. [28] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T22-03-44 [RRSAgent] ACTION: Gudge to respond to HFN and xmlp-cmment re issue 322 [29] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T22-04-01 [RRSAgent] ACTION: Editors: Issue 323 -- Make the change as in the proposal (the .../none URI) [30] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T22-45-49 [RRSAgent] ACTION: Volker: Respond to xmlp-comment re issue 323 [31] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T22-46-31 [RRSAgent] ACTION: DavidF: Respond to xmlp-comment and commentator re issue 324 [32] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T22-49-29 [RRSAgent] ACTION: Noah: Issue 292 -- propose a resolution that the processor may elect to report any fault it chooses (when multiple faults exist) [33] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T22-58-46 [RRSAgent] ACTION: ACTION: Noah: Send XML Schema a note to clarify whether the validity rules for the IDREF data type require match of an ID. (ALREADY DISCHARGED - Noah found the answer in Schema Part 1. IDREFs are validity checked.) [34] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T23-45-32 [RRSAgent] ACTION: XMLP WG: Restart the discussion of issue 303 regarding more encoding faults in section 3.2, part 2. [35] [RRSAgent] recorded in http://www.w3.org/2002/08/01-xmlprotocol-irc#T23-46-36