Update non-compliance version (#603)

uxlfoundation · Dec 11, 2024 · 177829a · 177829a
1 parent 1aabfdd
commit 177829a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/source/elements/oneMath/source/architecture/other_architecture.inc.rst b/source/elements/oneMath/source/architecture/other_architecture.inc.rst
@@ -26,7 +26,7 @@ The macros for each domain are listed as follows:
   | ONEMATH_STATS_SPEC_VERSION
   | ONEMATH_VM_SPEC_VERSION
 
-The specification version can be created by appending all digits of the specification version in the format of <MAJOR><MINOR>. MINOR version always uses two digits. This version can be used to check the compatibility of the implementation with the specification version. Note that the revision is not included here because it reflects changes only for the specification document without affecting the implementation. If the implementation is not compliant with any release of the specification, then the macro must have a numerical value of `000`.
+The specification version can be created by appending all digits of the specification version in the format of <MAJOR><MINOR>. MINOR version always uses two digits. This version can be used to check the compatibility of the implementation with the specification version. Note that the revision is not included here because it reflects changes only for the specification document without affecting the implementation. If the implementation is not compliant with any release of the specification, then the macro must have a numerical value of `001`. Versions between `001` and `100` are reserved for alpha/beta support of the specification in oneMKL and should only be used for special cases. A preprocessor may evaluate an undefined macro to `0`, so `000` should not be used.
 
 Version Example