"OO" features of WSDL 2.0

Hi,

 

There are some aspects of WSDL 2.0 that have an OO flavour, and I'm
wondering what the motivation, scope/limitations, and expected use of
these are. For example (related to inheritance, extension and service
instances):

 

Is it possible to model and expose arbitrary service inheritance
relationships? Other service relationships? Can these be applied to
abstract services, concrete services, or instances of services?

 

Does interface inheritance apply only across same service/implementation
of a service?

 

What mechanisms are used to model service instances? (in the stateful or
grid sense)

 

Can services have properties? Values? (run-time) State? (c.f. say OGSA
SDEs)

 

Regards,

 

Paul

--

Paul Brebner www.ict.csiro.au/staff/Paul.Brebner
Senior Software Research Engineer 
CSIRO ICT Centre www.ict.csiro.au <http://www.ict.csiro.au/> 
Australian National University, Canberra, Australia 
+61 2 6216 7062