uddi-spec message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [uddi-spec] UDDI QoS Metrics TN Telecon - 9 March 2004, 12:00 pacific
- From: "Adam Blum" <adam.blum@systinet.com>
- To: <uddi-spec@lists.oasis-open.org>
- Date: Tue, 9 Mar 2004 14:20:53 -0800
Thanks to everyone who attended. The
following is an attempt by me to summarize the meeting quickly. I
was too much involved to take word for word notes however (next time I will try
to enlist a minutes taker. :-)
- Adam
Meeting
Summary
Date: March 9, 2004
Attendees:
Fred Carter,
Amberpoint
Tony Rogers, CA
Maud Cahuzac, France Telecom
Shishir Garg, France Telecom
John Colgrave,
IBM
Andrew Hately, IBM
Luc Clement, Individual
Adam Blum, Systinet
Purpose:
This was a section by section walkthrough of the UDDI
QoS Metrics Tech Note
Walkthrough:
Section 1.3.1 Developers and Users
Enhanced to discuss:
- who uses aggregate information in what
ways
- who uses raw data (counts) in what
ways
- who uses the externally access web service
information
- what are the range-based queries if any? (wouldn't be
supported now, but use case should be presented)
- what information is rating based?
- what do the queries look like? Single, few or
many attributes?
- are we tackling usage and query of QoS metric
information for external B2B or extranet registry scenarios? (assuming no,
needs to state)
Section 1.3.2 Administrators and Service
Publishers
Enhance to discuss service publisher scenario
explicitly.
Section 1.3.3 Web Service Management
Software
Needs to be a description of the WSM software use of
the registry, not a discussion of what web services management software is.
Describe just what information is populated by Web Services Management software
vendor and how often. What information if any, from the registry is used by the
WSM software. (actually this is postmeeting analysis and opinion while reviewing
the document).
Section 2.1 tModel to External Web
Service
Agreement that this is not the
goal.
Section 2.2 Place Categories for QoS Attributes on
Binding Template
Tony thinks is "pretty" and we agree. But it won't
support V2
Section 2.3 Extend the UDDI Data
Structure
Violates V2 assumption. Tony said might be okay given
timing. Luc and Adam said goal is shorter term release. Andrew said that
if QoS considered to be extremely important might be worth
doing. Adam said we would lose ability to use the techniques as a
model for other types of information (this may or may not be
desired)
Section 2.4 tModels with QoS Information Categories
Referred from Bindings
This works with V2 and allows single queries. Luc
brought up problem with generation of many tModels, one per binding
template. He feels UDDI spec doesn't handle managing this volume of
tModel creation, and especially problems of deletion of tModels,
well
Section 2.5 Business Services Representing
Management Service with QoS Information Categories for Each Binding
Template
This section does not exist now (see Action Item below
for Luc to Create). Luc has proposal to create a business service for each
binding template an operational web service under management. Categories
for each QoS metric could then be placed on the "management business
service". Second order issues were raised such
as:
- is the business for these "management business
services" the same as the web service under management. Luc proposes no
that they would be under a separate, "management software" business.
Andrew thinks this will create complex queries for the user
- are there links from the "managed"
operational binding template over to the management web service?
Luc says he thinks that users can just make a find_service call given that they
know the binding template which they want to find the management service (and
hence the QoS information) for. Adam raised concerns about the difficulty
for users and web services-consuming developers of making a find call versus
following a link. Luc points out that this makes it easier for
publishers.
- There was agreement that both of these issues are
second order concerns.
- Andrew raised more general concerns about the
complexity and potential multi (or two) step access to the QoS information on a
web service for consuming users.
We agreed that we would collectively enhance the
usecases and Luc would document this proposal and then revisit the topic and the
TN in general shortly after the New Zealand meeting.
Action Items:
1)
Adam - update section 1.3 Developers and Users
2)
Adam - move content from section 3 to section 2.4 since there are perhaps
two recommended solutions now
3) Andrew - add to section
1.3
4) Luc - update and add to section 1.4 Administrators
and Service Publishers
5) Luc - add section 2.5 on Business Services
Representing Management Service with QoS Information Categories for Each Binding
Template
6) Adam to schedule meeting for shortly
after New Zealand (April 6)
Please
let me know if I have captured the content of the meeting and the action
items
Call meeting
request (see attached) for those
whose calendars can accept them.
Time:Tuesday, 9 March 2004,
12:00pm to 02:00pm Pacific Time
Description:
Telecon to be held Tue 9 March 2004 at 12:00 US Pacific
time, for 2 hrs.
Call hosted by Systinet
Call details:
- Toll-free:
888-502-0190
- Toll: 706-643-6177
-
Participant passcode:
868241
Other conference call times were as follows by
region: UTC: Tue-20:00, Seattle: Tue-12:00, New York: Tue-15:00, London:
Tue-20:00, Frankfurt: Tue-21:00, Moscow: Tue-23:00, Tokyo: Wed-05:00, Sydney:
Wed-07:00, Auckland: Wed-09:00
Agenda:
Agenda forthcoming.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]