uddi-spec message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: TModel for QoS Information Containing Multiple Categories of QoS
- From: Luc Clément <luc@iclement.net>
- To: <uddi-spec@lists.oasis-open.org>
- Date: Sat, 24 Jan 2004 11:15:54 -0800
I don't know who this is
from.
>>We just have a little concern about the use of WSDL in UDDI and
probably you can help us to clarify our thoughts: Usually, a tModel
represents a reusable concept. In this solution, if the QoSInformation
tModel is categorized with the QoS metrics of a particular service, it is tight
to
this service and this is not what a tModel is meant to be. We
thing that a
tModel should be as generic as possible, representing a specific
concept/protocole/taxonomy (such as QoS information) but it should not include
any information that are bound to one service. What do you think? Are we wrong
or did we misunderstand the method?<<
You may be right and that we
should just put categories right onto the bindingTemplate.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]