Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [asciidoc-wg] BALLOT: Approval to Create the AsciiDoc Language Specification Project
I haven't seen anything official from Red Hat since Robert was on PTO during the majority of this vote. I'm also not sure I can actually speak as his second, but I for one will give this a +1. I'm happy to see it move forward, and I believe Red Hat does as well.

On Sun, Jul 26, 2020 at 11:42 AM Vincent Smit <v.smit.mail@xxxxxxxxx> wrote:
+1

On Tue, Jul 21, 2020 at 10:58 PM Sharon Corbett <sharon.corbett@xxxxxxxxxxxxxxxxxxxxxx> wrote:

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


--

Jason Porter

He / Him / His

Principal Software Engineer

Red Hat NA

jporter@xxxxxxxxxx   
M: 801-231-1199     IM: lightguardjp

8D51 20A4 A885 9E1D 4B06 3A2D BEDF CFB3 0FB7 2D11

Back to the top