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

RE: [RTF]Proposal for AC019

From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
Date: Fri, 21 Jun 2002 16:56:19 -0500
Message-ID: <40AC2C8FB855D411AE0200D0B7458B2B07C59764@scidalmsg01.csg.stercomm.com>
To: "'Hao He'" <Hao.He@thomson.com.au>, "''ECKERT,ZULAH (HP-Cupertino,ex1) ' '" <zulah_eckert@hp.com>, "'''kreger@us.ibm.com' ' '" <kreger@us.ibm.com>, "''Hao.He@thomson.ocm.au ' '" <Hao.He@thomson.ocm.au>, "''adiber@att.com ' '" <adiber@att.com>, "''chrisfer@us.ibm.com' '" <chrisfer@us.ibm.com>
Cc: "'Wsa-public (E-mail) '" <www-ws-arch@w3.org>

Hi Hao,

Thanks for your comments. Just to add some clarity,
19.1.x is fashioned along the lines of HTTP Client error codes
These are available only with HTTP, but the idea is that WSA will make it
at the SOAP level and/or below for all transport (er, OSI layer 7,
application) protocols.
In particular SMTP.


Sterling Commerce   

-----Original Message-----
From: Hao He [mailto:Hao.He@thomson.com.au]
Sent: Friday, June 21, 2002 4:41 PM
To: Damodaran, Suresh; ''ECKERT,ZULAH (HP-Cupertino,ex1) ' ';
'''kreger@us.ibm.com' ' '; ''Hao.He@thomson.ocm.au ' '; ''adiber@att.com
' '; ''chrisfer@us.ibm.com' '
Cc: 'Wsa-public (E-mail) '
Subject: RE: [RTF]Proposal for AC019

hi, Suresh,

Looks good. Some comments added.


-----Original Message-----
From: Damodaran, Suresh
To: 'ECKERT,ZULAH (HP-Cupertino,ex1) '; ''kreger@us.ibm.com' ';
'Hao.He@thomson.ocm.au '; 'adiber@att.com '; 'chrisfer@us.ibm.com'
Cc: Wsa-public (E-mail)
Sent: 6/22/02 7:03 AM
Subject: [RTF]Proposal for AC019

Hi all,

Below is the new text (including two of the accepted AC019.1 & 19.2  in
ballot [1]) for AC019 [2].
Earlier discussions on the topic are in [3]. There are some follow-up
discussions to [3], if you really like
to dig deeper.
I have put in as much as I can think of, and comments, so please excuse
for its bulkiness.


Sterling Commerce
[1] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002May/0127.html 
[2] http://www.w3.org/TR/2002/WD-wsa-reqs-20020429
 [3] http://lists.w3.org/Archives/Public/www-ws-arch/2002Apr/0019.html


	The Web Service Architecture enables conforming Web Services to
reliable, stable, and evolvable over time.
AR019.1 Web Services conforming to Web Service Architecture can be
discovered, accessed, and executed.
[<sd> This was accepted text from the ballot. A potential change
the semantics is s/can/MAY </sd>]
D-AR019.1.1 If a Web Service is relocated, Web Service Architecture will
enable detection of the relocated Web Service.

Since each WS is identified by a URI, is it resonable to ask a WS to keep
URI persistent? If a WS has to change its URI, it should make its old URI
So, how about adding :
"A Web Service should keep its URI persistent."  to D-AR019.1.1 

D-AR019.1.2 If a Web Service is not available, Web Service Architecture
enable that information to be conveyed.
[<sd> so the service requester does not hang or get time-out exception
Is this really necessary and doable?

AR019.2 The Web Service Architecture enables a conforming Web Service
implementation to be stable with respect to its definition.
[<sd> accepted in the ballot </sd>
	D-AR019.2.1 A Web Service can be defined independent of its
	[<sd> I don't think this is explicitly stated elsewhere. So here

<hh>This is a good one.</hh>

D-AR019.2.2 The functional behavior of two or more web service
the same version (see AR019.3.1) of a web service definition is
	[<sd> the reverse may be true also - two implementations may
the same behavior but different definitions, but is not worth mentioning

D-AR019.3 The Web Service Architecture enables a conforming Web Service
definition to be evolvable.
	D-AR019.3.1 A Web Service definition includes its version.
	D-AR019.3.2 A Web Service definition is governed by a well
versioning scheme (policy)  that enables an earlier version of the Web
Service definition to be identified, and a corresponding implementation
discovered, accessed and executed. 
	[<sd> The versioning info created per versioning scheme will
the Service Requester information on another implemented version that
can be
executed if necessary </sd>]
D-AR019.3.3 The information on the existence of implementations of other
versions may be available. The changes in a new Web Service from an
version of Web Service may be documented .
	D-AR019.3.4 If a Web Service Definition evolves into another,
information regarding this evolution may be available.
Received on Friday, 21 June 2002 17:56:45 UTC

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