On 6/16/07, Thomas Nichols <[EMAIL PROTECTED]> wrote:
This looks a workable option for us (and is in fact what we were doing
last time we played with this). The 'profile' idea is also interesting
-- though for consistency with other mime-types would this be the
optimal syntax? With embedded space/newline and semi-colon?
The newline wasn't intentional, darned email, but yes, like Content-Type.
content := "Content-Type" ":" type "/" subtype *(";" parameter)
I suggested the parameter because something similar is specified for
[`application/xhtml+xml` RFC][rfc3236].
[rfc3236]: http://tools.ietf.org/html/rfc3236#section-8
If the profile is not sufficient precisely to identify the supported
language syntax, I'm not sure it would have much practical value for us.
Of course, `text/x-markdown+extra` won't give you that either.
The primary advantage of a URL is that it provides a discovery
mechanism. It also makes explicit that different "profiles" are all in
the Markdown family, which a shared `x-markdown` prefix doesn't.
Anyway, Michel Fortin is probably right, and the whole scheme is too
complicated to bother with.
Never mind. :)
_______________________________________________
Markdown-Discuss mailing list
[email protected]
http://six.pairlist.net/mailman/listinfo/markdown-discuss
