<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:copyright="http://blogs.law.harvard.edu/tech/rss" xmlns:image="http://purl.org/rss/1.0/modules/image/">
    <channel>
        <title>BizTalk</title>
        <link>http://saltaji.com/weblog/category/4.aspx</link>
        <description>BizTalk</description>
        <language>en-US</language>
        <copyright>F.S.</copyright>
        <managingEditor>firas@saltaji.com</managingEditor>
        <generator>Subtext Version 1.9.5.176</generator>
        <item>
            <title>BizTalk or Windows Workflow Foundation (WF)</title>
            <link>http://saltaji.com/weblog/archive/2007/06/04/biztalk_windows_workflow_foundation_wf.aspx</link>
            <description>Perhaps the most well-known Microsoft implementation of workflow today is in BizTalk Server. BizTalk Server lets developers create system workflows for business process management (BPM), enterprise application integration (EAI), and business-to-business (B2B) integration. 

BizTalk Server and WF have some obvious similarities. To a developer, for example, the BizTalk Server Orchestration Designer looks much like WF’s Workflow Designer. This commonality is no accident—the same group at Microsof&lt;img src="http://saltaji.com/weblog/aggbug/14.aspx" width="1" height="1" /&gt;</description>
            <dc:creator>F.S.</dc:creator>
            <guid>http://saltaji.com/weblog/archive/2007/06/04/biztalk_windows_workflow_foundation_wf.aspx</guid>
            <pubDate>Mon, 04 Jun 2007 15:48:34 GMT</pubDate>
            <comments>http://saltaji.com/weblog/archive/2007/06/04/biztalk_windows_workflow_foundation_wf.aspx#feedback</comments>
            <wfw:commentRss>http://saltaji.com/weblog/comments/commentRss/14.aspx</wfw:commentRss>
        </item>
    </channel>
</rss>