<xsd:schema targetNamespace="http://oval.mitre.org/XMLSchema/system_characteristics" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:system_characteristics="http://oval.mitre.org/XMLSchema/system_characteristics" elementFormDefault="qualified" version="4.2">
<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="https://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd"/>
<xsd:annotation>
<xsd:documentation>The following is a description of the elements, types, and attributes that compose the core schema for encoding Open Vulnerability and Assessment Language (OVAL) System Characteristics. The Core System Characteristics Schema defines all operating system independent objects. These objects are extended and enhanced by individual family schemas, which are described in separate documents. Each of the elements, types, and attributes that make up the Core System Characteristics Schema are described in detail and should provide the information necessary to understand what each object represents. This document is intended for developers and assumes some familiarity with XML. A high level description of the interaction between these objects is not outlined here.</xsd:documentation>
<xsd:documentation>The OVAL Schema is maintained by The Mitre Corporation and developed by the public OVAL Community. For more information, including how to get involved in the project and how to submit change requests, please visit the OVAL website at http://oval.mitre.org.</xsd:documentation>
<xsd:appinfo>
<schema>Core System Characteristics</schema>
<version>4.2</version>
<date>2 December 2005</date>
</xsd:appinfo>
</xsd:annotation>
<!-- =============================================================================== -->
<!-- =============================================================================== -->
<!-- =============================================================================== -->
<xsd:element name="system_characteristics">
<xsd:annotation>
<xsd:documentation>The system_characteristics element is the root of an OVAL System Characteristics Document, and must occur exactly once. Its purpose is to bind together the three major sections of a system characteristics file - generator, system_info, and system_data - which are the children of the system_characteristics element. The generator section must be present and provides information about when the system characteristics file was compiled and under what version. The require system_info element is used to record information about the system being described. The optional system_data section defines the specific characteristics that have been collected from the system.</xsd:documentation>
<xsd:documentation>The optional Signature element allows an XML Signature as defined by the W3C to be attached to the document. This allows authentication and data integrety to be provided to the user. Enveloped signatures are supported.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>family</attributes>
<content>none</content>
<parent_elements>none</parent_elements>
<child_elements>generator, system_info, [system_data], [Signature]</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="system_characteristics:generator" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:system_info" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:system_data" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="ds:Signature" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="family" type="system_characteristics:families" use="required"/>
</xsd:complexType>
<xsd:key name="itemIdKey">
<xsd:annotation>
<xsd:documentation>Enforce uniqueness amongst the individual ids.</xsd:documentation>
</xsd:annotation>
<xsd:selector xpath="system_characteristics:system_data/*/*"/>
<xsd:field xpath="@id"/>
</xsd:key>
</xsd:element>
<!-- =============================================================================== -->
<!-- ================================= GENERATOR ================================= -->
<!-- =============================================================================== -->
<xsd:element name="generator">
<xsd:annotation>
<xsd:documentation>The generator element is used to format information about what application generated a particular file. This type is used to specify the source of the OVAL Definitions, the application used for the analysis, and optionally the application used for data collection.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>none</content>
<parent_elements>system_characteristics</parent_elements>
<child_elements>product_name, product_version, schema_version, timestamp</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="system_characteristics:product_name" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="system_characteristics:product_version" minOccurs="0" maxOccurs="1"/>
<xsd:element ref="system_characteristics:schema_version" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:timestamp" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="product_name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The name of the application used to generate this file of OVAL definitions.</xsd:documentation>
<xsd:appinfo>
<cardinality>0-1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>generator</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="product_version" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The version of the product used to generate this file of OVAL definitions</xsd:documentation>
<xsd:appinfo>
<cardinality>0-1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>generator</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="schema_version" type="xsd:decimal">
<xsd:annotation>
<xsd:documentation>This element defines the version of the OVAL schema that the document has been validated against.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>decimal</content>
<parent_elements>generator</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="timestamp" type="system_characteristics:timeStamp">
<xsd:annotation>
<xsd:documentation>This element specifies the date/time at which the document was created. This timestamp can be used to differentiate between multiple OVAL files and to determine which document is the most up-to-date. The timestamp is of the form yyyymmddhhmmss.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>generator</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!-- =============================================================================== -->
<!-- ================================ SYSTEM INFO ================================ -->
<!-- =============================================================================== -->
<xsd:element name="system_info">
<xsd:annotation>
<xsd:documentation>The system_info element specifies general information about the system that data was collected from including information that can be used to identify the system.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>system_characteristics</parent_elements>
<child_elements>os_name, os_version, architecture, primary_host_name, interfaces</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="system_characteristics:os_name" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:os_version" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:architecture" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:primary_host_name" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:interfaces" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="os_name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The operating system of the machine the data was collected from.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>system_info</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="os_version" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The version of the operating system of the machine the data was collected from.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>system_info</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="architecture" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The architecture of the machine the data was collected from.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>system_info</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="primary_host_name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The primary host name of the machine the data was collected from.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>system_info</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="interfaces">
<xsd:annotation>
<xsd:documentation>The interfaces element holds a collection of interface elements that describe each interface on the machine that data was collected from.</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>system_info</parent_elements>
<child_elements>interface</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="system_characteristics:interface" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="interface">
<xsd:annotation>
<xsd:documentation>The interface element is used to describe an interface on a system.</xsd:documentation>
<xsd:appinfo>
<cardinality>1-n</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>interfaces</parent_elements>
<child_elements>interface_name, ip_address, mac_address</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="system_characteristics:interface_name" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:ip_address" minOccurs="1" maxOccurs="1"/>
<xsd:element ref="system_characteristics:mac_address" minOccurs="1" maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="interface_name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The name of the interface</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>interface</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ip_address" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The ip address of the interface</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>interface</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="mac_address" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The mac address of the interface</xsd:documentation>
<xsd:appinfo>
<cardinality>1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>interface</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<!-- =============================================================================== -->
<!-- ================================ SYSTEM DATA ================================ -->
<!-- =============================================================================== -->
<xsd:element name="system_data">
<xsd:annotation>
<xsd:documentation>The system_data element is a container for one or more item_container elements.</xsd:documentation>
<xsd:appinfo>
<cardinality>0-1</cardinality>
<attributes>none</attributes>
<content>none</content>
<parent_elements>system_characteristics</parent_elements>
<child_elements>item_container</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="system_characteristics:item_container" minOccurs="1" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="item_container" abstract="true">
<xsd:annotation>
<xsd:documentation>The item_container abstract element is extended (via substitution groups) by the different containers found in the family schemas. Each item_container should contain a number of abstract item elements.</xsd:documentation>
<xsd:appinfo>
<cardinality>1-n</cardinality>
<attributes>none</attributes>
<content>none</content>
<parent_elements>system_data</parent_elements>
<child_elements>item</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="item" type="system_characteristics:itemType" abstract="true">
<xsd:annotation>
<xsd:documentation>The abstract item element is a container for information about an item on a system. An item might be a file, a rpm, a process, etc. This element is extended by the different families through substitution groups. Each item represents a unique object as specified by the object section of the item. There are cases where the object declaration results in many different instances, all described by the unique object section. An example of this would be in the wmi_item where a wql query my return multiple instances. Each instance would be represented by a different item in the system characterics file, yet each item would have the same object section.</xsd:documentation>
<xsd:appinfo>
<cardinality>1-n</cardinality>
<attributes>id</attributes>
<content>none</content>
<parent_elements>item_container</parent_elements>
<child_elements>(specified through extension)</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="itemType">
<xsd:annotation>
<xsd:documentation>The itemType specifies an optional message element as well as the id attribute.</xsd:documentation>
<xsd:appinfo>
<attributes>id</attributes>
<content>none</content>
<child_elements>[message]</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element ref="system_characteristics:message" minOccurs="0" maxOccurs="1"/>
</xsd:sequence>
<xsd:attribute name="id" type="system_characteristics:itemId" use="required"/>
</xsd:complexType>
<xsd:element name="message" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The message element is used to store helpful messages reported during data collection on a system.</xsd:documentation>
<xsd:appinfo>
<cardinality>0-1</cardinality>
<attributes>none</attributes>
<content>string</content>
<parent_elements>item</parent_elements>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="objectType">
<xsd:annotation>
<xsd:documentation>The object type specifies an element that shall be used as a container for an object on a system. Examples of objects are: a file path, a registry key, a user name. If the specified object is not found on a system the optional status attribute is set to 'does not exist'.</xsd:documentation>
<xsd:appinfo>
<attributes>[status]</attributes>
<content>none</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:attribute name="status" type="system_characteristics:statusType" use="optional" default="exists"/>
</xsd:complexType>
<xsd:complexType name="dataType">
<xsd:annotation>
<xsd:documentation>The data type specifies an element that shall be used as a container for a data related to an object on a system. Examples of data are: a file version, a registry key value, a user's rights.</xsd:documentation>
<xsd:appinfo>
<attributes>none</attributes>
<content>none</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
</xsd:complexType>
<xsd:attributeGroup name="objectAttributes">
<xsd:annotation>
<xsd:documentation>The possible attributes for an element in the object section of an item. The optional datatype attribute can be either 'literal' or 'pattern match'. A value of pattern match is for reporting information about the collection of objects associated with a specific pattern. Helps answers the question 'How do I know that everything that matches this pattern is in the SC file?' The pattern would be presented and the status would reflect the data collection as a whole. Then each matching object would exists on their own with a datatype of literal.</xsd:documentation>
<xsd:appinfo>
<attributes>[datatype]</attributes>
</xsd:appinfo>
</xsd:annotation>
<xsd:attribute name="datatype" type="system_characteristics:objectDatatypes" use="optional" default="literal"/>
</xsd:attributeGroup>
<xsd:complexType name="objectIntType">
<xsd:annotation>
<xsd:documentation>Describes an integer element in an object section of an item and specified its attributes.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes objectAttributes)</attributes>
<content>integer</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:integer">
<xsd:attributeGroup ref="system_characteristics:objectAttributes"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="objectStringType">
<xsd:annotation>
<xsd:documentation>Describes a string element in an object section of an item and specified its attributes.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes objectAttributes)</attributes>
<content>string</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attributeGroup ref="system_characteristics:objectAttributes"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="objectBaseType">
<xsd:annotation>
<xsd:documentation>Describes complex data along with the standard object element attributes.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes objectAttributes)</attributes>
<content>(anyType)</content>
<child_elements>(anyType)</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:restriction base="xsd:anyType">
<xsd:attributeGroup ref="system_characteristics:objectAttributes"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<xsd:attributeGroup name="dataAttributes">
<xsd:annotation>
<xsd:documentation>The possible attributes for an element in the data section of an item. The optional datatype determines the type of data expected. (the default datatype is 'string') The datatype attribute is optional in order to keep the XML clean and readable. The default value is used most of the time and putting datatype="string" for each element would muddy up the XML. The optional status attribute holds information regarding the success of the data collection. For example, if there was an error collecting a particular piece of data, then the status would be 'error'.</xsd:documentation>
<xsd:appinfo>
<attributes>[datatype], [status]</attributes>
</xsd:appinfo>
</xsd:annotation>
<xsd:attribute name="datatype" type="system_characteristics:dataDatatypes" use="optional" default="string"/>
<xsd:attribute name="status" type="system_characteristics:statusType" use="optional" default="exists"/>
</xsd:attributeGroup>
<xsd:complexType name="dataBoolType">
<xsd:annotation>
<xsd:documentation>Describes simple boolean data along with the standard data element attributes. The empty string is listed to allow and element of this type to be empty. This might occur when an error is reported on that element.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes dataAttributes)</attributes>
<content>boolean</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="system_characteristics:dataStringType">
<xsd:enumeration value="true"/>
<xsd:enumeration value="false"/>
<xsd:enumeration value="1"/>
<xsd:enumeration value="0"/>
<xsd:enumeration value=""/>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="dataIntType">
<xsd:annotation>
<xsd:documentation>Describes simple integer data along with the standard data element attributes.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes dataAttributes)</attributes>
<content>integer</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:integer">
<xsd:attributeGroup ref="system_characteristics:dataAttributes"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="dataStringType">
<xsd:annotation>
<xsd:documentation>Describes simple string data along with the standard data element attributes.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes dataAttributes)</attributes>
<content>string</content>
<child_elements>none</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attributeGroup ref="system_characteristics:dataAttributes"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="dataBaseType">
<xsd:annotation>
<xsd:documentation>Describes complex data along with the standard data element attributes.</xsd:documentation>
<xsd:appinfo>
<attributes>(includes dataAttributes)</attributes>
<content>(anyType)</content>
<child_elements>(anyType)</child_elements>
</xsd:appinfo>
</xsd:annotation>
<xsd:complexContent>
<xsd:restriction base="xsd:anyType">
<xsd:attributeGroup ref="system_characteristics:dataAttributes"/>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<!-- =============================================================================== -->
<!-- ================================= OTHER TYPES =============================== -->
<!-- =============================================================================== -->
<xsd:simpleType name="dataDatatypes">
<xsd:annotation>
<xsd:documentation>This simple type defines the legal data types that are used to describe data sub elements in items.</xsd:documentation>
<xsd:documentation>The component datatype represents a value that is built from one or more component strings. Each component can be a literal string or can reference a value held elsewhere, say a registry key.</xsd:documentation>
<xsd:documentation>The version datatype represents a value that is a hierarchical list of versions. For example '#.#.#' or '#-#-#-#' where the numbers to the left are 'more significant' than the numbers to the right.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="binary"/>
<xsd:enumeration value="boolean"/>
<xsd:enumeration value="component"/>
<xsd:enumeration value="float"/>
<xsd:enumeration value="int"/>
<xsd:enumeration value="string"/>
<xsd:enumeration value="version"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="families">
<xsd:annotation>
<xsd:documentation>The families simple type is a listing of families that OVAL supports at this time.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="aix"/>
<xsd:enumeration value="apache"/>
<xsd:enumeration value="debian"/>
<xsd:enumeration value="freebsd"/>
<xsd:enumeration value="hp-ux"/>
<xsd:enumeration value="ios"/>
<xsd:enumeration value="macos"/>
<xsd:enumeration value="openbsd"/>
<xsd:enumeration value="oracle"/>
<xsd:enumeration value="os400"/>
<xsd:enumeration value="pix"/>
<xsd:enumeration value="redhat"/>
<xsd:enumeration value="solaris"/>
<xsd:enumeration value="suse"/>
<xsd:enumeration value="windows"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="itemId">
<xsd:annotation>
<xsd:documentation>Define acceptable item ids as an integer.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:integer"/>
</xsd:simpleType>
<xsd:simpleType name="objectDatatypes">
<xsd:annotation>
<xsd:documentation>Define acceptable data types for an element in an object section.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="literal"/>
<xsd:enumeration value="pattern match"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="statusType">
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="error"/>
<xsd:enumeration value="exists"/>
<xsd:enumeration value="does not exist"/>
<xsd:enumeration value="not collected"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType name="timeStamp">
<xsd:annotation>
<xsd:documentation>Define acceptable timestamps as a string with the form yyyymmddhhmmss.</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:pattern value="\d{14}"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
|
XSD Schema Code: