Web Services Architecture WG F2F
27 Jan 2004

Attendees

Contents

• Topics
  1. global issue (Roger)
• Summary of Action Items

Scribe: http://www.w3.org/Guide/1998/08/teleconference-calendar#s_1254

<Roger> So do you know how to schedule one?
... Oops. We seem to have one already, but I'm told that Zakim has lost track somehow.

<hugo> Ralph is working on the problem

<mchampion> Katia scribes
... 1st agenda item: Global issues in documents

global issue (Roger)

Scribe: get rid of quotes

<hugo> ACTION: David to remove quotes in the documents

<Roger> zcv

<mchampion> ACTION: Editors will strive to remove apologies, e.g. "some may disagree, but ..."

mc: move d.o., rest to section 3

<hugo> ACTION: David to add a section at the beginning of the document to explain the relationship with other documents

db: should re address "constraints" differently?

Scribe: back from break

mc: wsa should have same status as soap 1.1

<Roger> This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time.

<mchampion> Publication of this Note by W3C indicates no endorsement by W3C or the W3C Team, or any W3C Members. W3C has had no editorial control over the preparation of this Note. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time.

<hugo> Publication as a Working Group Note does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time.
... from http://www.w3.org/TR/2004/NOTE-owl-parsing-20040121/
... dbooth, for the list of ids:
... cvs update ids.xsl
... xsltproc ids.xsl wd-wsa-arch-review2.xml

<hugo> ACTION: Frank to update models diagram
... ACTION 4= Frank to update model diagram

<hugo> ACTION: Mike to bring up the issue of location of address information

Scribe: tag says rddl is an acceptable namespace doc, but there may be others. likewise, for wsa, ws-addressing is an acceptable way to carry addresses in soap messages, but there may be others.
... It (MEP) descibes relationships (e.g., temporal, causal, sequential, etc.), if any, of multiple messages exchanged in conformance with the pattern, as well as the normal and abnormal termination of any message exchange conforming to the pattern.

frank: scale, atomicity of MEP ...

db: MEP TF in WSDWG ...

fm: one view mep is a choreography

roger: WSAWG against limiting it to atomicity, ... resolved?

hugo: glossary is newer re sync/async

mc: happiness is a warm delete key.

Scribe: In WSA 2.3.1.11.2, "originator" is not necessarily the "initial soap sender"

hugo: WSA "capability" == SOAP "Feature"?

frank: WSA "capability" !=? SOAP "feature"

Scribe: http://www.greatwallbedford.com/

<fgm> http://www.w3.org/TR/webarch/

Summary of Action Items