Yet another attempt to fix D-AC004

Issue: AC004 has been trimmed down to say:

  "does not preclude any programming model"

yet the contained CSFs and requirements are not relevant to this concept. 
They are relevant to the concept of the architecture being comprised of
loosely-coupled components primarily articulated in D-AC004.3.

So I propose the new top level CSF:

X 'is comprised of loosely-coupled components and their interrelationships' 

with the following subordinate requirements (from synthesizing D-AC004.2, 
D-AC004.3 and AR004.2):

AR00X.1 components are [minimally] defined in terms of unambiguous, well-
        defined interfaces.
AR00X.2 component interfaces define their inputs and outputs and also the 
        form and constraints on those inputs and outputs.
AR00X.3 component relationships are described in terms of messages and 
        message transmission protocols.
AR00X.4 messages are transmitted and consumed by the component interfaces 
        that make up the architecture.
AR00X.5 use XML based techniques for defining messages/protocols for 
        invoking web resources. (was D-AR004.3)


As for AC004 ("does not preclude any programming model"), I believe we 
should reuse the XMLP verbiage:

'The specification will make reasonable efforts to support (but not define)
a broad range of programming models suitable for the applications intended
for XP.'

and say

AR004.1 Support (but not define) a broad range of programming models suitable 
for Web Services applications.

See [1] for my earlier explaination of how XMLP satisfied this requirement.

BR, Mike 

[1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Jun/0031.html

Received on Tuesday, 25 June 2002 13:21:00 UTC