On Tuesday, January 8, 2019 at 2:04:49 AM UTC-5, Lex Trotman wrote: > > It raises the rather basic question of "what are we standardising?" > This part is easy.
asciidoc generates XML-DocBook as a lossless translation. You are standardizing that translation. Therefore, conformance will be defined by a set of test pairs, one of which is asciidoc source and one of which is XML-DocBook output. That test set will be accompanied by a narrative description of intent (the standards document itself). This philosophy has two huge advantages: 1. It is a crisp, well-defined test. 2. It sidesteps all the downstream issues about rendering and presentation. You don't instantly land in trouble when there's a new back end. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
