Webservice task flow description language
Say I expose some functionality via a webservice. These methods each have their own reason to exist; black boxes that deliver some output based on some input. The method details are, of course, described in a WSDL file.

Now say a combination of service calls could represent a certain business process within an organization. Some sort of task/work flow. I would like to expose such a task/work flow to a consumer using some (XML?) format. 

So, like a description of a webservice is delivered via a WSDL, I'm looking for (a) standard(s) that enables me to expose a task flow between certain webservice calls. 



Webservice task flow description language
===

Say I expose some functionality via a webservice. These methods each have their own reason to exist; black boxes that deliver some output based on some input. The method details are, of course, described in a WSDL file.

Now say a combination of service calls could represent a certain business process within an organization. Some sort of task/work flow. I would like to expose such a task/work flow to a consumer using some (XML?) format. 

So, like a description of a webservice is delivered via a WSDL, I'm looking for (a) standard(s) that enables me to expose a task flow between certain webservice calls. 


