RubyGems - stix_schema_spy - Versions diffs - 1.3 → 1.3.2 - Mend

stix_schema_spy 1.3 → 1.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (109) hide show

checksums.yaml +4 -4
data/config/1.2/stix/campaign.xsd +2 -2
data/config/1.2/stix/cybox/cybox_common.xsd +2700 -2700
data/config/1.2/stix/cybox/cybox_core.xsd +1145 -1145
data/config/1.2/stix/cybox/cybox_default_vocabularies.xsd +5180 -5180
data/config/1.2/stix/cybox/extensions/location/ciq_address_3.0.xsd +27 -27
data/config/1.2/stix/cybox/extensions/platform/cpe2.3.xsd +34 -34
data/config/1.2/stix/cybox/external/cpe_2.3/xml.xsd +145 -145
data/config/1.2/stix/cybox/external/oasis_ciq_3.0/xlink-2003-12-31.xsd +90 -90
data/config/1.2/stix/cybox/objects/API_Object.xsd +55 -55
data/config/1.2/stix/cybox/objects/ARP_Cache_Object.xsd +98 -98
data/config/1.2/stix/cybox/objects/AS_Object.xsd +50 -50
data/config/1.2/stix/cybox/objects/Account_Object.xsd +501 -501
data/config/1.2/stix/cybox/objects/Address_Object.xsd +127 -127
data/config/1.2/stix/cybox/objects/Archive_File_Object.xsd +134 -134
data/config/1.2/stix/cybox/objects/Artifact_Object.xsd +212 -212
data/config/1.2/stix/cybox/objects/Code_Object.xsd +417 -417
data/config/1.2/stix/cybox/objects/Custom_Object.xsd +42 -42
data/config/1.2/stix/cybox/objects/DNS_Cache_Object.xsd +53 -53
data/config/1.2/stix/cybox/objects/DNS_Query_Object.xsd +164 -164
data/config/1.2/stix/cybox/objects/DNS_Record_Object.xsd +92 -92
data/config/1.2/stix/cybox/objects/Device_Object.xsd +65 -65
data/config/1.2/stix/cybox/objects/Disk_Object.xsd +117 -117
data/config/1.2/stix/cybox/objects/Disk_Partition_Object.xsd +199 -199
data/config/1.2/stix/cybox/objects/Domain_Name_Object.xsd +57 -57
data/config/1.2/stix/cybox/objects/Email_Message_Object.xsd +278 -278
data/config/1.2/stix/cybox/objects/File_Object.xsd +397 -397
data/config/1.2/stix/cybox/objects/GUI_Dialogbox_Object.xsd +41 -41
data/config/1.2/stix/cybox/objects/GUI_Object.xsd +40 -40
data/config/1.2/stix/cybox/objects/GUI_Window_Object.xsd +46 -46
data/config/1.2/stix/cybox/objects/HTTP_Session_Object.xsd +633 -633
data/config/1.2/stix/cybox/objects/Hostname_Object.xsd +45 -45
data/config/1.2/stix/cybox/objects/Image_File_Object.xsd +124 -124
data/config/1.2/stix/cybox/objects/Library_Object.xsd +114 -114
data/config/1.2/stix/cybox/objects/Link_Object.xsd +36 -36
data/config/1.2/stix/cybox/objects/Linux_Package_Object.xsd +75 -75
data/config/1.2/stix/cybox/objects/Memory_Object.xsd +141 -141
data/config/1.2/stix/cybox/objects/Mutex_Object.xsd +40 -40
data/config/1.2/stix/cybox/objects/Network_Connection_Object.xsd +540 -540
data/config/1.2/stix/cybox/objects/Network_Flow_Object.xsd +1559 -1559
data/config/1.2/stix/cybox/objects/Network_Packet_Object.xsd +2934 -2934
data/config/1.2/stix/cybox/objects/Network_Route_Entry_Object.xsd +155 -155
data/config/1.2/stix/cybox/objects/Network_Route_Object.xsd +93 -93
data/config/1.2/stix/cybox/objects/Network_Socket_Object.xsd +529 -529
data/config/1.2/stix/cybox/objects/Network_Subnet_Object.xsd +64 -64
data/config/1.2/stix/cybox/objects/PDF_File_Object.xsd +595 -595
data/config/1.2/stix/cybox/objects/Pipe_Object.xsd +40 -40
data/config/1.2/stix/cybox/objects/Port_Object.xsd +40 -40
data/config/1.2/stix/cybox/objects/Process_Object.xsd +199 -199
data/config/1.2/stix/cybox/objects/Product_Object.xsd +65 -65
data/config/1.2/stix/cybox/objects/SMS_Message_Object.xsd +79 -79
data/config/1.2/stix/cybox/objects/Semaphore_Object.xsd +50 -50
data/config/1.2/stix/cybox/objects/Socket_Address_Object.xsd +50 -50
data/config/1.2/stix/cybox/objects/System_Object.xsd +410 -410
data/config/1.2/stix/cybox/objects/URI_Object.xsd +62 -62
data/config/1.2/stix/cybox/objects/URL_History_Object.xsd +104 -104
data/config/1.2/stix/cybox/objects/Unix_File_Object.xsd +164 -164
data/config/1.2/stix/cybox/objects/Unix_Network_Route_Entry_Object.xsd +56 -56
data/config/1.2/stix/cybox/objects/Unix_Pipe_Object.xsd +36 -36
data/config/1.2/stix/cybox/objects/Unix_Process_Object.xsd +143 -143
data/config/1.2/stix/cybox/objects/Unix_User_Account_Object.xsd +78 -78
data/config/1.2/stix/cybox/objects/Unix_Volume_Object.xsd +41 -41
data/config/1.2/stix/cybox/objects/User_Account_Object.xsd +110 -110
data/config/1.2/stix/cybox/objects/User_Session_Object.xsd +60 -60
data/config/1.2/stix/cybox/objects/Volume_Object.xsd +235 -235
data/config/1.2/stix/cybox/objects/Whois_Object.xsd +430 -430
data/config/1.2/stix/cybox/objects/Win_Computer_Account_Object.xsd +135 -135
data/config/1.2/stix/cybox/objects/Win_Critical_Section_Object.xsd +40 -40
data/config/1.2/stix/cybox/objects/Win_Driver_Object.xsd +270 -270
data/config/1.2/stix/cybox/objects/Win_Event_Log_Object.xsd +137 -137
data/config/1.2/stix/cybox/objects/Win_Event_Object.xsd +80 -80
data/config/1.2/stix/cybox/objects/Win_Executable_File_Object.xsd +1311 -1311
data/config/1.2/stix/cybox/objects/Win_File_Object.xsd +269 -269
data/config/1.2/stix/cybox/objects/Win_Filemapping_Object.xsd +175 -175
data/config/1.2/stix/cybox/objects/Win_Handle_Object.xsd +351 -351
data/config/1.2/stix/cybox/objects/Win_Hook_Object.xsd +152 -152
data/config/1.2/stix/cybox/objects/Win_Kernel_Hook_Object.xsd +109 -109
data/config/1.2/stix/cybox/objects/Win_Kernel_Object.xsd +128 -128
data/config/1.2/stix/cybox/objects/Win_Mailslot_Object.xsd +56 -56
data/config/1.2/stix/cybox/objects/Win_Memory_Page_Region_Object.xsd +198 -198
data/config/1.2/stix/cybox/objects/Win_Mutex_Object.xsd +42 -42
data/config/1.2/stix/cybox/objects/Win_Network_Route_Entry_Object.xsd +200 -200
data/config/1.2/stix/cybox/objects/Win_Network_Share_Object.xsd +205 -205
data/config/1.2/stix/cybox/objects/Win_Pipe_Object.xsd +73 -73
data/config/1.2/stix/cybox/objects/Win_Prefetch_Object.xsd +113 -113
data/config/1.2/stix/cybox/objects/Win_Process_Object.xsd +174 -174
data/config/1.2/stix/cybox/objects/Win_Registry_Key_Object.xsd +290 -290
data/config/1.2/stix/cybox/objects/Win_Semaphore_Object.xsd +42 -42
data/config/1.2/stix/cybox/objects/Win_Service_Object.xsd +287 -287
data/config/1.2/stix/cybox/objects/Win_System_Object.xsd +126 -126
data/config/1.2/stix/cybox/objects/Win_System_Restore_Object.xsd +207 -207
data/config/1.2/stix/cybox/objects/Win_Task_Object.xsd +755 -755
data/config/1.2/stix/cybox/objects/Win_Thread_Object.xsd +146 -146
data/config/1.2/stix/cybox/objects/Win_User_Account_Object.xsd +73 -73
data/config/1.2/stix/cybox/objects/Win_Volume_Object.xsd +161 -161
data/config/1.2/stix/cybox/objects/Win_Waitable_Timer_Object.xsd +90 -90
data/config/1.2/stix/cybox/objects/X509_Certificate_Object.xsd +275 -275
data/config/1.2/stix/data_marking.xsd +5 -5
data/config/1.2/stix/exploit_target.xsd +2 -2
data/config/1.2/stix/incident.xsd +1 -1
data/config/1.2/stix/indicator.xsd +6 -6
data/config/1.2/stix/report.xsd +6 -6
data/config/1.2/stix/stix_common.xsd +22 -22
data/config/1.2/stix/stix_core.xsd +7 -7
data/config/1.2/stix/stix_default_vocabularies.xsd +8 -8
data/config/1.2/stix/ttp.xsd +1 -1
data/lib/stix_schema_spy/models/has_children.rb +3 -3
data/lib/stix_schema_spy/version.rb +1 -1
metadata +2 -2

data/config/1.2/stix/cybox/objects/API_Object.xsd CHANGED Viewed

@@ -1,55 +1,55 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:APIObj="http://cybox.mitre.org/objects#APIObject-2" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#APIObject-2" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.1">
-	<xs:annotation>
-		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
-		<xs:appinfo>
-			<schema>API_Object</schema>
-			<version>2.1</version>
-			<date>01/22/2014</date>
-			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
-			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
-		</xs:appinfo>
-	</xs:annotation>
-	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
-	<xs:element name="API" type="APIObj:APIObjectType">
-		<xs:annotation>
-			<xs:documentation>The API element is intended to characterize a single Application Programming Interface.</xs:documentation>
-		</xs:annotation>
-	</xs:element>
-	<xs:complexType name="APIObjectType">
-		<xs:annotation>
-			<xs:documentation>The APIObjectType type is intended to characterize a specific Application Programming Interface.</xs:documentation>
-		</xs:annotation>
-		<xs:complexContent>
-			<xs:extension base="cyboxCommon:ObjectPropertiesType">
-				<xs:sequence>
-					<xs:element name="Description" type="cyboxCommon:StructuredTextType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Description field is intended for use in providing a brief description of the API.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Function_Name" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The function_name field contains the exact name of the API function called, e.g. CreateFileEx.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Normalized_Function_Name" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The normalized_function_name field contains the normalized name of the API function called, e.g. CreateFile.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Platform" type="cyboxCommon:PlatformSpecificationType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Platform field specifies the relevant platform for this API.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Address" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Address field contains the address of the API call in the binary.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-				</xs:sequence>
-			</xs:extension>
-		</xs:complexContent>
-	</xs:complexType>
-</xs:schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:APIObj="http://cybox.mitre.org/objects#APIObject-2" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#APIObject-2" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.1">
+	<xs:annotation>
+		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
+		<xs:appinfo>
+			<schema>API_Object</schema>
+			<version>2.1</version>
+			<date>01/22/2014</date>
+			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
+			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
+		</xs:appinfo>
+	</xs:annotation>
+	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
+	<xs:element name="API" type="APIObj:APIObjectType">
+		<xs:annotation>
+			<xs:documentation>The API element is intended to characterize a single Application Programming Interface.</xs:documentation>
+		</xs:annotation>
+	</xs:element>
+	<xs:complexType name="APIObjectType">
+		<xs:annotation>
+			<xs:documentation>The APIObjectType type is intended to characterize a specific Application Programming Interface.</xs:documentation>
+		</xs:annotation>
+		<xs:complexContent>
+			<xs:extension base="cyboxCommon:ObjectPropertiesType">
+				<xs:sequence>
+					<xs:element name="Description" type="cyboxCommon:StructuredTextType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Description field is intended for use in providing a brief description of the API.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Function_Name" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The function_name field contains the exact name of the API function called, e.g. CreateFileEx.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Normalized_Function_Name" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The normalized_function_name field contains the normalized name of the API function called, e.g. CreateFile.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Platform" type="cyboxCommon:PlatformSpecificationType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Platform field specifies the relevant platform for this API.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Address" type="cyboxCommon:HexBinaryObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Address field contains the address of the API call in the binary.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+				</xs:sequence>
+			</xs:extension>
+		</xs:complexContent>
+	</xs:complexType>
+</xs:schema>

data/config/1.2/stix/cybox/objects/ARP_Cache_Object.xsd CHANGED Viewed

@@ -1,98 +1,98 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ARPCacheObj="http://cybox.mitre.org/objects#ARPCacheObject-1" xmlns:AddressObj="http://cybox.mitre.org/objects#AddressObject-2" xmlns:SystemObj="http://cybox.mitre.org/objects#SystemObject-2" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#ARPCacheObject-1" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
-	<xs:annotation>
-		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
-		<xs:appinfo>
-			<schema>ARP_Cache_Object</schema>
-			<version>1.0</version>
-			<date>01/22/2014</date>
-			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
-			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
-		</xs:appinfo>
-	</xs:annotation>
-	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
-	<xs:import namespace="http://cybox.mitre.org/objects#AddressObject-2" schemaLocation="Address_Object.xsd"/>
-	<xs:import namespace="http://cybox.mitre.org/objects#SystemObject-2" schemaLocation="System_Object.xsd"/>
-	<xs:element name="ARP_Cache" type="ARPCacheObj:ARPCacheObjectType">
-		<xs:annotation>
-			<xs:documentation>The ARP_Cache object is intended to characterize an address resolution protocol (ARP) cache on a system.</xs:documentation>
-		</xs:annotation>
-	</xs:element>
-	<xs:complexType name="ARPCacheObjectType" mixed="false">
-		<xs:annotation>
-			<xs:documentation>The ARPCacheObjectType type is intended to characterize entries in a system's address resolution protocol (ARP) cache.</xs:documentation>
-		</xs:annotation>
-		<xs:complexContent>
-			<xs:extension base="cyboxCommon:ObjectPropertiesType">
-				<xs:sequence>
-					<xs:element name="ARP_Cache_Entry" type="ARPCacheObj:ARPCacheEntryType" maxOccurs="unbounded">
-						<xs:annotation>
-							<xs:documentation>The ARP_Cache_Entry field is intended to characterize a single address resolution protocol (ARP) cache entry.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-				</xs:sequence>
-			</xs:extension>
-		</xs:complexContent>
-	</xs:complexType>
-	<xs:complexType name="ARPCacheEntryType">
-		<xs:annotation>
-			<xs:documentation>The ARPCacheEntryType type is intended to characterize a single entry in a system's ARP cache.</xs:documentation>
-		</xs:annotation>
-		<xs:sequence>
-			<xs:element minOccurs="0" name="IP_Address" type="AddressObj:AddressObjectType">
-				<xs:annotation>
-					<xs:documentation>The IP_Address field specifies the IP address that is mapped to the physical address in the ARP cache entry.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-			<xs:element minOccurs="0" name="Physical_Address" type="cyboxCommon:StringObjectPropertyType">
-				<xs:annotation>
-					<xs:documentation>The Physical_Address field specifies the physical (e.g. MAC-48) address that is mapped to the IP address in the ARP cache entry. Either a colon (':') or a dash ('-') may be used as a separator between the octets.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-			<xs:element minOccurs="0" name="Type" type="ARPCacheObj:ARPCacheEntryTypeType">
-				<xs:annotation>
-					<xs:documentation>The Type field specifies the type of ARP cache entry, which typically refers to the way the entry was added to the cache.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-			<xs:element minOccurs="0" name="Network_Interface" type="SystemObj:NetworkInterfaceType">
-				<xs:annotation>
-					<xs:documentation>The Network_Interface field permits the specification of the network interface to which the ARP cache entry belongs.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-		</xs:sequence>
-	</xs:complexType>
-	<xs:complexType name="ARPCacheEntryTypeType">
-		<xs:annotation>
-			<xs:documentation>The ARPCacheEntryTypeType specifies ARP cache entry types via a union of the ARPCacheEntryTypeEnum type and the atomic xs:string type. Its base type is the CybOX Core BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
-		</xs:annotation>
-		<xs:simpleContent>
-			<xs:restriction base="cyboxCommon:BaseObjectPropertyType">
-				<xs:simpleType>
-					<xs:union memberTypes="ARPCacheObj:ARPCacheEntryTypeEnum xs:string"/>
-				</xs:simpleType>
-				<xs:attribute fixed="string" name="datatype" type="cyboxCommon:DatatypeEnum">
-					<xs:annotation>
-						<xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
-					</xs:annotation>
-				</xs:attribute>
-			</xs:restriction>
-		</xs:simpleContent>
-	</xs:complexType>
-	<xs:simpleType name="ARPCacheEntryTypeEnum">
-		<xs:annotation>
-			<xs:documentation>The ARPCacheEntryTypeEnum is an enumeration of arp cache entry types.</xs:documentation>
-		</xs:annotation>
-		<xs:restriction base="xs:string">
-			<xs:enumeration value="static">
-				<xs:annotation>
-					<xs:documentation>The static value specifies an IP address/physical address pair that was manually added to the cache table for a device and is kept in the cache on a permanent basis.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="dynamic">
-				<xs:annotation>
-					<xs:documentation>The dynamic value specifies an IP address/physical address pair added to the cache automatically as a result of successfully-completed past ARP resolutions.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-		</xs:restriction>
-	</xs:simpleType>
-</xs:schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ARPCacheObj="http://cybox.mitre.org/objects#ARPCacheObject-1" xmlns:AddressObj="http://cybox.mitre.org/objects#AddressObject-2" xmlns:SystemObj="http://cybox.mitre.org/objects#SystemObject-2" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#ARPCacheObject-1" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
+	<xs:annotation>
+		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
+		<xs:appinfo>
+			<schema>ARP_Cache_Object</schema>
+			<version>1.0</version>
+			<date>01/22/2014</date>
+			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
+			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
+		</xs:appinfo>
+	</xs:annotation>
+	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
+	<xs:import namespace="http://cybox.mitre.org/objects#AddressObject-2" schemaLocation="Address_Object.xsd"/>
+	<xs:import namespace="http://cybox.mitre.org/objects#SystemObject-2" schemaLocation="System_Object.xsd"/>
+	<xs:element name="ARP_Cache" type="ARPCacheObj:ARPCacheObjectType">
+		<xs:annotation>
+			<xs:documentation>The ARP_Cache object is intended to characterize an address resolution protocol (ARP) cache on a system.</xs:documentation>
+		</xs:annotation>
+	</xs:element>
+	<xs:complexType name="ARPCacheObjectType" mixed="false">
+		<xs:annotation>
+			<xs:documentation>The ARPCacheObjectType type is intended to characterize entries in a system's address resolution protocol (ARP) cache.</xs:documentation>
+		</xs:annotation>
+		<xs:complexContent>
+			<xs:extension base="cyboxCommon:ObjectPropertiesType">
+				<xs:sequence>
+					<xs:element name="ARP_Cache_Entry" type="ARPCacheObj:ARPCacheEntryType" maxOccurs="unbounded">
+						<xs:annotation>
+							<xs:documentation>The ARP_Cache_Entry field is intended to characterize a single address resolution protocol (ARP) cache entry.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+				</xs:sequence>
+			</xs:extension>
+		</xs:complexContent>
+	</xs:complexType>
+	<xs:complexType name="ARPCacheEntryType">
+		<xs:annotation>
+			<xs:documentation>The ARPCacheEntryType type is intended to characterize a single entry in a system's ARP cache.</xs:documentation>
+		</xs:annotation>
+		<xs:sequence>
+			<xs:element minOccurs="0" name="IP_Address" type="AddressObj:AddressObjectType">
+				<xs:annotation>
+					<xs:documentation>The IP_Address field specifies the IP address that is mapped to the physical address in the ARP cache entry.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element minOccurs="0" name="Physical_Address" type="cyboxCommon:StringObjectPropertyType">
+				<xs:annotation>
+					<xs:documentation>The Physical_Address field specifies the physical (e.g. MAC-48) address that is mapped to the IP address in the ARP cache entry. Either a colon (':') or a dash ('-') may be used as a separator between the octets.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element minOccurs="0" name="Type" type="ARPCacheObj:ARPCacheEntryTypeType">
+				<xs:annotation>
+					<xs:documentation>The Type field specifies the type of ARP cache entry, which typically refers to the way the entry was added to the cache.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element minOccurs="0" name="Network_Interface" type="SystemObj:NetworkInterfaceType">
+				<xs:annotation>
+					<xs:documentation>The Network_Interface field permits the specification of the network interface to which the ARP cache entry belongs.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+		</xs:sequence>
+	</xs:complexType>
+	<xs:complexType name="ARPCacheEntryTypeType">
+		<xs:annotation>
+			<xs:documentation>The ARPCacheEntryTypeType specifies ARP cache entry types via a union of the ARPCacheEntryTypeEnum type and the atomic xs:string type. Its base type is the CybOX Core BaseObjectPropertyType, for permitting complex (i.e. regular-expression based) specifications.</xs:documentation>
+		</xs:annotation>
+		<xs:simpleContent>
+			<xs:restriction base="cyboxCommon:BaseObjectPropertyType">
+				<xs:simpleType>
+					<xs:union memberTypes="ARPCacheObj:ARPCacheEntryTypeEnum xs:string"/>
+				</xs:simpleType>
+				<xs:attribute fixed="string" name="datatype" type="cyboxCommon:DatatypeEnum">
+					<xs:annotation>
+						<xs:documentation>This attribute is optional and specifies the expected type for the value of the specified property.</xs:documentation>
+					</xs:annotation>
+				</xs:attribute>
+			</xs:restriction>
+		</xs:simpleContent>
+	</xs:complexType>
+	<xs:simpleType name="ARPCacheEntryTypeEnum">
+		<xs:annotation>
+			<xs:documentation>The ARPCacheEntryTypeEnum is an enumeration of arp cache entry types.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:string">
+			<xs:enumeration value="static">
+				<xs:annotation>
+					<xs:documentation>The static value specifies an IP address/physical address pair that was manually added to the cache table for a device and is kept in the cache on a permanent basis.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="dynamic">
+				<xs:annotation>
+					<xs:documentation>The dynamic value specifies an IP address/physical address pair added to the cache automatically as a result of successfully-completed past ARP resolutions.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+		</xs:restriction>
+	</xs:simpleType>
+</xs:schema>

data/config/1.2/stix/cybox/objects/AS_Object.xsd CHANGED Viewed

@@ -1,50 +1,50 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ASObj="http://cybox.mitre.org/objects#ASObject-1" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#ASObject-1" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
-	<xs:annotation>
-		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
-		<xs:appinfo>
-			<schema>AS Object</schema>
-			<version>1.0</version>
-			<date>01/22/2014</date>
-			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
-			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
-		</xs:appinfo>
-	</xs:annotation>
-	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
-	<xs:element name="AS" type="ASObj:ASObjectType">
-		<xs:annotation>
-			<xs:documentation>The AS element is intended to characterize a single autonomous system (AS).</xs:documentation>
-		</xs:annotation>
-	</xs:element>
-	<xs:complexType name="ASObjectType">
-		<xs:annotation>
-			<xs:documentation>The ASObjectType type is intended to characterize an autonomous system (AS).</xs:documentation>
-		</xs:annotation>
-		<xs:complexContent>
-			<xs:extension base="cyboxCommon:ObjectPropertiesType">
-				<xs:sequence>
-					<xs:element minOccurs="0" name="Number" type="cyboxCommon:NonNegativeIntegerObjectPropertyType">
-						<xs:annotation>
-							<xs:documentation>The Number field specifies the number assigned to the autonomous system (AS). Such assignments are typically performed by a regional internet registry (RIR).</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Name" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Name field specifies the name of the autonomous system (AS).</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element minOccurs="0" name="Handle" type="cyboxCommon:StringObjectPropertyType">
-						<xs:annotation>
-							<xs:documentation>The Handle field specifies the handle for the autonomous system (AS), which is typically the AS number prepended with the string 'AS'.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element minOccurs="0" name="Regional_Internet_Registry" type="cyboxCommon:RegionalRegistryType">
-						<xs:annotation>
-							<xs:documentation>The Regional_Internet_Registry field specifies the name of the regional internet registry (RIR) that assigned the number to the autonomous system (AS).</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-				</xs:sequence>
-			</xs:extension>
-		</xs:complexContent>
-	</xs:complexType>
-</xs:schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:ASObj="http://cybox.mitre.org/objects#ASObject-1" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#ASObject-1" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">
+	<xs:annotation>
+		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
+		<xs:appinfo>
+			<schema>AS Object</schema>
+			<version>1.0</version>
+			<date>01/22/2014</date>
+			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
+			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
+		</xs:appinfo>
+	</xs:annotation>
+	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
+	<xs:element name="AS" type="ASObj:ASObjectType">
+		<xs:annotation>
+			<xs:documentation>The AS element is intended to characterize a single autonomous system (AS).</xs:documentation>
+		</xs:annotation>
+	</xs:element>
+	<xs:complexType name="ASObjectType">
+		<xs:annotation>
+			<xs:documentation>The ASObjectType type is intended to characterize an autonomous system (AS).</xs:documentation>
+		</xs:annotation>
+		<xs:complexContent>
+			<xs:extension base="cyboxCommon:ObjectPropertiesType">
+				<xs:sequence>
+					<xs:element minOccurs="0" name="Number" type="cyboxCommon:NonNegativeIntegerObjectPropertyType">
+						<xs:annotation>
+							<xs:documentation>The Number field specifies the number assigned to the autonomous system (AS). Such assignments are typically performed by a regional internet registry (RIR).</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Name" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Name field specifies the name of the autonomous system (AS).</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element minOccurs="0" name="Handle" type="cyboxCommon:StringObjectPropertyType">
+						<xs:annotation>
+							<xs:documentation>The Handle field specifies the handle for the autonomous system (AS), which is typically the AS number prepended with the string 'AS'.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element minOccurs="0" name="Regional_Internet_Registry" type="cyboxCommon:RegionalRegistryType">
+						<xs:annotation>
+							<xs:documentation>The Regional_Internet_Registry field specifies the name of the regional internet registry (RIR) that assigned the number to the autonomous system (AS).</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+				</xs:sequence>
+			</xs:extension>
+		</xs:complexContent>
+	</xs:complexType>
+</xs:schema>

data/config/1.2/stix/cybox/objects/Account_Object.xsd CHANGED Viewed

@@ -1,501 +1,501 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:AccountObj="http://cybox.mitre.org/objects#AccountObject-2" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#AccountObject-2" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.1">
-	<xs:annotation>
-		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
-		<xs:appinfo>
-			<schema>Account_Object</schema>
-			<version>2.1</version>
-			<date>01/22/2014</date>
-			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
-			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
-		</xs:appinfo>
-	</xs:annotation>
-	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
-	<xs:element name="Account" type="AccountObj:AccountObjectType">
-		<xs:annotation>
-			<xs:documentation>The Account object is intended to characterize generic accounts.</xs:documentation>
-		</xs:annotation>
-	</xs:element>
-	<xs:complexType name="AccountObjectType" mixed="false">
-		<xs:annotation>
-			<xs:documentation>The AccountObjectType type is intended to characterize generic accounts.</xs:documentation>
-		</xs:annotation>
-		<xs:complexContent>
-			<xs:extension base="cyboxCommon:ObjectPropertiesType">
-				<xs:sequence>
-					<xs:element name="Description" type="cyboxCommon:StringObjectPropertyType" minOccurs="0" maxOccurs="1">
-						<xs:annotation>
-							<xs:documentation>The Description field is used for providing a description of the account, if applicable.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Domain" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Domain field is used for specifying the domain that the account belongs to.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Authentication" type="AccountObj:AuthenticationType" minOccurs="0" maxOccurs="unbounded">
-						<xs:annotation>
-							<xs:documentation>The Authentication field specifies authentication information associated with this account.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Creation_Date" type="cyboxCommon:DateTimeObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Creation_Date field specifies the date and time that the account was created.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Modified_Date" type="cyboxCommon:DateTimeObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Modified_Date field specifies the date and time that the account was last modified.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-					<xs:element name="Last_Accessed_Time" type="cyboxCommon:DateTimeObjectPropertyType" minOccurs="0">
-						<xs:annotation>
-							<xs:documentation>The Last_Accessed_Time field specifies the date and time that the account was last accessed.</xs:documentation>
-						</xs:annotation>
-					</xs:element>
-				</xs:sequence>
-				<xs:attribute name="disabled" type="xs:boolean">
-					<xs:annotation>
-						<xs:documentation>The disabled field specifies whether or not the account is disabled.</xs:documentation>
-					</xs:annotation>
-				</xs:attribute>
-				<xs:attribute name="locked_out" type="xs:boolean">
-					<xs:annotation>
-						<xs:documentation>The locked_out field specifies whether or not the account is locked out.</xs:documentation>
-					</xs:annotation>
-				</xs:attribute>
-			</xs:extension>
-		</xs:complexContent>
-	</xs:complexType>
-	<xs:complexType name="AuthenticationType">
-		<xs:annotation>
-			<xs:documentation>The AuthenticationType type specifies authentication information for an account.</xs:documentation>
-		</xs:annotation>
-		<xs:sequence>
-			<xs:element name="Authentication_Type" type="cyboxCommon:ControlledVocabularyStringType" minOccurs="0">
-				<xs:annotation>
-					<xs:documentation>The Authentication_Type field specifies the type of authentication required by this Account.</xs:documentation>
-					<xs:documentation>This field is implemented through the xsi:type controlled vocabulary extension mechanism. The default vocabulary type is AuthenticationTypeVocab-1.0 in the http://cybox.mitre.org/objects#AccountObject-2 namespace.</xs:documentation>
-					<xs:documentation>Users may also define their own vocabulary using the type extension mechanism, specify a vocabulary name and reference using the attributes, or simply use this as a string field.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-			<xs:element name="Authentication_Data" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
-				<xs:annotation>
-					<xs:documentation>The Authentication_Data field specifies the data used for the authentication type specified by the Authentication_Type field. For example, if Authentication_Type is set to "Password", this would be the actual password value.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-			<xs:element name="Authentication_Token_Protection_Mechanism" type="cyboxCommon:ControlledVocabularyStringType" minOccurs="0">
-				<xs:annotation>
-					<xs:documentation>The Authentication_Token_Protection_Mechanism field specifies the method (typically algorithm) of protecting authentication tokens for this account.</xs:documentation>
-					<xs:documentation>This field is implemented through the xsi:type controlled vocabulary extension mechanism. The default vocabulary type is AuthenticationTokenProtectionMechanismTypeVocab-1.0 in the http://cybox.mitre.org/objects#AccountObject-2 namespace.</xs:documentation>
-					<xs:documentation>Users may also define their own vocabulary using the type extension mechanism, specify a vocabulary name and reference using the attributes, or simply use this as a string field.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-			<xs:element name="Structured_Authentication_Mechanism" minOccurs="0" type="AccountObj:StructuredAuthenticationMechanismType">
-				<xs:annotation>
-					<xs:documentation>The Structured_Authentication_Mechanism field provides authors a field for describing authentication mechanism information in a structured language defined outside of CybOX.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-		</xs:sequence>
-	</xs:complexType>
-	<xs:complexType name="StructuredAuthenticationMechanismType">
-		<xs:annotation>
-			<xs:documentation>Characterizes the description of an authentication mechanism, such as biometrics-based authentication.</xs:documentation>
-			<xs:documentation>In addition to capturing basic information, this type is intended to be extended to enable the structured description of an authentication mechanism using the XML Schema extension feature. No extension is provided by CybOX to support this, however those wishing to represent structured authentication mechanism information may develop such an extension.</xs:documentation>
-		</xs:annotation>
-		<xs:sequence>
-			<xs:element name="Description" type="cyboxCommon:StructuredTextType" minOccurs="0">
-				<xs:annotation>
-					<xs:documentation>The Description field provides an unstructured description of an individual StructuredAuthenticationMechanismType instance.</xs:documentation>
-				</xs:annotation>
-			</xs:element>
-		</xs:sequence>
-	</xs:complexType>
-	<xs:complexType name="AuthenticationTypeVocab-1.0">
-		<xs:annotation>
-			<xs:documentation>The AuthenticationTypeVocab is the default CybOX vocabulary for authentication types, used in the AuthenticationType/Authentication_Type found in the Account Object schema.</xs:documentation>
-		</xs:annotation>
-		<xs:simpleContent>
-			<xs:restriction base="cyboxCommon:ControlledVocabularyStringType">
-				<xs:simpleType>
-					<xs:union memberTypes="AccountObj:AuthenticationTypeEnum-1.0"/>
-				</xs:simpleType>
-				<xs:attribute name="vocab_name" type="xs:string" use="optional" fixed="CybOX Default Authentication Types"/>
-				<xs:attribute name="vocab_reference" type="xs:anyURI" use="optional" fixed="http://cybox.mitre.org/XMLSchema/objects/Account/2.1/Account_Object.xsd#AuthenticationTypeVocab-1.0"/>
-			</xs:restriction>
-		</xs:simpleContent>
-	</xs:complexType>
-	<xs:simpleType name="AuthenticationTypeEnum-1.0">
-		<xs:annotation>
-			<xs:documentation>The AuthenticationTypeEnum is a (non-exhaustive) enumeration of authentication types for accounts. This is leveraged by the Account Object.</xs:documentation>
-		</xs:annotation>
-		<xs:restriction base="xs:string">
-			<xs:enumeration value="No Authentication">
-				<xs:annotation>
-					<xs:documentation>The No Authentication value specifies that there is no authentication mechanism in place.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="Password">
-				<xs:annotation>
-					<xs:documentation>The Password value specifies password based authentication.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="Cryptographic Key">
-				<xs:annotation>
-					<xs:documentation>The Cryptographic Key value specifies cryptographic key based authentication.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="Biometrics">
-				<xs:annotation>
-					<xs:documentation>The Biometrics value specifies biometrics based authentication. Examples include fingerprint or retina readers.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="Hardware Token">
-				<xs:annotation>
-					<xs:documentation>The Hardware Token value specifies authentication requiring physical or hardware tokens. Examples include smart cards, bluetooth tokens, and usb tokens.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="Software Token">
-				<xs:annotation>
-					<xs:documentation>The Software Token value specifies an authentication device stored in software form.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-			<xs:enumeration value="Multifactor">
-				<xs:annotation>
-					<xs:documentation>The Multifactor authentication value specifies multifactor authentication.</xs:documentation>
-				</xs:annotation>
-			</xs:enumeration>
-		</xs:restriction>
-	</xs:simpleType>
-	<xs:complexType name="AuthenticationTokenProtectionMechanismTypeVocab-1.0">
-		<xs:annotation>
-			<xs:documentation>The AuthenticationTokenProtectionMechanismTypeVocab is the default CybOX vocabulary for authentication token protection mechanisms, used in the AuthenticationType/Authentication_Token_Protection_Mechanism found in the Account Object schema.</xs:documentation>
-		</xs:annotation>
-		<xs:simpleContent>
-			<xs:restriction base="cyboxCommon:ControlledVocabularyStringType">
-				<xs:simpleType>
-					<xs:union memberTypes="AccountObj:AuthenticationTokenProtectionMechanismTypeEnum-1.0"/>
-				</xs:simpleType>
-				<xs:attribute name="vocab_name" type="xs:string" use="optional" fixed="CybOX Default Authentication Token Protection Mechanism Types"/>
-				<xs:attribute name="vocab_reference" type="xs:anyURI" use="optional" fixed="http://cybox.mitre.org/XMLSchema/objects/Account/2.1/Account_Object.xsd#AuthenticationTokenProtectionMechanismTypeVocab-1.0"/>
-			</xs:restriction>
-		</xs:simpleContent>
-	</xs:complexType>
-	<xs:simpleType name="AuthenticationTokenProtectionMechanismTypeEnum-1.0">
-    	<xs:annotation>
-        	<xs:documentation>The AuthenticationTokenProtectionMechanismTypeEnum is a (non-exhaustive) enumeration of methods for the protection of authentication tokens.</xs:documentation>
-    	</xs:annotation>
-	    <xs:restriction base="xs:string">
-	        <xs:enumeration value="Plaintext">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens are stored in plaintext.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted GOST Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the GOST hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted GOST Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the GOST hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted HAVAL Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the HAVAL hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted HAVAL Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the HAVAL hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted MD2 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the MD2 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted MD2 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the MD2 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted MD4 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the MD4 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted MD4 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the MD4 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted MD5 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the MD5 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted MD5 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the MD5 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted PANAMA Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the PANAMA hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted PANAMA Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the PANAMA hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted RadioGatun Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the RadioGatun hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted RadioGatun Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the RadioGatun hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted RIPEMD Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted RIPEMD Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted RIPEMD-128/256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD-128/256 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted RIPEMD-128/256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD-128/256 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted RIPEMD-160 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD-160 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted RIPEMD-160 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD-160 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted RIPEMD-320 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD-320 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted RIPEMD-320 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD-320 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-0 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-0 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-0 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-0 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-1 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-1 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-1 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-1 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-256/224 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-256/224 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-256/224 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-256/224 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-512/384 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-512/384 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-512/384 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-512/384 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-3 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-3 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-3 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-3-224 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-224 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-3-224 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-224 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-3-256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-256 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-3-256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-256 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-3-384 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-384 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-3-384 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-384 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted SHA-3-512 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-512 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted SHA-3-512 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-512 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted Tiger(2)-192/160/128 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the Tiger(2)-192/160/128 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted Tiger(2)-192/160/128 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the Tiger(2)-192/160/128 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted WHIRLPOOL Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the WHIRLPOOL hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted WHIRLPOOL Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the WHIRLPOOL hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted Skein-256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the Skein-256 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted Skein-256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the Skein-256 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted Skein-512 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the Skein-512 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted Skein-512 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the Skein-512 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted Skein-1024 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the Skein-1024 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted Skein-1024 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the Skein-1024 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted Snefru-128 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the Snefru-128 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted Snefru-128 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the Snefru-128 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Salted Snefru-256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been salted and hashed with the Snefru-256 hash algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Unsalted Snefru-256 Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed with the Snefru-256 hash algorithm, without salting.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Iterative Hash">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been hashed using an iterative hashing algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="AES">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been encrypted with the AES algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="Blowfish">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been encrypted with the Blowfish algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="DES">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been encrypted with the DES algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="IDEA">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been encrypted with the IDEA algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="RC4">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been encrypted with the RC4 algorithm.</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	        <xs:enumeration value="TEA">
-	            <xs:annotation>
-	                <xs:documentation>The authentication tokens have been encrypted with the Tiny Encryption Algorithm (TEA).</xs:documentation>
-	            </xs:annotation>
-	        </xs:enumeration>
-	    </xs:restriction>
-	</xs:simpleType>
-</xs:schema>
+<?xml version='1.0' encoding='UTF-8'?>
+<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:AccountObj="http://cybox.mitre.org/objects#AccountObject-2" xmlns:cyboxCommon="http://cybox.mitre.org/common-2" targetNamespace="http://cybox.mitre.org/objects#AccountObject-2" elementFormDefault="qualified" attributeFormDefault="unqualified" version="2.1">
+	<xs:annotation>
+		<xs:documentation>This schema was originally developed by The MITRE Corporation. The CybOX XML Schema implementation is maintained by The MITRE Corporation and developed by the open CybOX Community. For more information, including how to get involved in the effort and how to submit change requests, please visit the CybOX website at http://cybox.mitre.org.</xs:documentation>
+		<xs:appinfo>
+			<schema>Account_Object</schema>
+			<version>2.1</version>
+			<date>01/22/2014</date>
+			<short_description>The following specifies the fields and types that compose this defined CybOX Object type. Each defined object is an extension of the abstract ObjectPropertiesType, defined in CybOX Common. For more information on this extension mechanism, please see the CybOX Specification. This document is intended for developers and assumes some familiarity with XML. </short_description>
+			<terms_of_use>Copyright (c) 2012-2014, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the CybOX License located at http://cybox.mitre.org/about/termsofuse.html. See the CybOX License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the CybOX Schema, this license header must be included.</terms_of_use>
+		</xs:appinfo>
+	</xs:annotation>
+	<xs:import namespace="http://cybox.mitre.org/common-2" schemaLocation="../cybox_common.xsd"/>
+	<xs:element name="Account" type="AccountObj:AccountObjectType">
+		<xs:annotation>
+			<xs:documentation>The Account object is intended to characterize generic accounts.</xs:documentation>
+		</xs:annotation>
+	</xs:element>
+	<xs:complexType name="AccountObjectType" mixed="false">
+		<xs:annotation>
+			<xs:documentation>The AccountObjectType type is intended to characterize generic accounts.</xs:documentation>
+		</xs:annotation>
+		<xs:complexContent>
+			<xs:extension base="cyboxCommon:ObjectPropertiesType">
+				<xs:sequence>
+					<xs:element name="Description" type="cyboxCommon:StringObjectPropertyType" minOccurs="0" maxOccurs="1">
+						<xs:annotation>
+							<xs:documentation>The Description field is used for providing a description of the account, if applicable.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Domain" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Domain field is used for specifying the domain that the account belongs to.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Authentication" type="AccountObj:AuthenticationType" minOccurs="0" maxOccurs="unbounded">
+						<xs:annotation>
+							<xs:documentation>The Authentication field specifies authentication information associated with this account.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Creation_Date" type="cyboxCommon:DateTimeObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Creation_Date field specifies the date and time that the account was created.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Modified_Date" type="cyboxCommon:DateTimeObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Modified_Date field specifies the date and time that the account was last modified.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+					<xs:element name="Last_Accessed_Time" type="cyboxCommon:DateTimeObjectPropertyType" minOccurs="0">
+						<xs:annotation>
+							<xs:documentation>The Last_Accessed_Time field specifies the date and time that the account was last accessed.</xs:documentation>
+						</xs:annotation>
+					</xs:element>
+				</xs:sequence>
+				<xs:attribute name="disabled" type="xs:boolean">
+					<xs:annotation>
+						<xs:documentation>The disabled field specifies whether or not the account is disabled.</xs:documentation>
+					</xs:annotation>
+				</xs:attribute>
+				<xs:attribute name="locked_out" type="xs:boolean">
+					<xs:annotation>
+						<xs:documentation>The locked_out field specifies whether or not the account is locked out.</xs:documentation>
+					</xs:annotation>
+				</xs:attribute>
+			</xs:extension>
+		</xs:complexContent>
+	</xs:complexType>
+	<xs:complexType name="AuthenticationType">
+		<xs:annotation>
+			<xs:documentation>The AuthenticationType type specifies authentication information for an account.</xs:documentation>
+		</xs:annotation>
+		<xs:sequence>
+			<xs:element name="Authentication_Type" type="cyboxCommon:ControlledVocabularyStringType" minOccurs="0">
+				<xs:annotation>
+					<xs:documentation>The Authentication_Type field specifies the type of authentication required by this Account.</xs:documentation>
+					<xs:documentation>This field is implemented through the xsi:type controlled vocabulary extension mechanism. The default vocabulary type is AuthenticationTypeVocab-1.0 in the http://cybox.mitre.org/objects#AccountObject-2 namespace.</xs:documentation>
+					<xs:documentation>Users may also define their own vocabulary using the type extension mechanism, specify a vocabulary name and reference using the attributes, or simply use this as a string field.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Authentication_Data" type="cyboxCommon:StringObjectPropertyType" minOccurs="0">
+				<xs:annotation>
+					<xs:documentation>The Authentication_Data field specifies the data used for the authentication type specified by the Authentication_Type field. For example, if Authentication_Type is set to "Password", this would be the actual password value.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Authentication_Token_Protection_Mechanism" type="cyboxCommon:ControlledVocabularyStringType" minOccurs="0">
+				<xs:annotation>
+					<xs:documentation>The Authentication_Token_Protection_Mechanism field specifies the method (typically algorithm) of protecting authentication tokens for this account.</xs:documentation>
+					<xs:documentation>This field is implemented through the xsi:type controlled vocabulary extension mechanism. The default vocabulary type is AuthenticationTokenProtectionMechanismTypeVocab-1.0 in the http://cybox.mitre.org/objects#AccountObject-2 namespace.</xs:documentation>
+					<xs:documentation>Users may also define their own vocabulary using the type extension mechanism, specify a vocabulary name and reference using the attributes, or simply use this as a string field.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+			<xs:element name="Structured_Authentication_Mechanism" minOccurs="0" type="AccountObj:StructuredAuthenticationMechanismType">
+				<xs:annotation>
+					<xs:documentation>The Structured_Authentication_Mechanism field provides authors a field for describing authentication mechanism information in a structured language defined outside of CybOX.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+		</xs:sequence>
+	</xs:complexType>
+	<xs:complexType name="StructuredAuthenticationMechanismType">
+		<xs:annotation>
+			<xs:documentation>Characterizes the description of an authentication mechanism, such as biometrics-based authentication.</xs:documentation>
+			<xs:documentation>In addition to capturing basic information, this type is intended to be extended to enable the structured description of an authentication mechanism using the XML Schema extension feature. No extension is provided by CybOX to support this, however those wishing to represent structured authentication mechanism information may develop such an extension.</xs:documentation>
+		</xs:annotation>
+		<xs:sequence>
+			<xs:element name="Description" type="cyboxCommon:StructuredTextType" minOccurs="0">
+				<xs:annotation>
+					<xs:documentation>The Description field provides an unstructured description of an individual StructuredAuthenticationMechanismType instance.</xs:documentation>
+				</xs:annotation>
+			</xs:element>
+		</xs:sequence>
+	</xs:complexType>
+	<xs:complexType name="AuthenticationTypeVocab-1.0">
+		<xs:annotation>
+			<xs:documentation>The AuthenticationTypeVocab is the default CybOX vocabulary for authentication types, used in the AuthenticationType/Authentication_Type found in the Account Object schema.</xs:documentation>
+		</xs:annotation>
+		<xs:simpleContent>
+			<xs:restriction base="cyboxCommon:ControlledVocabularyStringType">
+				<xs:simpleType>
+					<xs:union memberTypes="AccountObj:AuthenticationTypeEnum-1.0"/>
+				</xs:simpleType>
+				<xs:attribute name="vocab_name" type="xs:string" use="optional" fixed="CybOX Default Authentication Types"/>
+				<xs:attribute name="vocab_reference" type="xs:anyURI" use="optional" fixed="http://cybox.mitre.org/XMLSchema/objects/Account/2.1/Account_Object.xsd#AuthenticationTypeVocab-1.0"/>
+			</xs:restriction>
+		</xs:simpleContent>
+	</xs:complexType>
+	<xs:simpleType name="AuthenticationTypeEnum-1.0">
+		<xs:annotation>
+			<xs:documentation>The AuthenticationTypeEnum is a (non-exhaustive) enumeration of authentication types for accounts. This is leveraged by the Account Object.</xs:documentation>
+		</xs:annotation>
+		<xs:restriction base="xs:string">
+			<xs:enumeration value="No Authentication">
+				<xs:annotation>
+					<xs:documentation>The No Authentication value specifies that there is no authentication mechanism in place.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Password">
+				<xs:annotation>
+					<xs:documentation>The Password value specifies password based authentication.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Cryptographic Key">
+				<xs:annotation>
+					<xs:documentation>The Cryptographic Key value specifies cryptographic key based authentication.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Biometrics">
+				<xs:annotation>
+					<xs:documentation>The Biometrics value specifies biometrics based authentication. Examples include fingerprint or retina readers.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Hardware Token">
+				<xs:annotation>
+					<xs:documentation>The Hardware Token value specifies authentication requiring physical or hardware tokens. Examples include smart cards, bluetooth tokens, and usb tokens.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Software Token">
+				<xs:annotation>
+					<xs:documentation>The Software Token value specifies an authentication device stored in software form.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+			<xs:enumeration value="Multifactor">
+				<xs:annotation>
+					<xs:documentation>The Multifactor authentication value specifies multifactor authentication.</xs:documentation>
+				</xs:annotation>
+			</xs:enumeration>
+		</xs:restriction>
+	</xs:simpleType>
+	<xs:complexType name="AuthenticationTokenProtectionMechanismTypeVocab-1.0">
+		<xs:annotation>
+			<xs:documentation>The AuthenticationTokenProtectionMechanismTypeVocab is the default CybOX vocabulary for authentication token protection mechanisms, used in the AuthenticationType/Authentication_Token_Protection_Mechanism found in the Account Object schema.</xs:documentation>
+		</xs:annotation>
+		<xs:simpleContent>
+			<xs:restriction base="cyboxCommon:ControlledVocabularyStringType">
+				<xs:simpleType>
+					<xs:union memberTypes="AccountObj:AuthenticationTokenProtectionMechanismTypeEnum-1.0"/>
+				</xs:simpleType>
+				<xs:attribute name="vocab_name" type="xs:string" use="optional" fixed="CybOX Default Authentication Token Protection Mechanism Types"/>
+				<xs:attribute name="vocab_reference" type="xs:anyURI" use="optional" fixed="http://cybox.mitre.org/XMLSchema/objects/Account/2.1/Account_Object.xsd#AuthenticationTokenProtectionMechanismTypeVocab-1.0"/>
+			</xs:restriction>
+		</xs:simpleContent>
+	</xs:complexType>
+	<xs:simpleType name="AuthenticationTokenProtectionMechanismTypeEnum-1.0">
+    	<xs:annotation>
+        	<xs:documentation>The AuthenticationTokenProtectionMechanismTypeEnum is a (non-exhaustive) enumeration of methods for the protection of authentication tokens.</xs:documentation>
+    	</xs:annotation>
+	    <xs:restriction base="xs:string">
+	        <xs:enumeration value="Plaintext">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens are stored in plaintext.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted GOST Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the GOST hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted GOST Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the GOST hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted HAVAL Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the HAVAL hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted HAVAL Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the HAVAL hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted MD2 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the MD2 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted MD2 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the MD2 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted MD4 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the MD4 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted MD4 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the MD4 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted MD5 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the MD5 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted MD5 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the MD5 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted PANAMA Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the PANAMA hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted PANAMA Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the PANAMA hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted RadioGatun Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the RadioGatun hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted RadioGatun Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the RadioGatun hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted RIPEMD Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted RIPEMD Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted RIPEMD-128/256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD-128/256 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted RIPEMD-128/256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD-128/256 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted RIPEMD-160 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD-160 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted RIPEMD-160 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD-160 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted RIPEMD-320 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the RIPEMD-320 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted RIPEMD-320 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the RIPEMD-320 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-0 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-0 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-0 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-0 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-1 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-1 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-1 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-1 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-256/224 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-256/224 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-256/224 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-256/224 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-512/384 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-512/384 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-512/384 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-512/384 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-3 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-3 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-3 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-3-224 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-224 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-3-224 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-224 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-3-256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-256 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-3-256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-256 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-3-384 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-384 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-3-384 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-384 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted SHA-3-512 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the SHA-3-512 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted SHA-3-512 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the SHA-3-512 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted Tiger(2)-192/160/128 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the Tiger(2)-192/160/128 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted Tiger(2)-192/160/128 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the Tiger(2)-192/160/128 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted WHIRLPOOL Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the WHIRLPOOL hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted WHIRLPOOL Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the WHIRLPOOL hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted Skein-256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the Skein-256 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted Skein-256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the Skein-256 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted Skein-512 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the Skein-512 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted Skein-512 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the Skein-512 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted Skein-1024 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the Skein-1024 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted Skein-1024 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the Skein-1024 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted Snefru-128 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the Snefru-128 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted Snefru-128 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the Snefru-128 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Salted Snefru-256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been salted and hashed with the Snefru-256 hash algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Unsalted Snefru-256 Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed with the Snefru-256 hash algorithm, without salting.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Iterative Hash">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been hashed using an iterative hashing algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="AES">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been encrypted with the AES algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="Blowfish">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been encrypted with the Blowfish algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="DES">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been encrypted with the DES algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="IDEA">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been encrypted with the IDEA algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="RC4">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been encrypted with the RC4 algorithm.</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	        <xs:enumeration value="TEA">
+	            <xs:annotation>
+	                <xs:documentation>The authentication tokens have been encrypted with the Tiny Encryption Algorithm (TEA).</xs:documentation>
+	            </xs:annotation>
+	        </xs:enumeration>
+	    </xs:restriction>
+	</xs:simpleType>
+</xs:schema>