Re: [asciidoc-wg] Intro + feedback

[Dan Allen <dan@xxxxxxxxxxxxxx>]

Philippe,

There's one thing I forgot to mention. A key objective of this spec is that the community will no longer be split into "AsciiDoc.py / the Python version" vs "Asciidoctor". We'll have AsciiDoc the language with numerous compliant implementation choices. This will also put Python and Ruby users on equal footing. Right now, this is not the case since AsciiDoc.py lags well behind Asciidoctor. (Only the spec can properly reconcile this situation).

Naturally, implementations will foster their own ecosystem by providing tools and extensions (like Antora, for example). But when we talk about AsciiDoc the language, we'll know it means just one thing. It also means changes to the language will propagate faster to your implementation of choice.

Best Regards,

-Dan

--

Dan Allen, Vice President | OpenDevise Inc.
Content ∙ Strategy ∙ Community
opendevise.com