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

Comments on proposed requirements

From: Francis McCabe <fgm@fla.fujitsu.com>
Date: Tue, 30 Jul 2002 11:01:58 -0700
To: www-ws-arch@w3.org
Message-Id: <70ADC29D-A3E6-11D6-8D8F-000393A3327C@fla.fujitsu.com>

The following are based on a reading of the current version.

1. What is an architecture?

   This question is not directly addressed, and yet it seems to me to be 
vital in clarifying many of the issues we have faced.
   My suggestion (a drop-in for section 3.1.1):

   An architecture is a set of elements and a set of relationships 
between the elements that characterize the principal constraints and 
internal dependencies within the set of elements.

  If I had my druthers, I would continue:

  The first purpose of this work is to foster interoperability and 
reusability. To achieve this, it is necessary to identify the elements 
of the architecture that must be codified. Specifically, if two or more 
systems use different technologies to achieve some functional purpose, 
it is necessary to identify the common characteristics of the various 
approaches. This leads to the identification of architectural 
abstractions: abstract designs that can be formally related to every 
valid implementation.

(Some WSAWG members may recognize this quote ;-)

2. I have made proposals relating AG001, in summary they are:

   a. accept the wording of the goal itself.

   b. modify the text of D-AC001 to:

    provides a reference architecture that includes all the elements 
necessary to ensure interoperability between multiple implementations of 
web services and provides a demonstrable basis for identifying 
conformance and interoperability test suites

   c. DAC001.1 was actually accepted, D should be dropped

   d. DAC001.1.1 should be dropped as being too motherhood and apple-ish; 
and furthermore not reflecting political reality!

   e. DAC001.2 as it is subsumed by above proposal

   f. D-AC004 replaced with

    The WSA should ensure the proper separation of implementation from 
specification, allowing, for example, multiple implementations of 
equivalent specifications to interoperate.

   g. D-AC004.2 should be dropped in favor of revised D-AC004.3:

   h. D-AC004.3 should be replaced with:

    The web services architecture shall consist of a set of components 
and the relationships between them. Components are defined in terms of 
interfaces that define constraints on the behavior of the components.

  i. D-AC016 should be replaced with

   The WSAWG will identify those architectural and technology issues that 
might prevent interoperability, and to reference existing standards and 
technologies where available.

  k. D-AR016.4

Received on Tuesday, 30 July 2002 14:01:57 UTC

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