<xsd:complexType name="MetadataType">
<xsd:annotation>
<xsd:documentation>The MetadataType complex type contains all the metadata available to an OVAL Definition. This metadata is for informational purposes only and is not part of the criteria used to evaluate machine state. The required title child element holds a short string that is used to quickly identify the definition to a human user. The affected metadata item contains information about the system(s) for which the definition has been written. Remember that this is just metadata and not part of the criteria. Please refer to the AffectedType description for more information. The required description element contains a textual description of the configuration state being addressed by the OVAL Definition. In the case of a definition from the vulnerability class, the reference is usually the Common Vulnerability and Exposures (CVE) Identifier, and this description field corresponds with the CVE description.</xsd:documentation>
<xsd:documentation>Additional metadata is also allowed although it is not part of the official OVAL Schema. Individual organizations can place metadata items that they feel are important and these will be skipped during the validation. All OVAL really cares about is that the stated metadata items are there.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="title" type="xsd:string" minOccurs="1" maxOccurs="1" />
<xsd:element name="affected" type="oval-def:AffectedType" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="reference" type="oval-def:ReferenceType" minOccurs="0" maxOccurs="unbounded" />
<xsd:element name="description" type="xsd:string" minOccurs="1" maxOccurs="1" />
<xsd:any minOccurs="0" maxOccurs="unbounded" processContents="skip" />
<!-- For the next major release of OVAL, the xsd:any tag above will be modified to
only allow elements from namespaces other than the default namespace. This
fixes a bug in the current schema where the affected or reference element can
appear after the description element and still produce a vailid document.
<xsd:any minOccurs="0" maxOccurs="unbounded" namespace="##other" processContents="skip"/>
-->
</xsd:sequence>
</xsd:complexType>
|
XSD Schema Diagram:
