Editing markup http://criticmarkup.com/

Should this be considered for inclusion into the supported functionality of asciidoctor?
WDYT?

Interesting tool, but I think is not tight to any format so we can use it in AsciiDoc too. Of course to implement some kind of this syntax in AsciiDoc can be used by creating an extension.

Given the limited functionality of the spec (which is great for lots of use-cases), it may be desirable to have an asciidoctor specific set of markup, or asciidoc if coordinated with the asciidoc spec team.

The primary benefit of this approach is it would allow more complex use-cases, remove the inline only issue that critic markup suffers from (that is, our version could include block and inline markup) and could easily include things like ordering of edit comments, blame attribution, accepted/rejected (and other variations, for example, voting up/down), history etc.

This follows on from the issue raised in this thread http://discuss.asciidoctor.org/How-to-track-changes-with-text-files-tp453.html

I guess the big question is how much demand is there for adding editorial markup to the spec? Is it really needed?

Regardless, I think it is a good idea to support an extension for criticmarkup, and a number of text editors have plugins that support it. So I am sure some people would find it useful.