Reqs DR033/DR034

DR033: Support abstract interfaces
DR034: Support interfaces derived from abstract interfaces

----
Ideas behind these reqs.
Reqs DR033 and DR034 are related to the import functionnality in WSDL1.1 
(which could somehow be used as a derivation mean).
WSDL1.1 already supports abstract interfaces and derivation of 
interfaces, but a more precise model should be described.

I think that the import functionnality is not well explained (what if 
you redeclare the same portType in file A and file B, and file A is 
imported in file B for instance (is this example covered by the "Names 
within a name scope MUST be unique within the WSDL document" in WSDL1.1 
paragraph2.1.1?)). It might also become hard to maintain and understand 
WSDL files if all imports are possible.
It can be interesting to be able to qualify the level of abstraction of 
an interface, like saying "this interface contains only types, this 
interface specifies only types and messages....". An interface that 
declares itself as containing only types and messages should for 
instance not be able to import anything else than types and messages 
definition.
This could allow good programming rules to be enforced.

I think that we need to fix and/or clarify the use of the import 
functionnality. If we do so, we could take the opportunity to go a step 
further and add some OOP functionalities, like extending a portType (is 
it DR042?) by derivation (using or not the import functionnality) for 
instance. I do not think that it will cause a great overhead to do so.

I do not think that DR109 is sufficient to describe these ideas, we 
should maybe make DR033/DR034 more precise.

  Youenn

Received on Wednesday, 6 March 2002 07:59:48 UTC