diff --git a/oval-schemas/aix-definitions-schema.xsd b/oval-schemas/aix-definitions-schema.xsd
index 4132d98..9543da8 100644
--- a/oval-schemas/aix-definitions-schema.xsd
+++ b/oval-schemas/aix-definitions-schema.xsd
@@ -21,6 +21,119 @@
+
+
+
+
+ The interim fix test is used to check information associated with different interim or emergency fixes installed on the system. The information being tested is based off the emgr -l -u VUID command. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an interim_fix_object and the optional state element specifies the information to check.
+
+
+ interim_fix_test
+ interim_fix_object
+ interim_fix_state
+ interim_fix_item
+
+
+
+
+ 5.12
+ This test has been deprecated due to lack of documented usage and will be removed in version 6.0 of the language.
+
+
+
+
+
+ - the object child element of a must reference a interim_fix_object
+
+
+ - the state child element of a must reference a interim_fix_state
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The interim_fix_object element is used by a interim_fix_test to define the specific fix to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
+ An interim_fix_object consists of a single vuid entity that identifies the fix to be used.
+
+
+
+
+
+
+
+
+
+ State referenced in filter for '' is of the wrong type.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Virtually Unique ID. A combination of time and cpuid, this ID can be used to differentiate fixes that are otherwise identical.
+
+
+
+
+
+
+
+
+
+
+
+
+ The interim_fix_state element defines the different information associated with a specific interim fix installed on the system. Please refer to the individual elements in the schema for more details about what each represents.
+
+
+
+
+
+
+
+ Virtually Unique ID. A combination of time and cpuid, this ID can be used to differentiate fixes that are otherwise identical.
+
+
+
+
+ Each efix that is installed on a given system has a unique efix label.
+
+
+
+
+ Describes the efix package.
+
+
+
+
+ The the emergency fix state.
+
+
+
+
+
+
+
+
@@ -746,6 +859,67 @@
+
+
+
+
+
+ The oslevel test reveals information about the release and maintenance level of AIX operating system. This information can be retrieved by the /usr/bin/oslevel -r command. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an oslevel_object and the optional state element specifies the metadata to check.
+
+
+
+ - the object child element of a oslevel_test must reference a oslevel_object
+
+
+ - the state child element of a oslevel_test must reference a oslevel_state
+
+
+
+
+
+ 5.12
+ This test has been deprecated due to lack of documented usage and will be removed in version 6.0 of the language.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The oslevel_object element is used by an oslevel test to define those objects to be evaluated based on a specified state. There is actually only one object relating to oslevel and this is the system as a whole. Therefore, there are no child entities defined. Any OVAL Test written to check oslevel will reference the same oslevel_object which is basically an empty object element.
+
+
+
+
+
+
+
+
+
+ The oslevel_state element defines the information about maintenance level (system version). Please refer to the individual elements in the schema for more details about what each represents.
+
+
+
+
+
+
+
+ This is the maintenance level (system version) of current AIX operating system.
+
+
+
+
+
+
@@ -833,6 +1007,55 @@
+
+
+ The EntityStateInterimFixStateType complex type defines the different values that are valid for the state entity of a interim_fix_state state. Please refer to the AIX documentation of Emergency Fix States. The empty string is also allowed as a valid value to support an empty element that is found when a variable reference is used within the state entity. Note that when using pattern matches and variables care must be taken to ensure that the regular expression and variable values align with the enumerated values.
+
+
+
+
+
+ The efix was installed with a standard installation, and successfully completed the last installation operation.
+
+
+
+
+ The efix was installed with a mount installation operation, and successfully completed the last installation or mount operation.
+
+
+
+
+ The efix was installed with a mount installation operation and one or more efix files were unmounted in a previous emgr command operation.
+
+
+
+
+ An unrecoverable error occurred during an installation or removal operation. The status of the efix is unreliable.
+
+
+
+
+ The efix is in the process of installing.
+
+
+
+
+ The efix was installed successfully and requires a reboot to fully integrate into the target system.
+
+
+
+
+ The efix is in the process of being removed.
+
+
+
+
+ The empty string value is permitted here to allow for empty elements associated with variable references.
+
+
+
+
+
The lssec command lists attributes stored in the security configuration stanza files. The following security configuration files contain attributes that you can specify with the Attribute parameter.
diff --git a/oval-schemas/aix-system-characteristics-schema.xsd b/oval-schemas/aix-system-characteristics-schema.xsd
index 475d65d..c61111f 100644
--- a/oval-schemas/aix-system-characteristics-schema.xsd
+++ b/oval-schemas/aix-system-characteristics-schema.xsd
@@ -20,6 +20,42 @@ elementFormDefault="qualified" version="6.0">
+
+
+
+
+ From emgr -l -u VUID Command. See instfix manpage for specific fields.
+
+
+
+
+
+
+
+ Virtually Unique ID. A combination of time and cpuid, this ID can be used to differentiate fixes that are otherwise identical.
+
+
+
+
+ Each efix that is installed on a given system has a unique efix label.
+
+
+
+
+ Describes the efix package.
+
+
+
+
+ The the emergency fix state.
+
+
+
+
+
+
+
+
@@ -278,6 +314,28 @@ elementFormDefault="qualified" version="6.0">
+
+
+
+
+ Information about the release and maintenance level of AIX operating system. This information can be retrieved by the /usr/bin/oslevel -r command.
+
+
+
+
+
+
+
+ This is the maintenance level (system version) of current AIX operating system.
+
+
+
+
+
+
+
+
+
@@ -358,6 +416,55 @@ elementFormDefault="qualified" version="6.0">
+
+
+ The EntityItemInterimFixStateType complex type defines the different values that are valid for the state entity of a interim_fix_state state. Please refer to the AIX documentation of Emergency Fix States. The empty string value is permitted here to allow for detailed error reporting.
+
+
+
+
+
+ The efix was installed with a standard installation, and successfully completed the last installation operation.
+
+
+
+
+ The efix was installed with a mount installation operation, and successfully completed the last installation or mount operation.
+
+
+
+
+ The efix was installed with a mount installation operation and one or more efix files were unmounted in a previous emgr command operation.
+
+
+
+
+ An unrecoverable error occurred during an installation or removal operation. The status of the efix is unreliable.
+
+
+
+
+ The efix is in the process of installing.
+
+
+
+
+ The efix was installed successfully and requires a reboot to fully integrate into the target system.
+
+
+
+
+ The efix is in the process of being removed.
+
+
+
+
+ The empty string value is permitted here to allow for detailed error reporting.
+
+
+
+
+
The lssec command lists attributes stored in the security configuration stanza files. The following security configuration files contain attributes that you can specify with the Attribute parameter.
diff --git a/oval-schemas/solaris-definitions-schema.xsd b/oval-schemas/solaris-definitions-schema.xsd
index 4003f24..04d3b1b 100644
--- a/oval-schemas/solaris-definitions-schema.xsd
+++ b/oval-schemas/solaris-definitions-schema.xsd
@@ -21,6 +21,390 @@
+
+
+
+
+
+ The package test is used to check information associated with different SVR4 packages installed on the system. Image Packaging System (IPS) packages are not supported by this test. The information used by this test is modeled after the /usr/bin/pkginfo command. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an package_object and the optional state element specifies the information to check.
+
+
+ package_test
+ package_object
+ package_state
+ package_item
+
+
+
+
+
+
+ - the object child element of a package_test must reference a package_object
+
+
+
+ - the state child element of a package_test must reference a package_state
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The package_object element is used by a package test to define the SVR4 packages to be evaluated. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
+ A package object consists of a single pkginst entity that identifies the package to be used.
+
+
+
+
+
+
+
+
+
+ State referenced in filter for '' is of the wrong type.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The pkginst entity is a string that represents a package designation by its instance. An instance can be the package abbreviation or a specific instance (for example, inst.1 or inst.2).
+
+
+
+
+
+
+
+
+
+
+
+
+ The package_state element defines the different information associated with SVR4 packages installed on the system. Please refer to the individual elements in the schema for more details about what each represents.
+
+
+
+
+
+
+
+ The pkginst entity is a string that represents a package designation by its instance. An instance can be the package abbreviation or a specific instance (for example, inst.1 or inst.2).
+
+
+
+
+ The name entity is a text string that specifies a full package name.
+
+
+
+
+ The category entity is a string in the form of a comma-separated list of categories under which a package may be displayed. Note that a package must at least belong to the system or application category. Categories are case-insensitive and may contain only alphanumerics. Each category is limited in length to 16 characters.
+
+
+
+
+ The version entity is a text string that specifies the current version associated with the software package. The maximum length is 256 ASCII characters and the first character cannot be a left parenthesis. Current Solaris software practice is to assign this parameter monotonically increasing Dewey decimal values of the form: major_revision.minor_revision[.micro_revision] where all the revision fields are integers. The versioning fields can be extended to an arbitrary string of numbers in Dewey-decimal format, if necessary.
+
+
+
+
+ The vendor entity is a string used to identify the vendor that holds the software copyright (maximum length of 256 ASCII characters).
+
+
+
+
+ The description entity is a string that represents a more in-depth description of a package.
+
+
+
+
+
+
+
+
+
+
+
+
+ The package511_test provides support for checking the metadata of packages installed using the Solaris Image Packaging System. The test extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references a package511_object and the optional state elements reference package511_states that specify the metadata to check about a set of packages.
+
+
+ package511_test
+ package511_object
+ package511_state
+ package511_item
+
+
+
+
+
+ - the object child element of an package511_test must reference an package511_object
+
+
+ - the state child element of an package511_test must reference an package511_state
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The package511_object element is used by a package511_test to identify the set of packages to check on a system. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
+
+
+
+
+
+
+
+
+
+ State referenced in filter for '' is of the wrong type.
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The person, group of persons, or organization that is the source of the package. The publisher should be expressed without leading "pkg:" or "//" components.
+
+
+
+
+ The full hierarchical name of the package which is separated by forward slash characters. The full name should be expressed without leading "pkg:/" or "/" components.
+
+
+
+
+ The version of the package which consists of the component version, build version, and branch version.
+
+
+
+
+ The timestamp when the package was published in the ISO-8601 basic format (YYYYMMDDTHHMMSSZ).
+
+
+
+
+
+
+
+
+
+
+
+
+ The package511_state element defines the different system state information that can be used to check the metadata associated with the specified IPS packages on a Solaris system.
+
+
+
+
+
+
+
+ The person, group of persons, or organization that is the source of the package. The publisher should be expressed without leading "pkg:" or "//" components.
+
+
+
+
+ The full hierarchical name of the package which is separated by forward slash characters. The full name should be expressed without leading "pkg:/" or "/" components.
+
+
+
+
+ The version of the package which consists of the component version, build version, and branch version.
+
+
+
+
+ The timestamp when the package was published in the ISO-8601 basic format (YYYYMMDDTHHMMSSZ).
+
+
+
+
+ The Fault Management Resource Identifier (FMRI) of the package which uniquely identifies the package on the system.
+
+
+
+
+ A summary of what the package provides.
+
+
+
+
+ A description of what the package provides.
+
+
+
+
+ The category of the package.
+
+
+
+
+ A boolean value indicating whether or not updates are available for this package.
+
+
+
+
+
+
+
+
+
+
+
+
+ The patch test is used to check information associated with different patches for SVR4 packages installed on the system. Image Packaging System (IPS) packages do not support patches and are not supported by this test. The information being tested is based off the /usr/bin/showrev -p command. It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description for more information. The required object element references an inetd_object and the optional state element specifies the information to check.
+
+
+ patch54_test
+ patch54_object
+ patch_state
+ patch_item
+
+
+
+
+
+
+ - the object child element of a patch54_test must reference a patch54_object
+
+
+
+ - the state child element of a patch54_test must reference a patch_state
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The patch54_object element is used by a patch test to define the specific patch to be evaluated. Patches are identified by unique alphanumeric strings, with the patch base code first, a hyphen, and a number that represents the patch revision number. Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType description for more information. The common set element allows complex objects to be created using filters and set logic. Again, please refer to the description of the set element in the oval-definitions-schema.
+ A patch object consists of a base entity that identifies the patch to be used, and a version entity that represent the patch revision number.
+
+
+
+
+
+
+
+
+
+ State referenced in filter for '' is of the wrong type.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ The base entity represents a patch base code found before the hyphen.
+
+
+
+
+ The version entity represents a patch version number found after the hyphen.
+
+
+
+
+
+
+
+
+
+
+
+
+ The patch_state element defines the different information associated with a specific patch for an SVR4 package installed on the system. Patches are identified by unique alphanumeric strings, with the patch base code first, a hyphen, and a number that represents the patch revision number. Please refer to the individual elements in the schema for more details about what each represents.
+
+
+
+
+
+
+
+ The base entity reresents a patch base code found before the hyphen.
+
+
+
+
+ The version entity represents a patch version number found after the hyphen.
+
+
+
+
+
+
+
+
+
+ The PatchBehaviors complex type defines a number of behaviors that allow a more detailed definition of the patch_object being specified. Note that using these behaviors may result in some unique results. For example, a double negative type condition might be created where an object entity says include everything except a specific item, but a behavior is used that might then add that item back in.
+
+
+
+ 'supersedence' specifies that the object should also match any superseding patches to the one being specified. In Solaris, a patch can be superseded in two ways. The first way is implicitly when a new revision of a patch is released (e.g. patch 12345-02 supersedes patch 12345-01). The second way is explicitly where a new patch contains the complete functionality of another patch. If set to 'true', the resulting object set would be the original patch specified plus any superseding patches. The default value is 'false' meaning the object should only match the specified patch.
+
+
+
+
+
+
+
diff --git a/oval-schemas/solaris-system-characteristics-schema.xsd b/oval-schemas/solaris-system-characteristics-schema.xsd
index 1b38ba4..1784e7e 100644
--- a/oval-schemas/solaris-system-characteristics-schema.xsd
+++ b/oval-schemas/solaris-system-characteristics-schema.xsd
@@ -20,6 +20,139 @@
+
+
+
+
+ The package_item holds information about installed SVR4 packages. Output of /usr/bin/pkginfo. See pkginfo(1).
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ This item stores system state information associated with IPS packages installed on a Solaris system.
+
+
+
+
+
+
+
+ The person, group of persons, or organization that is the source of the package. The publisher should be expressed without leading "pkg:" or "//" components.
+
+
+
+
+ The full hierarchical name of the package which is separated by forward slash characters. The full name should be expressed without leading "pkg:/" or "/" components.
+
+
+
+
+ The version of the package which consists of the component version, build version, and branch version.
+
+
+
+
+ The timestamp when the package was published in the ISO-8601 basic format (YYYYMMDDTHHMMSSZ).
+
+
+
+
+ The Fault Management Resource Identifier (FMRI) of the package which uniquely identifies the package on the system.
+
+
+
+
+ A summary of what the package provides.
+
+
+
+
+ A description of what the package provides.
+
+
+
+
+ The category of the package.
+
+
+
+
+ A boolean value indicating whether or not updates are available for this package.
+
+
+
+
+
+
+
+
+
+
+
+
+ Patches for SVR4 packages are identified by unique alphanumeric strings, with the patch base code first, a hyphen, and a number that represents the patch revision number. The information can be obtained using /usr/bin/showrev -p. Please see showrev(1M).
+
+
+
+
+
+
+
+ The base entity reresents a patch base code found before the hyphen.
+
+
+
+
+ The version entity represents a patch version number found after the hyphen.
+
+
+
+
+
+
+
+