draft-ietf-appsawg-text-markdown-09.txt   draft-ietf-appsawg-text-markdown-10.txt 
Applications Area Working Group S. Leonard Applications Area Working Group S. Leonard
Internet-Draft Penango, Inc. Internet-Draft Penango, Inc.
Intended Status: Informational August 26, 2015 Intended Status: Informational August 30, 2015
Expires: February 27, 2016 Expires: March 2, 2016
The text/markdown Media Type The text/markdown Media Type
draft-ietf-appsawg-text-markdown-09 draft-ietf-appsawg-text-markdown-10
Abstract Abstract
This document registers the text/markdown media type for use with This document registers the text/markdown media type for use with
Markdown, a family of plain text formatting syntaxes that optionally Markdown, a family of plain text formatting syntaxes that optionally
can be converted to formal markup languages such as HTML. can be converted to formal markup languages such as HTML.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 2, line 22 skipping to change at page 2, line 22
3. Fragment Identifiers . . . . . . . . . . . . . . . . . . . . . 8 3. Fragment Identifiers . . . . . . . . . . . . . . . . . . . . . 8
3.1. Parameters . . . . . . . . . . . . . . . . . . . . . . . . 8 3.1. Parameters . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Content Disposition and preview-type . . . . . . . . . . . . . 8 4. Content Disposition and preview-type . . . . . . . . . . . . . 8
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6.1. Markdown Variants . . . . . . . . . . . . . . . . . . . . . 10 6.1. Markdown Variants . . . . . . . . . . . . . . . . . . . . . 10
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 12
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . . 13 8.1. Normative References . . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . . 14 8.2. Informative References . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
1.1. This Is Markdown! Or: Markup and Its Discontents 1.1. This Is Markdown! Or: Markup and Its Discontents
In computer systems, textual data is stored and processed using a In computer systems, textual data is stored and processed using a
continuum of techniques. On the one end is plain text: computer- continuum of techniques. On the one end is plain text: computer-
encoded text that consists only of a sequence of code points from a encoded text that consists only of a sequence of code points from a
given standard, with no other formatting or structural information given standard, with no other formatting or structural information
[UNICODE]. (On the other end is binary data, which computer systems [UNICODE]. (On the other end is binary data, which computer systems
skipping to change at page 6, line 19 skipping to change at page 6, line 19
the variant MAY be registered under another media type; this the variant MAY be registered under another media type; this
text/markdown registration does not preclude other registrations. text/markdown registration does not preclude other registrations.
Encoding considerations: Encoding considerations:
Markdown content is plain text content; any octet sequence is valid Markdown content is plain text content; any octet sequence is valid
as long as it conforms to the character codes of the charset as long as it conforms to the character codes of the charset
parameter. See [RFC2046]. Markup characters in [MDSYNTAX] are parameter. See [RFC2046]. Markup characters in [MDSYNTAX] are
limited to printable US-ASCII; however, other variants can define limited to printable US-ASCII; however, other variants can define
markup characters outside this range (including control characters markup characters outside this range (including control characters
such as NUL and characters encoded in multiple bytes). such as NUL and characters encoded in multiple octets).
Security considerations: Security considerations:
Markdown interpreted as plain text is relatively harmless. A text Markdown interpreted as plain text is relatively harmless. A text
editor need only display the text. The editor SHOULD take care to editor need only display the text. The editor SHOULD take care to
handle control characters appropriately, and to limit the effect of handle control characters appropriately, and to limit the effect of
the Markdown to the text editing area itself; malicious Unicode- the Markdown to the text editing area itself; malicious Unicode-
based Markdown could, for example, surreptitiously change the based Markdown could, for example, surreptitiously change the
directionality of the text. An editor for normal text would already directionality of the text. An editor for normal text would already
take these control characters into consideration, however. take these control characters into consideration, however.
skipping to change at page 13, line 29 skipping to change at page 13, line 29
<http://daringfireball.net/linked/2011/08/05/markdown- <http://daringfireball.net/linked/2011/08/05/markdown-
uti>. uti>.
[RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, November 1996. Bodies", RFC 2045, November 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2183] Troost, R., Dorner, S., and K. Moore, Ed., "Communicating
Presentation Information in Internet Messages: The
Content-Disposition Header Field", RFC 2183, August 1997.
[RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded [RFC2231] Freed, N. and K. Moore, "MIME Parameter Value and Encoded
Word Extensions: Character Sets, Languages, and Word Extensions: Character Sets, Languages, and
Continuations", RFC 2231, November 1997. Continuations", RFC 2231, November 1997.
[RFC3778] Taft, E., Pravetz, J., Zilles, S., and L. Masinter, "The [RFC3778] Taft, E., Pravetz, J., Zilles, S., and L. Masinter, "The
application/pdf Media Type", RFC 3778, May 2004. application/pdf Media Type", RFC 3778, May 2004.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005. 3986, January 2005.
skipping to change at page 14, line 14 skipping to change at page 14, line 18
[RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized [RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized
Email Headers", RFC 6532, February 2012. Email Headers", RFC 6532, February 2012.
[RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type [RFC6838] Freed, N., Klensin, J., and T. Hansen, "Media Type
Specifications and Registration Procedures", BCP 13, RFC Specifications and Registration Procedures", BCP 13, RFC
6838, January 2013. 6838, January 2013.
8.2. Informative References 8.2. Informative References
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046,
November 1996.
[UNICODE] The Unicode Consortium, "The Unicode Standard, Version [UNICODE] The Unicode Consortium, "The Unicode Standard, Version
8.0.0", The Unicode Consortium, August 2015. 8.0.0", The Unicode Consortium, August 2015.
[ISO646] International Organization for Standardization, [ISO646] International Organization for Standardization,
"Information technology - ISO 7-bit coded character set "Information technology - ISO 7-bit coded character set
for information interchange", ISO Standard 646, 1991. for information interchange", ISO Standard 646, 1991.
[HUMANE] Atwood, J., "Is HTML a Humane Markup Language?", May 2008, [HUMANE] Atwood, J., "Is HTML a Humane Markup Language?", May 2008,
<http://blog.codinghorror.com/is-html-a-humane-markup- <http://blog.codinghorror.com/is-html-a-humane-markup-
language/>. language/>.
[INETMEME] Solon, O., "Richard Dawkins on the internet's hijacking of [INETMEME] Solon, O., "Richard Dawkins on the internet's hijacking of
the word 'meme'", June 2013, the word 'meme'", June 2013,
<http://www.wired.co.uk/news/archive/2013-06/20/richard- <http://www.wired.co.uk/news/archive/2013-06/20/richard-
dawkins-memes>, <http://www.webcitation.org/6HzDGE9Go>. dawkins-memes>, <http://www.webcitation.org/6HzDGE9Go>.
[MDMTGUID] Leonard, S., "Guidance on Markdown: Design Philosophies, [MDMTGUID] Leonard, S., "Guidance on Markdown: Design Philosophies,
Stability Strategies, and Select Registrations", draft- Stability Strategies, and Select Registrations", draft-
ietf-appsawg-text-markdown-use-cases-03 (work in ietf-appsawg-text-markdown-use-cases-04 (work in
progress), August 2015. progress), August 2015.
[PANDOC] MacFarlane, J., "Pandoc", 2014, [PANDOC] MacFarlane, J., "Pandoc", 2014,
<http://johnmacfarlane.net/pandoc/>. <http://johnmacfarlane.net/pandoc/>.
[RFC4263] Lilly, B., "Media Subtype Registration for Media Type [RFC4263] Lilly, B., "Media Subtype Registration for Media Type
text/troff", RFC 4263, January 2006. text/troff", RFC 4263, January 2006.
Author's Address Author's Address
 End of changes. 7 change blocks. 
6 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/