Naming convention for Asciidoctor extensions

[djencks]

This certainly applies to processor extensions, and presumably also to converter, template, and highlighter extensions.

In order to encourage 3rd party extensions to release to ruby gems, it would be helpful to have a suggested naming convention that avoided collisions and credited the 3rd party.

In javascript, npm has namespaces. Thus I can release a @djencks/asciidoctor-openblock processor extension that won't collide with anyone else's asciidoctor-openblock extension. RubyGems apparently has no such namespace facility.

As a starting point for discussion, I suggest a pattern of <orgname>-asciidoctor-<extensionpurpose>. This doesn't fit with the advice that would indicate that this relates to Orgname::Asciidoctor::Extensionpurpose, but the existing extensions such as asciidoctor-mathematical don't do this either.

With this proposed convention, my ruby extension gem name would be djencks-asciidoctor-openblock.