W3C home > Mailing lists > Public > xml-dist-app@w3.org > July 2000

RE: Biztalk entry update needed in XML protocol comparisons

From: Satish Thatte <satisht@MICROSOFT.com>
Date: Mon, 3 Jul 2000 09:03:36 -0700
Message-ID: <2DCBFADAFCBBD21189D400805F6FA1AB13D6F7C1@RED-MSG-12>
To: "'Eric Prud'hommeaux'" <eric@w3.org>
Cc: xml-dist-app@w3.org, Andrew Layman <andrewl@MICROSOFT.com>
Eric,

Thanks for the update.  There is one further update needed.  The BizTalk row
says "see SOAP" for facets.  That is only partly accurate.  In addition to
SOAP facets, BTF2 adds reliable messaging under the "protocol" facet, and
business process context under the "business process" facet.  The addition
of attachments does not seem to fit under any facet currently listed --
although there is a lot of discussion of this currently -- ebXML defines a
similar approach to attachments. Perhaps we need a new facet:

Packaging 
Construction of multi-document messages including non-XML documents as
attachments.  Usually includes mechanisms for constructing URI references to
packaged documents.

Regards,
Satish

-----Original Message-----
From: Eric Prud'hommeaux [mailto:eric@w3.org]
Sent: Wednesday, June 28, 2000 10:03 AM
To: Satish Thatte
Cc: xml-dist-app@w3.org; Andrew Layman
Subject: Re: Biztalk entry update needed in XML protocol comparisons


On Wed, Jun 28, 2000 at 08:56:06AM -0700, Satish Thatte wrote:
> A draft
> (http://msdn.microsoft.com/xml/articles/biztalk/biztalkfwv2draft.asp) of
the
> BizTalk Framework 2.0 (BTF2)Specification was released yesterday: .  This
> necessitates some updates to the description of BizTalk
> (http://www.w3.org/2000/03/29-XML-protocol-matrix#BizTalk).  Specifically,
> BTF2 is a SOAP 1.1 extension.  As such it supports everything SOAP 1.1
does

done (I said "see SOAP" for the facets).

> except the RPC usage pattern.  In addition, the BTF2 draft adds
> 
> 1. Attachments to SOAP 1.1 messages (binary or otherwise)
> 2. Simple reliable messaging

does that fall under routing
[http://www.w3.org/2000/03/29-XML-protocol-matrix#layers_routing]?

> 3. Business process context

done

> The relationship of BTF2 to namespaces, schemas and DTD is exactly the
same
> as SOAP 1.1.

done

> The status of the protocol is that it will be finalized by the end of July
> and will be supported in the BizTalk Server 1.0 beta that will appear at
> that time.  It will also be in limited deployment by that time.
> 
> An example of a minimal BTF2 message:
> 
> <SOAP-ENV:Envelope
>                 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
>                 xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
>     <SOAP-ENV:Header>
>        <dlv:delivery SOAP-ENV:mustUnderstand="1"
>
xmlns:dlv="http://schemas.biztalk.org/btf-2-0/delivery"
>                      xmlns:agr="http://www.trading-agreements.org/types/">
>            <dlv:to>
>                <dlv:address xsi:type="agr:department">Book Order
> Department</dlv:address>           
>            </dlv:to>
>            <dlv:from>
>                <dlv:address xsi:type="agr:organization">Booklovers
> Anonymous</dlv:address>           
>            </dlv:from>
>        </dlv:delivery>
>        <prop:properties SOAP-ENV:mustUnderstand="1"
>  
> xmlns:prop="http://schemas.biztalk.org/btf-2-0/properties">
>  
> <prop:identity>uuid:74b9f5d0-33fb-4a81-b02b-5b760641c1d6</prop:identity>
>            <prop:sentAt>2000-05-14T03:00:00+08:00</prop:sentAt>
>            <prop:expiresAt>2000-05-15T04:00:00+08:00</prop:expiresAt>
>  
> <prop:topic>http://electrocommerce.org/purchase_order/</prop:topic>
>        </prop:properties>
>     </SOAP-ENV:Header>
>     <SOAP-ENV:Body>
>         <po:PurchaseOrder
> xmlns:po="http://electrocommerce.org/purchase_order/">
>             <po:Title>Essential BizTalk</po:Title>
>         </po:PurchaseOrder>
>     </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

done

> I am currently responsible for BTF2, so you should probably replace
Andrew's
> name with mine in the row.

done
-- 
-eric

(eric@w3.org)
Received on Monday, 3 July 2000 12:04:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:56 GMT