Initial impression about requirements placed by WSCL on WSDL

 
These are my initial impressions on the kind of requirements WSCL places on
WSDL.  
 
1)       WSCL is a very minimal set and does not clearly provide many
details needed (such as a clear mechanism for making abstract concepts
concrete).  So it is hard to determine what kind of requirements might be
placed on WSDL.
2)       It does seem like at minimum, WSDL will need to be able to model
interactions as operations.  Since WSCL operations all use document centric
computing, The message parts in WSDL should be able to handle attachments.
This is already covered by use case UC0006.
3)       WSCL errors have to be mapped to faults.  The mechanism should be
similar to the one above.
4)       WSCL defines 4 types of interactions.  Those 4 types of
interactions match the 4 kinds of operations described by WSDL.
5)       WSCL conversations are clearly out-of-scope for WSDL.
6)       I am fuzzy on how WSCL expects the protocol bindings to be
specified.
 
In general, WSCL seems to be incomplete.  Just like WSDL, It defines the
abstract concepts.  Unlike WSDL, it does not define how to make those
abstract concepts concrete.  That seems to represent a grey area.  For right
now, I could not see any other requirements jump out of WSCL.  WSCL is not
as rigorous as WSFL in mapping to web services.  My confusion is that it
seems like the lack of rigor in that area is by design and I am not sure
why?  Anyway, I don't not mean for this thread to become a discussion of
WSCL so I will leave it there.
 
Thanks,
 
 
_______________________________________________
Waqar Sadiq
 
EDS EIT ESAI - Enterprise Consultant
MS: H3-4C-22
5400 Legacy Drive
Plano, Texas 75024
 
phone: +01-972-797-8408 (8-837)
e-mail: waqar.sadiq@eds.com <mailto:waqar.sadiq@eds.com> 
fax: +01-972-605-4071
_______________________________________________