Sandbox Approach and Conventions

The OVAL Language Sandbox utilizes an experimental namespace to distinguish experimental capabilities from those in the official OVAL Language. The experimental namespace uses the following format.

http://oval.mitre.org/XMLSchema/x-<schema-destination>-<capability>

In this format, <schema-destination> is the OVAL Language schema where the capability will reside if migrated into an official OVAL Language release (e.g. oval, oval-def, macos, macos-def, etc.) and <capability> is the name of the new capability (e.g. pkgutil-test, artifact-hunting, etc.). For consistency, if multiple words are used for either of these values, they should be separated using hyphens. Similarly, the schema files that contain the experimental capabilities will use the following format.

x-<schema-destination>-<capability>.xsd

The primary reason for allowing capabilities to be specified in their own schema files as opposed to requiring that all capabilities destined for a particular OVAL Language schema be specified in a single file (e.g. all Windows capabilities going into a Windows schema file) is to allow for the flexibility of only using the capabilities that are needed. That is, not everyone will want to use every experimental capability for a particular OVAL Language schema. This also has the added benefit of making it much easier to review a particular capability and any changes that are made to it.

Lastly, to allow for the experimental capabilities to build off of the constructs in the official release of the OVAL Language, the schemas associated with the most current official OVAL Language release will be included in the OVAL Language Sandbox. This will ensure that the community has the ability to use the latest constructs in the OVAL Language, capabilities will progress with the OVAL Language, and the migration of capabilities into an official release of the OVAL Language will be as smooth as possible.