Major 4. Now, as to Statements of Use, sounds like you are in good shape. The requirements on those are pretty simple: the provider of an SoU must cite the published CS (including the version # and the approval date) and state that they have put together an implementation the meets the conformance clauses and listing the ccs they meet. So, for example, if someone has an implementation that uses the classification model, they simply need to list the relevant clauses that apply. Your conformance clauses look very thorough at a quick glance so you should have no problem there. Here is a template people can use for the SoU:
"As Primary Representative for <member name> to OASIS, I approve the following Statement of Use: <-- NOTE: this is needed for member companies, obviously not needed for non-member submissions
"<member name> has successfully implemented <title and version #> Committee Specification 01, approved <date of approval on the CS>, in accordance with < all mandatory conformance clauses therein | conformance clauses in sections #### | etc. > and OASIS policy. This implementation <did | did not> include interoperation with multiple independent implementations".
People are free to provide more information if they like. See for example these quite detailed statements for KMIP: https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/60994/KMIP-SOU-Cryptsoft-18-Jun-2017.pdf, https://www.oasis-open.org/apps/org/workgroup/kmip/download.php/61007/KMIP-SOU-P6R-18-June-2017-R2.pdf
The Statements of Use will need to be accepted by a resolution by the TC passed in a meeting and included in its minutes.