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

[RTF] Meeting Notes June 25, 2002

From: Damodaran, Suresh <Suresh_Damodaran@stercomm.com>
Date: Tue, 25 Jun 2002 19:39:44 -0500
Message-ID: <40AC2C8FB855D411AE0200D0B7458B2B07C5979E@scidalmsg01.csg.stercomm.com>
To: "Wsa-public (E-mail)" <www-ws-arch@w3.org>



RTF Meeting Notes Summary
June 25, 3-4PM  US Central Time

Present:

Ayse Dilber
Zulah Eckert
Hao He
Heather Kreger
Suresh Damodaran

Note Takers: Suresh Damodaran & Zulah Eckert (Thanks!)
--------------------------------------------
Summary:

We worked on AC018 proposed by Heather and Zulah [1], and comments [2].
Accomplished:
	- clarification of differences between 18.1, 18.2 & 18.3
	- tentative wording for 18.1
	- tentative wording for 18.1.1
	- need to define a few phrases in the glossary

------------------------------------------------------------
Actions:
	1. "implementation of the Web Service Architecture" to be defined in
glossary.
	Propose wording to the list - Zulah 
	2. "management of Web services" to be defined in glossary.
	Propose wording to the list  - Heather
	3. "metric of Architectural component" to be defined in glossary.
	Propose wording to the list  - Suresh
	4. Kickoff a discussion on "Management Conceptual Model" - Hao

------------------------------------------------------------

Agreed upon text so far:

AC018 Enables the management of web services 

AC018.1 Enables that the implementations of the Web Services Architecture
are manageable in a uniform 
and interoperable way.
AR018.1.1 Define a base set of standard metrics for architectural
components and their interactions accompanied by guidelines for measurement.

Discussions:

	18.1 deals with the manageability of infrastructure that will be an
implementation of WSA,
whereas 18.2 deals specifically with manageability of WS, and 
	18.3 deals with management applications that run on the
implementations of WSA.

Terms that are not immediately understood are to be explained in glossary.

Management consists of metrics, operations, events, and configurations of
these.
Management applies to every component of WSA. The focus is on
"instrumentation" of the components
to collect the management metrics.
The goal is to provide "hooks" for management of component, and not
specifying all the elements
of management. E.g., Hooks to use SLAs are provided, but the contents of SLA
is not specified.
of WSA.  
Examples of metrics are throughput, #accesses, #time-outs, #access errors,
etc.
The available metrics may be discovered by accessing the configurations.
The metrics may be different from component to component, but there is a
base set.

Hot discussion on whether we need a management "conceptual" model.
Hao believes the need, though others expressed concerns because of the lack
of a model in the architecture, and thus the inability to "require" it at
this stage.
There is agreement that a model will be good, but skepticism is on whether
we can
specify it as a "requirement." We will decide next week based on reaction of
members
on Hao's email, and our own analysis.

Thanks,

-Suresh
Sterling Commerce   


[1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Jun/0116.html
[2] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002Jun/0094.html
Received on Tuesday, 25 June 2002 20:40:02 GMT

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