-
BizTalk is a registered trademark of Microsoft Corporation. -
W3C Notes are technical documents on topics related to the work of W3C and submitted to the organization for discussion. Acceptance as a Note by the W3C implies no endorsement, nor does the W3C claim any editorial responsibility for its contents. -
XML Protocol Activity Statement, World Wide Web Consortium, 4 April 2001, www.w3.org/2000/xp/Activity. -
SOAP Messages with Attachments,W3C Note, 11 December 2000, World Wide Web Consortium, www.w3.org/TR/SOAP-attachments. -
"Introduction," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. -
"SOAP Envelope," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. -
This is not a typo. One of the less endearing features of technical documents in information technology is "camel case" notation that not only strings together words but capitalizes in the middle of the string, ostensibly to see where one concatenated word ends and the next begins. While camel case is common for engineers , it contributes to the well-founded but still unfortunate dread that normal people have of technical writing. -
"SOAP Header," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. -
"SOAP Body," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. -
To the credit of the SOAP authors, the specifications say that this sub-element should also "provide at least some information explaining the nature of the fault." -
"SOAP Fault," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. -
R. Srinivasan,"RPC: Remote Procedure Call Protocol SpecificationVersion 2," Internet Engineering Task Force, Request For Comments (RFC): 1831,August 1995, www.ietf.org/rfc/rfc1831.txt. -
"XML Schema Part 2: Datatypes," W3C Candidate Recommendation, 24 October 2000, www.w3.org/TR/2000/CR-xmlschema-2-20001024/datatypes.html. -
"SOAP Encoding," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. -
"Using SOAP for RPC," Simple Object Access Protocol (SOAP) 1.1, World Wide Web Consortium, 8 May 2000, www.w3.org/TR/2000/NOTE-SOAP-20000508. Note, however, that using SOAP for RPC is not limited to the HTTP protocol binding. -
Industry Leaders Join to Accelerate Business Integration and Commerce on the Internet, 6 September 2000, www.uddi.org/uddipr09062000.html. -
UDDI Executive White Paper, 6 September 2000, pp. 2 “3. -
UDDI Technical White Paper, 6 September 2000, p. 2. -
UDDI Technical White Paper, 6 September 2000, pp. 6 “8. -
"Core structure reference," UDDI Data Structure ReferenceV1.0., UDDI Open Draft Specification, 30 September 2000, pp. 5 “6. -
UDDI Programmer's API Specification,Version 1.0, 6 September 2000. -
Information and Content Exchange, World Wide Web Consortium, 26 October 1998, www.w3.org/TR/NOTE-ice. -
The Web Distributed Data Exchange, www.openwddx.org/. -
Uche Ogbuji,"Using WSDL in SOAP applications," IBM Developer Works,Web Services Library, November 2000, www-106.ibm.com/developerworks/library/ws-soap/index.html?dwzone= webservices . -
Web Services Description Language (WSDL) 1.1, IBM Developer Works,Web Services Library, 21 March 2001, www.w3.org/TR/wsdl. -
See www.biztalk.org/home/framework.asp. -
"'Signed, Sealed and Delivered' ”BizTalk Server 2000 Released to Manufacturing; Pricing and Licensing Detailed," 12 December 2000, www.microsoft.com/presspass/press/2000/Dec00/ManfReleasePR.asp. -
"Introduction, Specification Scope and Evolution," BizTalk Framework 2.0: Document and Message Specification, December 2000, pp. 2 “6. -
"Logical Layering," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, p. 9. -
"BizTalk Document Header Entries," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 13 “14. -
Universal Unique Identifier,The Open Group , 1997, www.opengroup.org/onlinepubs/9629399/apdxa.htm. -
"Document Identification and Properties," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 14 “15. -
"Delivery Services," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 16 “17. -
"Document Catalog," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 18 “20. -
"Process Management," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 20 “21. -
"The BizTalk Document Body," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 11 “12. -
"Use of XML Schema Data Types," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp.6 “7. -
"Reliable Delivery of BizTalk Documents," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 22 “28. -
"Securing BizTalk Documents and Messages," BizTalk Framework 2.0: Document and Message Specification, 12 December 2000, pp. 34 “38. -
See www.census.gov/epcd/www/naics.html for details. -
Timothy Dyck, "XML Messaging Framework," eWeek, 12 March 2001, www.zdnet.com/eweek/stories/general/0,11011,2694009,00,html. -
"BizTalk.org Web Site Upgraded," 31 January 2001, www.biztalk.org/news/biztalk_org_upgrade.asp. -
BizTalk Help, undated, www.biztalk.org/Help/help.asp.  |
