W3C home > Mailing lists > Public > www-ws-arch@w3.org > August 2002

Status of AG006 - "web friendly"

From: ECKERT,ZULAH (HP-Cupertino,ex1) <zulah_eckert@hp.com>
Date: Thu, 22 Aug 2002 19:52:51 -0400
Message-ID: <580F4ACFCD8F4E439B06B815110418C78880B2@xcup03.cup.hp.com>
To: "WSA W3C Public (E-mail)" <www-ws-arch@w3c.org>
Cc: "ECKERT,ZULAH (HP-Cupertino,ex1)" <zulah_eckert@hp.com>

Recall that AG006 includes AC007, AC008, AC012, AC013, and AC015. [1] is the
original proposal what was considered in the 7/18/02 WSAWG meeting [2]. The
bulk of these AC's and sub ACs need no further discussion. With the
following issues:

* The following is incorrect needs to be corrected in the document. The
approved AC is:

AC008.6 The definition and use of the components is consistent within
the Web Service Architecture.

* The following were removed from the document but were approved by vote:

AC015.2 and AC015.4. These ACs have the same issues as we had with the other
AC015 sub ACs that the WSAWG agreed to remove. (IMO) The editors have done
the right thing and these should be removed. 

I feel uncomfortable with a high level AC that we cannot decompose into
parts. This AC really addresses how the WSAWG will organize itself to
provide time-to-market for the WSA. My rcommendation is that either we
remove it or we add some CSFs and requirements that address the AC. Here is
a proposal of some possible critical success factors that address WSAWG
organization and that are critical success factors (that is, if we are not
successful with these, its fairly safe to say that we aren't being

- the WSAWG must work in parallel 
	(1)internally so that usage, requirements, and architecture do not
gate one another but instead are iteratively developed
	(2)within the W3C WS activity 
		- to reduce the time to kick off WGs and hence specification
		- (recognizing that company supplied expertise is an
important resource) to allow those resources to be applied in focused
		- to iterate over the charter and architecture of each WG to
arrive at a consistent architecture
	(3)with the rest of web service related the standards community
(recognizing that not all work to realize the WSA will be done by the W3C)
		- to focus external standards efforts that can become a part
of the WSA
		- to establish and create liaison's to gather requirements
and usage, and to provide feedback on WSAWG drafts 

- The WSAWG must prioritize its effort based on market needs
-  (recognizing that we should have an up-to-date view of what could become
a WSA contribution) maintain up-to-date information about external standards
efforts and possible contributions that relate to the architecture. And
disseminate WSA status information back to these groups. 

- understand and communicate in a timely fashion the relationship of WS
related contributions that could contribute to the WSA.

These seem to me to be things that we can do that would lead to success with
AC015. We also have some chance of measuring whether or not we re fulfilling
these roles.  


[1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Jul/0205.html
[2] http://www.w3.org/2002/ws/arch/2/07/18-minutes
Received on Thursday, 22 August 2002 19:52:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:58 UTC