Minutes of XML Protocol Telcon, 2 October 2002

Based on IRC Log.

[scribe]
1. Roll call.

Present 22/17
AT&T Mark Jones
Ericsson Nilo Mitra
IBM John Ibbotson
IBM David Fallside
IBM Noah Mendelsohn
Intel Highland Mary Mountain
IONA Technologies Oisin Hurley
Macromedia Glen Daniels
Microsoft Corporation Henrik Nielsen
Microsoft Corporation Martin Gudgin
Netscape Ray Whitmer
Oracle Anish Karmarkar
Progress Software Colleen Evans
Rogue Wave Murali Janakiraman
SeeBeyond Pete Wenzel
Software AG Michael Champion
Sun Microsystems Marc Hadley
Tibco Don Mullen
W3C Yves Lafon
W3C Carine Bournez
WebMethods Camilo Arbelaez
WebMethods Asir Vedamuthu

Excused
AT&T Michah Lerner
Intel Brad Lund
IONA Technologies Eric Newcomer
Netscape Vidur Apparao
Oracle Jeff Mischkinsky
Rogue Wave Patrick Thompson
Software AG Dietmar Gaertner
Tibco Amy Lewis

Regrets
BEA Systems David Orchard
Canon Jean-Jacques Moreau
DaimlerChrysler R. & Tech Mario Jeckle
Matsushita Electric Ryuji Inoue
Mitre Paul Denning
SAP AG Volker Wiechers
SAP AG Gerd Hoelzing
Systinet (IDOOX) Jacek Kopecky
Unisys Lynne Thompson

Absent
Canon Herve Ruellan
DaimlerChrysler R. & Tech Andreas Riegg
Fujitsu Limited Kazunori Iwasa
Fujitsu Limited Masahiko Narita
Martsoft Jin Yu
Mitre Marwan Sabbouh
Systinet (IDOOX) Miroslav Simek
Unisys Nick Smilonich
[scribe]
2. Agenda review, and AOB (12.05 + 5)
[scribe]
3. Approval of 25 Sept telcon minutes
[scribe]
http://www.w3.org/2000/xp/Group/Admin/#schedule
[scribe]
No objections to approving minutes.
[scribe]
MINUTES APPROVED
[scribe]
4. Review action items
[Yves]
Asir: PENDING
[Yves]
Editors: DONE
[Yves]
DavidF: Pending
[scribe]
David checking with implementors, including ones no longer on XMLP
[Yves]
DavidF: Pending
[Yves]
Editors: DONE
[Yves]
DavidF: DONE
[Yves]
Editors: PENDING
[Yves]
Jacek: draft sent, so PENDING
[marc]
URI decision was on 11th Sept con-call
[Yves]
Henrik: DONE
[GlenD]
Was there an email thread about that as well?
[GlenD]
URI-izing?
[Gudge]
On URI-izing?
[Gudge]
250 is not URI-izing
[Yves]
Editors: DONE
[GlenD]
QNames are very easy to represent in XML (for instance in WSDL). URI's not so much.
[GlenD]
"Make state, role, and failure properties URIs"
[marc]
i think the TAG finding on URIs vs QNames was the deciding factor
[Yves]
Jacek: DONE
[Yves]
DavidF: DONE
[GlenD]
marc: Have a URL for that?
[Gudge]
I thought the TAG said QNames were fine?
[Yves]
Jacek: DONE
[Yves]
Editors: DONE
[GlenD]
Do they think XML is a bad idea too? :)
[Yves]
DonM: DONE
[Yves]
Jacek: DONE
[marc]
i don;t have a link handy
[Yves]
Editors: Pending
[GlenD]
OK, thanks, though. I'll research it.
[Yves]
Editors: DONE
[Yves]
Henrik: DONE
[Yves]
Noah: DONE
[Yves]
Carine: PENDING
[scribe]
5. Status reports (12.25 + 15)
[scribe]
Primer: nothing to report
[scribe]
Spec : nothing to report
[Noah]
Noah also fulfilled another action assigned on last week's call, but not apparently captured as an action, which was to propose resolution to concerns about issue 231. DF reports it's on the agenda for today.
[scribe]
Attachment feature : no feedback as yet, WSD group planning on giving feedback, deadline 19th
[Gudge]
The deadline for review is the date on or before which review comments must arrive ;-)
-- many participants bumped from phone bridge
[DavidF]
looks like we lost the entire bridge!!
[marc]
was it something we said
[asir]
Possibly
[Henrik]
not all
[scribe]
[Horrible screeching feedback interrupts call]
[asir]
I re-dialed and it is not letting me thru
[marc]
did anyone else get the french hold music ?
[DavidF]
asir - try again it sometimes cannot deal w/ lots of simult redials
[asir]
I got in
[DavidF]
non!
[scribe]
-- Implementation tracking
[Yves]
http://lists.w3.org/Archives/Public/xmlp-comments/2002Oct/0002.html
[Yves]
http://lists.w3.org/Archives/Public/xmlp-comments/2002Sep/0081.html
[scribe]
(Henrik notes two xmlp-comments mails re: LC)
[scribe]
David indicates we need to update the Test Collection doc to reflect LC issue decisions
[scribe]
Need to discuss interop requirements and testing techniques at some point.
[scribe]
-- Media type draft, IANA application: need to revisit as we approach resolution of last last-call issues
[scribe]
-- Planning Oct f2f [http://www.w3.org/2000/xp/Group/2/09/F2Fmeeting.html]
[marc]
gudge: no, they weren't, at least one of them wasa QName
[scribe]
13 registered so far
[scribe]
deadline is 18 Oct
-- Chair encourages people to register asap because meeting room has limited capacity.
[anish]
looking at the meeting webpage only 6 members have registered
[Gudge]
marc: Ahh, in 7.5 a lot of the failureReason were QNames
[scribe]
6. LC Issues [http://www.w3.org/2000/xp/Group/xmlp-lc-issues] (12.40 + 80)
[Gudge]
marc: despite the fact that the table 2 defines failureReason as a URI
[Yves]
MarkB: http://lists.w3.org/Archives/Public/xmlp-comments/2002Sep/0081.html
[scribe]
df: Are we willing to accept MarkB's late request as an issue?
[scribe]
NO DISSENT. df: we will create a new issue for Mark's comment
-- df: with regard the other late LC comment http://lists.w3.org/Archives/Public/xmlp-comments/2002Oct/0002.html, members have not had time to review it and so somone will evaluet it to detemrine whether to accept it as an issue.
[scribe]
-- Discussion of pushback to any issues we have closed
[scribe]
no pushback so far
[scribe]
-- 338, state machine description questions
[scribe]
Asir drafted a response
[scribe]
Response is currently in progress, pending clarification question.
[scribe]
Q: If the transition between two states is unconditional, why bother having two states?
[scribe]
We decided at the f2f to maintain status quo.
[scribe]
Marc: transition is conditional on having a message to send....
[scribe]
Asir : INIT & REQUESTING are distinct states in the HTTP binding. Transition is "start sending".
[scribe]
Asir : if condition is real, let's specify it
[scribe]
[mumblings of agreement]
[scribe]
"unconditional" -> "transmission of request message initiated"
[scribe]
(suggested wording from DavidF)
[marc]
gudge: darn, looks like I missed all those fail:xxxx, although it looks like I did add the <attval> markup :-(
[scribe]
Asir : MEP state machine doesn't define states fully, but the binding version does.
[Noah]
+1, self descriptive
[Yves]
+1
[Noah]
zakim would be clueless about such matters
[scribe]
[general feeling that states were self-descriptive enough at present]
[scribe]
df: Any objection to the change above? (i.e. "unconditional" -> "transmission of request message initiated")
[scribe]
NO OBJECTIONS
[scribe]
[discussion of faults while streaming]
[scribe]
Marc leaps in to summarize : text is good as it stands. You can just stop sending if you run into problems without having to generate faults.
[scribe]
If receiving, you can just stop but can't generate a fault (soap processing never started)
[scribe]
df: there is no sentiment for closing the issue with any action other than replacing "unconditional" as above.
-- ISSUE 338 CLOSED
[scribe]
-- 302, data model edges orignating and not terminating
[scribe]
[summary : "Encyclopedia Brown and the Text That Wasn't There"]
[scribe]
df: Are there any objections to closing this issue with the text currently in the editor's copy?
[scribe]
NO OBJECTIONS
[scribe]
ISSUE 302 CLOSED
[scribe]
-- 231, what is the difference between a struct and an array in the edge case?
[scribe]
http://lists.w3.org/Archives/Public/xml-dist-app/2002Sep/0192.html
[scribe]
[scribe gets booted off IRC, reconnects]
[scribe]
Ray : this is non-normative, and might seem to contradict the normative stuff. Should we clarify?
[scribe]
Gudge agrees there is some confusion.
[scribe]
Noah : problem is dissonance between "defaulting" values and the fact that normatively we don't describe/allow defaulting...
[scribe]
Noah : isn't this sort of the same as with xsi:type?
[scribe]
[Discussion of schema rules vs. SOAP rules, and how information gets discovered from each]
[scribe]
df: let's push this towards conclusion via email. Please propose text changes if you have issues with Noah's text
[scribe]
df: Will revisit next week
[scribe]
df: we will go ahead and choose the attribute's name
[scribe]
POLL: Everyone gets one vote (per aganda).
[scribe]
class : 1
[scribe]
content : 0
[scribe]
content : 1
[scribe]
form : 2
[scribe]
format : 0
[scribe]
kind : 0
[scribe]
node : 0
[scribe]
nodeType : 7
[scribe]
type : 0
[scribe]
valueFormat : 0
[scribe]
valueType : 0
[asir]
it is nodeType
[scribe]
df: "nodeType" will be the name of the attribute
[scribe]
-- 356, Allow unqualified elements as children of Body
[scribe]
http://lists.w3.org/Archives/Public/xml-dist-app/2002Sep/0128.html
-- df: any objection to closing issue 356 by saying child elems SHOULD be namespace qualified, and using Noah's text as modified by Gudge's proposal
[scribe]
NO OBECTIONS
[scribe]
ISSUE 356 CLOSED
[scribe]
-- 358, length of URIs
[scribe]
Proposal to close as dup of 356
[scribe]
df: any objections to closing 358 as a duplicate of 336?
[scribe]
NO OBJECTIONS
[scribe]
ISSUE 358 CLOSED
[scribe]
-- 370, no definition of SOAP Processor
[scribe]
Proposal to close this issue by replacing all instances of "SOAP processor"
[scribe]
with "SOAP node"
[scribe]
df: are there any objections to closing 370 with this proposal?
[scribe]
NO OBJECTIONS : ISSUE 370 CLOSED
[scribe]
-- 300, How is version transition handled in the HTTP binding?
[scribe]
Marc: SOAP 1.2 HTTP binding has to be tweaked if it's to accept SOAP 1.1
[Noah]
Yes, I agree with what Glen's saying.
[marc]
our binding wouldn't recognise it as a SOAP message
[scribe]
MarkJ : The upgrade stuff talks about behavior of a SOAP 1.2 node when it receives a SOAP 1.1 message.
-- further discussion, proposal to be sent in email
[scribe]
-- 301, Missing universal transport binding
[scribe]
df: are there any objections to closing this issue by saying it is out of scope?
[scribe]
NO OBJECTIONS. ISSUE 301 CLOSED
[scribe]
-- 326, NS qualify all attributes
[scribe]
PROPOSAL : make id and ref part of the SOAP-ENC namespace
[scribe]
df: are there any objections to namespace qualifying these attributes?
[scribe]
NO OBJECTIONS. ISSUE 326 CLOSED.
[scribe]
-- 360, modularize Part 2
[scribe]
Split part 2 into multiple specs?
[scribe]
PROPOSAL : Close since it has been dealt with before
[scribe]
df: are there any objections to closing this issue as a duplicate of 198?
[scribe]
NO OBJECTIONS. ISSUE 360 CLOSED
:37 [scribe]
MEETING ADJOURNED
:44 [RRSAgent]
I see 14 open action items:
:44 [RRSAgent]
ACTION: Editors to resolve and close issue 250 and respond to reagle@w3.org [2]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T18-19-58
:44 [RRSAgent]
ACTION: Issues list maintainer to creat a new issue for http://lists.w3.org/Archives/Public/xmlp-comments/2002Sep/0081.html [3]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T18-44-28
:44 [RRSAgent]
ACTION: Gudge to evaluate http://lists.w3.org/Archives/Public/xmlp-comments/2002Oct/0002.html and inform WG whether a new issue should be generated [4]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T18-45-41
:44 [RRSAgent]
ACTION: Gudge to send resolution text for Issue 302 to xmlp-comments and commentator [5]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-10-54
:44 [RRSAgent]
ACTION: Noah to send resolution text for Issue 353 to xmlp-comments and commentator [6]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-11-09
:44 [RRSAgent]
ACTION: Group to take 231 proposal to e-mail. Gudge and Ray to propose modifications to Noah's text [7]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-30-52
:44 [RRSAgent]
ACTION: Henrik to send closing text for issue 356 to xmlp-comments and commentator [8]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-38-22
:44 [RRSAgent]
ACTION: Don Mullen to send closing text for issue 358 to xmlp-comments and commentator [9]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-40-32
:44 [RRSAgent]
ACTION: Don Mullen to send closing text for issue 370 to xmlp-comments and commentator [10]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-40-53
:44 [RRSAgent]
ACTION: GlenD to make a proposal for clarifying Part 1 appendix A ( regarding Issue 300 ) [11]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-55-35
:44 [RRSAgent]
ACTION: Colleen Evans to send closing text for Issue 301 to xmlp-comments and commentator [12]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T19-57-50
:44 [RRSAgent]
ACTION: Gudge to send closing text for issue 326 to xmlp-comments and commentator [13]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T20-00-17
:44 [RRSAgent]
ACTION: Collen to send closing text for issue 360 to xmlp-comments and commentator [14]
:44 [RRSAgent]
recorded in http://www.w3.org/2002/10/02-xmlprotocol-irc#T20-02-10