- From: Liu, Kevin <kevin.liu@sap.com>
- Date: Thu, 11 Mar 2004 23:30:50 +0100
- To: "'Umit Yalcinalp'" <umit.yalcinalp@oracle.com>
- Cc: Sanjiva Weerawarana <sanjiva@watson.ibm.com>, www-ws-desc@w3.org
- Message-ID: <99CA63DD941EDC4EBA897048D9B0061DA95ECC@uspalx20a.pal.sap.corp>
Hi Umit, it seems more complicated than it may appear. for example, if one defines a service feature, what does it mean? does it apply to all corresponding binding operations and interface operations? what're the rules of resolving potential conflicts if some conflicting features are defined for one binding or interface operation. etc. Anyway, I DO believe F&P is an important issue and deserve careful design, but I don't think it belongs to WSDL. BTW, I am not sure if Sanjiva was proposing anything in his message, in my reading, he was trying to clarifying a point. Best Regards, Kevin -----Original Message----- From: Umit Yalcinalp [mailto:umit.yalcinalp@oracle.com] Sent: Thursday, Mar 11, 2004 01:41 PM To: Liu, Kevin Cc: Sanjiva Weerawarana; www-ws-desc@w3.org Subject: Re: features & properties: anywhere or only selected places?? Liu, Kevin wrote: I don't recall the group has ever agreed that F&P can appear under <service>. What's the use case for that? I am making a proposal and agreeing with Sanjiva that we should not be restrictive. Typically, we are not restrictive in our specs especially for things that are extensions to the model. It's only a few days to our last call, how many of us in the group are confident that he/she fully understand how the WSDL F&P things work. Am I the only one worrying? Since Feature and property are such an important area, I am very concerned that we are making WSDL unnecessarily complicated while only provide a partial solution. That is the whole point, in order not to provide a partial solution, we should not put restrictions and extend it to the service element. The use case is very simple. Instead of applying a particular feature to a specific binding, it may apply to all endpoints in a service. If I were to publish an OperationName feature, it could easily belong to a service element as to indicate that it applies to all the endpoints. </snip> Best Regards, Kevin --umit -----Original Message----- From: www-ws-desc-request@w3.org <mailto:www-ws-desc-request@w3.org> [mailto:www-ws-desc-request@w3.org <mailto:www-ws-desc-request@w3.org> ] On Behalf Of Umit Yalcinalp Sent: Wednesday, Mar 10, 2004 11:52 AM To: Sanjiva Weerawarana Cc: www-ws-desc@w3.org <mailto:www-ws-desc@w3.org> Subject: Re: features & properties: anywhere or only selected places?? Sanjiva Weerawarana wrote: Hi Guys, I was always under the impression that <feature> and <property> elements are allowed under any element .. however, the spec says otherwise. Did I just get confused? Sanjiva. I guess you mean any component? We definitely need F&P under the service element (more precisely ServiceType ;-)) in addition to interface/operation/binding/binding operation components. --umit -- Umit Yalcinalp Consulting Member of Technical Staff ORACLE Phone: +1 650 607 6154 Email: umit.yalcinalp@oracle.com <mailto:umit.yalcinalp@oracle.com>
Received on Thursday, 11 March 2004 17:31:27 UTC