Version 5.5 (Archived)

This page provides information on proposed changes to the OVAL Language. All information about the new version is included in this centralized location. Read the Review Process.

Downloads

Includes downloads for the Version 5.5 Definition Schema, System Characteristics Schema, Results Schema, Variable Schema, and Documentation.

KEY
Complete Schema - has all documentation embedded and the Schematron mark-up.
Minimal Schema - includes the raw xml schema only.
Schematron - a schema that can provide additional validation of OVAL V5 documents.
Documentation pdf - includes element dictionaries, etc., which users can elect to view in a browser or save.
All files zip - all files zipped together to allow for one simple download.
xsd - a user can either right click to download the file or left click to open the file in their default viewer.

OVAL Definition Schema Downloads

File Name Complete Schema Minimal Schema Documentation Schematron
All Files zip zip zip zip
Core xsd xsd html -
Common xsd xsd html -
Independent xsd xsd html -
Apache xsd xsd html -
Apple Macintosh xsd xsd html -
Cisco CatOS xsd xsd html -
Cisco IOS xsd xsd html -
Cisco PixOS xsd xsd html -
FreeBSD xsd xsd html -
HP-UX xsd xsd html -
IBM AIX xsd xsd html -
Linux xsd xsd html -
Microsoft Windows xsd xsd html -
Sun Solaris xsd xsd html -
UNIX xsd xsd html -
Vmware ESX xsd xsd html -
 
 

OVAL System Characteristics Schema Downloads

File Name Complete Schema Minimal Schema Documentation Schematron
All Files zip zip zip zip
Core xsd xsd html -
Common xsd xsd html -
Independent xsd xsd html -
Apache xsd xsd html -
Apple Macintosh xsd xsd html -
Cisco CatOS xsd xsd html -
Cisco IOS xsd xsd html -
Cisco PixOS xsd xsd html -
FreeBSD xsd xsd html -
HP-UX xsd xsd html -
IBM AIX xsd xsd html -
Linux xsd xsd html -
Microsoft Windows xsd xsd html -
Sun Solaris xsd xsd html -
UNIX xsd xsd html -
Vmware ESX xsd xsd html -
 

OVAL Results Schema Downloads

File Name Complete Schema Minimal Schema Documentation Schematron
All Files zip zip zip zip
Core xsd xsd html -
Common xsd xsd html -
 

OVAL Variables Schema Downloads

File Name Complete Schema Minimal Schema Documentation Schematron
All Files zip zip zip zip
Core xsd xsd html -
Common xsd xsd html -
 

Example XML Stylesheets

File Name Description
results_to_html.xsl The results_to_html stylesheet converts an OVAL Results document into a more readable html format.
minimal_schema.xsl The minimal_schema stylesheet removes all annotation elements from the OVAL Schema leaving only the minimal schema.
element_dictionary.xsl The element_dictionary stylesheet creates documentation files from the OVAL Schema.
reference_mapping.xsl The reference_mapping stylesheet creates a map between each OVAL Definition in a document and a specified reference source.
Back to top

New in Version 5.5

Version 5.5 of the OVAL Schema is a direct result of feedback from the OVAL Community. This will be a minor version change and should not require extensive development by tools that support earlier versions of the Language. Existing content will be forward compatible with the 5.4 schemas. The changes pending to the different schemas are outlined below. "Open" status means the item is under consideration or being worked upon, "Closed" status means that the item has been incorporated and work on it is completed, and "Suspended" status means that the item will not be included in this version but may be included in a future version.

Items addressed in this version include:

ID Title Status Date Opened Resolution
8966 make sure minoccurs or maxoccurs appears in element dictionaries Closed 2006-06-15 n/a
Priority: Very Low | Category: n/a | Date Closed: 2008-08-04 23:45:35
Details:
There seems to be some types/groups with missing MinOccurs and MaxOccurs information.  It appears that this is because such information was not put into the schema file as the schema file uses defaults in this case.
Follow-ups:
Date Added: 2008-08-04 23:45:35
fixed the stylesheet to use the defualt value of 1 if a minOccurs or MaxOccurs attribute is not present.

15099 add schematron to make the var_check attribute required when var_ref used Closed 2008-04-18 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-08-04 21:20:32
Details:
currently var_check is optional with default of 'all'.  We find that users don't add the var_check and it could be dangerous if the default is not understood.  Through schematron, we should make var_check required when var_ref is used.
Follow-ups:
Date Added: 2008-08-04 21:20:32
added in the specific schematron statement to the EntityStateBaseType

15329 restrict operation via schematron for <xpath> entity to just equals Closed 2008-05-14 n/a
Priority: High | Category: n/a | Date Closed: 2008-08-04 21:07:05
Details:
>In the file you mentioned I see a generic mapping of data types to
>supported operations. I don't see the special cases, though. For
>example, in the 5.3 schema, the xpath object entity (which is a string)
>in the xmlfilecontent_object explicitly restricts the operation to
>"equals". I don't see any such restriction in 5.4. Am I just overlooking
>it?

Unfortunately, no you are not overlooking it.  I had forgot that a special restriction had been made for the <xpath> entity.  Now thinking about, I think there might be 1 or 2 similar entities that had special restrictions.  This is an argument against these special restrictions.  Of course on the flip side, allowing an operation of 'not equals' for the <xpath> entity does not make sense.

Would a best of both worlds solution be that we make a general mapping between datatype and operation in the declaration of the EntityBaseType as done in version 5.4, but then make addition restrictions on entities like <xpath> that need them like we did in version 5.3.  This would allows us to keep the benefit of reducing all the duplicative schematron statements (as well as centralize the mapping) that was the reason for the change between versions.

This change would be made in version 5.5.  For now, I would have a tool throw an unknown result if it ever came across an <xpath> with an operation other than 'equals' since it is unknown how to deal with this.
Follow-ups:
Date Added: 2008-05-16 20:56:21
If we do this, we may also need to make restrictions for things like var_check. We need to go through the logic and see if further restrictions need to be made. Check out the thread on the developer list from May 2008 entitled "questions on the var_check attribute on entity objects"

Date Added: 2008-08-04 21:07:05
added schematron to the specific individual entities to restrict the operation attribute to the desired value

15332 incorrect schematron mapping between default and string datatype Closed 2008-05-14 n/a
Priority: High | Category: n/a | Date Closed: 2008-07-30 16:33:53
Details:
the mapping of valid operations for each datatype (look at EntityBaseType in oval-definitions-schema.xsd) is inconsistent between the default datatype and the string datatype.  These should be the same.  The default is correct.
Follow-ups:
Date Added: 2008-07-30 16:33:53
fixed the schematron related to the string datatype

15925 clarify version datatype documentation related to the use of different delimeter characters Closed 2008-07-08 n/a
Priority: Low | Category: Definition Schemas | Date Closed: 2008-07-30 17:42:01
Details:
Clarification is needed regarding how to treat version strings like 5.2-3.4.  Currently the schemas says that "The version datatype represents a value that is a hierarchical list of non-negative integers separated by a single character delimiter".  It doesn't give any guidance about when more than one type of non-number character is used.
Follow-ups:
Date Added: 2008-07-08 17:54:23
The solution to this is to add a sentence to the schema documentation that says to treat any non-number character as a delimeter. This means that 5.2-3.4 would be the same as 5.2.3.4 as well as 5f2f3m4

Date Added: 2008-07-30 17:42:01
added the following documentation: Note that any non-number character can be used as a delimiter and that different characters can be used within the same version string. So '#.#-#' is the same as '#.#.#' or '#c#c#'.

16201 fix error in entity names in user_sid_test Closed 2008-07-26 n/a
Priority: High | Category: n/a | Date Closed: 2008-07-30 16:30:02
Details:
In the user sid test (oval 5.4 draft), 
user_sid_object is having 
              - "user" as element name whereas it should be "user_sid"
user_sid_state is having
              - "user" as element name, it should be "user_sid" 
              - "group" as element name, it should be "group_sid".
Follow-ups:
Date Added: 2008-07-30 16:30:02
Deprecated the <user_sid_test> and added a new <user_sid55_test> that fixes the entity names.

16274 clarify intention of a .* pattern match with a trustee_sid entity Closed 2008-07-30 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-07-30 16:45:41
Details:
When a .* pattern match is given for a trustee_sid, should the object set include all possible sids found in the domain?  Or just those associated with the file/key/etc?
Follow-ups:
Date Added: 2008-07-30 16:41:26
Added the following documentation to the trustee_sid entity: "If a pattern match operation is used attempts to identify all the trustees (for exampl a .* pattern) then the search should be limited to just the trustees on the DACL/SACL of the object in question."

16275 remove stale object_ref mention from ItemType documentation in SC schema Closed 2008-07-30 n/a
Priority: Low | Category: System Characteristics Schemas | Date Closed: 2008-07-30 16:54:12
Details:
Looks like there is an old reference to an object_ref attribute in the ItemType documentation.  This is part of the oval-system-characteristics-schema.xsd.
Follow-ups:
Date Added: 2008-07-30 16:54:12
removed unnecessary documentation

16277 document what value the instance entity of a textfilecontent54_test starts at Closed 2008-07-30 n/a
Priority: Medium | Category: Definition Schemas | Date Closed: 2008-07-30 16:58:16
Details:
We need to document what value the first instance of a content match would be.
Follow-ups:
Date Added: 2008-07-30 16:58:16
added the following: The first match is given an instance value of 1, the second match is given and instance value of 2, and so on.

16280 document what happens if an individual component of a local_variable returns multiple values Closed 2008-07-30 n/a
Priority: Low | Category: n/a | Date Closed: 2008-07-30 17:15:28
Details:
We need to clarify what happens when an individual component of a local variable return multiple values.
Follow-ups:
Date Added: 2008-07-30 17:15:28
added the following: Note that if an individual component is used and it returns multiple values, then there will be multiple values associated with the local_variable. For example, if an object_component is used and it references a file object that identifies a set of 5 files, then the local variable would represent these 5 values.

16321 enhanced documentation related to illegal datatype casting Closed 2008-07-31 n/a
Priority: Low | Category: n/a | Date Closed: 2008-07-31 23:56:41
Details:
We need to expand the documentation related to how to report cases when a value can not be cast to the specified datatype.  For example if the datatype is integer and the value is NULL.
Follow-ups:
Date Added: 2008-07-31 23:56:41
added the following documentation to the EntityBaseType: If a cast can not be made, (trying to cast 'abc' to an integer) then an error should be thrown. For example, if the datatype is set to 'integer' and the value of the entity is empty. There is no way to cast the empty string (or NULL) to an integer, and in cases like this an error should be reported.

16351 add a new PIX OS schema Closed 2008-08-04 n/a
Priority: Low | Category: n/a | Date Closed: 2008-08-04 20:43:08
Details:
HP has submitted a PIX OS schema to be added to 5.5
Follow-ups:
Date Added: 2008-08-04 20:43:08
we have added in the PIX schema

16400 add a new line test to the CatOS schema Closed 2008-08-06 n/a
Priority: Low | Category: n/a | Date Closed: 2008-08-06 21:20:14
Details:
HP has proposed the line test for the catos schema that tests the results of the SHOW command.  This is similar to the ios and pix schema line tests.
Follow-ups:
Date Added: 2008-08-06 21:20:14
test has been added

16430 add a function for comparing date-time strings Closed 2008-08-08 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-08-08 23:41:05
Details:
A function is needed to compare different date-time strings and return the number of seconds between the two times.  McAfee has submitted a proposal for this.
Follow-ups:
Date Added: 2008-08-08 23:41:05
added the McAfee function

16431 add a function for capturing a substring based on a regex Closed 2008-08-08 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-08-08 23:40:55
Details:
A function is needed that uses a regex to capture a substring in a given input.  McAfee has submitted a proposal for such a function.
Follow-ups:
Date Added: 2008-08-08 23:40:55
added the McAfee function

16434 modification of the ios version_test Closed 2008-08-09 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-08-27 22:14:59
Details:
A proposal has been made to modify the IOS version test.
Follow-ups:
Date Added: 2008-08-27 22:14:59
modification has been made

16435 modification of the catos version test Closed 2008-08-09 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-08-27 23:16:38
Details:
A proposal has been made to modify the CatOS version test.
Follow-ups:
Date Added: 2008-08-27 23:16:38
modification has been made

16669 add a new test around the WUA update search interface Closed 2008-08-27 n/a
Priority: High | Category: n/a | Date Closed: 2008-08-27 20:08:36
Details:
add a new test around the WUA update search interface
Follow-ups:
Date Added: 2008-08-27 20:08:36
added the wuaupdatesearcher_test

17007 fix errors found in schematron (submitted by Secure Elements) Closed 2008-09-16 n/a
Priority: Medium | Category: n/a | Date Closed: 2008-09-16 20:52:48
Details:
This email encompasses the feedback from the developers at Secure Elements:

The results of my schema syntax review of OVAL 5.5 RC1 are as follows:

found 9 schematron errors in the windows definitions schema.
found 2 schematron errors in the solaris definitions schema
found 1 XML schema error in the pixos definitions schema.
found 1 schematron error in the catos definitions schema.

found 9 schematron errors in the windows syschar schema
found 1 XML schema error in the pixos syschar schema
found 4 XML schema errors in the aix syschar schema

These findings are detailed below.


Details:

IN windows-definitions-schema.xsd

at line 5826
update <sch:rule context="win-def:regkeyeffectiverights_test/win-def:state">
to     <sch:rule context="win-def:regkeyeffectiverights53_test/win-def:state">

at line 6729/6730
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_read_permission entity of a sharedresource_state should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_read_permission entity of a sharedresource_state should be 'boolean'</sch:assert>

at line 6742/6743
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_write_permission entity of a sharedresource_state should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_write_permission entity of a sharedresource_state should be 'boolean'</sch:assert>


at line 6755/6756
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_create_permission entity of a sharedresource_state should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_create_permission entity of a sharedresource_state should be 'boolean'</sch:assert>

at line 6768/6769
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_exec_permission entity of a sharedresource_state should be 'bool'</sch:assert>
update <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_exec_permission entity of a sharedresource_state should be 'boolean'</sch:assert>
 
at line 6781/6782
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_delete_permission entity of a sharedresource_state should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_delete_permission entity of a sharedresource_state should be 'boolean'</sch:assert>

at line 6794/6795
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_atrib_permission entity of a sharedresource_state should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_atrib_permission entity of a sharedresource_state should be 'boolean'</sch:assert>

at line 6807/6808
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_perm_permission entity of a sharedresource_state should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_perm_permission entity of a sharedresource_state should be 'boolean'</sch:assert>

at line 6820/6821
update <sch:assert test="not(@datatype) or @datatype='bool'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_all_permission entity of a sharedresource_state should be 'bool'</sch:assert>
update <sch:assert test="not(@datatype) or @datatype='boolean'">
          <sch:value-of select="../@id"/> - datatype attribute for the access_all_permission entity of a sharedresource_state should be 'boolean'</sch:assert>



IN SCHEMA solaris-definitions-schema.xsd
at line 27
update <sch:assert test="@object_ref=/oval-def:oval_definitions/oval-def:objects/sol-def:smf_object/@id">
to     <sch:assert test="@object_ref=/oval-def:oval_definitions/oval-def:objects/sol-def:isainfo_object/@id">

at line 31
update <sch:assert test="@state_ref=/oval-def:oval_definitions/oval-def:states/sol-def:smf_state/@id">
to     <sch:assert test="@state_ref=/oval-def:oval_definitions/oval-def:states/sol-def:isainfo_state/@id">

IN SCHEMA pixos-definitions-schema.xsd
at line 3
update <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5" xmlns:oval-def="http://oval.mitre.org/XMLSchema/oval-definitions-5" xmlns:pixos-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#pixos" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-definitions-5#pix" elementFormDefault="qualified" version="5.5">
to     <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5" xmlns:oval-def="http://oval.mitre.org/XMLSchema/oval-definitions-5" xmlns:pixos-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#pixos" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-definitions-5#pixos" elementFormDefault="qualified" version="5.5">

IN SCHEMA catos-definitions-schema.xsd
at line 127
update <sch:assert test="@state_ref=/oval-def:oval_definitions/oval-def:states/catos-def:module_number/@id"><sch:value-of select="../@id"/> - the state child element of a module_test must reference a module_state</sch:assert>
to     <sch:assert test="@state_ref=/oval-def:oval_definitions/oval-def:states/catos-def:module_state/@id"><sch:value-of select="../@id"/> - the state child element of a module_test must reference a module_state</sch:assert>


IN SCHEMA windows-system-characteristics.xsd
at line 14
insert <sch:ns prefix="xsi" uri="http://www.w3.org/2001/XMLSchema-instance"/>

at line 3746
update <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_read_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to     <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_read_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3758
update	<sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_write_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_write_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3770
update  <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_create_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_create_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3782
update  <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_exec_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_exec_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3794
update  <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_delete_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_delete_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3806
update  <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_atrib_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_atrib_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3818
update  <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_perm_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_perm_permission entity of a sharedresource_item should be 'boolean'</sch:assert>

at line 3830
update  <sch:assert test="not(@datatype) or @datatype='bool'">item <sch:value-of select="../@id"/> - datatype attribute for the access_all_permission entity of a sharedresource_item should be 'bool'</sch:assert>
to      <sch:assert test="not(@datatype) or @datatype='boolean'">item <sch:value-of select="../@id"/> - datatype attribute for the access_all_permission entity of a sharedresource_item should be 'boolean'</sch:assert>


IN SCHEMA pixos-system-characteristics.xsd
at line 2
update  <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" xmlns:pixos-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#pix" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#pixos" elementFormDefault="qualified" version="5.5">
to      <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5" xmlns:pixos-sc="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#pixos" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-system-characteristics-5#pixos" elementFormDefault="qualified" version="5.5">

IN SCHEMA aix-system-characteristics.xsd
delete line 178

at line 180
update  <xsd:restriction base="oval-def:EntityItemStringType">
to      <xsd:restriction base="oval-sc:EntityItemStringType">

at line 226
update  <xsd:annotation>>
to      <xsd:annotation>

at line 230
update  <xsd:restriction base="oval-def:EntityItemStringType">
to      <xsd:restriction base="oval-sc:EntityItemStringType">



Follow-ups:
Date Added: 2008-09-16 20:52:48
fixed

9248 add table to show how evaluation works related to the ExistenceEnumeration Closed 2006-07-05 n/a
Priority: Medium | Category: Result Schemas | Date Closed: 2008-08-04 23:29:28
Details:
need to add a nice table that relates sc flag values to result values
Follow-ups:
Date Added: 2008-07-08 18:54:11
We need to update/expand the current table found under the ExistenceEnumeration in the oval-common-schema. Right now it is incorrectly based off of the status values.

Date Added: 2008-08-04 23:29:28
expanded documentation of ExistenceEnumeration and added a table with the FlagEnumeration. better doc is probably still possible

16323 definition of DatatypeEnumeration should be updated to base datatypes on XML Schema types Closed 2008-08-01 n/a
Priority: Medium High | Category: n/a | Date Closed: 2008-08-08 22:26:23
Details:
From email on the developer list
Date: Thu 7/24/2008 8:21 PM 
Subject: "Request for 5.5 or 6.0"

==================================================
Please add a comment that

datatype="boolean" means that it is encode per W3C,
http://www.w3.org/TR/xmlschema-2/#boolean
datatype="binary" means that it is encode per W3C,
http://www.w3.org/TR/xmlschema-2/#hexBinary 
datatype="float" means that it is encode per W3C,
http://www.w3.org/TR/xmlschema-2/#float 
datatype="int" means that it is encode per W3C,
http://www.w3.org/TR/xmlschema-2/#int 
datatype="string" means that it is encode per W3C,
http://www.w3.org/TR/xmlschema-2/#string 

Also, add schematron to enforce it.   It will help greatly when someone
is new to XML and coming from C++ or C# and may assume that binary is
0x0F   or any other variation that works in C++.

For us long time Xml folks, the above is completely self-evident... but
that is not always the case
=================================================
Follow-ups:
Date Added: 2008-08-01 17:42:04
To clarify... this change should be made where the datatypes defined by the DatatypeEnumeration align with the XML Schema spec. We should also include better documentation for all the other datatypes (evr_string,ios_version, etc) Readers of the documentation should be able to easily look up the definition of these types. how about links to the source docs?

Date Added: 2008-08-07 22:51:26
I have updated the documentation associated with each datatype. I have also added some potential schematron rules to validate that data is in the correct format. These rules utilize xpath 2.0 and there is some question whether the OVAL community wants this.

16582 add functions to support arithmetic operations: add and multiply Closed 2008-08-19 n/a
Priority: Medium High | Category: Definition Schemas | Date Closed: 2009-08-31 15:54:50
Details:
Requested by Todd Dolinsky of HP
Friday, August 08, 2008 9:17 AM
Follow-ups:
Date Added: 2008-08-26 20:56:37
An arithmetic function has been added, but only for add and multiply. We need to add a required position attribute to the components in order to do subtract and multiply. This requires a major version. A tracker item for this has been added for version 6.0

Back to top

Timeline for Version 5.5

PLANNING DRAFT RELEASE CANDIDATE OFFICIAL
24 July 2008 08 August 2008 10 September 2008 01 October 2008
Back to top

Status Reports on Version 5.5

Status updates are included below. You may also review the Community Forum Archives for discussions about Version 5.5, or enter "Version 5.5" as a keyword search for a list of forum discussions about the new version.

[2008-10-01]

Version 5.5 has been officially released. Many thanks to all in the community that helped with this minor release.

[2008-09-19]

Based on the feedback from the community, some corrections regarding typos in certain schematron rules and in the pixos namespace have been made. A second release candiate (RC2) has been issued. As always, if there are any more issues found please report them to the community so they can be fixed before the official release.

[2008-09-10]

The release candidate for Version 5.5 has been submitted. Nothing new has been added since the last draft. At this point we ask that all members of the community fully test this version and verify that it is ready for the official release.

[2008-08-27]

A second draft of Version 5.5 has been released. This new draft includes the proposed WUA Update Searcher test in the Windows Schema as well as modifications to the Version test in both the IOS schema and the CatOS schema. In addition, new functions were added to the variable section of the core definition schema. These additions have caused us to push back the release candidate date to September 10 in order to give everyone a chance to review things.

[2008-08-08]

A first draft of Version 5.5 has been released. This includes the addition of a new schema for PIX OS (submitted by Hewlett-Packard). In addition, it includes some updated documentation, some modified tests for catos, and some updated schematron related to datatypes.

[2008-07-24]

Version 5.5 is currently in the planning stage. If you have any suggestions for changes that should be included, please send them to the OVAL Community.

Back to top

Page Last Updated: December 12, 2011