W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2002

Comments on Web Service Usage Scenarios 23 April 2002

From: <ryman@ca.ibm.com>
Date: Thu, 2 May 2002 14:03:12 -0400
To: www-ws-desc@w3.org
Message-ID: <OF485B1DA8.CAA918B0-ON85256BAD.006144E0@torolab.ibm.com>
Here are my comments on

Status, paragraph 1. Typo: "requirements document" -> "usage scenarios

Introduction, VP2. tools may also generate server skeletons in the case
that you want to implement a Web service given its interface description, Don't these relate to VP1? How do they relate to VP2?

2.1.2 Typo: "Gauranteed" -> "Guaranteed" in two places (run a spelling
checker) Grammar: should be "they do want to receive" Grammar: should be "is an ebXML" Formatting: break the <attachment> elements across two lines so
they fit on a page,,, eliminate the code examples since they
don't clarify the scenarios. add more text to explain the scenarios the example to justify the requirement is not very compelling. is
there a better justification? are we talking about XA compliant transactions here? I personally
doubt this is the way to go for Web services (compensating operations are
more suitable). In any case simply saying an operational is transactional
is not precise enough. there are many forms of transactional behavior,
(look at the EJB spec), e.g. requires a transaction, must not be in a
transaction, starts a new transaction, etc. need to add detail on the semantics of version numbers. what do the
major and minor revisions mean? are minor revisions just small changes like
better documentation? do they guarantee that the operation signatures are

2.2.6 not a very compelling scenario. is there a better example to justify
this? Grammar: should be "I want the response") seems like a fairly exotic scenario. is there a better
justification? Typo: obtainign -> obtaining

Arthur Ryman
Received on Thursday, 2 May 2002 14:03:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:22 UTC