The complexity of the concept means it will take time to settle on a standard, said Sinisa Zimek, SAP advisory committee representative to W3C and a member of various W3C working groups.
"Choreography is a pretty broad area," Zimek said. "It's much more complex to standardise choreographies than, for example, Soap and WSDL."
Although WSDL and Soap enable development of simple Web services such as stock quote notifications, more complicated Web services, such as invoice processing, will require choreography of processes.
The W3C this week held its Advisory Committee Forum, formed to hold open discussions on issues such as choreography. Major vendors including Sun and Microsoft were represented.
Upon conclusion of the advisory meeting, W3C members will continue until mid-December to provide input on a proposal to form a Web services choreography working group. W3C director Tim Berners-Lee will decide whether to form such a panel. Members concurred that W3C should be the forum for standardising Web services, according to Zimek.
The panel is pondering the Sun-driven Web Services Choreography Interface (WSCI) proposal as a basis for Web services choreography and is waiting to hear from IBM and Microsoft on whether they will submit their rival plan, Business Process Extension Language for Web Services (BPEL4WS), to the W3C for consideration.
As of last week, both IBM and Microsoft were pondering a decision on submitting BPEL4WS to a standards body. A Microsoft representative said the company had still not made a decision.