The zip file contains
1. Samplev20.xml: This is an XML file that does validate against the version 2.0 XSD. 
The XML file represents a subset of the database. 
The XML file was generated mostly using real data but synthetic data was inserted wherever real data was missing.
   

2. AIRSv2.0.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 . 

The following changes have been made to the AIRS XSD:
1.  Introduced a new element to the Agency, VirtualAgency, Site and Service elements named "Key" and of type nonNegativeInteger. The Key represents the identifier used for the parent element in the database (from where the XML has been generated). Please note that the Key is not of type ID, this is because of the unnormalized nature of the XML instance.  An attribute/element of type ID takes a unique value all over the XML instance.  Consider an example, many agencies may provide the same Service and therefore that particular Service element will be repeated in every Agency it belongs to. Therefore, an attribute of type ID can not be used due to cases like the example.  We have deliberately avoided using the word "ID" to name the element as some validators  enforce the uniqueness constraint for every attribute named ID irrespective of the type attached to it.

2. We have added two elements to  ServiceSiteLink named SiteKey and ServiceKey in line with the changes made to the Site and Service elements above.

3. The attribute ID of the Taxonomy element has been removed as the same taxonomy code might be used by many ServiceSiteLink and hence a unique ID 
     over the whole XML document is not possible.


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.