Home > Articles > Software Development & Management

Like this article? We recommend

BizTalk Schemas

We need to differentiate between several uses of the term schema, ranging from general to specific.

Schema, in computer lingo, generally refers to an information model of some application domain. This information model defines the logical relationships among the various entities, elements, and fields within that application domain. In directory services environments, for example, schemas refer to the information model applicable to various directory entities, as expressed through fields, attributes, and rows in the directory.

Specifically, an XML schema primarily addresses the information model instantiated in a particular XML document-type. In other words, the schema defines the relation of entities, elements, and fields within XML documents of that type. This is the primary sense in which BizTalk Framework 2.0 uses the term. An XML schema is an entity that defines the permissible elements, attributes, and values contained in an XML document-type. The entity defining the schema may be a separate linked document or simply lines of XML code in the document that instantiates the schema.

The primary purpose of XML schemas is to help receiving applications automatically determine the prescribed logical relationship among items, and thereby detect when some new item deviates from the permissible. For example, to ascertain whether an incoming document conforms to the BizTalk 2.0 document type, a BizTalk-enabled application invokes a validating processor, which compares the document to the structure prescribed in the entity defining its schema. The BizTalk Message or Document is valid if it complies with the constraints expressed in the schema provided in the BizTalk Framework 2.0.

Another way to look at XML schemas is that they provide human-readable metadata pertinent to a document and its elements. Metadata is simply data that comments on other data; and XML tags, which are terse and descriptive, perform this role in the context of an XML document.

The BizTalk XML schema defines the tags (BizTags) that describe the logical structure and content of a BizTalk Document; hence the core of a BizTalk Message (which includes an outer, non-XML envelope specific to the particular transport protocol over which it's being transmitted). Other XML schemas—such as those defined under such vertical-market initiatives as RosettaNet and Information and Content Exchange (ICE)—define XML tags specific to Business Documents that a BizTalk Document would contain.

Consequently, a typical BizTalk Message would reference at least one non-BizTalk schema in addition to the BizTalk schema. The destination BizTalk server and application would work together to validate these dual layers of schemas, according to the following processing.

  1. A destination BizTalk server parses the structure of the incoming BizTalk Message's outer, non-XML-based transport envelope, and validates that structure using procedures defined outside the BizTalk Framework specifications.

  2. The destination BizTalk server extracts the BizTalk Document from the BizTalk Message, parses the structure of the BizTalk Document's XML envelope, and validates that structure against the BizTalk schema.

  3. The destination BizTalk server sends the validated XML-formatted BizTalk Documents to the destination application.

  4. The destination application extracts the Business Documents contained in the BizTalk Document, parses their XML structures, validates them against the relevant application-specific XML schemas, and processes the data contained in these documents according to application-specific business rules. According to the BizTalk Framework, some of these Business Documents may include non-XML data, in which case the destination application would have separate procedures for parsing, validating, and processing them.

Currently, the BizTalk Framework defines BizTalk document schemas in the XML Data Reduced (XDR) format. Microsoft developed XDR and submitted it as a proposal to the W3C in 1998, but it is not an industry standard, nor is it on a W3C standards track. Acknowledging this fact, and committed to supporting open and ratified standards where available, Microsoft now identifies XDR solely as a transitional schema-definition format for use within the BizTalk Framework. The company recognizes that the W3C's more recent XML Schema specifications are on a standards fast track, and has committed to supporting them in a future version of the framework.

Microsoft chose XDR over XML 1.0's native Document Type Definition (DTD) schema format due to XDR's support for more robust data typing and object-oriented functionality. The XML Schema specification draws on concepts and conventions developed in XDR and other schema-definition proposals submitted to the W3C, including such proposals as Schema for Object-Oriented XML (SOX) and Document Content Description (DCD).

XDR renders document schemas through tagged XML element nametags, rather than DTD declaration statements. XML parsers must recognize XML-Data schemas in order to validate documents against them. XDR schemas include tags for declaring the following:

  • Conceptual-graph and syntactical-tree schemas, plus rules for mapping between them

  • DTD-like document constructs, such as elements, attributes, entities, and notations

  • Object classes, such as class hierarchies, properties, constraints, and relationships

  • Data types, including all highly popular data types, all built-in data types of popular database and programming languages, parsing rules, and implementation formats

The XDR specification identifies data types for particular elements through references to Web Uniform Resource Identifiers (URIs). The data type's URI refers to a part of the XML document's schema that declares the appropriate parser and storage format of the element.

XDR supports open content models in addition to the closed content models defined under XML 1.0. Open content models allow XML documents to contain subelements that were not explicitly listed in their schema declarations. A closed content model, by contrast, requires that all elements and attributes be listed explicitly, and declares as invalid any XML document that includes undeclared content. XDR also defines tags for defining elements as keys and foreign keys. This is useful for instantiating a conceptual data model among elements within an XML document and for supporting database-style joins.

As we noted, XDR (and XML Schema) defines the schema or information model applicable to a valid XML document type, such as a BizTalk Document. The BizTalk Document is an envelope around one or more application-specific Business Documents. Some, but not all, of them must be in XML format. In order to validate the structure and contents of an XML-formatted Business Document, an XML-enabled application would have to access the XML schema appropriate to that document-type.

Microsoft established an online repository in which organizations may publish their application-specific Business Document schemas. The schema repository is available free of charge to all comers at http://www.biztalk.org, a non-profit clearinghouse. Schemas for Business Documents do not contain any BizTags, only the XML tags required to support the business transaction. Business Document schemas are designed by various companies, industry groups, and other implementing organizations—not by Microsoft. However, Microsoft defined general requirements and guidelines for Business Document schema implementations, and made them available at http://www.biztalk.org.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020