Web Services Flow Language, abbreviated WSFL and issued as version 1.0, was an XML-based language that IBM proposed in 2001 for describing how web services are composed into larger services. It covered two kinds of composition. The first described a business process as a collection of web services, and the second described the interactions between partners that take part in such a process. WSFL was designed to sit on top of the Web Services Description Language, so that the services it combined were described through that existing interface standard. Its main lasting importance is as one of the two sources of the later standard for web service orchestration. In 2003 IBM and Microsoft combined WSFL with Microsoft's Xlang to produce BPEL4WS and submitted that language to OASIS for standardization, and OASIS then published it under the name WS-BPEL so that it fitted the naming of other WS-star standards.
Facts
First Released Primary Use Domain Connections
Influenced
Source Business Process Execution Language (Wikipedia)
Predecessor Of
Source Business Process Execution Language (Wikipedia)
In the Other Atlases
Developed By
Also in Business Atlas: the developer of this subject.
Source Web Services Flow Language (Wikipedia)LeadQuote, Lead
an XML programming language proposed by IBM in 2001 for describing Web services compositions
Sources
1. Web Services Flow Language (Wikipedia)
Lead
an XML programming language proposed by IBM in 2001 for describing Web services compositions
Lead, primary use domain
for describing business processes as a collection of web services
View the SourceBusiness Process Execution Language (Wikipedia)
Influenced: Business Process Execution Language, History
The origins of WS-BPEL go back to Web Services Flow Language (WSFL) and Xlang.
Predecessor Of: Business Process Execution Language, History, predecessor
IBM and Microsoft decided to combine these languages into a new language, BPEL4WS
View the SourceReader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.