- From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
- Date: Tue, 23 Apr 2002 14:41:58 -0700
- To: "'Austin, Daniel'" <Austin.D@ic.grainger.com>, www-ws-arch@w3.org
Comment 1 - The folding of D-AC0017 (providing EDI-like function) into D-AG0005 (Scalability and Extensibility) is fine with me. One little quibble, or perhaps question ... Is it really appropriate to keep saying "must" in D-AC0017? I think that these success factors are important, but somehow "must" seems a bit over the top to me. I guess my personal feeling is that if, for some weird reason, one of these objectives turned out to be very difficult or incompatible with some other objective -- well, I would be surprised and disappointed, but I wouldn't then say that web services are useless. Would "should" be more appropriate? And finally, would it make sense to further fold D-AC0017 into D-AC0003? Comment 2 - The folding of D-AC0005 (simplicity, barriers to entry) into D-AG0005 (Scalability and Extensibility) seems a bit unnatural to me. It seems to me that simplicity is a goal on the same level as scalability and extensibility, and that it is not a part of either. In fact, if anything I would say that "extensibility" is a subset (or dimension) of "scalability". Perhaps the identification of simplicity as part of scalibility comes from the F2F, and there was some discussion there that made this make sense to people. Not having heard that discussion, however, it seems odd to me. Now, if you had folded simplicity into D-AG0003 (Web-friendly) it would have made a lot more sense to me. Isn't simplicity one of the grand traditions of the web? Or, if not that, D-AG0006 (Team Goals - meeting the needs of the web community)? -----Original Message----- From: Austin, Daniel [mailto:Austin.D@ic.grainger.com] Sent: Tuesday, April 23, 2002 3:29 PM To: www-ws-arch@w3.org Subject: Web Services Architecture Requirements 23 April 2002 Gentlebeings, I've uploaded the most recent version of the requirements document to: http://www.w3.org/2002/ws/arch/2/wd-wsawg-reqs-04232002.html This version incorporates many changes from our discussions both at the face to face meeting and on the telephone and in the mailing list. This version is intended for publication as a Working Draft upon approval of the W3C. Here is a (partial) list of the changes in this version: * removed user scanrios section * added top-level goals from f2f * relettered prior goals to CSFs * modified each CSF to reflect current wording and requirements * removed some sections * reworked document organization and structure * changed from editor's draft to working draft * updated status section * lots of other small changes. There are still some issues with this version: * numbering is irregular * list formatting is inconsistent * analysis matrices not yet added * document text needs coherence * does not yet pass publication validator at W3C Please send comments and feedback to the list! Thanks to Chris, Hugo, and of course Abbie and Sharad for all the hard work. Regards, D- *********************************************************************** Dr. Daniel Austin, Sr. Technical Architect austin.d@ic.grainger.com (847) 793 5044 Visit: http://www.grainger.com "Sapere Aude!"
Received on Tuesday, 23 April 2002 17:53:04 UTC