@Dan-ODS That is my understanding and Open Referral UK already have a 'Compliance` model.
My main concern about not using terms like Compliance and Compatibility is how we frame the documentation for 3.0.
It is difficult for the documentation to remain completely neutral and just specify publication options and not specify any recomendation on how to use any of them.
We could just say that we “recommend”, APIs over Datapackages, for example, but that does not feel like strong enough language. I would prefer if we just said that publishing datapackages were “deprecated” but maybe that is too strongly worded.
On top of this, I think the documation needs reframing, to move the API approach into the “Human Services Data Spec” top section, replacing the “Formats and Packaging” section. The datapackage option could then be moved to where HSDA is now and expressed as an “alternate”/“deprecated” or “non recommended” option. Ideally we would also have examples of the produced JSON througout the whole of the “HSDS Reference” section.
I feel the documentation needs to push people to the “API” approach even if we do no explicitely use the terms “complience” (with the exception of OR-UK of course).