oval_developer@lists.cisecurity.org

A list for people interested in developing the OVAL language.

View all threads

OVAL Versioning Policy

DP
Dragos Prisaca
Tue, Jan 24, 2017 8:18 PM

Hello,

According to the OVAL Version Policy (
http://ovalproject.github.io/documentation/policy/versioning/), the version
of a Platform Extension looks like:
“CORE-MAJOR.CORE-MINOR.CORE-UPDATE:PLAT-MAJOR.PLAT-MINOR.PLAT-UPDATE”. I am
trying to find out when does the CORE version portion of a Platform
extension change?

For instance, the 5.11.2 core was recently released, but none of the core
portion of platform extension versions was updated (i.e.
windows-definitions-schema.xsd shows <version>5.11.1:1.4</version>). Is
this by design? or was it supposed to be updated?

Thanks,

_Dragos.

...

Hello, According to the OVAL Version Policy ( http://ovalproject.github.io/documentation/policy/versioning/), the version of a Platform Extension looks like: “CORE-MAJOR.CORE-MINOR.CORE-UPDATE:PLAT-MAJOR.PLAT-MINOR.PLAT-UPDATE”. I am trying to find out when does the CORE version portion of a Platform extension change? For instance, the 5.11.2 core was recently released, but none of the core portion of platform extension versions was updated (i.e. windows-definitions-schema.xsd shows <version>5.11.1:1.4</version>). Is this by design? or was it supposed to be updated? Thanks, _Dragos. ...
DS
David Solin
Thu, Jan 26, 2017 5:05 PM

Hi Dragos,

This was by design.  There was a discussion by the OVAL board about it, and I summarized our conclusions in issue #281:
https://github.com/OVALProject/Language/issues/281 https://github.com/OVALProject/Language/issues/281

Basically, if there’s no reason that an updated platform schema can’t be used in conjunction with an older base schema (e.g., some new object or state requires a new datatype), then we don’t rev the base schema version.

Best regards,
—David Solin

David A. Solin
Co-Founder, Research & Technology
solin@jovalcm.com mailto:solin@jovalcm.com
http://jovalcm.com/
  https://www.facebook.com/jovalcm https://www.linkedin.com/company/joval-continuous-monitoring

On Jan 24, 2017, at 2:18 PM, Dragos Prisaca dragos.prisaca@G2-INC.COM wrote:

Hello,

According to the OVAL Version Policy (http://ovalproject.github.io/documentation/policy/versioning/ http://ovalproject.github.io/documentation/policy/versioning/), the version of a Platform Extension looks like: “CORE-MAJOR.CORE-MINOR.CORE-UPDATE:PLAT-MAJOR.PLAT-MINOR.PLAT-UPDATE”. I am trying to find out when does the CORE version portion of a Platform extension change?

For instance, the 5.11.2 core was recently released, but none of the core portion of platform extension versions was updated (i.e. windows-definitions-schema.xsd shows <version>5.11.1:1.4</version>). Is this by design? or was it supposed to be updated?

Thanks,
_Dragos.

...


OVAL_Developer mailing list
OVAL_Developer@lists.cisecurity.org mailto:OVAL_Developer@lists.cisecurity.org
http://lists.cisecurity.org/mailman/listinfo/oval_developer_lists.cisecurity.org http://lists.cisecurity.org/mailman/listinfo/oval_developer_lists.cisecurity.org

...

Hi Dragos, This was by design. There was a discussion by the OVAL board about it, and I summarized our conclusions in issue #281: https://github.com/OVALProject/Language/issues/281 <https://github.com/OVALProject/Language/issues/281> Basically, if there’s no reason that an updated platform schema can’t be used in conjunction with an older base schema (e.g., some new object or state requires a new datatype), then we don’t rev the base schema version. Best regards, —David Solin David A. Solin Co-Founder, Research & Technology solin@jovalcm.com <mailto:solin@jovalcm.com> <http://jovalcm.com/>   <https://www.facebook.com/jovalcm> <https://www.linkedin.com/company/joval-continuous-monitoring> > On Jan 24, 2017, at 2:18 PM, Dragos Prisaca <dragos.prisaca@G2-INC.COM> wrote: > > Hello, > > According to the OVAL Version Policy (http://ovalproject.github.io/documentation/policy/versioning/ <http://ovalproject.github.io/documentation/policy/versioning/>), the version of a Platform Extension looks like: “CORE-MAJOR.CORE-MINOR.CORE-UPDATE:PLAT-MAJOR.PLAT-MINOR.PLAT-UPDATE”. I am trying to find out when does the CORE version portion of a Platform extension change? > > For instance, the 5.11.2 core was recently released, but none of the core portion of platform extension versions was updated (i.e. windows-definitions-schema.xsd shows <version>5.11.1:1.4</version>). Is this by design? or was it supposed to be updated? > > Thanks, > _Dragos. > > > ... > _______________________________________________ > OVAL_Developer mailing list > OVAL_Developer@lists.cisecurity.org <mailto:OVAL_Developer@lists.cisecurity.org> > http://lists.cisecurity.org/mailman/listinfo/oval_developer_lists.cisecurity.org <http://lists.cisecurity.org/mailman/listinfo/oval_developer_lists.cisecurity.org> ...
DP
Dragos Prisaca
Thu, Jan 26, 2017 6:55 PM

Thank you David! It makes sense.

The info from the issue #281 is a great example to be included to the OVAL
Version Policy (
http://ovalproject.github.io/documentation/policy/versioning/).

Thanks,

_Dragos.

From: David Solin [mailto:solin@jovalcm.com]
Sent: Thursday, January 26, 2017 12:06 PM
To: Dragos Prisaca; OVAL Developer List
Subject: Re: [OVAL DEVELOPER] OVAL Versioning Policy

Hi Dragos,

This was by design.  There was a discussion by the OVAL board about it, and
I summarized our conclusions in issue #281:

https://github.com/OVALProject/Language/issues/281

Basically, if there’s no reason that an updated platform schema can’t be
used in conjunction with an older base schema (e.g., some new object or
state requires a new datatype), then we don’t rev the base schema version.

Best regards,

—David Solin

David A. Solin
Co-Founder, Research & Technology
solin@jovalcm.com

[image: Joval Continuous Monitoring] http://jovalcm.com

[image: Facebook]  https://www.facebook.com/jovalcm[image: Linkedin]
https://www.linkedin.com/company/joval-continuous-monitoring

On Jan 24, 2017, at 2:18 PM, Dragos Prisaca dragos.prisaca@G2-INC.COM
wrote:

Hello,

According to the OVAL Version Policy (
http://ovalproject.github.io/documentation/policy/versioning/), the version
of a Platform Extension looks like:
“CORE-MAJOR.CORE-MINOR.CORE-UPDATE:PLAT-MAJOR.PLAT-MINOR.PLAT-UPDATE”. I am
trying to find out when does the CORE version portion of a Platform
extension change?

For instance, the 5.11.2 core was recently released, but none of the core
portion of platform extension versions was updated (i.e.
windows-definitions-schema.xsd shows <version>5.11.1:1.4</version>). Is
this by design? or was it supposed to be updated?

Thanks,

_Dragos.

...


OVAL_Developer mailing list
OVAL_Developer@lists.cisecurity.org
http://lists.cisecurity.org/mailman/listinfo/oval_developer_lists.cisecurity.org

...

Thank you David! It makes sense. The info from the issue #281 is a great example to be included to the OVAL Version Policy ( http://ovalproject.github.io/documentation/policy/versioning/). Thanks, _Dragos. *From:* David Solin [mailto:solin@jovalcm.com] *Sent:* Thursday, January 26, 2017 12:06 PM *To:* Dragos Prisaca; OVAL Developer List *Subject:* Re: [OVAL DEVELOPER] OVAL Versioning Policy Hi Dragos, This was by design. There was a discussion by the OVAL board about it, and I summarized our conclusions in issue #281: https://github.com/OVALProject/Language/issues/281 Basically, if there’s no reason that an updated platform schema can’t be used in conjunction with an older base schema (e.g., some new object or state requires a new datatype), then we don’t rev the base schema version. Best regards, —David Solin *David A. Solin* Co-Founder, Research & Technology solin@jovalcm.com [image: Joval Continuous Monitoring] <http://jovalcm.com> [image: Facebook] <https://www.facebook.com/jovalcm>[image: Linkedin] <https://www.linkedin.com/company/joval-continuous-monitoring> On Jan 24, 2017, at 2:18 PM, Dragos Prisaca <dragos.prisaca@G2-INC.COM> wrote: Hello, According to the OVAL Version Policy ( http://ovalproject.github.io/documentation/policy/versioning/), the version of a Platform Extension looks like: “CORE-MAJOR.CORE-MINOR.CORE-UPDATE:PLAT-MAJOR.PLAT-MINOR.PLAT-UPDATE”. I am trying to find out when does the CORE version portion of a Platform extension change? For instance, the 5.11.2 core was recently released, but none of the core portion of platform extension versions was updated (i.e. windows-definitions-schema.xsd shows <version>5.11.1:1.4</version>). Is this by design? or was it supposed to be updated? Thanks, _Dragos. ... _______________________________________________ OVAL_Developer mailing list OVAL_Developer@lists.cisecurity.org http://lists.cisecurity.org/mailman/listinfo/oval_developer_lists.cisecurity.org ...