See also: IRC log
Present: , Geoff Arnold Sun Microsystems, Inc., Abbie Barbir Nortel Networks Editor, David Booth W3C, Mike Brumbelow Apple, Doug Bunting Sun Microsystems, Inc., Martin Chapman Oracle Corporation, Ugo Corda SeeBeyond Technology Corporation, Colleen Evans Sonic Software, Shishir Garg France Telecom, Hugo Haas W3C, Hao He Thormpson Corporation, Mark Jones AT&T, Sandeep Kumar Cisco Systems Inc, Michael Mahan Nokia, Francis McCabe Fujitsu, David Orchard BEA Systems , Igor Sedukhin Computer Associates, Sinisa Zimek SAP
Regrets: Assaf Arkin, Mike Champion, Roger Cutler, Gerald Edgar, Zulah Eckert, Mario Jeckle, Katia Sycara,
Chair: Hugo Haas
Scribe: DOrchard
<hugo> ACTION: Chris to summarize
WS-Policy spec for the list -- -- PENDING
... ACTION: Daniel, and the usual suspects will work on defining
the relationship between messaging and description/choreog -- --
PENDING
... ACTION: Hugo to send pointer to task force mailing list to WSA
(WSD task force) -- -- PENDING
... ACTION: Editors will reconcile terminology used with WSDL -- --
PENDING
... ACTION: Hugo to increase number of lines for editors' call
... ACTION: Eric will close issue 21 -- -- PENDING
... ACTION: Geoff to report on asynch def next week (17)
... ACTION: Daniel to check Mark J's text following Scottsdale F2F
re MEP -- PENDING
<DaveO> No real discussion about MEP glossary
items
... Discussion about publication of ws arch doc, and whether to
publish.
... DaveO: concern about not having time at the f2f to work on doc,
perhaps significant edits on material to be reviewed.
... Eric: How about we make a go/no-go on May 1 for publication?
there's momentum around the editorial duties.
... Decision: Eric's proposal adopted.
... Eric: discussion about difference in diagrams. Sometimes you
want a map (get from here to there), sometimes you need a blueprint
(how stuff relates).
... Geoff: difference in diagrams.
... daveO: should have all diagrams, should have abstract model
(like reliability), and then have actual specs fit in
somewhere.
... eric: do simple stack first to get agreement on high level.
... daveo: wonderful words ... can't track all the discussion and
participate.
... daveo: argues for why stack diagram should have reliablility,
security, etc. shown as part of messaging to show areas of
interest. It's not complete, but it's relevent for a particular
audience.
<ericn> Right, and it's also important to think
about a diagram as it will appear in the document with associated
text
... Meaning that we can explain some things in the text that are
not self-evident in the document
... Sorry the diagram
<DaveO> geoff: thought we were supposed to come up
with an architecture document for doing w3c recommendations.
... frank: the uses diagrams are good, but it's not quite clear how
this relates to things like security.
... daveo: talk about updates to use case.
... Colleen: how are the use case document and best practices to be
used by this group?
... daveo: presents TAG discussion on new issue #37, WSDL abstract
components.
... Discussion about protocol independence.
... ericN: Iona does multi-protocol, as do others.
<hugo> ACTION: Geoff and Eric to
propose text about protocol independance by Thursday 24 April
... ADJOURNED