The zip file contains
1. Data2_Subset_v201.xml: This is an XML file that does validate against the version 2.01 XSD. 
It is a subset of the database. An artificial  Canadian address has been inserted.
The XML file was generated mostly using real data but synthetic data was inserted wherever real data was missing.
   

2. AIRSv2.01.xsd  The XSD used to validate the XML. If you are going to validate the XML, please make 
   sure to set the xsi:noNamespaceSchemaLocation attribute of the Source element to the XSD.

The XML files have been validated using XMLSPY v2004 rel. 4 and the validation tool using Microsoft's validators at
http://apps.gotdotnet.com/xmltools/xsdvalidator/Default.aspx  

Reasons for the change:
The reason behind the change was an ambiguity in the XML Schema definition. This ambiguity has led
to varying behavior among different implementations of the standard. The ambiguity is
in the choice group element. There were problems reported that documents that were validated
using XML spy were not validating on the .Net platform. These errors were  due to
the difference in the implementation of the XML schema standard. To steer away from
the ambiguity in the specification the address type (tAddress) has undergone a few changes.

The change:
The tAddress type allows for an address to be follow Canadian or American format.
Initially, the Country element in each of these choice groups was assigned the fixed value of
"CA"/"USA". In version 2.01 the Country element for Canadian address the Country element
is replaced by an element named "CA" and that has an implicit value of CA and similarly
a "USA" element replaces Country for American addresses.
In the XML instances it is not required to give a value to the element.
For example:
<MailingAddress Confidential="false">
  <ZipCode>68000</ZipCode> 
  <State>NE</State> 
  <City>CityName</City> 
  <USA/> 
  <Line1>Address Line </Line1> 
  </MailingAddress>



The primary goal of generating the XML was to provide a sample XML instance to test functionality
of uploading to the central database and was not to test conformance of vendor systems with the 
AIRS standard.