logicalproduct.xsd

<?xml version="1.0" encoding="UTF-8"?>
<!--

Copyright (c) 2014 DDI Alliance, DDI 3.2 release, 2014-02-05

This file is part of DDI 3.2 XML Schema.

DDI 3.2 XML Schema is free software: you can redistribute it and/or modify
it under the terms of the GNU Lesser General Public License as published by the
Free Software Foundation, either version 3 of the License, or (at your
option) any later version.

DDI 3.2 XML Schema is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License
for more details.

You should have received a copy of the GNU Lesser General Public License along
with DDI 3 dev XML Schema. If not, see <http://www.gnu.org/licenses/>.

-->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="ddi:logicalproduct:3_2" xmlns:r="ddi:reusable:3_2" targetNamespace="ddi:logicalproduct:3_2" elementFormDefault="qualified">
	<xs:import namespace="ddi:reusable:3_2" schemaLocation="reusable.xsd"/>
	<!-- BASE LOGICAL PRODUCT -->
	<xs:element name="BaseLogicalProduct" type="BaseLogicalProductType" abstract="true">
		<xs:annotation>
			<xs:documentation>This is an abstract structure which serves as a substitution base for current and future LogicalProduct definitions relating to specific data types. Used as an extension base for all other LogicalProducts within its substitution group, it ensures that all DDI LogicalProduct descriptions will contain a consistent means of linking a physical data file to its logical (intellectual) description via the LogicalRecord found in DataRelationship.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="BaseLogicalProductType" abstract="true">
		<xs:annotation>
			<xs:documentation>This is an abstract structure which serves as a substitution base for current and future LogicalProduct definitions relating to specific data types. Used as an extension base for all other LogicalProducts within its substitution group, it ensures that all DDI LogicalProduct descriptions will contain a consistent means of linking a physical data file to its logical (intellectual) description via the LogicalRecord found in DataRelationship. The extension base includes the standard name, label, and description, coverage information, a structure to define data relationships (identifies each logical record and the relationship(s) between them), as well as OtherMaterial related to its contents.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="LogicalProductName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the LogicalProduct. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the LogicalProduct. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the LogicalProduct. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Coverage" minOccurs="0">
						<xs:annotation>
							<xs:documentation>The Coverage statement at this level may be used to restrict the coverage described in the StudyUnit module. For example if this specific logical product from a population and housing census only covers housing questions or only provides State and County level data these should be noted here. If there are no changes in the coverage from the coverage of the StudyUnit module, no entry is needed here.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="DataRelationship">
							<xs:annotation>
								<xs:documentation>Contains a written description of how the logical contents of the file relate to each other for programming purposes. For example, noting that there are household, family and person items where the household is identified by variable, the unique family by the concatenation of variable_H and variable_F, and the unique person within a household by the concatenation of variable_H and variable_P.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:DataRelationshipReference">
							<xs:annotation>
								<xs:documentation>References a written description of how the logical contents of the file relate to each other for programming purposes. For example, noting that there are household, family and person items where the household is identified by variable, the unique family by the concatenation of variable_H and variable_F, and the unique person within a household by the concatenation of variable_H and variable_P. TypeOfObject should be set to DataRelationship.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:element ref="r:OtherMaterial" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Describes Other Materials that have a specific relation to the logical product. For example the printed data dictionary or printed output for the logical product.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="LogicalProductName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Logical Product using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<!-- LOGICAL PRODUCT -->
	<xs:element name="LogicalProduct" type="LogicalProductType" substitutionGroup="BaseLogicalProduct">
		<xs:annotation>
			<xs:documentation>A module describing the logical (intellectual) contents of the quantitative data. It is a member of the substitution group BaseLogicalProduct and contains all of the common features of the BaseLogicalProduct as well as content specific to quantitative data.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="LogicalProductType">
		<xs:annotation>
			<xs:documentation>A module describing the logical (intellectual) contents of the quantitative data. It is a member of the substitution group BaseLogicalProduct and contains all of the common features of the BaseLogicalProduct as well as content specific to quantitative data. This is a member of the BaseLogicalProduct substitution group and in addition to the content inherited from the BaseLogicalProduct, contains CategorySchemes, CodeListSchemes, ManagedRepresentationSchemes, RepresentedVariableSchemes, VariableSchemes an NCubeSchemes both in-line an by reference.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="BaseLogicalProductType">
				<xs:sequence>
					<xs:choice maxOccurs="unbounded" minOccurs="0">
						<xs:element ref="CategoryScheme">
							<xs:annotation>
								<xs:documentation>Contains descriptions of particular categories used as question responses and in the logical product. Their relationships and code values are described in the code scheme.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:CategorySchemeReference">
							<xs:annotation>
								<xs:documentation>Reference to a previously defined category scheme either internal to or external to the XML instance.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice maxOccurs="unbounded" minOccurs="0">
						<xs:element ref="CodeListScheme">
							<xs:annotation>
								<xs:documentation>Lists the code values used to represent categories for a variable or question. Also describes hierarchical relationships between categories used in the code scheme.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:CodeListSchemeReference">
							<xs:annotation>
								<xs:documentation>Reference to a previously defined code scheme either internal to or external to the DDI instance.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="r:ManagedRepresentationScheme">
							<xs:annotation>
								<xs:documentation>A scheme containing representations that are being managed as reusable sources for response domains and value representations.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:ManagedRepresentationSchemeReference">
							<xs:annotation>
								<xs:documentation>Inclusion of an existing ManagedRepresentationScheme by reference. TypeOfObject should be set to ManagedRepresentationScheme.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="RepresentedVariableScheme">
							<xs:annotation>
								<xs:documentation>A set of RepresentedVariables managed by an agency. RepresentedVariables are the core reusable parts of a Variable. RepresentedVariable maps to the GSIM Represented Variable. In addition to the standard name, label, and description, allows for the inclusion of an existing RepresentedVariableScheme by reference and RepresentedVariables either in-line or by reference. RepresentedVariables may be grouped for management purposes.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:RepresentedVariableSchemeReference">
							<xs:annotation>
								<xs:documentation>Inclusion of an existing RepresentedVariableScheme by reference. TypeOfObject should be set to ManagedRepresentationScheme.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice maxOccurs="unbounded" minOccurs="0">
						<xs:element ref="VariableScheme">
							<xs:annotation>
								<xs:documentation>Contains a collection of variables and variable groups.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:VariableSchemeReference">
							<xs:annotation>
								<xs:documentation>A reference to a previously defined variable scheme either internal to or external to the DDI instance.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice maxOccurs="unbounded" minOccurs="0">
						<xs:element ref="NCubeScheme">
							<xs:annotation>
								<xs:documentation>Contains a collection of NCubes and NCube groups.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:NCubeSchemeReference">
							<xs:annotation>
								<xs:documentation>A reference to a previously defined NCube scheme either internal to or external to the DDI instance.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<!-- CATEGORIES -->
	<xs:complexType name="CategorySchemeType">
		<xs:annotation>
			<xs:documentation>A scheme containing a set of Categories managed by an agency. These are used to manage category definitions used as a domain for data element and basic content for a category representations. In addition to the name, label, and description of the scheme, the structure supports the inclusion of another CategoryScheme by reference, a set of Category descriptions either in-line or by reference, and the description of a CategoryGroup either in-line or by reference.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="CategorySchemeName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the scheme. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the scheme. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the scheme. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:CategorySchemeReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows for inclusion by reference of other category schemes.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="Category">
							<xs:annotation>
								<xs:documentation>A description of a particular category or response. OECD Glossary of Statistical Terms: Generic term for items at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:CategoryReference">
							<xs:annotation>
								<xs:documentation>Reference to a description of a particular category or response. OECD Glossary of Statistical Terms: Generic term for items at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. TypeOfObject should be set to Category.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="CategoryGroup">
							<xs:annotation>
								<xs:documentation>Allows categories to be grouped with or without hierarchical structure.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="CategoryGroupReference">
							<xs:annotation>
								<xs:documentation>Inclusion of a CategoryGroup that allows categories to be grouped with or without hierarchical structure by reference. TypeOfObject should be set to Category.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="CategoryGroupReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Inclusion of a CategoryGroup that allows categories to be grouped with or without hierarchical structure by reference. TypeOfObject should be set to CategoryGroup.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CategorySchemeName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Category Scheme using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="CategoryGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of Category descriptions, which may be ordered or hierarchical. In addition to the name, label, and description of the group, the structure allows for defining the group as a valid category value using a DefiningCategoryReference, and a listing of Categories and CategoryGroups in any order.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="TypeOfCategoryGroup" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A brief textual identification of the group type. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="CategoryGroupName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the group. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the category group. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the CategoryGroup. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="DefiningCategoryReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A reference to a category that defines the group, thereby allowing the group to define the contents of that category by explicitly identifying its members.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement describing the persons or other objects to which the contents of this group pertain.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the concept expressed by the objects in this group.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Subject" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If subjects are listed for this group, it is strongly recommended that the subjects listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of subject at the group level allows for associating objects as a type of subject based group or to identify subject characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Keyword" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If keywords are listed for this group, it is strongly recommended that the keywords listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of keyword at the group level allows for associating objects as a type of keyword based group or to identify keyword characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="r:CategoryReference">
							<xs:annotation>
								<xs:documentation>A category defined as a member of this group.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="CategoryGroupReference">
							<xs:annotation>
								<xs:documentation>A category group that is a member of this group (nesting structure).</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
				<xs:attribute name="isOrdered" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>If set to "true" indicates that the content of the group is ordered as it appears within the XML structure.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="DefiningCategoryReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing Category using the Reference structure. TypeOfObject should be set to Category.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="TypeOfCategoryGroup" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>A brief textual description of the type of group created to associate a number of Categories. Supports the use of an external controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CategoryGroupName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Category Group using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="CategoryType">
		<xs:annotation>
			<xs:documentation>A description of a particular category or response. OECD Glossary of Statistical Terms: Generic term for items at any level within a classification, typically tabulation categories, sections, subsections, divisions, subdivisions, groups, subgroups, classes and subclasses. In addition to the standard name, label, and description, a category may contain a reference to a defining concept, provide information on how the category was generated (membership defined), and indicate if it is the description of a type of missing value.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="CategoryName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the category. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the category. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations or of different types or applications.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the category. May be expressed in multiple languages and supports the use of structured content. Note that comparison of categories is done using the content of description.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the defining concept.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="Generation" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Describes how the category is derived or generated. A process for describing the determination of category membership.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="SubCategoryReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to one or more categories for which the current category is a broader definition. Allows for a reference to the narrower category and the ability to define the relationship as a specialization or part.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="isMissing" type="xs:boolean" use="optional">
					<xs:annotation>
						<xs:documentation>If the category is describing a classification of "missing data" set the value of isMissing to "true".</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="CategoryName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Category using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="SubCategoryReference" type="SubCategoryReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to one or more categories for which the current category is a broader definition. Allows for a reference to the narrower category and the ability to define the relationship as a specialization or part. TypeOfObject should be set to Category.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="SubCategoryReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to one or more categories for which the current category is a broader definition. Allows for a reference to the narrower category and the ability to define the relationship as a specialization or part. TypeOfObject should be set to Category.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:ReferenceType">
				<xs:attribute name="typeOfSubCategory" type="SubCategoryType">
					<xs:annotation>
						<xs:documentation>Defines the sub-category in terms being generic or partitive in nature. For example, a radial tire is a type of tire (generic) while a tire is a part of a car (partitive). The value refers to the role of the SubCategory within the broader category .</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:simpleType name="SubCategoryType">
		<xs:annotation>
			<xs:documentation>Defines the sub-category in terms being generic or partitive in nature. For example, a radial tire is a type of tire (generic) while a tire is a part of a car (partitive). The value refers to the role of the SubCategory within the broader category .</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="specialization">
				<xs:annotation>
					<xs:documentation>Defines the relationship of the sub-category as being generic in nature, i.e. that the sub-category is a "specialization" of the category which references it.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="isPartOf">
				<xs:annotation>
					<xs:documentation>Defines the relationship of the sub-category as being partitive in nature, i.e. that the sub-category is a "isPartOf" of the category which references it.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<!-- CodeLists -->
	<xs:element name="CodeListScheme" type="CodeListSchemeType">
		<xs:annotation>
			<xs:documentation>A scheme containing sets of CodeLists that are used by reference to define code representations used by value representations and response domains.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="CodeListSchemeType">
		<xs:annotation>
			<xs:documentation>A scheme containing sets of CodeLists that are used by reference to define code representations used by value representations and response domains. In addition to the standard name, label, description, the CodeListScheme may contain another CodeListScheme by reference, CodeLists either in-line or by reference, and CodeListGroups either in-line or by reference.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="CodeListSchemeName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the CodeListScheme. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the CodeListScheme. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the CodeListScheme. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:CodeListSchemeReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows for the inclusion of another CodeListScheme by reference.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="CodeList">
							<xs:annotation>
								<xs:documentation>A structure used to associate a list of code values to specified categories. May be flat or hierarchical. A maintainable CodeList listed in the CodeListScheme in-line.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:CodeListReference">
							<xs:annotation>
								<xs:documentation>A reference to an existing CodeList to be added to this CodeListScheme by reference.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="CodeListGroup">
							<xs:annotation>
								<xs:documentation>In-line description of a group of CodeLists for conceptual, administrative or other purposes.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="CodeListGroupReference">
							<xs:annotation>
								<xs:documentation>The inclusion of an existing CodeListGroup by reference.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>

	<xs:element name="CodeListSchemeName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Code List Scheme using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CodeListGroupReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing CodeListGroup using the Reference structure. TypeOfObject should be set to CodeListGroup.</xs:documentation>
		</xs:annotation>
	</xs:element>

	<xs:complexType name="CodeListType">
		<xs:annotation>
			<xs:documentation>A structure used to associate a list of code values to specified categories. May be flat or hierarchical. This is a maintainable object. In addition to the standard name, label, and description the CodeList specifies a recommended data type, the hierarchical nature of the CodeList, level descriptions, individual code values and associated category, and whether the CodeList contents are used to represent system specific missing values. May include another CodeList by reference. If including other CodeLists make sure there are no code conflicts in the overall content. A code value must be unique within the CodeList. May also include a reference to a default CategoryScheme.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="CodeListName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the CodeList. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the CodeList. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the CodeList. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:RecommendedDataType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>This field provides the recommended treatment of the data within an application. This field is important as some codes represented as numeric should be treated as strings, i.e., many standardized codes for industry, occupation, education, etc. The value should come from a controlled vocabulary - recommended values include the set found in W3C XML Schema Part 2, but excluding string sub-types, QNAME, and NOTATION.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:CodeListReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows for inclusion by reference of another CodeList. Care must be taken to ensure that all code values of the resulting CodeList are unique.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:CategorySchemeReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to a default category scheme, with the assumption that all categories referenced by the subsequent codes are part of it, unless overwritten by the scheme reference in the CategoryReference field of the code.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="HierarchyType" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Identifies the type of hierarchy used in the nesting of categories. Possible values are Regular and Irregular. A regular nesting indicates that the category hierarchy is consistent at all lower levels of the hierarchy, i.e., the lowest levels of the hierarchy are at the same level for every branch on the hierarchy.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="Level" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Describes the levels of the code hierarchy. The level describes the nesting structure of a hierarchical coding structure. Note that the attribute levelNumber is used for referencing specific codes to their level identifier.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="Code" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Includes a code value, references the category label, and describes the code's position in a hierarchy.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="isSystemMissingValue" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>If "true" contents are used to represent system specific missing values. The default value is "false".</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="CodeListName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Code List using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="LevelType">
		<xs:annotation>
			<xs:documentation>Used to describe the levels of the code list hierarchy. The level describes the nesting structure of a hierarchical coding structure. A level could have data attached to it (summary of its children) or no data attached to it (the equivalent of creating a category group in 2.0 and earlier versions Note that the attribute levelNumber is used for referencing specific codes to their level identifier. Although Code Lists can be physically nested, the use of a Level description and the level number on a specific code is needed to specify subsets of the CodeList for use in CodeRepresentations by level specification. Provides a name, description and level number. Specifies the relationship between the categories at that level and interval value if the relationship has the value of Interval.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="LevelName" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Name of a level in a code scheme. This should be short and explicit, such as Major Industrial Groups (2 digit SIC Codes) or NUTS 1. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:Description" minOccurs="0">
				<xs:annotation>
					<xs:documentation>A description of the code Level. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="CategoryRelationship" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Describes the relationships among categories at that respective level. Possible values are either Nominal, Ordinal, or Interval. Note that different levels may have different types of relationships within the same hierarchy. For example, Level 1 items may be ordinal and Level 2 (the children of Level 1 items) may be nominal.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="Interval" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Identifies the interval between each value of the codes at this level. Used only for codes with interval relationship.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="levelNumber" type="xs:integer" use="required">
			<xs:annotation>
				<xs:documentation>Designated identifier for the level; generally increases as the level of indention for nesting increases.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="CodeType">
		<xs:annotation>
			<xs:documentation>A structure that links a unique value of a code to a specified category and provides information as to the location of the code within a hierarchy, whether it is discrete, represents a total for the CodeList contents, and if its sub-elements represent a comprehensive coverage of the code. The Code is identifiable, but the value within the code must also be unique within the CodeList.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:IdentifiableType">
				<xs:sequence>
					<xs:element ref="r:CategoryReference">
						<xs:annotation>
							<xs:documentation>Reference to the category that the code value represents.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Value">
						<xs:annotation>
							<xs:documentation>The value of the code. In a microdata file this would be the value found in the data file. If used as the description of an NCube dimension the value provides the coordinate value for that dimension. Note that r:Value has an attribute xml:space with the default value of "default". If white space is critical to the understanding of this code value (such as critical leading or tailing spaces, or multiple spaces within the code) change the value of xml:space to "preserve".</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="Code" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows for nesting of codes.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="isDiscrete" type="xs:boolean" default="true">
					<xs:annotation>
						<xs:documentation>Indicates whether the code is discrete (that is, placed at the lowest level in a hierarchy and has no children).</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="levelNumber" type="xs:integer" use="optional">
					<xs:annotation>
						<xs:documentation>Level number of the code.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="isComprehensive" type="IsComprehensiveType" default="Unknown">
					<xs:annotation>
						<xs:documentation>Used in hierarchical structures at upper level values to indicate whether or not the subelements of the code are comprehensive in coverage. Not applicable if attribute isDiscrete is set to "true".</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="isTotal" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>This expresses a total whether or not isComprehensive is true. If isComprehensive = "true" then if addition is supported by the measure type, the contained categories can be aggregated to calculate the total. If isComprehensive = "false" or "unknown" the content of this field cannot be calculated if the value is not provided in the data.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:complexType name="IntervalType">
		<xs:annotation>
			<xs:documentation>Describes the structure, starting point and increment step of an interval.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="Anchor" type="xs:string">
				<xs:annotation>
					<xs:documentation>Identifies the start value for this interval.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="Increment" type="xs:string">
				<xs:annotation>
					<xs:documentation>Value specifying the increment between categories.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:element name="CodeListGroup" type="CodeListGroupType">
		<xs:annotation>
			<xs:documentation>A grouping of CodeLists for conceptual or administrative purposed.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="CodeListGroupType">
		<xs:annotation>
			<xs:documentation>A grouping of CodeLists for conceptual or administrative purposed. May be hierarchical.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="TypeOfCodeListGroup" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A brief textual identification of the group type. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="CodeListGroupName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the CodeListGroup. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the CodeList group. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the CodeListGroup. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement describing the persons or other objects to which the contents of this CodeList group pertain.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the concept expressed by the CodeLists in this group.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Subject" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If subjects are listed for this group, it is strongly recommended that the subjects listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of subject at the group level allows for associating objects as a type of subject based group or to identify subject characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Keyword" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If keywords are listed for this group, it is strongly recommended that the keywords listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of keyword at the group level allows for associating objects as a type of keyword based group or to identify keyword characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="r:CodeListReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent CodeList.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="CodeListGroupReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent CodeListGroup. This allows for nesting of CodeListGroups.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
				<xs:attribute name="isOrdered" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>If set to "true" indicates that the content of the group is ordered as it appears within the XML structure.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="CodeListGroupName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Code List Group using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="TypeOfCodeListGroup" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>A brief textual description of the type of group created to associate a number of code lists. Supports the use of an external controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>

	<!-- VARIABLES -->
	<xs:complexType name="VariableSchemeType">
		<xs:annotation>
			<xs:documentation>Contains a set of Variables and VariableGroups. In addition to the standard name, label, and description of the Variable Scheme, may contain another VariableScheme by reference, a listing of Variables (in-line or by reference), and a listing of VariableGroups (in-line or by reference).</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="VariableSchemeName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the VariableScheme. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the scheme. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the VariableScheme. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:VariableSchemeReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows for the inclusion of another VariableScheme by reference.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="Variable">
							<xs:annotation>
								<xs:documentation>Describes a Variable in-line. This is the applied expression of a data item within a data set.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:VariableReference">
							<xs:annotation>
								<xs:documentation>Allows for the inclusion of an existing variable by reference.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="VariableGroup">
							<xs:annotation>
								<xs:documentation>Contains a group of Variables, which may be ordered or hierarchical.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="VariableGroupReference">
							<xs:annotation>
								<xs:documentation>Allows the inclusion of an existing VariableGroup by reference.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="VariableSchemeName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Variable Scheme using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="VariableType">
		<xs:annotation>
			<xs:documentation>Describes the structure of a Variable. This is the applied expression of a data item within a data set and maps to the GSIM ImplementedVariable. In addition to the standard name, label, and description, includes a reference to a source parameter, represented variable, conceptual variable, universe, concept, question, source variable, and embargo information. It identifies the normal source of the data in the variable, the unit of analysis, whether the variable provides temporal or geographic information, or serves as a weight for other variables in the data, and provides a full description of its representation.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="VariableName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the Variable. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the Variable. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the Variable. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:OutParameter" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Assigns a parameter that contains output from the Variable so that it can be bound to an InParameter of an instruction or act as the SourceParameter of another Variable.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:SourceParameterReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to an OutParameter that serves as the source for the content of this variable.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:SourceVariableReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to variable(s) used as a basis for recoding, derivation, or other means of calculating the data for this variable. This reference is intended to provide basic information on the source variable structure including value representation, measurement unit, etc. Note that if a variable is used by reference within multiple VariableSchemes you can identify its role within a specific VariableScheme by including that VariableScheme in the sourceContext attribute of the reference. Use ProcessingInstructionReference to provide additional information on the transformation of the source variable(s) into the data for this variable. If additional processing detail is required use the InParameter, OutParameter, and ParameterLinkage options in the GenerationInstruction and ProcessingInstructionReference.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="RepresentedVariableReference" minOccurs="0" maxOccurs="1">
						<xs:annotation>
							<xs:documentation>Reference to the RepresentedVariable that describes the core of this variable (the RepresentedVariable that the variable is the implementation of). The RepresentedVariable contains the broad reusable specification of the Variable, i.e., concept, universe, and value representation. These may be constrained by specifications within the Variable description. TypeOfObject should be set to RepresentedVariable.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptualVariableReference" minOccurs="0" maxOccurs="1">
						<xs:annotation>
							<xs:documentation>Reference to the ConceptualVariable that describes the core of this variable. The ConceptualVariable provides linked Concept and Universe specifications. These may be constrained by specifications within the Variable description. TypeOfObject should be set to ConceptualVariable.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement containing a description of the persons or other elements that this variable refers to, and to which any analytic results refer. If more than one universe is referenced the universe of the variable is the intersect of the referenced universes.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the concept measured by this variable.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:QuestionReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to question(s) used to collect data for this variable. This references the wording and response domain of the question, not the question flow (if the same question was asked in reference to multiple objects (i.e., Age of each child). Use SourceParameterReference and/or VariableRepresentation/ProcessingInstructionReference to differentiate sources associated with flow patterns or data processing instructions.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="EmbargoReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to any embargoes placed on the contents of this variable. Embargoes may limit access to the data and/or metadata to specific groups and/or for specified periods of time.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="SourceUnit" minOccurs="0">
						<xs:annotation>
							<xs:documentation>The normal source of the information contained in the variable. In the case of a survey this may be a respondent, proxy, interviewer, or other source. In the case of administrative data the position of a field on a form e.g., "top of page", "item 3", "generated by data processor", etc. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:AnalysisUnit" minOccurs="0">
						<xs:annotation>
							<xs:documentation>The entity to which the data refer, for example, individuals, families or households, groups, institutions/organizations, administrative units, etc. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="VariableRepresentation" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Describes the representation of the variable in the data set, including allowed content, data typing, and computation information.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="isTemporal" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>Set to "true" if the variable relays time-related information (date, time, season, relative time, etc.).</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="isGeographic" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>Set to "true" if the variable relays geographic information, i.e., geographic code, area name, relative location, etc.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="isWeight" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>Set to "true" if the variable is used a weight when analyzing data within the data set.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="VariableName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Variable using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="SourceUnit" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>The normal source of the information contained in the variable. In the case of a survey this may be a respondent, proxy, interviewer, or other source. In the case of administrative data the position of a field on a form e.g., "top of page", "item 3", "generated by data processor", etc. Supports the use of an external controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="VariableRepresentationType">
		<xs:annotation>
			<xs:documentation>Describes the representation of the variable in the data set. Describes the function of the variable, variables or standard weights that may be used to weight this variable during analysis, imputation and processing information, other variables used to create the value of this variable through concatenation, valid value representations (valid for analysis of respondents), missing value representations, aggregation methods used to generate the content of the variable, and additivity information.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="VariableRole" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Describes a specific function of the variable, such as identity, weight, geographic variable, time, date, currency, etc. This is a more extensive means of identifying the function of the variable than the Boolean indicators on the variable. Allows for agency specific designations. Supports the use of a controlled vocabulary.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:WeightVariableReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to one or more weight variables that may be used in analyzing this variable.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="StandardWeightReference" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Reference to the StandardWeight found in the Weighting description, which is relevant for analyzing this variable. A standard weight is a single weight used for all variables of a specific type or for a specified sub-universe.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="ImputationReference" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Reference to the imputation process described as a General Instruction in a ProcessingInstructionScheme.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="ConcatenatedValue" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Provides a reference to other variables and describes the method for deriving the value of this variable by concatenating a collection of other variables. This is useful in creating concatenated keys.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:ProcessingInstructionReference" minOccurs="0">
				<xs:annotation>
					<xs:documentation>A reference to either a general or generation instruction that was provided to those who converted information from one form to another to create a particular variable. This might include the reordering of numeric information into another form or the conversion of textual information into numeric information.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:choice minOccurs="0">
				<xs:element ref="r:ValueRepresentation">
					<xs:annotation>
						<xs:documentation>Describes the actual representation of the variables' values. Allows for the listing of values to be treated as missing in order to support 3.1 structures. The preferred method is the use of a reference to ManagedMissingValues description using MissingValuesReference. If both are used and there is a conflict in the content, MissingValuesReference will override the content provided in the ValueRepresentationReference.</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element ref="r:ValueRepresentationReference">
					<xs:annotation>
						<xs:documentation>Allows for the use of a ManagedRepresentation by reference. ValueRepresentationReference is the abstract head of a substitution group and may be replaced with any valid substitution for ValueRepresentationReference.</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:choice>
			<xs:element ref="MissingValuesReference" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Reference to an existing MissingValuesRepresentation using the Reference structure. If this content conflicts with content provided in the ValueRepresentation regarding Missing Values. The content of the MissingValuesRepresentation overrides. TypeOfObject will be MissingValuesRepresentation</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:MeasurementUnit" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Records the measurement unit, for example, 'km', 'miles', etc. Supports the use of a controlled vocabulary.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:ContentDateOffset" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Identifies the difference between the date applied to the data as a whole and this specific item such as previous year's income or residence 5 years ago.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:AggregationMethod" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Indicates the type of aggregation method used. Supports the use of a controlled vocabulary.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="additivity" type="AdditivityCodeType" use="optional">
			<xs:annotation>
				<xs:documentation>Records type of additivity, such as 'stock', 'flow', 'non-additive'.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:element name="MissingValuesReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing ManagedMissingValuesRepresentation using the Reference structure. TypeOfObject should be set to ManagedMissingValuesRepresentation.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="ConcatenatedValueType">
		<xs:annotation>
			<xs:documentation>Lists the variables whose values when concatenated result in the value for this variable.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="r:VariableReference" minOccurs="2" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Identifies the variables whose values are concatenated to form the concatenated variable. Note that the order of these variables determines the order of concatenation.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="GenerationType">
		<xs:annotation>
			<xs:documentation>Description of the process used to generate the category content. Includes a reference to component parts, a description of the generation process, a structured command, and other materials that are needed in the generation process. The item may be designated as a derivation process (default value) and be qualified in some way by a qualification attribute.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="ComponentReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to a category used in the generation process.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:Description" minOccurs="0">
				<xs:annotation>
					<xs:documentation>A description of the generation process. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:CommandCode" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Structured information used by a system to generate the category.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:OtherMaterial" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>External documentation required for creating the generation - for example, a chart or table for defining poverty.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="isDerived" type="xs:boolean" default="true">
			<xs:annotation>
				<xs:documentation>If not a derivation process set this attribute to "false".</xs:documentation>
			</xs:annotation>
		</xs:attribute>
		<xs:attribute name="qualification" type="xs:string" default="optional">
			<xs:annotation>
				<xs:documentation>A qualification for the generation process expressed as a simple string.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="VariableGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of Variables, which may be ordered or hierarchical. In addition to the name, label, and description of the group, the structure allows for defining the type of group using an optional controlled vocabulary, a reference to a defining universe or concept for the group, a subject classification for the group, and a listing of Variables and VariableGroups in any order.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="TypeOfVariableGroup" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A brief textual identification of the group type. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="VariableGroupName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the group. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the variable group. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the VariableGroup. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement describing the persons or other objects to which the contents of this variable group pertain.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the concept expressed by the Variables in this group.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Subject" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If subjects are listed for this group, it is strongly recommended that the subjects listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of subject at the group level allows for associating objects as a type of subject based group or to identify subject characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Keyword" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If keywords are listed for this group, it is strongly recommended that the keywords listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of keyword at the group level allows for associating objects as a type of keyword based group or to identify keyword characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="r:VariableReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent Variable.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="VariableGroupReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent VariableGroup. This allows for nesting of VariableGroups.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
				<xs:attribute name="isOrdered" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>If set to "true" indicates that the content of the group is ordered as it appears within the XML structure.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="VariableGroupName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Variable Group using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>


	<!-- nCUBES -->
	<xs:complexType name="NCubeSchemeType">
		<xs:annotation>
			<xs:documentation>A set of NCubes maintained by an agency and used to structure data items into relational structures. In addition to the standard name, label, and description of the scheme, contains descriptions of individual NCubes and NCubeGroups as well as allowing the inclusion of another NCubeScheme by reference.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="NCubeSchemeName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the NCubeScheme. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the NCubeScheme. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the NCubeScheme. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="NCube">
							<xs:annotation>
								<xs:documentation>Describes the logical structure of an NCube which is a 1..n dimension structure which relates a set of individual value to each other by defining them within a matrix.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:NCubeReference">
							<xs:annotation>
								<xs:documentation>Includes by reference a description of the logical structure of an NCube which is a 1..n dimension structure which relates a set of individual value to each other by defining them within a matrix. TypeOfObject should be set to NCube.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="NCubeGroup">
							<xs:annotation>
								<xs:documentation>Describes a group of NCubes for conceptual or administrative purposes, which may be ordered or hierarchical.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="NCubeGroupReference">
							<xs:annotation>
								<xs:documentation>Includes by reference a description of a group of NCubes for conceptual or administrative purposes, which may be ordered or hierarchical. TypeOfObject should be set to NCubeGroup.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:element ref="r:NCubeSchemeReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Allows for inclusion of other NCube schemes by reference.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="NCubeSchemeName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the NCube Scheme using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="AttributeType">
		<xs:annotation>
			<xs:documentation>An attribute may be any object which should be attached to all or part of the NCube. It may be defined as a Variable or contain textual content (such as a footnote).</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:IdentifiableType">
				<xs:sequence>
					<xs:choice>
						<xs:element ref="r:VariableReference">
							<xs:annotation>
								<xs:documentation>A reference to a variable that describes the attribute.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element name="AttachmentValue" type="xs:string">
							<xs:annotation>
								<xs:documentation>The value of the attachment expressed as a string, if not a variable.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:element ref="AttachmentRegionReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the CoordinateRegion that defines the attachment point for the attribute.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:MeasureDefinitionReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the MeasureDefinition that the attribute is attached to.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Value" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the specified Value of the MeasureDefinition that the attribute is attached to.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="attachmentLevel" type="AttachmentLevelCodeType" default="Cube">
					<xs:annotation>
						<xs:documentation>Describes the attachment level of the attribute as Cube, CoordinateRegion, Dimension, Measurement, or MeasurementValue.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:complexType name="NCubeType">
		<xs:annotation>
			<xs:documentation>An NCube is a 1..n dimension structure which relates a set of individual values to each other by defining them within a matrix. The NCube may be the result of aggregations, cross-tabulation, time-series, etc. The NCube is described by its dimensions which are represented by categorical variables (variables with a set number of values of specific definition that can be used to identify a specific cell as part of a matrix address). The resulting cells can contain one or more measures, also defined by variables. In addition to the standard name, label, and description of the NCube, it contains a reference to a universe, defines both the normal source of the data in the cells and unit of analysis, the purpose of creating the structured data, the dimensions and measures, as well as the ability to attached any other attribute (i.e., footnote, cell or region specific note) to a specified area of the NCube. Three attribute serve as informational check values; dimensionCount, cellCount, and isClean.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="NCubeName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the NCube. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the NCube. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and structure of the NCube. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to an imputation process described as a GeneralInstruction or GenerationInstruction held in a ProcessingInstructionScheme.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="ImputationReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>The normal source of the information contained in the NCube. In the case of a survey this may be a respondent, proxy, interviewer, or other source. In the case of administrative data the position of a field on a form e.g., "top of page", "item 3", "generated by data processor", etc.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="SourceUnit" minOccurs="0">
						<xs:annotation>
							<xs:documentation>The normal source of the information contained in the NCube. In the case of a survey this may be a respondent, proxy, interviewer, or other source. In the case of administrative data the position of a field on a form e.g., "top of page", "item 3", "generated by data processor", etc. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:AnalysisUnit" minOccurs="0">
						<xs:annotation>
							<xs:documentation>The entity to which the data refer, for example, individuals, families or households, groups, institutions/organizations, administrative units, etc. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Purpose" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Purpose for which the NCube was created. For example, designed to support a set of age pyramids generated yearly.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="Dimension" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>NCubes are defined by their dimensions. A dimension is provided a rank and a reference to a variable that describes it. Cell locations are "addressed" by the value of their intersect on each dimension provided in rank order.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="CoordinateRegion" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Defines the area of attachment for an attribute. It may be defined as the NCube as a whole or as certain dimensions or values of dimensions.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="MeasureDefinition" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Defines the structure and type of measure captured within the cells. This may be repeated to describe multiple measure for the cells (i.e., count, percent of universe, dimensional percent, index, text, suppression flag, etc.).</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="Attribute" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>An attribute may be any object which should be attached to all or part of the NCube. It may be defined as a Variable or contain textual content (such as a footnote).</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="dimensionCount" type="xs:integer" use="optional">
					<xs:annotation>
						<xs:documentation>The number of dimensions found in the NCube. Caution in using optional checksums is recommended. Conflict between checksums and the items being counted can cause problems with warning flags during processing. If using checksum to capture information for internal processing purposes, the use of automatically generated check sums is strongly urged.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="cellCount" type="xs:integer" use="optional">
					<xs:annotation>
						<xs:documentation>The number of cells (measures) found in the NCube. Note that this is the number of cells produced by dimension structure not the number of cells containing data in a sparse NCube. Caution in using optional checksums is recommended. Conflict between checksums and the items being counted can cause problems with warning flags during processing. If using checksum to capture information for internal processing purposes, the use of automatically generated check sums is strongly urged.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="isClean" type="xs:boolean" default="true">
					<xs:annotation>
						<xs:documentation>A value of "true" indicates that all cells have the potential for content values. If set to "false" Attribute and CoordinateRegion should be used to define the sparse areas of the NCube, those that have no content by definition. For example a cross-tabulation between Household Type (Family, Non-Family) and Number of persons in Household (1,2,3,4,5,6,7+) would need an attribute for Family/1 Person as this will always be empty due to the definition of Family as two or more related persons.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="NCubeName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the NCube using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="DataRelationshipType">
		<xs:annotation>
			<xs:documentation>Describes the relationships among logical records in the dataset. Date Relationship is needed to create the appropriate link between the logical record and the physical storage description. Data Relationship is optional because a logical product can contain only a category scheme and/or code scheme. In addition to the standard name, label, and description, it contains structures to describe the LogicalRecord and RecordRelationship.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="DataRelationshipName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the DataRelationship. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the DataRelationship. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the DataRelationship. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="LogicalRecord" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A logical record is a description of all of the elements (variables or NCubes) related to a single case or analysis unit. Required to link a description of a physical record structure to its logical record.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="RecordRelationship" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Describes the relationship between records of different types or of the same type within a longitudinal study. Identifies the key and linking value relationships. All relationships are pairwise. Multiple pairwise relationships maybe needed to clarify all record relationships within a logical product or data set.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="DataRelationshipName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Data Relationship using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="LogicalRecordType">
		<xs:annotation>
			<xs:documentation>A logical record is a description of all of the elements (variables or NCubes) related to a single case or analysis unit. Required to link a description of a physical record structure to its logical record. In addition to the standard name, label, and description, the structure identifies the variable designating its record type, describes case identification within the record type, indicates support for multiple storage segments, and defines a default set of missing values used by the record. In a data set with multiple records repeat to describe each logical record, such as a household, family, person, or event, record. A LogicalRecord is required to link a description of a physical record structure to its logical record.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:IdentifiableType">
				<xs:sequence>
					<xs:element ref="LogicalRecordName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the LogicalRecord. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the LogicalRecord. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the LogicalRecord. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="VariableValueReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A reference the variable containing the record type locator and the value being used. Files with single record types or which store records in different files may not have a record type locator. If this element is used set the attribute hasLocator to "true".</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="SupportForMultipleSegments" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Information concerning support for breaking the logical record into segments for storage purposes. Some files may be broken into record segments for storage but lack variables to support identification of specific segments. In this case segments are identified by their physical order within the storage file.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="CaseIdentification" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Describes the information needed to identify an individual case within a record type. This may be the variable or concatenated variable used to identify a unique case of a particular record type. Often referred to as a unique key. There may be more than one means of identifying a record. For example a US Census Summary File has a LogicalRecordIdentifier that is unique to the original file within which it was published. A specific geography has a set of fields that uniquely identify it.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0">
						<xs:element ref="VariablesInRecord">
							<xs:annotation>
								<xs:documentation>List of all variables used in the record, either directly or as found in a defined VariableGroup; note that a variable can be used in multiple records. The variables in the logical record can be noted by inclusion or exclusion to facilitate listing. The attribute allVariablesInLogicalProduct, when set to 'true', includes all variables in the LogicalProduct. VariableSchemeReference can then be used to exclude individual Variables schemes or include schemes from other logical products. In the same way VariableReference can be used to exclude specific variables from the previously defined variable set or include variables not already included. The simplest LogicalProduct descriptions with a single LogicalRecord can be described using only the attribute allVariablesInLogicalProduct with a value of true.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="NCubesInRecord">
							<xs:annotation>
								<xs:documentation>List of all NCubes used in the record, either directly or as found in a defined NCubeGroup; note that an NCube can be used in multiple records. The NCubes in the logical record can be noted by inclusion or exclusion to facilitate listing. The attribute allNCubesInLogicalProduct, when set to 'true', includes all NCubes in the LogicalProduct. NCubeSchemeReference can then be used to exclude individual NCubes schemes or include schemes from other logical products. In the same way NCubeReference can be used to exclude specific variables from the previously defined variable set or include variables not already included. The simplest LogicalProduct descriptions with a single LogicalRecord can be described using only the attribute allNCubesInLogicalProduct with a value of true.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:element ref="DefaultMissingValues" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Identifies the default missing value parameter for the this logical record by referencing a ManagedMissingValuesRepresentation or by stating that there is a default missing values parameter used but it is undocumented. Note that a conflicting DefaultMissingValues definition in a PhysicalInstance will override that found in the LogicalRecord.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="hasLocator" type="xs:boolean" use="optional">
					<xs:annotation>
						<xs:documentation>If "true" indicates that the record type has a field which identifies its record type. In logical structures with a single record type there is generally no identifier. Most multi-record files will have a variable that identifies the record type.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="variableQuantity" type="xs:integer" use="optional">
					<xs:annotation>
						<xs:documentation>Number of variables in the logical record. Caution in using optional checksums is recommended. Conflict between checksums and the items being counted can cause problems with warning flags during processing. If using checksum to capture information for internal processing purposes, the use of automatically generated check sums is strongly urged.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="LogicalRecordName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Logical Record using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>

	<xs:complexType name="NCubesInRecordType">
		<xs:annotation>
			<xs:documentation>Identifies the NCubes and any variables in the record external to NCube structures such as case identification variables that are contained in the logical record by indicating that all NCubes contained in the logical product are included, inclusion of a NCubeScheme to include, or listing individual NCubes to include. When the attribute allNCubesInLogicalProduct is set to "false" use the NCubeSchemeReference (which allows for exclusions) and NCubeReference to specify the included variables. A nested VariablesInRecord structure is used to include non-NCube variables in the record.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="VariablesInRecord" minOccurs="0">
				<xs:annotation>
					<xs:documentation>Use VariablesInRecord to describe any variables in the record that are external to the NCube such as case identifiers.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:NCubeSchemeReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to an NCubeScheme whose members are included in the logical record. Note that individual items may be excluded from the scheme if not used by the logical record.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:NCubeReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to an NCube to include in the logical record. This may be used to supplement the contents of an included NCubeScheme or to list all the variables individually.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="allNCubesInLogicalProduct" type="xs:boolean" use="optional">
			<xs:annotation>
				<xs:documentation>When the value is true, then the logical record contains all listed NCubes in the logical product module.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="VariableValueReferenceType">
		<xs:annotation>
			<xs:documentation>A reference to the variable containing the record type locator and the value being used. TypeOfObject should be set to Variable.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="r:VariableReference">
				<xs:annotation>
					<xs:documentation>Reference to the variable containing the record type locator.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="RelatedValue" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Value of variable indicating this record type, multiple entries allow for multiple valid values or ranges. Indicates if the variable should be equal to, greater than, less than, greater than or equal to, less than or equal to, or not equal to the stated value.(default value is "Equal"). Also allows the conditional value to be defined as blank (or no content).</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="VariablesInRecordType">
		<xs:annotation>
			<xs:documentation>Identifies the variables contained in the logical record by indicating that all variable contained in the logical product are included, inclusion of a scheme of variable to include, or listing individual variables to include. When the attribute allVariablesInLogicalProduct is set to "false" use the VariableSchemeReference (which allows for exclusions) and VariableUsedReference to specify the included variables.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="r:VariableSchemeReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to a VariableScheme whose members are included in the logical record. Note that individual items may be excluded from the scheme if not used by the logical record.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="VariableUsedReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to a variable to include in the logical record. This may be used to supplement the contents of an included VariableScheme or to list all the variables individually.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="allVariablesInLogicalProduct" type="xs:boolean" use="optional">
			<xs:annotation>
				<xs:documentation>Set to "true" when the logical record contains all the variables identified within the logical product module.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="CaseIdentificationType">
		<xs:annotation>
			<xs:documentation>Describes the information needed to identify an individual case within a record type. This may be the variable or concatenated variable used to identify a unique case of a particular record type. Often referred to as a unique key. There may be more than one means of identifying a record. For example a US Census Summary File has a LogicalRecordIdentifer that is unique to the original file within which it was published. A specific geography has a set of fields that uniquely identify it.</xs:documentation>
		</xs:annotation>
		<xs:choice minOccurs="0">
			<xs:element ref="FixedIdentifier">
				<xs:annotation>
					<xs:documentation>Reference to the variable containing the unique identifier. This may be a concatenated variable which indicates the combination of variable required to create a unique identification. If more than one variable reference is included the combination of the variable field contents must be unique and all variables are required for case identification.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="ConditionalIdentifier">
				<xs:annotation>
					<xs:documentation>Describes the information needed to identify a specific record or case within a record type. Repeating the field allows multiple means of identifying a case referencing multiple variables.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:choice>
		<xs:attribute name="isPrimary" type="xs:boolean" default="true">
			<xs:annotation>
				<xs:documentation>Indicates whether the case identifier is the primary key.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:element name="FixedIdentifier" type="FixedIdentifierType">
		<xs:annotation>
			<xs:documentation>Reference to the variable containing the unique identifier.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="FixedIdentifierType">
		<xs:annotation>
			<xs:documentation>Reference to the variable containing the unique identifier. This may be a concatenated variable which indicates the combination of variable required to create a unique identification. If more than one variable reference is included the combination of the variable field contents must be unique and all variables are required for case identification.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="r:VariableReference" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Reference to a variable used as a fixed identifier either singly or in combination with additional reference variables.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:element name="ConditionalIdentifier" type="ConditionalIdentifierType">
		<xs:annotation>
			<xs:documentation>Reference to the variable containing the unique identifier given the conditional value.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="ConditionalIdentifierType">
		<xs:annotation>
			<xs:documentation>Describes the information needed to identify a specific record or case within a record type. Repeating the field allows multiple means of identifying a case referencing multiple variables.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="CaseSpecification" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>Case specification allows different unique identifiers to be used based on the value of an identified variable. In some cases the value of a variable (such as a geographic level) results in a different set of variables required to identify a unique case. Case specification is used to capture these combinations. For example: a file containing State, County, and Place records. The unique identifier for a State requires a combination of GeoLevel=State and the variable STATE. Place would require a combination of GeoLevel=Place and the variables STATE and PLACE.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="CaseSpecificationType">
		<xs:annotation>
			<xs:documentation>Case specification allows different unique identifiers to be used based on the value of an identified variable. In some cases the value of a variable (such as a geographic level) results in a different set of variables required to identify a unique case. Case specification is used to capture these combinations. For example: a file containing State, County, and Place records. The unique identifier for a State requires a combination of GeoLevel=State and the variable STATE. Place would require a combination of GeoLevel=Place and the variables STATE and PLACE.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="ConditionalVariableReference">
				<xs:annotation>
					<xs:documentation>References the variable containing the conditional content, provides the value of the condition.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="r:VariableReference" minOccurs="1" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>The variables required to provide a unique identification when the conditional variable contains the stated value.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:element name="ConditionalVariableReference" type="ConditionalVariableReferenceType">
		<xs:annotation>
			<xs:documentation>Value of variable indicating this record type. TypeOfObject should be set to Variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="ConditionalVariableReferenceType">
		<xs:annotation>
			<xs:documentation>Value of variable indicating this record type, multiple entries allow for multiple valid values or ranges. Includes a reference to the variable an the specified related value. TypeOfObject should be set to Variabele.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:ReferenceType">
				<xs:sequence>
					<xs:element ref="RelatedValue">
						<xs:annotation>
							<xs:documentation>Use to specify the value of variable for which this is a case specification (i.e., GeoLevel in the example for Case Specification).</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:complexType name="RecordRelationshipType">
		<xs:annotation>
			<xs:documentation>Describes the relationship between records of different types or of the same type within a longitudinal study. Identifies the key and linking value relationships. All relationships are pairwise. Multiple pairwise relationships maybe needed to clarify all record relationships within a logical product or data set. In addition to the standard name, label, and description, the structure identifies the pair of logical records for which the relationship is defined as SourceLogicalRecord and TargetLogicalRecord, describes the link between these two records and indicates the relationship of the of the source record to the target record.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:IdentifiableType">
				<xs:sequence>
					<xs:element ref="RecordRelationshipName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the RecordRelationship. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the RecordRelationship. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the RecordRelationship. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="SourceLogicalRecordReference">
						<xs:annotation>
							<xs:documentation>A reference to the Logical Record acting as the Source Record. All relationship information is from the source to the target. If the relationship is not unidirectional (i.e., sibling) simply assign one record as the source and the other as the target.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="TargetLogicalRecordReference">
						<xs:annotation>
							<xs:documentation>A reference to the Logical Record acting as the Target Record.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="SourceTargetLink" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Each SourceTargetLink provides a pair of variables which act as all or part of a link between the source and the target records. Repeat if more than one set of variables is required to make the link.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:attribute name="relationToTarget" type="RelationCodeType" default="Unknown">
					<xs:annotation>
						<xs:documentation>Indicates the relationship of the source to the target. The value describes the role of the source in the relationship. This is a restricted list of Parent, Child, Sibling, Unknown.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="RecordRelationshipName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Record Relationship using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="SourceTargetLink" type="SourceTargetLinkType">
		<xs:annotation>
			<xs:documentation>Contains a set of variables, one from the source record and one from the target record used as all or part of a link between the source and target records.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="SourceTargetLinkType">
		<xs:annotation>
			<xs:documentation>Contains a set of variables, one from the source record and one from the target record used as all or part of a link between the source and target records.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="SourceLinkVariableReference">
				<xs:annotation>
					<xs:documentation>A reference to the variable in the Source Record containing the value that is equal to the value in the identified variable in the Target Record.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element ref="TargetLinkVariableReference">
				<xs:annotation>
					<xs:documentation>A reference to the variable in the Target Record containing the value that is equal to the value in the identified variable in the Source Record.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:element name="SourceLogicalRecordReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing LogicalRecord using the Reference structure. TypeOfObject should be set to LogicalRecord.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="TargetLogicalRecordReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing LogicalRecord using the Reference structure. TypeOfObject should be set to LogicalRecord.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="TargetLinkVariableReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing Variable using the Reference structure. TypeOfObject should be set to Variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="SourceLinkVariableReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing Variable using the Reference structure. TypeOfObject should be set to Variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="RelatedValueType">
		<xs:annotation>
			<xs:documentation>The characteristic value expressed as a string with an indicator of the specific relationship of the variable value to the characteristic value. The default is "Equal". The value may be defined as containing no content (blank) by setting the attribute valueIsBlank to "true".</xs:documentation>
		</xs:annotation>
		<xs:simpleContent>
			<xs:extension base="r:ValueType">
				<xs:attribute name="type" type="RelatedValueTypeCodeType" default="Equal">
					<xs:annotation>
						<xs:documentation>Indicates value type as "GreaterThan", LessThan", "Equal", "GreaterThanOrEqual", "LessThanOrEqual", or "NotEqual".</xs:documentation>
					</xs:annotation>
				</xs:attribute>
				<xs:attribute name="valueIsBlank" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>Set to "true" if the value of the conditional variable is blank.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:simpleContent>
	</xs:complexType>
	<xs:simpleType name="IsComprehensiveType">
		<xs:annotation>
			<xs:documentation>Indicates the values are comprehensive, they cover all possible values. If the data collected for these values is additive the sum of the values should equal the value of the parent.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="True">
				<xs:annotation>
					<xs:documentation>True, the values are comprehensive.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="False">
				<xs:annotation>
					<xs:documentation>False, the values are not comprehensive, some possible values have not been included. These should be treated as a specified sub-set of the parent.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Unknown">
				<xs:annotation>
					<xs:documentation>Unknown, the documentation is lacking to make an assertion as to whether the values listed are comprehensive.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="RelatedValueTypeCodeType">
		<xs:annotation>
			<xs:documentation>Indicates the relationship of the value of a source object to a target object. Except in the case of equality or non-equality of the relationship is unidirectional (source to target).</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="GreaterThan">
				<xs:annotation>
					<xs:documentation>The value of the source object is greater than the value of the target object.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="LessThan">
				<xs:annotation>
					<xs:documentation>The value of the source object is less than the value of the target object.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Equal">
				<xs:annotation>
					<xs:documentation>The value of the source object is equal to the value of the target object.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="GreaterThanOrEqual">
				<xs:annotation>
					<xs:documentation>The value of the source object is greater than or equal to the value of the target object.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="LessThanOrEqual">
				<xs:annotation>
					<xs:documentation>The value of the source object is less than or equal to the value of the target object.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="NotEqual">
				<xs:annotation>
					<xs:documentation>The value of the source object is not equal the value of the target object.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="RelationCodeType">
		<xs:annotation>
			<xs:documentation>Indicates the relationship of a source object to a target object. Except in the case of sibling the relationship is unidirectional (source to target).</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="Parent">
				<xs:annotation>
					<xs:documentation>The source object is the parent of the target object. The target object is a sub-part or member of the parent source.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Child">
				<xs:annotation>
					<xs:documentation>The source object is the child of the source object. The target object is the parent or contains the source object as a sub-part or member.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Sibling">
				<xs:annotation>
					<xs:documentation>The source object is the sibling of the target object. One object is not a member of or subsidiary to the other. They may be equal members of the same group.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Unknown">
				<xs:annotation>
					<xs:documentation>The relationship between the source and target objects is unknown.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:complexType name="NCubeGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of NCubes, which may be ordered or hierarchical. In addition to the name, label, and description of the group, the structure allows for defining the type of group using an optional controlled vocabulary, a reference to a defining universe or concept for the group, and a listing of NCubes and NCubeGroups in any order.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="TypeOfNCubeGroup" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A brief textual identification of the group type. Supports the use of an external controlled vocabulary.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="NCubeGroupName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the group. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the NCube group. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the NCubeGroup. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement describing the persons or other objects to which the contents of this NCube group pertain.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the concept expressed by the NCubes in this group.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Subject" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If subjects are listed for this group, it is strongly recommended that the subjects listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of subject at the group level allows for associating objects as a type of subject based group or to identify subject characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Keyword" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If keywords are listed for this group, it is strongly recommended that the keywords listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of keyword at the group level allows for associating objects as a type of keyword based group or to identify keyword characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="r:NCubeReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent NCube.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="NCubeGroupReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent NCubeGroup. This allows for nesting of NCubeGroups.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
				<xs:attribute name="isOrdered" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>If set to "true" indicates that the content of the group is ordered as it appears within the XML structure.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="NCubeGroupName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the NCube Scheme using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="CoordinateRegionType">
		<xs:annotation>
			<xs:documentation>Defines the area of attachment for an NCube attribute. It may be defined as the NCube as a whole or as certain dimensions or values of dimensions.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:IdentifiableType">
				<xs:sequence>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the CoordinateRegion. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement containing a description of the persons or other elements that this CoordinateRegion refers to, and to which any analytic results refer. If more than one universe is referenced the universe of the CoordinateRegion is the intersect of the referenced universes. Use when the CoordinateRegion describes a subset of the NCube universe.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content of the CoordinateRegion. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="DimensionValue" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Defines the included set of values needed to describe the coordinate region of the NCube on a Dimension by Dimension basis.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:complexType name="CohortType">
		<xs:annotation>
			<xs:documentation>Defines the included values of a dimension by means of individual value references or by defining a range of values to include. Allows the included values to be identified by reference to the Code, the Category used by the Code, or the Value of the Code (which by definition should be unique). The dimension is identified by its rank value.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:choice>
				<xs:sequence>
					<xs:element ref="r:CategoryReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the Category represented by the Value of the Code assigned in a CodeList. Repeat for including multiple values.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:sequence>
					<xs:element ref="r:CodeReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the Code within the CodeList used by the variable describing the dimension. Repeat for including multiple values.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
				<xs:sequence>
					<xs:element ref="r:Range" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Use when multiple values are included. This uses the unique Value provided for the Code as a means of identification. Provides the range of Values for this dimension that are within the area being defined. Repeat for non-contiguous values.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:choice>
		</xs:sequence>
		<xs:attribute name="rank" type="xs:integer" use="required">
			<xs:annotation>
				<xs:documentation>Identify the dimension being described by its rank value within the NCube description.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="DimensionType">
		<xs:annotation>
			<xs:documentation>A dimension is provided a rank and a reference to a variable that describes it. Cell locations are "addressed" by the value of their intersect on each dimension provided in rank order.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element ref="r:VariableReference">
				<xs:annotation>
					<xs:documentation>Identifies the variable describing this dimension. The dimension uses the CodeList and related categories, or a fixed range of numeric values to define the labels and intersect points for the dimension. The data set will contain a value for each cell in the NCube rather than the code from the CodeList.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="rank" type="xs:integer" use="required">
			<xs:annotation>
				<xs:documentation>The rank order of this dimension (the order in which the value for this dimension will appear in the cell address)denoted with a 1-based indexing. Provides coordinate order (1,2,n) for the intersect point of this dimension within the cell address. For example, if the rank of this dimension is 2, the intersect point on this dimension will be the second value listed in the cell address.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<xs:complexType name="MeasureDefinitionType">
		<xs:annotation>
			<xs:documentation>Defines the structure and type of measure captured within the cells. This may be repeated to describe multiple measure for the cells (i.e., count, percent of universe, dimensional percent, index, text, suppression flag, etc.). Includes a reference to the defining variable and an optional aggregation definition for use in defining content relying on the use of independent and dependent variables (such as the percentage of a specific dimension (like a row or column percent on a table).</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:IdentifiableType">
				<xs:sequence>
					<xs:element ref="r:VariableReference">
						<xs:annotation>
							<xs:documentation>A reference to the variable that defines the measure of the NCube.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="AggregationDefinition" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Identifies the independent (denominator) and dependent (numerator) dimensions for calculating aggregate measures such as percent. When two or more independent or dependent dimensions are listed here, the value is defined as the intersection of the listed dimensions.</xs:documentation>
						</xs:annotation>
					</xs:element>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="AggregationDefinition" type="AggregationDefinitionType">
		<xs:annotation>
			<xs:documentation>Identifies the independent (denominator) and dependent (numerator) dimensions for calculating aggregate measures such as percent.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="AggregationDefinitionType">
		<xs:annotation>
			<xs:documentation>Identifies the independent (denominator) and dependent (numerator) dimensions for calculating aggregate measures such as percent. When two or more independent or dependent dimensions are listed here, the value is defined as the intersection of the listed dimensions.</xs:documentation>
		</xs:annotation>
		<xs:sequence>
			<xs:element name="IndependentDimension" type="xs:integer" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>The rank of a dimension that acts as the denominator (independent variable).</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="DependentDimension" type="xs:integer" minOccurs="0" maxOccurs="unbounded">
				<xs:annotation>
					<xs:documentation>The rank of a dimension that acts as the numerator (dependent variable).</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:sequence>
		<xs:attribute name="isNCubeUniverse" type="xs:boolean" default="true">
			<xs:annotation>
				<xs:documentation>When true indicates that total count of the NCube as described by the universe acts as the independent variable (denominator) and that all dimensions are used to define the dependent variable (numerator). When false, use the IndependentDimension and DependentDimension elements to assign each rank to its appropriate role.</xs:documentation>
			</xs:annotation>
		</xs:attribute>
	</xs:complexType>
	<!-- code schemes -->

	<xs:simpleType name="AdditivityCodeType">
		<xs:annotation>
			<xs:documentation>Describes the nature of additivity for the content. By designating the type of content, a user will understand whether the contents can be summed or must be treated differently in terms of processing an aggregation.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="Stock">
				<xs:annotation>
					<xs:documentation>A count of objects at one specific time. In general items in a non-hierarchical table of Stock figures can be added together to determine the total.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Flow">
				<xs:annotation>
					<xs:documentation>A measure that is taken over time and should be treated as the number of items per a unit of time. Analogous to a rate or a speed.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="NonAdditive">
				<xs:annotation>
					<xs:documentation>Due to the nature of the content or the measure, these data cannot be aggregated to determine a sum or accounting of activity.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>

	<xs:simpleType name="HierarchyCodeType">
		<xs:annotation>
			<xs:documentation>Defines the type of hierarchical structure as Regular or Irregular.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="Regular">
				<xs:annotation>
					<xs:documentation>A hierarchy where each section has the same number of nested levels, i.e., the lowest level represents the most discrete values.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Irregular">
				<xs:annotation>
					<xs:documentation>A hierarchy where each section can vary in the number of nested levels it contains. The most discrete objects in an irregular hierarchy must be individually identified.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:simpleType name="AttachmentLevelCodeType">
		<xs:annotation>
			<xs:documentation>Identifies the contextual level of an NCube to which the attribute is attached; the full cube, a specific set of coordinates, a full dimension, a specific measurement, or a specific measurement value.</xs:documentation>
		</xs:annotation>
		<xs:restriction base="xs:NMTOKEN">
			<xs:enumeration value="Cube">
				<xs:annotation>
					<xs:documentation>Attaches to the whole NCube.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="CoordinateRegion">
				<xs:annotation>
					<xs:documentation>Attaches to a group of cells described by a coordinate region which specifies the range of coordinate values contained within the region.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Dimension">
				<xs:annotation>
					<xs:documentation>Attaches to a full dimension.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="Measurement">
				<xs:annotation>
					<xs:documentation>Attaches to a specific measurement type.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
			<xs:enumeration value="MeasurementValue">
				<xs:annotation>
					<xs:documentation>Attaches to a specific value of a specified measurement.</xs:documentation>
				</xs:annotation>
			</xs:enumeration>
		</xs:restriction>
	</xs:simpleType>
	<xs:element name="TypeOfVariableGroup" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>A brief textual description or classification of the created to associate a number of variables. Supports the use of an external controlled vocabulary. DDI strongly recommends the use of a controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="TypeOfNCubeGroup" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>A brief textual description or classification of the created to associate a number of NCubes. Supports the use of an external controlled vocabulary. DDI strongly recommends the use of a controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CategoryScheme" type="CategorySchemeType">
		<xs:annotation>
			<xs:documentation>A scheme containing a set of Categories managed by an agency.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CodeList" type="CodeListType">
		<xs:annotation>
			<xs:documentation>A structure used to associate a list of code values to specified categories. May be flat or hierarchical.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="NCubeScheme" type="NCubeSchemeType">
		<xs:annotation>
			<xs:documentation>A set of NCubes maintained by an agency and used to structure data items into relational structures.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableScheme" type="VariableSchemeType">
		<xs:annotation>
			<xs:documentation>Contains a set of Variables and VariableGroups.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="DataRelationship" type="DataRelationshipType">
		<xs:annotation>
			<xs:documentation>Describes the relationships among logical records in the dataset. Date Relationship is needed to create the appropriate link between the logical record and the physical storage description.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Category" type="CategoryType">
		<xs:annotation>
			<xs:documentation>A description of a particular category or response.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CategoryGroup" type="CategoryGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of Category descriptions, which may be ordered or hierarchical.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Generation" type="GenerationType">
		<xs:annotation>
			<xs:documentation>Description of the process used to generate the category content.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="HierarchyType" type="HierarchyCodeType">
		<xs:annotation>
			<xs:documentation>Defines the type of hierarchical structure as Regular or Irregular.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Level" type="LevelType">
		<xs:annotation>
			<xs:documentation>Used to describe the levels of the code list hierarchy.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Code" type="CodeType">
		<xs:annotation>
			<xs:documentation>A structure that links a unique value of a code to a specified category .</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CategoryRelationship" type="r:CategoryRelationCodeType">
		<xs:annotation>
			<xs:documentation>Describes the relationship between the categories in terms of the significance of order and the distance between categories.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Interval" type="IntervalType">
		<xs:annotation>
			<xs:documentation>Describes the structure, starting point and increment step of an interval.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Variable" type="VariableType">
		<xs:annotation>
			<xs:documentation>Describes the structure of a Variable. This is the applied expression of a data item within a data set.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableGroup" type="VariableGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of Variables, which may be ordered or hierarchical.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableGroupReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing VariableGroup using the Reference structure. TypeOfObject should be set to VariableGroup.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="EmbargoReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing Embargo using the Reference structure. TypeOfObject should be set to Embargo.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableRepresentation" type="VariableRepresentationType">
		<xs:annotation>
			<xs:documentation>Describes the representation of the variable in the data set. TypeOfObject should be set to ManagedDateTimeRepresentation, ManagedNumericRepresentation, ManagedRepresentationGroup, ManagedRepresentationScheme, ManagedScaleRepresentation, or ManagedTextRepresentation.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="StandardWeightReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing StandardWeight using the Reference structure. TypeOfObject should be set to StandardWeight.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="ImputationReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing GenerationInstruction or GeneralInstruction using the Reference structure. TypeOfObject should be set to GenerationInstruction or GeneralInstruction.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="ConcatenatedValue" type="ConcatenatedValueType">
		<xs:annotation>
			<xs:documentation>Lists the variables whose values when concatenated result in the value for this variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="ComponentReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing Category using the Reference structure. TypeOfObject should be set to Category.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="NCube" type="NCubeType">
		<xs:annotation>
			<xs:documentation>An NCube is a 1..n dimension structure which relates a set of individual values to each other by defining them within a matrix.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="NCubeGroup" type="NCubeGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of NCubes, which may be ordered or hierarchical.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="AttachmentRegionReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing CoordinateRegion using the Reference structure. TypeOfObject should be set to CoordinateRegion.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CoordinateRegion" type="CoordinateRegionType">
		<xs:annotation>
			<xs:documentation>Defines the area of attachment for an NCube attribute.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Dimension" type="DimensionType">
		<xs:annotation>
			<xs:documentation>A dimension is provided a rank and a reference to a variable that describes it.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="MeasureDefinition" type="MeasureDefinitionType">
		<xs:annotation>
			<xs:documentation>Defines the structure and type of measure captured within the cells.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="Attribute" type="AttributeType">
		<xs:annotation>
			<xs:documentation>An attribute may be any object which should be attached to all or part of the NCube.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="NCubeGroupReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing NCubeGroup using the Reference structure. TypeOfObject should be set to NCubeGroup.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="DimensionValue" type="CohortType">
		<xs:annotation>
			<xs:documentation>Defines the included values of a dimension.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="LogicalRecord" type="LogicalRecordType">
		<xs:annotation>
			<xs:documentation>A logical record is a description of all of the elements (variables or NCubes) related to a single case or analysis unit.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="RecordRelationship" type="RecordRelationshipType">
		<xs:annotation>
			<xs:documentation>Describes the relationship between records of different types or of the same type within a longitudinal study. Identifies the key and linking value relationships.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="RelatedValue" type="RelatedValueType">
		<xs:annotation>
			<xs:documentation>The characteristic value expressed as a string with an indicator of the specific relationship of the variable value to the characteristic value. The default is "Equal".</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableValueReference" type="VariableValueReferenceType">
		<xs:annotation>
			<xs:documentation>A reference the variable containing the record type locator and the value being used. Variable</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableUsedReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing Variable using the Reference structure. TypeOfObject should be set to Variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="SupportForMultipleSegments" type="VariableValueReferenceType">
		<xs:annotation>
			<xs:documentation>A reference the variable containing the segment locator and the value being used. TypeOfObject should be set to Variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CaseIdentification" type="CaseIdentificationType">
		<xs:annotation>
			<xs:documentation>Describes the information needed to identify an individual case within a record type</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariablesInRecord" type="VariablesInRecordType">
		<xs:annotation>
			<xs:documentation>Identifies the variables contained in the logical record.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="CaseSpecification" type="CaseSpecificationType">
		<xs:annotation>
			<xs:documentation>Case specification allows different unique identifiers to be used based on the value of an identified variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="NCubesInRecord" type="NCubesInRecordType">
		<xs:annotation>
			<xs:documentation>Identifies the NCubes and any variables in the record external to NCube structures.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="LevelName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the Level using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="VariableRole" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>Describes a specific function of the variable, such as identity, weight, geographic variable, time, date, currency, etc. Supports the use of an external controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="DefaultMissingValues" type="DefaultMissingValuesType">
		<xs:annotation>
			<xs:documentation>Identifies the default missing value parameter for the this logical record by referencing a ManagedMissingValuesRepresentation or by stating that there is a default missing values parameter used but it is undocumented.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="DefaultMissingValuesType">
		<xs:annotation>
			<xs:documentation>Identifies the default missing value parameter for the this logical record by referencing a ManagedMissingValuesRepresentation or by stating that there is a default missing values parameter used but it is undocumented. Note that a conflicting DefaultMissingValues definition in a PhysicalInstance will override that found in the LogicalRecord.</xs:documentation>
		</xs:annotation>
		<xs:choice minOccurs="0">
			<xs:element ref="MissingValuesReference">
				<xs:annotation>
					<xs:documentation>Reference to the appropriate ManagedMissingValuesRepresentation describing the default values.</xs:documentation>
				</xs:annotation>
			</xs:element>
			<xs:element name="DefaultUsedNoDocumentation" type="xs:boolean" fixed="true">
				<xs:annotation>
					<xs:documentation>Use when it is known that a default missing values definition was use but there is NO documentation describing its content.</xs:documentation>
				</xs:annotation>
			</xs:element>
		</xs:choice>
	</xs:complexType>
	<xs:element name="RepresentedVariableScheme" type="RepresentedVariableSchemeType">
		<xs:annotation>
			<xs:documentation>A set of RepresentedVariables managed by an agency. RepresentedVariables are the core reusable parts of a Variable. RepresentedVariable maps to the GSIM Represented Variable. In addition to the standard name, label, and description, allows for the inclusion of an existing RepresentedVariableScheme by reference and RepresentedVariables either in-line or by reference. RepresentedVariables may be grouped for management purposes.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="RepresentedVariableSchemeType">
		<xs:annotation>
			<xs:documentation>A set of RepresentedVariables managed by an agency. RepresentedVariables are the core reusable parts of a Variable. RepresentedVariable maps to the GSIM Represented Variable. In addition to the standard name, label, and description, allows for the inclusion of an existing RepresentedVariableScheme by reference and RepresentedVariables either in-line or by reference. RepresentedVariables may be grouped for management purposes.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:MaintainableType">
				<xs:sequence>
					<xs:element ref="RepresentedVariableSchemeName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the RepresentedVariableScheme. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the RepresentedVariableScheme. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the RepresentedVariableScheme. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:RepresentedVariableSchemeReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Inclusion of an existing RepresentedVariableScheme by reference. TypeOfObject should be set to RepresentedVariableScheme</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="RepresentedVariable">
							<xs:annotation>
								<xs:documentation>Describes a RepresentedVariable contained in the RepresentedVariableScheme. A RepresentedVariable contains a reference to the Concept and Universe (or ConceptualVariable) as well as the representation of the RepresentedVariable. Representation may be provided in-line or by reference to a managed representation. RepresentedVariables are the core reusable parts of a Variable. RepresentedVariable maps to the GSIM Represented Variable.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="RepresentedVariableReference">
							<xs:annotation>
								<xs:documentation>Inclusion of an existing RepresentedVariable by reference. TypeOfObject should be set to RepresentedVariable.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="RepresentedVariableGroup">
							<xs:annotation>
								<xs:documentation>In-line description of a group of RepresentedVariables. RepresentedVariables may be grouped for a wide range of reasons including conceptual or universe grouping, usage, subject or keyword relationships, or other grouping reason that will assist in the management of a group of RepresentedVariables.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="RepresentedVariableGroupReference">
							<xs:annotation>
								<xs:documentation>The inclusion of an existing RepresentedVariableGroup by reference. TypeOfObject should be RepresentedVariableGroup.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="RepresentedVariableSchemeName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the RepresentedVariableScheme using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="RepresentedVariableGroupReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing RepresentedVariableGroup using the Reference structure. TypeOfObject should be RepresentedVariableGroup.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="RepresentedVariableGroup" type="RepresentedVariableGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of RepresentedVariables.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="RepresentedVariableGroupType">
		<xs:annotation>
			<xs:documentation>Contains a group of RepresentedVariables, which may describe an ordered or hierarchical relationship structure. RepresentedVariables may be grouped for a wide range of reasons including conceptual or universe grouping, usage, subject or keyword relationships, or other grouping reason that will assist in the management of a group of RepresentedVariables. Specifies the purpose of the group, a name, label, and description of the group, its relationship to a specific universe or concept, and lists the members of the group.</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="TypeOfRepresentedVariableGroup" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A generic element for specifying a reason for a RepresentedVariableGroup. Note that this element can contain either a term from a controlled vocabulary list or a textual description.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="RepresentedVariableGroupName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the group. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the RepresentedVariableGroup. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the content and purpose of the RepresentedVariableGroup. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>Reference to the universe statement describing the persons or other objects to which the contents of this group pertain. TypeOfObject should be set to Universe.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:ConceptReference" minOccurs="0">
						<xs:annotation>
							<xs:documentation>Reference to the concept expressed by the objects in this group. TypeOfObject should be set to Concept.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Subject" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If subjects are listed for this group, it is strongly recommended that the subjects listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of subject at the group level allows for associating objects as a type of subject based group or to identify subject characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Keyword" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>If keywords are listed for this group, it is strongly recommended that the keywords listed also be found in the TopicalCoverage element for the parent packaging element when this group is included directly or by reference in a module containing a coverage element. Use of keyword at the group level allows for associating objects as a type of keyword based group or to identify keyword characteristics of a reusable group of objects.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice minOccurs="0" maxOccurs="unbounded">
						<xs:element ref="RepresentedVariableReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent RepresentedVariable (from the substitution group). TypeOfObject should be set to RepresentedVariable.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="RepresentedVariableGroupReference">
							<xs:annotation>
								<xs:documentation>Reference to constituent RepresentedVariableGroup. This allows for nesting of RepresentedVariableGroups. TypeOfObject should be set to RepresentedVariableGroup.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
				<xs:attribute name="isOrdered" type="xs:boolean" default="false">
					<xs:annotation>
						<xs:documentation>If set to "true" indicates that the content of the group is ordered as it appears within the XML structure.</xs:documentation>
					</xs:annotation>
				</xs:attribute>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="RepresentedVariableGroupName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the InstructionGroup using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="TypeOfRepresentedVariableGroup" type="r:CodeValueType">
		<xs:annotation>
			<xs:documentation>A brief textual description of the type of group created to associate a number of Instructions. Supports the use of an external controlled vocabulary.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="RepresentedVariable" type="RepresentedVariableType">
		<xs:annotation>
			<xs:documentation>Describes a RepresentedVariable contained in the RepresentedVariableScheme. A RepresentedVariable contains a reference to the Concept and Universe (or ConceptualVariable) as well as the representation of the RepresentedVariable. Representation may be provided in-line or by reference to a managed representation. RepresentedVariables are the core reusable parts of a Variable. RepresentedVariable maps to the GSIM Represented Variable.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:complexType name="RepresentedVariableType">
		<xs:annotation>
			<xs:documentation>Describes a RepresentedVariable contained in the RepresentedVariableScheme. In addition to the standard name, label, and description a RepresentedVariable contains a reference to the Concept and Universe (or ConceptualVariable) as well as the representation of the RepresentedVariable. Representation may be provided in-line or by reference to a managed representation. RepresentedVariables are the core reusable parts of a Variable. RepresentedVariable maps to the GSIM Represented Variable. In addition to the standard name, label, and description</xs:documentation>
		</xs:annotation>
		<xs:complexContent>
			<xs:extension base="r:VersionableType">
				<xs:sequence>
					<xs:element ref="RepresentedVariableName" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A name for the RepresentedVariable. May be expressed in multiple languages. Repeat the element to express names with different content, for example different names for different systems.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Label" minOccurs="0" maxOccurs="unbounded">
						<xs:annotation>
							<xs:documentation>A display label for the RepresentedVariable. May be expressed in multiple languages. Repeat for labels with different content, for example, labels with differing length limitations.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:element ref="r:Description" minOccurs="0">
						<xs:annotation>
							<xs:documentation>A description of the RepresentedVariable. May be expressed in multiple languages and supports the use of structured content.</xs:documentation>
						</xs:annotation>
					</xs:element>
					<xs:choice>
						<xs:element ref="r:ConceptualVariableReference" minOccurs="0" maxOccurs="1">
							<xs:annotation>
								<xs:documentation>A reference to a ConceptualVariable which provides the linkage to the Universe and Concept used by this RepresentedVariable. TypeOfObject should be set to ConceptualVariable.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:sequence>
							<xs:element ref="r:UniverseReference" minOccurs="0" maxOccurs="1">
								<xs:annotation>
									<xs:documentation>Reference to the universe statement containing a description of the widest possible group of persons or other elements that this RepresentedVariable refers to, and to which any analytic results refer. TypeOfObject should be set to Universe.</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element ref="r:ConceptReference" minOccurs="0" maxOccurs="1">
								<xs:annotation>
									<xs:documentation>Reference to the concept measured by this RepresentedVariable. TypeOfObject should be set to Concept.</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:sequence>
					</xs:choice>
					<xs:choice minOccurs="0">
						<xs:element ref="r:CategorySchemeReference">
							<xs:annotation>
								<xs:documentation>Reference to a category scheme that contains the representation domain of the RepresentedVariable. Use this element when only the category specifications are provided. If both a code and the related category must be specified use CodeRepresentation (member of the substitution group ValueRepresentation). TypeOfObject should be set to CategoryScheme.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:ValueRepresentation">
							<xs:annotation>
								<xs:documentation>Describes the actual representation of the RepresentedVariables' values. ValueRepresentation is the head of a substitution group which supports a number of representation types, i.e. CodeRepresentation, NumericRepresentation, TextRepresentation, DateTimeRepresentation, ScaleRepresentation, GeographicStructureCodeRepresentation, and GeographicLocationCodeRepresentation. Although the structure allows for specification of missing values these features should be used with caution. Like the definition of the universe and concept, the specification of the representation can be constrained by the Variable (the GSIM ImplementedVariable), for example a NumericRepresentation could be constrained with a lower top coding specification. Missing Values can be assigned separately by the Variable without impact on the ValueRepresentation of the specified valid values provided here.</xs:documentation>
							</xs:annotation>
						</xs:element>
						<xs:element ref="r:ValueRepresentationReference">
							<xs:annotation>
								<xs:documentation>Allows for the use of managed value representations by reference. ValueRepresentationReference is the head of a substitution group which supports a number of representation types not managed within existing schemes, i.e. ManagedNumericRepresentation, ManagedTextRepresentation, ManagedDateTimeRepresentation, and ManagedScaleRepresentation. TypeOfObject should be set to ManagedNumericRepresentation, ManagedTextRepresentation, ManagedDateTimeRepresentation, or ManagedScaleRepresentation.</xs:documentation>
							</xs:annotation>
						</xs:element>
					</xs:choice>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
	<xs:element name="RepresentedVariableName" type="r:NameType">
		<xs:annotation>
			<xs:documentation>Name of the RepresentedVariable using the DDI Name structure.</xs:documentation>
		</xs:annotation>
	</xs:element>
	<xs:element name="RepresentedVariableReference" type="r:ReferenceType">
		<xs:annotation>
			<xs:documentation>Reference to an existing RepresentedVariable using the Reference structure. TypeOfObject should be set to RepresentedVariable</xs:documentation>
		</xs:annotation>
	</xs:element>
</xs:schema>