- From: Ramkumar Menon <ramkumar.menon@gmail.com>
- Date: Tue, 23 May 2006 11:36:15 -0700
- To: www-ws-desc@w3.org
Three fundamental questions. Would it be useful to add a clause for the <service> component stating The "interface" attribute information item should point to an interface that has non zero number of "operation" element information items within it. If not, we cd as well have service components that could possible be empty, and allow them to extend other service components, reflecting the same semantics we have defined for interface inheritance - considering that one service component is related to exactly one interface. Am I right if I state that if all "binding" attribute info items that had been defined on the endpoint node should have been associated with an "interface" attribute information item? What does it mean to be otherwise ? Moreover, if the service component has an interface attribute info item that extends from two other interfaces, can the endpoint defined within it refer to bindings that were defined for the parent interfaces ? If yes/no, should this be reflected in the core language spec ? rgds, Ram -- Shift to the left, shift to the right! Pop up, push down, byte, byte, byte! -Ramkumar Menon A typical Macroprocessor
Received on Tuesday, 23 May 2006 18:36:24 UTC