Introduction BizTalk Document Schemas – Part II

Posted: July 4, 2009  |  Categories: BizTalk Schemas

Schema Namespaces

Has posted before (link), BizTalk Server uses a combination of Namespace + Root Node name to identify and resolve schemas references.

Therefore, is possible to have two schemas with the same namespace as long the root name designation is different, or the opposite, two schemas with the same root node and different namespace designation.

By default, BizTalk Schema editor put the namespace with the following structure:



  • [SOLUTIONNAME] is the name of the project solution
  • [SCHEMANAME] is the name of the schema

You can change the namespace by:

  • Selecting <schema> node, right-click and select properties;
  • Modify target namespace property

There is no standard naming for BizTalk namespaces, normally, companies adopted their own specification, however one well-adopting structure namespace is:

  • http://[COMPANYNAME].[PROJECT].BizTalk.Schemas.[SCHEMA].[VERSION]

My “standard” is a little different (more simple):

  • http://[COMPANYNAME].[PROJECT].Schemas.[SCHEMA]
  • And in some cases .[VERSION]
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *


Back to Top