Thanks for reaching out, and for taking the time to get the wording right. It's great to see a new implementation targeting the specification and the TCK.
Your wording is accurate and the caveat is the important part. Today there is no official certification or compatibility program: it is one of the goals of the AsciiDoc Working Group for 2027 (we are starting to plan a self-certification process), and the specification and TCK are still in progress. So "compatibility is a work in progress and not an official certification" is exactly the right message. I would only suggest saying "aims to be compatible with" rather than "implement ... in a way that is compatible".
There is no official terminology or report format yet. Until there is one, I would suggest reporting:
- the TCK version (tag or commit hash) you tested against
- the number of passing and failing tests
- the list of tests you skip or don't support yet, with the reason, and any feature you intentionally don't support
That should make your results easy to compare once a certification process exists. If you are willing, we would also welcome your feedback on what you find along the way (TCK gaps, ambiguous parts of the specification): the best place is the AsciiDoc chat (
https://chat.asciidoc.org), or an issue on the specification / TCK repositories (
https://gitlab.eclipse.org/eclipse/asciidoc-lang).
Finally, "AsciiDoc" is a trademark. Using it in a project name to describe what it processes is common, but guidelines for naming and for claiming compatibility are being prepared, so keep an eye on
asciidoc.org and the WG announcements.
Best regards,
Guillaume