Docs for schema item oval_results in Open Vulnerability and Assessment Language (OVAL®)

The root element of an OVAL Results Document binding all of the results together along with the associated test elements. It must contain exactly one generators child element and exactly one system_info child element. The other child elements are optional. The oval_results element is the root of an OVAL results document, and must occur exactly once. Its purpose is to bind together the five major sections of a results file - generators, system_info, definitions, tests, and variables - which are the children of the oval_results element. The generator section must be present and provides information about when the results file was compiled and under what version. The require system_info element is used to record information about the system being described. 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:element name="oval_results"> <xsd:annotation> <xsd:documentation>The root element of an OVAL Results Document binding all of the results together along with the associated test elements. It must contain exactly one generators child element and exactly one system_info child element. The other child elements are optional.</xsd:documentation> <xsd:documentation>The oval_results element is the root of an OVAL results document, and must occur exactly once. Its purpose is to bind together the five major sections of a results file - generators, system_info, definitions, tests, and variables - which are the children of the oval_results element. The generator section must be present and provides information about when the results file was compiled and under what version. The require system_info element is used to record information about the system being described.</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>none</attributes> <content>none</content> <parent_elements>none</parent_elements> <child_elements>generators, system_info, [definitions], [tests], [variables], [Signature]</child_elements> </xsd:appinfo> </xsd:annotation> <xsd:complexType> <xsd:sequence> <xsd:element ref="oval_results:generators" minOccurs="1" maxOccurs="1" /> <xsd:element ref="oval_results:system_info" minOccurs="1" maxOccurs="1" /> <xsd:element ref="oval_results:definitions" minOccurs="0" maxOccurs="1" /> <xsd:element ref="oval_results:tests" minOccurs="0" maxOccurs="1" /> <xsd:element ref="oval_results:variables" minOccurs="0" maxOccurs="1" /> <xsd:element ref="ds:Signature" minOccurs="0" maxOccurs="1" /> </xsd:sequence> </xsd:complexType> <xsd:key name="definitionInstanceKey"> <xsd:annotation> <xsd:documentation>Enforce uniqueness in the combination of OVAL id and instance id in order to differentiate the individual definition elements.</xsd:documentation> </xsd:annotation> <xsd:selector xpath="oval_results:definitions/oval_results:definition" /> <xsd:field xpath="@id" /> <xsd:field xpath="@instance" /> </xsd:key> <xsd:key name="testVersionKey"> <xsd:annotation> <xsd:documentation>Enforce uniqueness in the combination of the individual test ids and the version of the test.</xsd:documentation> </xsd:annotation> <xsd:selector xpath="oval_results:tests/*" /> <xsd:field xpath="@id" /> <xsd:field xpath="@version" /> </xsd:key> <xsd:key name="variableVersionKey"> <xsd:annotation> <xsd:documentation>Enforce uniqueness in the combination of the individual variable ids and the version of the variable.</xsd:documentation> </xsd:annotation> <xsd:selector xpath="oval_results:variables/oval_results:variable" /> <xsd:field xpath="@id" /> <xsd:field xpath="@version" /> </xsd:key> <xsd:keyref name="testVersionKeyRef" refer="oval_results:testVersionKey"> <xsd:annotation> <xsd:documentation>Require each test reference in a criterion element to refer to a valid test id, version combination.</xsd:documentation> </xsd:annotation> <xsd:selector xpath="oval_results:definitions/oval_results:definition/oval_results:criteria/oval_results:*/oval_results:criterion" /> <xsd:field xpath="@test_ref" /> <xsd:field xpath="@version" /> </xsd:keyref> <xsd:keyref name="subtestVersionKeyRef" refer="oval_results:testVersionKey"> <xsd:annotation> <xsd:documentation>Require each test reference in a subtest element to refer to a valid test id, version combination.</xsd:documentation> </xsd:annotation> <xsd:selector xpath="oval_results:tests/oval_results:compound_test/oval_results:subtest" /> <xsd:field xpath="@test_ref" /> <xsd:field xpath="@version" /> </xsd:keyref> </xsd:element>

Definition Type:	Element
Name:	oval_results
Namespace:	http://oval.mitre.org/XMLSchema/oval_results
Containing Schema:	oval-results-schema.xsd
Abstract
Documentation:	The root element of an OVAL Results Document binding all of the results together along with the associated test elements. It must contain exactly one generators child element and exactly one system_info child element. The other child elements are optional. The oval_results element is the root of an OVAL results document, and must occur exactly once. Its purpose is to bind together the five major sections of a results file - generators, system_info, definitions, tests, and variables - which are the children of the oval_results element. The generator section must be present and provides information about when the results file was compiled and under what version. The require system_info element is used to record information about the system being described. 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.