This is a modified schema. xs:any tags have been removed/commented out so that this schema can be imported. tService was reintroduced, and a target and default namespace were added.
AIRS XML Data Transfer Record Format Version 3.0 (Final)
unless set, the default minOccurs="1" maxOccurs="1"
element of tSite
One type of Address to cover all locations. US, Canadian and other addresses are handled the same way.
Use this if the address can not be shared due to security concerns, such as an assaulted women’s shelter. While it is possible to code an address as confidential="true", In this case the address is so confidential that it won't be shared at all
element of Source and tAgency
Agencies are organizations that offer services at locations. Agencies provide services directly or they may have “child” agencies that offer these services. Services are offered at sites that belong to an agency. Services are represented by the combination of taxonomy codes offered at a location; this idea is called a SiteService. To recap: Agencies don’t provide services directly, they provide them through sites
This is a unique number representing a vendor's internal way of tracking an agency. This can be used as meta data to uniquely describe an Agency
Agency Definition: Parent/Child relationships are handled through recursion. Agency elements within another agency (the parent) are child agencies, that is they belong to a parent agency: e.g. Transportation Security Administration(TSA) is a child of Homeland Security. Therefore TSA and all associated Sites can be created inside the Homeland Security Agency element
This is a unique string indicating the organization that created and maintains this Agency record
element of tSiteService
Information about any age or gender related requirements or inclusions for a particular service at a particular location
element of tAgency and tSite
These are alternate names for an object, Confidential indicates that the alternate name won't be shared with the public
element of tServiceGroup and tSiteService
ApplicationProcess describes the steps taken to apply for or access the service or services; also known as the ‘intake process’.For example, “Call for an appointment” or “Walk in only”
element of tAgency, tResourceInfo and tSite
1) Contact is the person at an Agency, or Site who will interface with the public or who has responsibility for the entity, like a site manager or director.
2) Contact is also used by ResourceInfo to indicate the person within each agency who has overall responsibility for updating the information about the agency, its sites and its services, etc.
This is the type of contact, for example an Administrator or Owner
element of tTimeOpen
This can be used for any day of the week
element of tSiteService
A document that is required in order to access services offered at a SiteService
element of tAgency, tContact, and tSite
Email Address: restricted by regular expression, see www.regexlib.com
element of tSiteService
This is the geographic area served by the SiteService. This can be anything from a single neighborhood to an entire country. Types can also be mixed; perhaps one city and 6 nearby ZIP codes. In this case the required element would be City and there would be additional ZIP codes. A national 1-800 hotline would have one Country element
At least one of the following must be selected. Then any number of additional elements can be included
element of tSite and tSiteService
Language spoken and the TimeOpen the language is available
element of tAgency
If applicable, information about the license/accreditation held by the agency and the body that licensed/accredited it
element of tSite
This is something without a physical presence; Description is what the entity is/does, and Explanation is why is doesn't have a physical presence
element of tAgency, tContact, tSite and tSiteService
Phone numbers
Use this if the phone can not be shared due to security concerns, such as a spousal abuse group home. While it is possible to code an phone as confidential="true", In this case the phone is so confidential that it won't be shared at all
element of tAgency and tSiteService
information about the data
This is a person who created/maintains the data
element of tSiteService
Activities that are only offered a certain time of year, such as seasonal tax preparation, summer camps and holiday meals
This type is a modification to the standard 3_0 AIRS Schema. It existed in version 2.07 and was taken out, yet a suitable replacement for this functionality was not reintroduced. HUD HMIS XML needs tService(Program) functionality.
This is an optional unique number representing a vendor's internal way of tracking a service (akin to a program, by some definitions). This can be used as metadata to uniquely describe a Service.
This represents ID of parent Agency.
element of tAgency
Service Groups are a way to group related services, which may be sometimes but not necessarily be known as "Programs". However not all vendors implement this. This will provide a key that can be added to SiteService.ServiceGroupKey so that multiple SiteServices can belong to the same ServiceGroup
This number is used by a SiteService to know what ServiceGroup it is part of (if any). This must be unique between all child agencies
required name and used internally. May be the same as the programName
optional, publicly visible name. e.g. Headstart
element of tAgency
Sites are physical locations or none physical locations (a website or hotline). Site is used for two purposes. First it is used by Agency to provide the location of the agency Agency.AgencyLocation (Note this type of Site would never have any SiteService children). Second sites are also the location where services are provided. This would be the Agency.Site element (Note this type of Site would have SiteService children
This an optional unique number representing a vendor's internal way of tracking a Site. The can be used as meta data to describe a Site uniquely
element of tSite
SiteService is the smallest unit describing a "service" that is offered at a Site. It can be thought of as the intersection of a Site and a Taxonomy code (or related Taxonomy codes) and meta data about what is offered. *This documentation is modified from the AIRS Final 3.0 Data Standard. It used to also say "A "Service" however is not represented as its own element because the "Service" cannot exist without a location (the site).", but this modified version adds a tService to describe aspects of a "Service" or "Program" common to add its Sites.
This an optional unique number representing a vendor's internal way of tracking a SiteService. The can be used as meta data to describe a SiteService uniquely
Requirements include any Exclusions, so both negative and positive requirements i.e. must have/ can't have are all requirements
Can this service be offered outside of the physical location? true/false
optional value linking this SiteService to a ServiceGroup (Program)
element of tSite
Spatial location is information about the physical location where a site is in the world
A datum also defines the association of latitude and longitude coordinates to points on the surface of the earth, there is more than one way to do this
element of tSiteService
Taxonomy Codes are a structured system created by AIRS/INFO Line to index human services
No checking is done at the XSD, verify validity of codes before export!
element of tLanguages, tSite and tSiteService
TimeOpen refers to the times a service is open or available
element of tAgency and tSite
URL (Web Address): restricted by regular expression, see www.regexlib.com
No checking is done at the XSD, verify validity of url before export! also allows for ftp now
Root Element- contains all other elements
This is a description of the sources of data used in the data dump. If multiples sources of data are used, include them here, additionally any RecordOwner codes used should be listed here as well