3. Dependencies

[Previous] [Next]

3.1 Normative Specifications

Each BizTalk Framework document lists the existing or emerging Internet standards that it is built upon as normative references. Some of the content of the normative references may need to be reproduced for expository purposes in BizTalk Framework specifications. In all such cases, the normative references are authoritative. Every effort has been made to avoid discrepancies between the normative references and their usage in BizTalk Framework specifications. However, if a discrepancy is found, the normative reference provides the correct interpretation and the BizTalk Framework specification is in need of correction.

The following specifications are normative for this specification:

• Extensible Markup Language (XML) 1.0
• Simple Object Access Protocol (SOAP) Version 1.1
• Namespaces in XML
• Uniform Resource Identifiers (URI): Generic Syntax
• ISO 8601: Representations of dates and times
• Hypertext Transfer Protocol—HTTP/1.1
• XML Media Types
• MIME Part One: Format of Internet Message Bodies
• MIME Part Two: Media Types
• MIME Part Three: Message Header Extensions for Non-ASCII Text
• MIME Part Four: Registration Procedures
• Content-ID and Message-ID Uniform Resource Locators

3.2 Non-Normative Specifications

The following specifications have had an influence on this specification, but the relationship is not foundational and their content is not normative for this specification:

• XML-Data Reduced (XDR)
• XML Schema Part 1: Structures
• XML Schema Part 2: Data types
• XML-Signature Syntax and Processing

3.3 Use of XML Schema Data Types

This specification uses the type-qualification xsi:type attribute as well as a number of specific data types from the XML Schema specifications. These are listed below with explanations. This specification, however, does not mandate the use of a specific method for defining XML schemas.

The xsi:type attribute allows an element to explicitly assert its type in a specific XML document instance. This can be used to validate the structure of the element.

The data type timeInstant represents a specific instant of time. The value space of timeInstant is the space of combinations of date and time of day values as defined in section 5.4 of the ISO 8601 standard.

The uriReference data type represents a URI reference as defined in Section 4 of Request for Comments (RFC) 2396. A URI reference may be absolute or relative, and may have an optional fragment identifier.

A complexType is an element with content that is not a simple type, such as a string or a decimal number; the element contains subelements and/or attributes with their own content.