| Re: [asciidoc-wg] BALLOT: Approval to Create the AsciiDoc Language Specification Project |
_______________________________________________+1 from a non voting associate member – will be following this with interest but can unfortunately only offer resources in a review capacity
Best,
Ben Engel
ASAM e.V.
+49 1516 1645 936
Von: asciidoc-wg-bounces@xxxxxxxxxxx <asciidoc-wg-bounces@xxxxxxxxxxx> Im Auftrag von Magnus Nordstrand
Gesendet: 23 July 2020 08:06
An: AsciiDoc Working Group Discussions <asciidoc-wg@xxxxxxxxxxx>
Betreff: Re: [asciidoc-wg] BALLOT: Approval to Create the AsciiDoc Language Specification Project
+1
Looking forward to things to come, and hope I can be of some help along the way.
Magnus Nordstrand
On Thu, 23 Jul 2020, 08:50 Manfred Moser, <manfred@xxxxxxxxxxxxxxxx> wrote:
+1 .. great work .. looking forward to all the progress being made.
Manfred Moser
Sharon Corbett wrote on 2020-07-21 13:57 (GMT -07:00):
Greetings AsciiDoc Specification Committee Representatives:
Your vote is required to approve the creation of the AsciiDoc Language Specification Project with the following scope:
The AsciiDoc Language project defines and maintains the AsciiDoc Language Specification and Technology Compatibility Kit (TCK), its artifacts, and the corresponding language and API documentation. The AsciiDoc Language Specification describes the syntax and grammar, Abstract Semantic Graph (ASG), Document Object Model (DOM), referencing system, and APIs for processing, converting, and extending the language. The TCK is used to verify and certify that an AsciiDoc processor implementation is compatible with this specification.
Specifically, the project scope includes the:
AsciiDoc language syntax and grammar (e.g., EBNF)
doctype structure and objects
ASG: namely the encoded form for use in the TCK (e.g., JSON)
TCK: Technology Compatibility Kit for the AsciiDoc language
DOM API: in memory semantic representation of the encoded information
Processor API (load, convert)
Converter API
Extension API
Extended syntax processors (e.g., custom block or macro)
Resolvers (e.g., path and attribute resolvers, ID generator)
Parse events and lifecycle interceptors (e.g., input processor, output processor, tree processor)
Integration adapters: syntax highlighter, STEM, bibliography, docinfo
Expected converter behaviors (e.g., toc, ID generation, icon type, safe mode)
Internal and external referencing system: (e.g., xrefs, includes, images)
Reference converter and output format (e.g., HTML w/ reference stylesheet, DocBook)
Built-in attributes and reserved attribute namespaces
AsciiDoc media type (MIME) and .adoc file extension
Per the Eclipse Foundation Specification Process, this will be a seven day ballot, ending on July 27, 2020. We require a super-majority positive vote of the Specification Committee representatives.
While only Specification Committee representatives votes will be binding, all are welcome and encouraged to participate.
Please respond to this message with +1 (positive), 0 (abstain), or -1 (reject). Any feedback that you can provide to support your vote will be appreciated (although not required).
Best Regards,
Sharon Corbett
Eclipse Foundation Inc._______________________________________________
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg
asciidoc-wg mailing list
asciidoc-wg@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/asciidoc-wg