RE: Summary: D-AG0011

I suggest removing the words "to the greatest extent possible".  All goals
are to the greatest extent possible.

I'd like to remove the word "existing".

Generally "web" is capitalized.

I'm dubious about the success factors.  They seem to be an attempt to
summarize the principles of the web architecture from an "ilities" and a
technical spec perspective.  These things are up to the TAG to
document/define.  I would suggest that the critical success factors should
be more along the lines of:

CF1: The Web Services reference architecture complies with the architectural
principals and design goals of the Web:
CF1-A: as defined by the work products that the TAG produces that define the
web architecture.

This allows us to use documents, findings, review notes, etc. from the TAG.
It also allows us to ask the TAG what it thinks of our compliance, then they
can issue documents/findings that detail our compliance.  I believe that a
critical success factor will be whether or not the TAG deems that web
services fit in the web architecture.

If you want to make a more explict CF along the lines of
CF1-B: and as a result of solicited review by the TAG.

I'm ok with that too.

Cheers,
Dave



> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of michael.mahan@nokia.com
> Sent: Friday, March 29, 2002 1:26 PM
> To: www-ws-arch@w3.org
> Subject: Summary: D-AG0011
>
>
> This is the summary of the 'Consistency' goal. Still, very little
> traction... So most of the below is my fault.
>
>
> Original Goal:
>
> "To develop a standard reference architecture for web services
> that is consistent with the existing web and its heterogenous
> environment and distributed architecture to the greatest extent
> possible."
>
> Proposed Goal:
>
> "To develop a standard reference architecture for web services
> that is consistent with the existing web to the greatest extent
> possible."
>
> Proposed Critical Success Factors:
>
> CF1) The Web Services reference architecture complies with the
> architectural principals and design goals of the existing web.
> Derived sub-goals:
>
> CF1-A) universal identifiers
> CF1-B) simplicity
> CF1-C) opaqueness
> CF1-D) decentralization
> CF1-E) statelessness
> CF1-F) scalability of component interactions
> CF1-G) generality of interfaces
> CF1-H) immediate deployment of components
> CF1-I) intermediary components to reduce interaction latency
> CF1-J) enforces security
> CF1-K) encapsulate legacy systems
> CF1-L) caching semantics (?)
> CF1-M) platform independence
>
> CF2) The Web Services reference architecture recommends the use
> of existing web technologies which adhere to the above principals
> and which provide clear functional coverage of the responsibilities
> and constraints for a component identified in the reference
> architecure. Derived sub-goals:
>
> CF2-A) Use of a standard identifier technology (URI)
> CF2-B) Use of a standard transport technology (HTTP/S over TCP/UPD/IP)
> CF3-C) Use of a standard data encoding technology (XML)
>
>
> Note that this is a first cut at CSFs. There is assuredly overlap
> with other goals here. By its nature, this goal is more of a
> meta-goal...
>
> Regards,
> Mike Mahan - Nokia
>
>
>
>

Received on Saturday, 30 March 2002 20:00:55 UTC