Session idea: accessible and interoperable authoring and annotation tooling

[csarven]

Spec editors use different tools and environments for authoring ie. not only respec, bikeshed - while some prefer desktop/terminal text editors, the brave among us go through convoluted installation processes, learn non-standardised tool-specific ("proprietary") hybrid languages ... in order to generate an HTML document.

AFAIK, W3C does not mandate the use of specific authoring tools. It is the final HTML output that needs to meet certain criteria eg. https://www.w3.org/pubrules/doc

Thus, to foster an inclusive space in the Spec Editors CG as well as to align with W3C's mission on "web for all", I propose sessions - potentially a work-item - towards building accessible and interoperable authoring and annotation tooling for specs.

[marcoscaceres]

@csarven, thanks for this proposal! It might be good to focus it a bit more just on your particular tool (i.e., something like "Using Dokieli to collaboratively annotate a spec" or something similar). That way, it's nice and focused on just one small thing. The purpose being to show the value, and how it works, but not necessary to mandate it in any way.