RFC 7111: URI Fragment Identifiers for the text/csv Media Type
In plain English — editorial summary, not part of the RFC
This memo defines URI fragment identifiers for text/csv MIME entities. These fragment identifiers make it possible to refer to parts of a text/csv MIME entity identified by row, column, or cell. Fragment identification can use single items or ranges.
Document record
- Document ID
- RFC7111
- Published
- January 2014
- Authors
- M. Hausenblas; E. Wilde; J. Tennison
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 13
- Also known as
- —
- Updates:
- RFC 4180
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7681Email Exchange of Secondary School TranscriptsCurrent
October 2015
- RFC 6922The application/sql Media TypeCurrent
April 2013
- RFC 6657Update to MIME regarding "charset" Parameter Handling in Textual Media TypesCurrent
July 2012
- RFC 6522The Multipart/Report Media Type for the Reporting of Mail System Administrative MessagesUpdated
January 2012
- RFC 8081The "font" Top-Level Media TypeCurrent
February 2017
- RFC 6109La Posta Elettronica Certificata - Italian Certified Electronic MailCurrent
April 2011
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 5686RTP Payload Format for mU-law EMbedded Codec for Low-delay IP Communication (UEMCLIP) Speech CodecCurrent
October 2009
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?