Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [asciidoc-lang-dev] AsciiDoc Language Specification / TCK compatibility

Hi Michal,

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

Le mar. 7 juil. 2026 à 00:32, Michal Harakal via asciidoc-lang-dev <asciidoc-lang-dev@xxxxxxxxxxx> a écrit :
Hello AsciiDoc Language maintainers,

I am building an AsciiDoc processor implementation (Kotlin Multiplatform + WASM for plugins) and would like to make its compatibility goal clear and accurate.

Project link: https://github.com/markup-poets/asciidoc-kmp/tree/main

My current wording is:

“This project aims to implement the AsciiDoc language in a way that is compatible with the official AsciiDoc Language Specification and its Technology Compatibility Kit (TCK). Compatibility is currently a work in progress and should not be interpreted as official certification.”

Is this wording acceptable, or is there preferred terminology for projects that target the AsciiDoc TCK but are not yet officially certified?

I also want to confirm the recommended way to report TCK results, such as the TCK version or commit tested against, pass/fail status, and unsupported features.

Thank you.

Best regards,
   Michal
_______________________________________________
asciidoc-lang-dev mailing list
asciidoc-lang-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/asciidoc-lang-dev

Back to the top