You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 2, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 2, 2024. It is now read-only.
moving oval-def:NotesType to OVAL Common breaks backward compatibility #237
In addressing issue #6, we ended up breaking backward compatibility because we moved the NotesType construct from the OVAL Definitions Model to the OVAL Common Model. As a result, when pre-OVAL 5.11 content is validated against OVAL 5.11, it is finding oval-def:notes and oval-def:note elements, but, is expecting oval:notes and oval:note elements.
Please see the following thread for more information.
There is one issue, the change allows empty elements whereas they weren't allowed previously. I believe we can address this in schematron but I haven't implemented that yet. It could also be addressed with xsd:assert but we'd need to use XSD 1.1 which is not well supported.
Activity
Changed OVAL 5.11 XSD, allow oval:note and oval-def:note inside notes
mpreisler commentedon Mar 18, 2015
The following commit fixes compatibility issues in openscap. Could serve as an inspiration for OVAL 5.11.1 change addressing this.
OpenSCAP/openscap@8e1f69c
There is one issue, the change allows empty elements whereas they weren't allowed previously. I believe we can address this in schematron but I haven't implemented that yet. It could also be addressed with xsd:assert but we'd need to use XSD 1.1 which is not well supported.
Comments welcome.
5.11.1 Core Fixes