Hi Dan, I gave up trying to get into the Eclipse site (couldn't manage to create a password combination that worked - tried in two different browsers in two different OSs... ) but anyway, I skimmed the group mission and saw this:
To execute this mission, the Working Group will: > > Foster the design and development of the AsciiDoc language specification, > which includes the syntax, rules, built-in attributes, Abstract Semantic > Graph (ASG), DOM (Document Object Model), API and options, conversion > model, referencing system, extension SPI, and runtime-agnostic technology > compatibility kit (TCK), all to ensure interoperability and portability of > information encoded in AsciiDoc. > We do a lot of exactly this, e.g. see these two specs - Archetype Definition Language <https://specifications.openehr.org/releases/AM/latest/ADL2.html> (a syntax spec) - Archetype Object Model <https://specifications.openehr.org/releases/AM/latest/AOM2.html> (the related ASG spec, which is also an ISO std) You'll see that we do a lot of syntax, diagrams, UML (in the second one), for which we have an OS extractor for MagicDraw. Plus bibtex. You have probably already worked out what you are doing, but feel free to plunder any stylistic, presentation or other ideas. We also manage all these specs (there are about 30) as adoc source + UML + draw.io diags in Github with Jira projects to manage change requests in the long term. We publish on the server via Github webhooks and scripts. Some governance ideas here <https://www.openehr.org/programs/specification/governance>. Again, you've probably got everything worked out, but as we've been doing this for 20y and 4y with the Asciidoctor publishing set up) I thought I'd at least point to it in case anyone was looking for ideas. best - thomas On Thursday, 30 April 2020 00:02:24 UTC+1, Dan Allen wrote: > > thomas, > > That's great to hear. We welcome your participation! > > Both the charter for the working group and the language specification > project have been proposed (following the EFSP). You can find them here: > > * https://www.eclipse.org/org/workinggroups/asciidoc-charter.php > * https://projects.eclipse.org/proposals/asciidoc-language > > Also see https://www.eclipse.org/lists/asciidoc-wg/msg00035.html > > To follow along with this effort as it gets underway, I encourage you to > join the working group mailinglist at > https://accounts.eclipse.org/mailing-list/asciidoc-wg. Once the > specification process is approved, it will get its own mailinglist as well, > which is where the technical discussions will happen. > > Best Regards, > > -Dan > > On Mon, Apr 20, 2020 at 6:07 AM Thomas Beale <[email protected] > <javascript:>> wrote: > >> Interested to know the current status of this effort. Having worked in >> standards for over 20y, and also 4y ago converted all our specifications >> (which are used as de facto standards) to Asciidoctor, and having had some >> passing experience with Eclipse Foundation, I may be able to contribute an >> idea or two. >> >> - thomas >> >> On Monday, 7 January 2019 21:36:20 UTC, Dan Allen wrote: >>> >>> I'm excited to share with you some much anticipated news. >>> >>> After numerous calls for an AsciiDoc specification over the past year, >>> it's very clear the community is ready for AsciiDoc to take this step. As >>> we established in previous threads, Lex and I are in agreement. I also >>> reached out to Stuart and we have his support as well. So now's the perfect >>> time to pursue it. >>> >>> == A new home at the Eclipse Foundation >>> >>> We all want AsciiDoc to have a strong future and the resources it needs >>> to evolve and grow. To achieve this, I'm planning to submit a proposal for >>> an AsciiDoc language specification to the Eclipse Foundation. The Eclipse >>> Foundation provides a home for developing specifications and is committed >>> to transparency and open source, values that align well with AsciiDoc and >>> its community. Specifically, the Eclipse Foundation Specification Process >>> (EFSP) provides a clear, yet customizable structure that reduces the risk >>> of the process stalling and ensures the outcome will be usable in the real >>> world. The process is public, vendor neutral, and all source materials and >>> final artifacts are open source. >>> >>> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/asciidoc/7aeea5d4-1dc7-444e-9aab-63a8aacb3cbf%40googlegroups.com >> >> <https://groups.google.com/d/msgid/asciidoc/7aeea5d4-1dc7-444e-9aab-63a8aacb3cbf%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > > > -- > Dan Allen | @mojavelinux | https://twitter.com/mojavelinux > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/asciidoc/3af8051f-c50b-4320-87d5-17cc549b4781%40googlegroups.com.
