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

RE: proposed AC018 rewording

From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
Date: Thu, 20 Jun 2002 14:32:34 -0500
Message-ID: <40AC2C8FB855D411AE0200D0B7458B2B07C59742@scidalmsg01.csg.stercomm.com>
To: "'Sedukhin, Igor'" <Igor.Sedukhin@ca.com>, "ECKERT,ZULAH (HP-Cupertino,ex1)" <zulah_eckert@hp.com>, "'kreger@us.ibm.com'" <kreger@us.ibm.com>, Hao.He@thomson.ocm.au, adiber@att.com, wsgeek2002@yahoo.com
Cc: "WSA W3C Public (E-mail)" <www-ws-arch@w3c.org>
Igor,
 
My understanding is that AC018 is not limited to Reliability management.
 
Thanks,

-Suresh 
Sterling Commerce   

-----Original Message-----
From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com]
Sent: Thursday, June 20, 2002 12:48 PM
To: ECKERT,ZULAH (HP-Cupertino,ex1); Damodaran, Suresh; 'kreger@us.ibm.com';
Hao.He@thomson.ocm.au; adiber@att.com; wsgeek2002@yahoo.com
Cc: WSA W3C Public (E-mail)
Subject: RE: proposed AC018 rewording


Very nice, Zulah&Heather!
 
Although I'm coming with the same question as I did before: does the group
think that all the important things listed under AC018 serve only the
Reliability and that is what they are for?
 
For example, management events in AR18.1.3, do they somehow improve or
affect the Reliability or may be Security, or possibly price? Is everyone
happy with only Reliability being the target for the management events, in
this example?

-- Igor Sedukhin .. (Igor.Sedukhin@ca.com) 
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 

-----Original Message-----
From: ECKERT,ZULAH (HP-Cupertino,ex1) [mailto:zulah_eckert@hp.com] 
Sent: Wednesday, June 19, 2002 3:10 PM
To: 'Damodaran, Suresh'; 'kreger@us.ibm.com'; Hao.He@thomson.ocm.au;
adiber@att.com; ECKERT,ZULAH (HP-Cupertino,ex1); wsgeek2002@yahoo.com
Cc: WSA W3C Public (E-mail)
Subject: proposed AC018 rewording


 
Hi All,
 
 Here is a proposed rewording of AC018 from Heather and Zulah.
 
Comments?
Zulah
 
----------------------------------------------------------------------
AC018 Enables the management of web services 

AC018.1 Ensures that implementations of the Web Services Architecture are
manageable.
AR018.1.1 Define a base set of standard metrics for architectural components
and their interactions accompanied by guidelines for measurement.
AR018.1.2 Define a base set of standard management operations for Web
Services Architecture implementations. Management operations includes, but
is not limited to, support for configuration control and lifecycle control.
AR018.1.3 Define a base set of management events to be issued by the Web
Services Architecture implementation. 
AR018.1.4 Define a standard methodology for accessing management
capabilities from the Web Services Architecture implementation. 

AC018.2 Ensures that implementations of the Web Service instances are
manageable.
AR018.2.1 Define how a web service should expose web service specific
metrics, configuration, operations, and events.
AR018.2.2 Support the discovery of web service management capabilities.
AR018.2.3 Define a standard methodology for accessing management
capabilities of a Web Service through the Web Services Architecture
implementation.

AC018.3 Ensure that at least the following types of management applications
are supported: Performance Monitoring, Availability, Configuration, Control,
and Service Level Agreements. 


 
Received on Thursday, 20 June 2002 15:34:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:00 GMT