|Re: [asciidoc-wg] AsciiDoc implementation for the Java/JVM ecosystem / project proposal|
> This was when a very basic question arose:
> What indeed will be THE main -- and so most important - - benefit of
> the standardisation process?
> Will it indeed be the syntax, so to say the UI part of Asciidoc?
> Or will it be the standardised DOM/AST supported by an API, on which
> the syntax parser and the backend converters will work?
here's my understanding: The AsciiDoc language specification will define
the syntax and the AST/ASG, see the current draft of the charter:
The TCK will provide test cases, and might also include a transformation
to one example HTML format (although that is not set in stone yet).
All compatible implementations - I assume there will be multiple - will
then be able to parse a document according to the same syntax. The value
of different implementations lies in how they provide access to
extensions to the AST/ASG and to different output formats.
Given a source document and mulitple implementations, I assume they will
create differently styled PDFs and differently styled HTMLs.
As a user of AsciiDoc this allows you to pick the implementation that
best matches your output format or plugin needs. When your requirements
change, you can change the implementation, but can continue to use your
AsciiDoc sources. If you written your own (implementation specific)
plugins, you might need to rewrite them when you change implementations.
I hope this answers your question. I didn't follow the discussion
regarding RustDoc; if you want to go into details, please provide a link
or some context.
Alexander Schwartz (alexander.schwartz@xxxxxxx)
asciidoc-wg mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg
Back to the top