Definition Type: ComplexType
Name: componentType
Namespace: http://oval.mitre.org/XMLSchema/oval#macos
Type: oval:subtestBaseType
Containing Schema: macos-schema.xsd
Abstract
Documentation:
The componentType allows a value to be obtained by combining pieces from different sources. Each string defined by the different component elements is concatenated together to form the final string used. Each child component element has an attribute called type. The value of this attribute determines where to get the string used to build the file path. A type of literal means to use the value of the child component element as is, and to just concatenated it to the other strings. If a pattern match operator has been specified with a componentType, then the final string should be thought of as the pattern to test. As of Version 4 of the OVAL schema, pattern match can not be specified for the idividual components.
Collapse XSD Schema Diagram:
Drilldown into component in schema macos-schema_xsd Drilldown into var_ref in schema oval-schema_xsd Drilldown into operator in schema oval-schema_xsd Drilldown into datatype in schema oval-schema_xsd Drilldown into subtestAttributes in schema oval-schema_xsd Drilldown into subtestBaseType in schema oval-schema_xsd Drilldown into maxdepth in schema macos-schema_xsd Drilldown into recurse in schema macos-schema_xsdXSD Diagram of componentType in schema macos-schema_xsd (Open Vulnerability and Assessment Language (OVAL®))
Collapse XSD Schema Code:
<xsd:complexType name="componentType">
    <xsd:annotation>
        <xsd:documentation>The componentType allows a value to be obtained by combining pieces from different sources.  Each string defined by the different component elements is concatenated together to form the final string used.  Each child component element has an attribute called type.  The value of this attribute determines where to get the string used to build the file path.  A type of literal means to use the value of the child component element as is, and to just concatenated it to the other strings.  If a pattern match operator has been specified with a componentType, then the final string should be thought of as the pattern to test.  As of Version 4 of the OVAL schema, pattern match can not be specified for the idividual components.</xsd:documentation>
        <xsd:appinfo>
            <extends>oval:subtestBaseType</extends>
            <attributes>(includes oval:subtestAttributes)</attributes>
            <content>none</content>
            <child_elements>component</child_elements>
        </xsd:appinfo>
    </xsd:annotation>
    <xsd:complexContent>
        <xsd:extension base="oval:subtestBaseType">
            <xsd:sequence>
                <xsd:element name="component" minOccurs="1" maxOccurs="unbounded">
                    <xsd:complexType>
                        <xsd:simpleContent>
                            <xsd:extension base="xsd:string">
                                <xsd:attribute name="type" use="required">
                                    <xsd:simpleType>
                                        <xsd:restriction base="xsd:string">
                                            <xsd:enumeration value="environment_variable" />
                                            <xsd:enumeration value="group_homedirs" />
                                            <xsd:enumeration value="literal" />
                                            <xsd:enumeration value="user_homedirs" />
                                        </xsd:restriction>
                                    </xsd:simpleType>
                                </xsd:attribute>
                            </xsd:extension>
                        </xsd:simpleContent>
                    </xsd:complexType>
                </xsd:element>
            </xsd:sequence>
            <xsd:attribute name="recurse" default="NONE">
                <xsd:annotation>
                    <xsd:documentation>Defines how to recurse into the PATH element.  Default is 'NONE' for no recursion, other options define if the recursion examines files only, directories only, or both.</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                        <xsd:enumeration value="NONE" />
                        <xsd:enumeration value="FILES" />
                        <xsd:enumeration value="DIRECTORIES" />
                        <xsd:enumeration value="FILE_AND_DIRECTORIES" />
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
            <xsd:attribute name="maxdepth" default="-1">
                <xsd:annotation>
                    <xsd:documentation>
							Defines the maximum depth to traverse to during recursion.  Default is '-1', meaning 'no limitation'.  A value of 0 is equivalent to no recursion, 1 means to step only one directory level down, and so on.  These values (0+) are equivalent to the command line 'find' command.
						</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                    <xsd:restriction base="xsd:integer">
                        <xsd:fractionDigits value="0">
                        </xsd:fractionDigits>
                    </xsd:restriction>
                </xsd:simpleType>
            </xsd:attribute>
        </xsd:extension>
    </xsd:complexContent>
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
component macos:component 1 unbounded
Collapse Child Attributes:
Name Type Default Value Use
datatype oval:datatype string Optional
operator oval:operator equals Optional
var_ref oval:var_ref Optional
recurse macos:recurse NONE (Optional)
maxdepth macos:maxdepth -1 (Optional)
<anyAttribute>
Collapse Derivation Tree:
Collapse References:
macos:path, macos:path, macos:path, macos:path