Why does implicit OSCAL namespace lack a version number? #1258
-
Related to #1247 : Why is the implicitly assumed OSCAL namespace |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
We want things like a The XML namespace is intended to be major version specific, since major version updates will allow backwards compatibility breaking changes. Yes, This is why the part/prop namespace differs from the XML namespace. |
Beta Was this translation helpful? Give feedback.
We want things like a
prop
orpart
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 first2.x
release is made.This is why the part/prop namespace differs from the XML namespace.