WSLA and WSML contain
more sophisticated details about the QoS guarantees, price/penalty statements, and
partner information. Our specification itself does not provide much detail definition
for service partner??™s information. It depends on external ontology OWL-S to
describe the provider??™s details and use the object-oriented approach to define the
QoS profile and QoS metrics structure based on ontology level.
UDDIe allows choosing between Web services based on their QoS attributes, such
as bandwidth, CPU and memory requirements. This is a lightweight and highly
integrated matching framework for UDDI. However they do not support the reusable
constructor for the QoS constraints yet. The adding of new attributes definition
lacks a good solution for sharing between partners.
UX supports local and federated QoS-aware service discovery for UDDI. It uses the
requesters??™ QoS feedback as the selection criteria. A basic metrics set is predefined
for sharing between service requester??™s feedbacks. However, how to precisely define
0 Zhou, Ch a, and Lee
Copyright ?© 2007, Idea Group Inc.
Pages:
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440