XML Protocol Working Group telcon, Date: 20 Dec 2000
Active Data Exchange Eric Fedok alternate Akamai Technologies Mark Nottingham principal AT&T Mark Jones principal Bowstreet Alex Ceponkus alternate Calico Commerce Rekha Nagarajan principal Canon Herve Ruellan alternate Cisco Krishna Sankar principal Compaq Yin-Leng Husband principal DaimlerChrysler R. & Tech Mario Jeckle principal Data Research Associates Mark Needleman principal DataChannel Yan Xu principal DataChannel Brian Eisenberg alternate DevelopMentor Martin Gudgin principal Engenia Software Jeffrey Kay principal Hewlett Packard David Ezell principal Hewlett Packard Stuart Williams alternate IBM David Fallside chair IBM John Ibbotson principal Informix Software Soumitro Tagore alternate Jamcracker David Orchard principal Library of Congress Ray Denenberg principal Lotus Development Noah Mendelsohn principal Microsoft Corporation Henrik Nielsen principal Microsoft Corporation Paul Cotton alternate Mitre Marwan Sabbouh principal Mitre Paul Denning alternate Netscape Ray Whitmer alternate Oracle David Clay principal Oracle Jim Trezzo alternate Philips Research Amr Yassin alternate Rogue Wave Murali Janakiraman principal SAP AG Volker Wiechers principal Software AG Michael Champion principal Sun Microsystems Ed Mooney principal Tibco Frank DeRose principal W3C Yves Lafon team contact WebMethods Randy Waldrop principal Xerox Bill Anderson principal (SCRIBE) XMLSolutions Kevin Mitchell principal
Active Data Exchange Richard Martin principal Bowstreet James Tauber principal Canon Jean-Jacques Moreau principal Compaq Kevin Perkins alternate DaimlerChrysler R. & Tech Andreas Riegg alternate DevelopMentor Don Box alternate Engenia Software Michael Freeman alternate IBM Fransisco Cubera alternate Informix Software Charles Campbell principal Library of Congress Rich Greenfield alternate Netscape Vidur Apparao principal Philips Research Yasser alSafadi principal Rogue Wave Patrick Thompson alternate SAP AG Gerd Hoelzing alternate Software AG Dietmar Gaertner alternate Sun Microsystems Mark Baker alternate W3C Hugo Haas alt team contact Xerox Tom Breuel alternate XMLSolutions John Evdemon alternate
Intel Randy Hall principal IONA Technologies Oisin Hurley principal IONA Technologies Eric Newcomer alternate OMG Henry Lowe principal Progress Software David Cleary principal Progress Software Andrew Eisenberg alternate Unisys Lynne Thompson principal Unisys Nick Smilonich alternate
ABSENT WITHOUT EXPLANATION
Allaire Glen Daniels principal Allaire Simeon Simeonov alternate Commerce One David Burdett principal Commerce One Murray Maloney alternate Epicentric Bjoern Heckel principal Epicentric Dean Moses alternate Fujitsu Software Corporation Kazunori Iwasa principal Fujitsu Software Corporation Masahiko Narita alternate Group 8760 Dick Brooks ebXML contact NCR Vilhelm Rosenqvist principal NCR Lew Shannon alternate Vitria Technology Inc. Waqar Sadiq principal Vitria Technology Inc. Richard Koo alternate
The minutes to be approved consist of the unaudited minutes at  and , plus the attendance list attached to the end of this email. Approval of these minutes to become public (10 mins)
DF: merge the 2 sets of minutes
JeffKay: willing to do the merge - separate actual decisions from conversation
DF: propose to split decisions from transcript. Jeff to consult with Noah to insure consistent consolidation. Minutes need not be ready until Jan 2 EOB.
Publication status: congratulations, XML Protocol WG has published first working draft of req'ts.
some DRs remain; what is status?
David Ezell: preparing to put information out in the next few days, even though votes will probably happen after the new year. (DR305, DR309)
Use cases, section 8. still pending.
Status report from editorial team/section leads/glossary ed. some changing wording from "accept/generate" to "receive/send"
PCotton: process: how will we deal with commentary?
A long meta discussion followed regarding issues of ownership, editing, production of req'ts from use cases, use cases as illustrating boundaries of in- and out-of-scope req'ts, what exactly is the work product, including reference to req't R900.
One item of discussion resulted in a proposal to change our use of the term "use cases" to the term "usage scenarios."
PCotton: uniformity of representation is an editorial task that can be done outside of the actual content discussion.
DF: start discussion with some examples (meta conversation will be back again):
Starting with Dick Brooks use scenarios: http://lists.w3.org/Archives/Public/xml-dist-app/2000Nov/0271.html
Suggestion to work on use cases in the same way as req'ts; accept as drafts, and split use cases into individual scenarios.
John Ibbotson/Dick Brooks: will make draft proposals to the group (use draft scenario (DS) numbers)
1.1 ::= DS1:
separate DS1 into DS1 (single party) DS2 (muliple parties)
1.2 ::= DS3:
JohnI: separate this into 2 scenarios, 1 whose message is a business document, and one whose message is an RPC.
JohnI: action to send out the ebXML use scenarios as individual scenarios for discussion (promised by week's end).
Last meta comment: need descriptive phrases for each scenario, and it would be good to use phrases from the glossary.
Happy New Year!