The text/markdown Media Type
draft-ietf-appsawg-text-markdown-11

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Author Sean Leonard 
Last updated 2015-10-14 (latest revision 2015-09-03)
Replaces draft-seantek-text-markdown-media-type
Stream IETF
Intended RFC status Informational
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Murray Kucherawy
Shepherd write-up Show (last changed 2015-06-17)
IESG IESG state IESG Evaluation::AD Followup
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Barry Leiba
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
Applications Area Working Group                               S. Leonard
Internet-Draft                                             Penango, Inc.
Intended Status: Informational                         September 3, 2015
Expires: March 6, 2016                                                  

                      The text/markdown Media Type
                  draft-ietf-appsawg-text-markdown-11

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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.     

 

Leonard                    Exp. March 6, 2016                   [Page 1]
Internet-Draft        The text/markdown Media Type        September 2015

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
     1.1. This Is Markdown! Or: Markup and Its Discontents  . . . . .  2
     1.2. Markdown Is About Writing and Editing . . . . . . . . . . .  3
     1.3. Definitions . . . . . . . . . . . . . . . . . . . . . . . .  5
   2. Markdown Media Type Registration Application  . . . . . . . . .  5
   3. Fragment Identifiers  . . . . . . . . . . . . . . . . . . . . .  8
     3.1. Parameters  . . . . . . . . . . . . . . . . . . . . . . . .  8
   4.  Content Disposition and preview-type . . . . . . . . . . . . .  8
   5.  Example  . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
     6.1. Markdown Variants . . . . . . . . . . . . . . . . . . . . . 10
   7. Security Considerations . . . . . . . . . . . . . . . . . . . . 12
   8. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     8.1. Normative References  . . . . . . . . . . . . . . . . . . . 13
     8.2. Informative References  . . . . . . . . . . . . . . . . . . 14
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 15

1. Introduction

1.1. This Is Markdown! Or: Markup and Its Discontents

   In computer systems, textual data is stored and processed using a
   continuum of techniques. On the one end is plain text: computer-
   encoded text that consists only of a sequence of code points from a
   given standard, with no other formatting or structural information
   [UNICODE]. (On the other end is binary data, which computer systems
   store and process with bit-for-bit accuracy.) Many of these standards
   include control characters that are used as in-band signaling to
   cause effects other than the addition of a symbol (or grapheme) to
   the text.

   Markup offers an alternative means to encode this signaling
   information by overloading certain graphic characters (see, e.g.,
   [ISO646]) with additional meanings. Therefore, markup languages allow
   for annotating a document in a syntactically distinguishable way from
   the text, while keeping the annotations printable. Markup languages
   are (reasonably) well-specified and tend to follow (mostly)
   standardized syntax rules. Examples of formal markup languages
   include SGML, HTML, XML, and LaTeX. Standardized rules lead to
   interoperability between markup processors, but impose skill
   requirements on new users that lead to markup languages becoming less
   accessible to beginners. These rules also reify "validity": content
   that does not conform to the rules is treated differently (i.e., is
   rejected) than content that conforms.

 

Leonard                    Exp. March 6, 2016                   [Page 2]
Show full document text