OVAL Version 5.11.1 RC Announcement

classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

OVAL Version 5.11.1 RC Announcement

drothenberg

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

https://github.com/drothenberg/Language/commits/511_updates

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

https://github.com/drothenberg/Language/commits/5_11_1_platform_updates

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

changelog.txt (15K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
We don’t need to roll back to fix #237, because Martin Preisler (from RedHat) and I collaborated on a substitution group fix.  See oval-definitions-schema.xsd and oval-common-schema.xsd here:
https://github.com/joval/jOVAL/tree/5.11.X/scap/schemas/oval-5.11

Regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 25, 2015, at 11:10 PM, Rothenberg, David B. <[hidden email]> wrote:

All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email]. <changelog.txt>

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
In reply to this post by drothenberg
Hi David,

Will your Github repository become the staging area for OVAL language updates, or will there be a branch created in the Sandbox project, or … will we be doing something else?

I’m hoping to actually test out these release candidates with working code, since we are working on 5.11 support anyway, and there have been quite a number of issues we’ve uncovered so far.

Best regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 25, 2015, at 11:10 PM, Rothenberg, David B. <[hidden email]> wrote:

All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email]. <changelog.txt>

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
In reply to this post by drothenberg
I’ve been talking with both Ubuntu and RedHat folks about this issue.  David’s OVAL Sandbox issue sums it up well, and includes an illustrative example of the real problem.

An alternative proposal is to perform context-sensitive comparisons with the existing evr_string datatype, when used by an RPM-related state or a Debian Package-related state.  But, a new datatype would be required in order to make it possible to use an EVR string in a variable without either being ambiguous, or making one or the other comparison style unusable in conjunction with variable_states.

The problem with adding a new datatype is that all existing linux:dpkginfo_states will be incompatible with this change.  New content will have to specify the new dpkg_evr_string as the datatype for the evr entity.  Fortunately, upgrading the content should be extremely simple to do.

(As an aside, this will also require the addition of Entity[State/Item]DpkgEVRStringTypes).

Any feedback on the above is welcome.

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 25, 2015, at 11:10 PM, Rothenberg, David B. <[hidden email]> wrote:

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.


To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

drothenberg
In reply to this post by David Solin-3

Hi David,

I had consolidated all of the changes being considered for the OVAL Language in the branches linked below. Please use these schemas for any purpose you may need prior  to the OVAL 5.11.1 release.

 

Thanks,

David Rothenberg

 

From: David Solin [mailto:[hidden email]]
Sent: Thursday, March 26, 2015 4:38 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Hi David,

 

Will your Github repository become the staging area for OVAL language updates, or will there be a branch created in the Sandbox project, or … will we be doing something else?

 

I’m hoping to actually test out these release candidates with working code, since we are working on 5.11 support anyway, and there have been quite a number of issues we’ve uncovered so far.

 

Best regards,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Image removed by sender. Joval Continuous Monitoring

Image removed by sender. FacebookImage removed by sender. Linkedin

 

 

On Mar 25, 2015, at 11:10 PM, Rothenberg, David B. <[hidden email]> wrote:

 

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email]. <changelog.txt>

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

drothenberg
In reply to this post by drothenberg

Based on feedback and further investigations, we have expanded on some fixes identified below.

 

The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.

 

In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.

 

These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.

 

Thanks,

David Rothenberg

 

From: Rothenberg, David B. [mailto:[hidden email]]
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

https://github.com/drothenberg/Language/commits/511_updates

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

https://github.com/drothenberg/Language/commits/5_11_1_platform_updates

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
Hi David,

From a quick scan of the last update, I have a question.  Do you think we could inline-define the Entity[State/Item]DebianEVRStringType in the context of the dpkginfo_[state/item]/evr entities, rather than declaring fully-fledged classes?  There is only the one entity in the definitions and system-characteristics schemas that require this particular restriction, and I don’t want to encourage the idea that there could be others by creating a separate class.

For examples of what I mean, take a look at the definitions of epoch, version and release entity definitions of the rpminfo_state and rpminfo_item.

Best regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:

Based on feedback and further investigations, we have expanded on some fixes identified below.
 
The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.
 
In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.
 
These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.
 
Thanks,
David Rothenberg
 
From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
In reply to this post by drothenberg
Hi David,

This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!

Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?

Thanks,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:

Based on feedback and further investigations, we have expanded on some fixes identified below.
 
The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.
 
In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.
 
These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.
 
Thanks,
David Rothenberg
 
From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

drothenberg

Hi David,

I went ahead and merged all previous changes into a single branch:

 

https://github.com/drothenberg/Language/tree/5_11_1_all_updates

 

The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.

 

Thanks,

David Rothenberg

 

From: David Solin [mailto:[hidden email]]
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Hi David,

 

This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!

 

Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?

 

Thanks,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Image removed by sender. Joval Continuous Monitoring

Image removed by sender. FacebookImage removed by sender. Linkedin

 

 

On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Based on feedback and further investigations, we have expanded on some fixes identified below.

 

The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.

 

In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.

 

These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.

 

Thanks,

David Rothenberg

 

From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
Thanks David.

So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).

Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.

If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.

Regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:

Hi David,
I went ahead and merged all previous changes into a single branch:
 
 
The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Hi David,
 
This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!
 
Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?
 
Thanks,
—David Solin
 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 
 
On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Based on feedback and further investigations, we have expanded on some fixes identified below.
 
The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.
 
In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.
 
These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.
 
Thanks,
David Rothenberg
 
From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

drothenberg

David,

I understand why that would be wanted; we have even implemented something similar in OVALDI previously for this purpose. See http://sourceforge.net/p/ovaldi/code/HEAD/tree/trunk/xml/schemaLocation.conf. However, this should remain an optional alternative and not be included in the OVAL Version 5.11.1 release.

 

That said, where you had requested an inline fix for Entity[State/Item]DebianEVRStringType, I would assume the intent was “Entity[State/Item]DebianRPMEVRStringType”. This change will be pulled into the Language since it is only used in one location.

 

As initially stated, we had targeted 3/30 for the release of OVAL Version 5.11.1. When this change has been made, I plan to start merging my local branch and begin the official release process through GitHub. I will issue a follow-up email to notify when this has been completed.

 

Thanks,

David Rothenberg

 

From: David Solin [mailto:[hidden email]]
Sent: Tuesday, March 31, 2015 2:27 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Thanks David.

 

So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).

 

Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.

 

If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.

 

Regards,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Image removed by sender. Joval Continuous Monitoring

Image removed by sender. FacebookImage removed by sender. Linkedin

 

 

On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Hi David,

I went ahead and merged all previous changes into a single branch:

 

 

The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.

 

Thanks,

David Rothenberg

 

From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Hi David,

 

This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!

 

Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?

 

Thanks,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 

 

On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Based on feedback and further investigations, we have expanded on some fixes identified below.

 

The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.

 

In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.

 

These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.

 

Thanks,

David Rothenberg

 

From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
See below...

Sent from my iPhone

On Mar 31, 2015, at 3:56 PM, Rothenberg, David B. <[hidden email]> wrote:

David,

I understand why that would be wanted; we have even implemented something similar in OVALDI previously for this purpose. See http://sourceforge.net/p/ovaldi/code/HEAD/tree/trunk/xml/schemaLocation.conf. However, this should remain an optional alternative and not be included in the OVAL Version 5.11.1 release.

 

That said, where you had requested an inline fix for Entity[State/Item]DebianEVRStringType, I would assume the intent was “Entity[State/Item]DebianRPMEVRStringType”. This change will be pulled into the Language since it is only used in one location.


Yes, that is correct, thanks!

 

As initially stated, we had targeted 3/30 for the release of OVAL Version 5.11.1. When this change has been made, I plan to start merging my local branch and begin the official release process through GitHub. I will issue a follow-up email to notify when this has been completed.


Well, you know, best laid plans and all that...

I will try and finish testing now.

 

Thanks,

David Rothenberg

 

From: David Solin [[hidden email]]
Sent: Tuesday, March 31, 2015 2:27 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Thanks David.

 

So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).

 

Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.

 

If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.

 

Regards,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

<image001.jpg>

<image002.jpg><image002.jpg>

 

 

On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Hi David,

I went ahead and merged all previous changes into a single branch:

 

 

The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.

 

Thanks,

David Rothenberg

 

From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Hi David,

 

This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!

 

Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?

 

Thanks,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 

 

On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Based on feedback and further investigations, we have expanded on some fixes identified below.

 

The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.

 

In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.

 

These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.

 

Thanks,

David Rothenberg

 

From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
In reply to this post by drothenberg
Stop the presses, please!

Did we not agree to add a check_existence attribute to EntityStateSimpleBaseType?!

Regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 3:56 PM, Rothenberg, David B. <[hidden email]> wrote:

David,
I understand why that would be wanted; we have even implemented something similar in OVALDI previously for this purpose. Seehttp://sourceforge.net/p/ovaldi/code/HEAD/tree/trunk/xml/schemaLocation.conf. However, this should remain an optional alternative and not be included in the OVAL Version 5.11.1 release.
 
That said, where you had requested an inline fix for Entity[State/Item]DebianEVRStringType, I would assume the intent was “Entity[State/Item]DebianRPMEVRStringType”. This change will be pulled into the Language since it is only used in one location.
 
As initially stated, we had targeted 3/30 for the release of OVAL Version 5.11.1. When this change has been made, I plan to start merging my local branch and begin the official release process through GitHub. I will issue a follow-up email to notify when this has been completed.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 2:27 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Thanks David.
 
So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).
 
Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.
 
If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.
 
Regards,
—David Solin
 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 
 
On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Hi David,
I went ahead and merged all previous changes into a single branch:
 
 
The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Hi David,
 
This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!
 
Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?
 
Thanks,
—David Solin
 
David A. Solin
Co-Founder, Research & Technology
[hidden email]
 
 
On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Based on feedback and further investigations, we have expanded on some fixes identified below.
 
The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.
 
In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.
 
These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.
 
Thanks,
David Rothenberg
 
From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and  should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
And also, EntityStateComplexBaseType.

See:


David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 5:13 PM, David Solin <[hidden email]> wrote:

Stop the presses, please!

Did we not agree to add a check_existence attribute to EntityStateSimpleBaseType?!

Regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 3:56 PM, Rothenberg, David B. <[hidden email]> wrote:

David,
I understand why that would be wanted; we have even implemented something similar in OVALDI previously for this purpose. Seehttp://sourceforge.net/p/ovaldi/code/HEAD/tree/trunk/xml/schemaLocation.conf. However, this should remain an optional alternative and not be included in the OVAL Version 5.11.1 release.
 
That said, where you had requested an inline fix for Entity[State/Item]DebianEVRStringType, I would assume the intent was “Entity[State/Item]DebianRPMEVRStringType”. This change will be pulled into the Language since it is only used in one location.
 
As initially stated, we had targeted 3/30 for the release of OVAL Version 5.11.1. When this change has been made, I plan to start merging my local branch and begin the official release process through GitHub. I will issue a follow-up email to notify when this has been completed.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 2:27 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Thanks David.
 
So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).
 
Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.
 
If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.
 
Regards,
—David Solin
 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 
 
On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Hi David,
I went ahead and merged all previous changes into a single branch:
 
 
The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Hi David,
 
This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!
 
Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?
 
Thanks,
—David Solin
 
David A. Solin
Co-Founder, Research & Technology
[hidden email]
 
 
On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Based on feedback and further investigations, we have expanded on some fixes identified below.
 
The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.
 
In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.
 
These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.
 
Thanks,
David Rothenberg
 
From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and  should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].


To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

David Solin-3
Additionally, I made a number of changes to the unix:FileState that do not appear to be reflected in the branch. See:

Why are those changes not being included?

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 5:24 PM, David Solin <[hidden email]> wrote:

And also, EntityStateComplexBaseType.

See:


David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 5:13 PM, David Solin <[hidden email]> wrote:

Stop the presses, please!

Did we not agree to add a check_existence attribute to EntityStateSimpleBaseType?!

Regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Joval Continuous Monitoring

Facebook Linkedin



On Mar 31, 2015, at 3:56 PM, Rothenberg, David B. <[hidden email]> wrote:

David,
I understand why that would be wanted; we have even implemented something similar in OVALDI previously for this purpose. Seehttp://sourceforge.net/p/ovaldi/code/HEAD/tree/trunk/xml/schemaLocation.conf. However, this should remain an optional alternative and not be included in the OVAL Version 5.11.1 release.
 
That said, where you had requested an inline fix for Entity[State/Item]DebianEVRStringType, I would assume the intent was “Entity[State/Item]DebianRPMEVRStringType”. This change will be pulled into the Language since it is only used in one location.
 
As initially stated, we had targeted 3/30 for the release of OVAL Version 5.11.1. When this change has been made, I plan to start merging my local branch and begin the official release process through GitHub. I will issue a follow-up email to notify when this has been completed.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 2:27 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Thanks David.
 
So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).
 
Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.
 
If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.
 
Regards,
—David Solin
 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 
 
On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Hi David,
I went ahead and merged all previous changes into a single branch:
 
 
The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.
 
Thanks,
David Rothenberg
 
From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
Hi David,
 
This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!
 
Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?
 
Thanks,
—David Solin
 
David A. Solin
Co-Founder, Research & Technology
[hidden email]
 
 
On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:
 
Based on feedback and further investigations, we have expanded on some fixes identified below.
 
The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.
 
In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.
 
These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.
 
Thanks,
David Rothenberg
 
From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
 
All,
We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:
 
 
The list of issues addressed in this Core update include the following:
·         Updated schema_version attribute and documentation. (#236)
·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)
·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)
·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)
 
There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.
 
Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:
 
 
Below is a list of the platform extensions to be updated, and the issues they fix or partially address:
·         Independent (#247)
·         Windows (#243) (#189)
·         Linux (#249) (#253)
·         Apple iOS (#252)
·         MacOS (#235)
·         UNIX (#235)
·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)
 
Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and  should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.
 
Thanks,
The OVAL Team
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
 
To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].



To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: OVAL Version 5.11.1 RC Announcement

drothenberg

Yet again, you are correct that further changes should be included. We will not issue the release tonight and instead target April 1.

 

Thanks,

David Rothenberg

 

From: David Solin [mailto:[hidden email]]
Sent: Tuesday, March 31, 2015 6:40 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Cc: Rothenberg, David B.; Haynes, Dan; OVAL
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement
Importance: High

 

Additionally, I made a number of changes to the unix:FileState that do not appear to be reflected in the branch. See:

 

Why are those changes not being included?

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Image removed by sender. Joval Continuous Monitoring

Image removed by sender. FacebookImage removed by sender. Linkedin

 

 

On Mar 31, 2015, at 5:24 PM, David Solin <[hidden email]> wrote:

 

And also, EntityStateComplexBaseType.

 

See:

 

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Image removed by sender. Joval Continuous Monitoring

Image removed by sender. FacebookImage removed by sender. Linkedin

 

 

On Mar 31, 2015, at 5:13 PM, David Solin <[hidden email]> wrote:

 

Stop the presses, please!

 

Did we not agree to add a check_existence attribute to EntityStateSimpleBaseType?!

 

Regards,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

Image removed by sender. Joval Continuous Monitoring

Image removed by sender. FacebookImage removed by sender. Linkedin

 

 

On Mar 31, 2015, at 3:56 PM, Rothenberg, David B. <[hidden email]> wrote:

 

David,

I understand why that would be wanted; we have even implemented something similar in OVALDI previously for this purpose. Seehttp://sourceforge.net/p/ovaldi/code/HEAD/tree/trunk/xml/schemaLocation.conf. However, this should remain an optional alternative and not be included in the OVAL Version 5.11.1 release.

 

That said, where you had requested an inline fix for Entity[State/Item]DebianEVRStringType, I would assume the intent was “Entity[State/Item]DebianRPMEVRStringType”. This change will be pulled into the Language since it is only used in one location.

 

As initially stated, we had targeted 3/30 for the release of OVAL Version 5.11.1. When this change has been made, I plan to start merging my local branch and begin the official release process through GitHub. I will issue a follow-up email to notify when this has been completed.

 

Thanks,

David Rothenberg

 

From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 2:27 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Thanks David.

 

So… now that we are on the same branch, I might want to make some modifications and submit them in a pull request for review and consideration by the OVAL community (and other board members).

 

Would it be alright if I removed all the schemaLocation attributes from the xsi:import statements, and added a TR9401 catalog file instead?  Using a catalog (which maps namespace URIs to file locations) is much more convenient for real-world applications involving lots of schema files, vs. relying on locations that are hard-coded in the schema documents themselves.

 

If not, I will need to make changes in multiple sets of files — one with hard-coded schemaLocations, and another that I will actually be using for testing.

 

Regards,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 

 

On Mar 31, 2015, at 12:19 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Hi David,

I went ahead and merged all previous changes into a single branch:

 

 

The previous breakdown was to prepare the update in stages to allow for simpler tagging. Please let me know if you need anything else.

 

Thanks,

David Rothenberg

 

From: David Solin [[hidden email]] 
Sent: Tuesday, March 31, 2015 9:27 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

Hi David,

 

This is difficult to test, because the updates to the core schemas and platform schemas are in different branches — yet the platform schema updates are dependent upon the core schema updates!

 

Could you consolidate these updates into a single branch, so that they can be tested without having to manually stitch together changes from different branches?

 

Thanks,

—David Solin

 

David A. Solin
Co-Founder, Research & Technology
[hidden email]

 

 

On Mar 30, 2015, at 4:27 PM, Rothenberg, David B. <[hidden email]> wrote:

 

Based on feedback and further investigations, we have expanded on some fixes identified below.

 

The NotesType substitution group schema proposal by David Solin in collaboration with Martin Preisler allows for both oval: and oval-def: namespace prefixed notes elements. This allows for all notes content written before and after 5.11.0 to work as expected.

 

In addition, it was determined that the debian_evr_string simple datatype is a necessity when comparing dpkg information since the comparison algorithms function differently. This was implemented to allow for the evr_string to remain in old content, but will cause a new Schematron rule to alert the user to this new datatype.

 

These changes were committed to the same branches listed below. Please take some time to inspect both the original and recent commits for this candidate of OVAL Version 5.11.1.

 

Thanks,

David Rothenberg

 

From: Rothenberg, David B. [[hidden email]] 
Sent: Thursday, March 26, 2015 12:11 AM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: [OVAL-DEVELOPER-LIST] OVAL Version 5.11.1 RC Announcement

 

All,

We are pleased to announce the list of issues targeted for the OVAL Version 5.11.1 release. This release is planned for Monday, March 30th. The full list of changes is available in the attached changelog file. To break this list down, all Core changes outlined in this announcement have been implemented in schema and currently reside as a planned pull request in the following GitHub branch:

 

 

The list of issues addressed in this Core update include the following:

·         Updated schema_version attribute and documentation. (#236)

·         Reverted the move of the NotesType used in oval-def to be that of OVAL Common. A duplicated NotesType remains in OVAL Common for use with OVAL Variables. We had previously investigated the substitution group approach and identified it as a more complex fix to a simple problem. With no uncommented OVAL content being written against 5.11.0, this should have minimal impact. (#237)

·         Improved and corrected documentation for the GlobToRegex OVAL Function. (#245)

·         Further Schematron rule fixes applied to platform schemas. (#235) (#252) (#253)

 

There is one open issue (OVAL Sandbox #142) targeting the Core, regarding the introduction of a dpkg_evr_string datatype to assist with the differences between RPM and dpkg version comparisons. This change would affect both content and tools, and would thus need further discussion before incorporating into the Language.

 

Following the revised separate versioning policy, all platforms have been reset to the minimum version of 5.11.1:1.0. Several platforms have received further updates to accompany this release, and will be subsequently updated to 5.11.1:1.1. The list of changes to platform extensions were limited to those with considerable impact, and those with schema implementations already present. These changes can be found as a planned pull request at the following GitHub branch:

 

 

Below is a list of the platform extensions to be updated, and the issues they fix or partially address:

·         Independent (#247)

·         Windows (#243) (#189)

·         Linux (#249) (#253)

·         Apple iOS (#252)

·         MacOS (#235)

·         UNIX (#235)

·         Cisco IOS, IOS-XE, ASA (#240) (#241) (#242) (#252)

 

Further updates to platform extensions are encouraged to have schema implementations to be included in the next platform update, and  should have relevant discussions establishing justification. Any open issue not included in the list above should be considered for the next platform update rather than potentially delaying this necessary release.

 

Thanks,

The OVAL Team

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].

 

To unsubscribe, send an email message to [hidden email] with SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have difficulties, write to [hidden email].