New Version Notification for draft-ietf-appsawg-text-markdown-02.txt

Tue Sep 23 15:00:10 EDT 2014

While I'm always a fan of seeing my metadata format from MMD used, I echo Sean's comment -- this is NOT Markdown when you do this.

Let's not go down this road.

FTP

-- 
Fletcher T. Penney
fletcher at fletcherpenney.net 

On Sep 23, 2014, at 2:35 PM, Sean Leonard <dev+ietf at seantek.com> wrote:

> 
> On Sep 23, 2014, at 8:15 AM, Dennis E. Hamilton <dennis.hamilton at acm.org> wrote:
> 
>> Thanks for this, Sean.
>> 
>> It occurs to me that the attributes of the MIME type will also work perfectly on a #! line prefixed to the file, something that might be quite handy for the many cases when a MIME type associations is not directly usable/preserved. 
>> 
>> Three examples: (1) when the MD is embedded in PGP ASCII-armor as text/plain for verification of reliable transmission/authenticity, (2) when it occurs recursively, as when embedded in comments in a program that might be part of a literate-programming construction as it does in F#, and (3) in an export format from a Wiki for preservation/transport as wikiText to another Wiki that might deal with flavors for import.
> 
> Thanks for the observation, Dennis. I agree that you could use a syntax like #! to preserve this processing metadata.
> 
> You could also use an Internet message format file, like:
> 
> ILoveMarkdown.eml
> *****
> MIME-Version: 1.0
> Content-Type: text/markdown; flavor=Original; processor="pandoc -s -f markdown_strict+ tex_math_double_backslash+tex_math_dollars -t html" 
> Content-Transfer-Encoding: binary
> Subject: I Love Markdown
> Keywords: World, MacFarlane
> 
> Hello [Markdown World][mw]! $e=mc^2$ and \\(e=mc^2\\) are the same.
> 
> [mw]: http://johnmacfarlane.net/pandoc/
> *****
> 
> The overall point that I want to make (to the community), however, is that once you start introducing these metadata blocks, the content is no longer Markdown. Specifically, it’s no longer Gruber’s Original Markdown. It’s something else. It’s MultiMarkdown; it’s pandoc Markdown with a title block; it’s a tar file with extended attributes; it’s a ZIP file with some kind of manifest; it’s YAML; it’s HTML; it’s XML; it’s JSON…ultimately, it’s some container format. And (Gruber’s) Markdown isn’t a container format. It’s about content; it was designed that way. It’s a feature, and it’s a limitation. And that’s just fine.
> 
> The first premise of the Internet-Draft is that “text/markdown” will be sufficient to identify all Markdown content (the alternatives being “don’t label it as anything, keep it text/plain”, and “register hundreds upon hundreds of different media types”—the former is not useful and the latter is not interoperable). The second premise is that we are not going to touch the syntax—any imposition of structure on the content, however small, is a change to the syntax. Which is what leads us to the parameters.
> 
> Some people have said that parameters aren’t a good place to put “these things” because parameters aren’t preserved in (for example) files. But I find that argument pretty thin. The label “text/markdown” is also not guaranteed to be preserved when you save a file, because there is no uniform way to associate Content-Types with files across file systems. But if you’re going to label Markdown content as “text/markdown”, you’re already in a data storage regime that supports Internet media types, so the data storage regime should be supporting parameters just as well.
> 
> Sean
> 
>> 
>> 
>> -- Dennis E. Hamilton
>>   dennis.hamilton at acm.org    +1-206-779-9430
>>   https://keybase.io/orcmid  PGP F96E 89FF D456 628A
>>   X.509 certs used and requested for signed e-mail
>> 
>> 
>> 
>> -----Original Message-----
>> From: Markdown-Discuss On Behalf Of Sean Leonard
>> Sent: Monday, September 22, 2014 16:51
>> To: markdown-discuss at six.pairlist.net
>> Subject: New Version Notification for draft-ietf-appsawg-text-markdown-02.txt
>> 
>> Just a notification that draft-02 of the text/markdown registration has 
>> been posted. It incorporates a lot of public and private comments that 
>> were received over the last few weeks.
>> 
>> A change log is in Appendix A.
>> 
>> ********************
>> 
>> A new version of I-D, draft-ietf-appsawg-text-markdown-02.txt
>> has been successfully submitted by Sean Leonard and posted to the
>> IETF repository.
>> 
>> Name:		draft-ietf-appsawg-text-markdown
>> Revision:	02
>> Title:		The text/markdown Media Type
>> Document date:	2014-09-22
>> Group:		appsawg
>> Pages:		25
>> URL:            http://www.ietf.org/internet-drafts/draft-ietf-appsawg-text-markdown-02.txt
>> Status:         https://datatracker.ietf.org/doc/draft-ietf-appsawg-text-markdown/
>> Htmlized:       http://tools.ietf.org/html/draft-ietf-appsawg-text-markdown-02
>> Diff:           http://www.ietf.org/rfcdiff?url2=draft-ietf-appsawg-text-markdown-02
>> 
>> Abstract:
>>   This document registers the text/markdown media type for use with
>>   Markdown, a family of plain text formatting syntaxes that optionally
>>   can be converted to formal markup languages such as HTML.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> 
>> _______________________________________________
>> Markdown-Discuss mailing list
>> Markdown-Discuss at six.pairlist.net
>> https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
>> 
>> _______________________________________________
>> Markdown-Discuss mailing list
>> Markdown-Discuss at six.pairlist.net
>> https://pairlist6.pair.net/mailman/listinfo/markdown-discuss
> 
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss at six.pairlist.net
> https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist6.pair.net/pipermail/markdown-discuss/attachments/20140923/5805397d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4903 bytes
Desc: not available
URL: <https://pairlist6.pair.net/pipermail/markdown-discuss/attachments/20140923/5805397d/attachment-0001.bin>