wsdm message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [wsdm] MOWS Metric Issues
- From: David E Cox <decox@us.ibm.com>
- To: wsdm@lists.oasis-open.org
- Date: Wed, 26 Oct 2005 10:16:37 -0400
Hi Kirk,
My discussion about Web services
operations as resources was intended to drive the discussion beyond metrics,
and into other areas of manageability, such as status, relationships, message
processing state, and notifications. I did not intend to formally
propose that we model operations as resources. I do think it is more
than just OperationalStatus as mentioned in #2-b.
Regards,
David E Cox
"Wilson, Kirk D"
<Kirk.Wilson@ca.com>
10/26/2005 10:02 AM
|
To
| <wsdm@lists.oasis-open.org>
|
cc
|
|
Subject
| [wsdm] MOWS Metric Issues |
|
All,
The following summarizes issues that have
arisen regarding MOWS Metrics. Heather, you may wish to discuss these
further on the Thurs conf. call or at the F2F.
1. Proposal
by Kirk Wilson to include Max/Last Request/ResponseSize metrics. [1]
a. Should
these properties be included in both service level and operation level
metric capabilities? [2]
2. Extensions
to other capabilities:
a. Proposal
by KW to include the operation-level attributes introduced by Fred in the
OperationMetrics capability proposal, operationName & portType, in
the Request Processing state elements [3]
b. Proposal
by Dave Cox/Tony Gullotta to extend OperationalStatus to operations (as
well as State, perhaps) [4] [5]
3. Proposal
by DC to treat operations as manageable resources in their own right [4]
a. This
proposal has been opposed by Bryan Murray and Dave Snelling. [6] [7]
b. This
editor’s opinion: The extensions in #2 do not require making operations
manageable resources. There would be additional model issues to handle
the relationship between a web service and its associated operations that
only serve to complicate the representation of a web service.
4. Proposal
by KW to replace the word “Operation” with “Request” in the operation-level
capabilities, e.g., RequestMetric capability, RequestNumberofRequests (hmm,
perhaps not too good), RequestOperationalStatus (but more preferable than
OperationOperationalStatus). This would keep the vocabulary consistent
with “RequestProcessingState”. [3]
[1] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00061.html
[2] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00062.html
[3] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00064.html
[4] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00065.html
[5] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00069.html
[6] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00066.html
[7] http://www.oasis-open.org/apps/org/workgroup/wsdm/email/archives/200510/msg00071.html
Kirk Wilson
Computer Associates
Architect, Development
Office of the CTO
Tele: + 1 802 765-4337
Fax: + 1 802 765-4339
<mailto:kirk.wilson@ca.com>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]