Re: [apps-discuss] New I-D: text/markdown Media Type - draft-seantek-text-markdown-media-type-00

[Carsten Bormann <[e-mail]>]

As Graham noted, pandoc shows us the way here:

1) define tags, one for each of the extensions and willful violations ("flavors”).
   The tags defined by pandoc could serve as a starter set here.
	http://johnmacfarlane.net/pandoc/demo/example9/pandocs-markdown.html
   Add an IANA registry with “specification required” policy.
2) mark an instance by the set of tags that apply to it (or, possibly could apply to it)
3) “Accept:” instances by the set of tags that can be processed (i.e. any subset is acceptable).

If the registry has numeric values added, the sets could be efficiently indicated as a numerically encoded bit set.
(Otherwise the tags get a bit unwieldy, e.g. gfm = pipe_tables, raw_html, tex_math_single_backslash, fenced_code_blocks, fenced_code_attributes, auto_identifiers, ascii_identifiers, backtick_code_blocks, autolink_bare_uris, intraword_underscores, strikeout, hard_line_breaks.)

So this doesn’t seem too hard to do.

Worth it?

Grüße, Carsten