RFC 7764: Guidance on Markdown: Design Philosophies, Stability Strategies, and Select Registrations
In plain English — editorial summary, not part of the RFC
This document elaborates upon 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. Background information, local storage strategies, and additional syntax registrations are supplied.
Document record
- Document ID
- RFC7764
- Published
- March 2016
- Authors
- S. Leonard
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 28
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7763The text/markdown Media TypeCurrent
March 2016
- RFC 7741RTP Payload Format for VP8 VideoCurrent
March 2016
- RFC 7790Mapping Characters for Classes of the Preparation, Enforcement, and Comparison of Internationalized Strings (PRECIS)Current
February 2016
- RFC 7798RTP Payload Format for High Efficiency Video Coding (HEVC)Current
March 2016
- RFC 7728RTP Stream Pause and ResumeCurrent
February 2016
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 7808Time Zone Data Distribution ServiceCurrent
March 2016
- RFC 7809Calendaring Extensions to WebDAV (CalDAV): Time Zones by ReferenceCurrent
March 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?