Skip to content

Why does implicit OSCAL namespace lack a version number? #1258

Answered by david-waltermire
galtm asked this question in Q&A
Discussion options

You must be logged in to vote

We want things like a prop or part name to persist across multiple major OSCAL revisions. This is why the namespace used in these contexts is not major version specific.

The XML namespace is intended to be major version specific, since major version updates will allow backwards compatibility breaking changes. Yes, 1.0 includes a minor version. We will fix this when the first 2.x release is made.

This is why the part/prop namespace differs from the XML namespace.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@galtm
Comment options

Answer selected by david-waltermire
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants