URI Fragment Identifiers for the text/csv Media Type
RFC 7111
| Document | Type |
RFC - Informational
(January 2014; Errata)
Updates RFC 4180
Was draft-hausenblas-csv-fragment (individual)
|
|
|---|---|---|---|
| Authors | Michael Hausenblas , Erik Wilde , Jeni Tennison | ||
| Last updated | 2019-01-08 | ||
| Stream | ISE | ||
| Formats | plain text html pdf htmlized bibtex | ||
| IETF conflict review | conflict-review-hausenblas-csv-fragment | ||
| Stream | ISE state | Published RFC | |
| Consensus Boilerplate | Unknown | ||
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | RFC 7111 (Informational) | |
| Telechat date | |||
| Responsible AD | Barry Leiba | ||
| Send notices to | (None) | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Independent Submission M. Hausenblas
Request for Comments: 7111 MapR Technologies
Updates: 4180 E. Wilde
Category: Informational UC Berkeley
ISSN: 2070-1721 J. Tennison
Open Data Institute
January 2014
URI Fragment Identifiers for the text/csv Media Type
Abstract
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.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This is a contribution to the RFC Series, independently of any other
RFC stream. The RFC Editor has chosen to publish this document at
its discretion and makes no statement about its value for
implementation or deployment. Documents approved for publication by
the RFC Editor are not a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7111.
IESG Note
The change to the text/csv media type registration requires IESG
approval, as the IESG is the change controller for that registration.
The IESG has, after consultation with the IETF community, approved
the change, which is specified in Section 5 of this document.
Hausenblas, et al. Informational [Page 1]
RFC 7111 text/csv Fragment Identifiers January 2014
Copyright Notice
Copyright (c) 2014 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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. What is text/csv? . . . . . . . . . . . . . . . . . . . . 3
1.2. Why text/csv Fragment Identifiers? . . . . . . . . . . . 3
1.2.1. Motivation . . . . . . . . . . . . . . . . . . . . . 3
1.2.2. Use Cases . . . . . . . . . . . . . . . . . . . . . . 4
1.3. Incremental Deployment . . . . . . . . . . . . . . . . . 4
1.4. Notation Used in this Memo . . . . . . . . . . . . . . . 4
2. Fragment Identification Methods . . . . . . . . . . . . . . . 5
2.1. Row-Based Selection . . . . . . . . . . . . . . . . . . . 5
2.2. Column-Based Selection . . . . . . . . . . . . . . . . . 6
2.3. Cell-Based Selection . . . . . . . . . . . . . . . . . . 6
2.4. Multi-Selections . . . . . . . . . . . . . . . . . . . . 7
3. Fragment Identification Syntax . . . . . . . . . . . . . . . 7
4. Fragment Identifier Processing . . . . . . . . . . . . . . . 8
4.1. Syntax Errors in Fragment Identifiers . . . . . . . . . . 8
4.2. Semantics of Fragment Identifiers . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
5.1. The text/csv media type . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 12
Hausenblas, et al. Informational [Page 2]
RFC 7111 text/csv Fragment Identifiers January 2014
1. Introduction
This memo updates the text/csv media type defined in RFC 4180
[RFC4180] by defining URI fragment identifiers for text/csv MIME
entities.
The change to the text/csv media type registration required IESG
approval, as the IESG is the change controller for that registration.
The IESG has, after consultation with the IETF community, approved
the change, which is specified in Section 5 of this document.
This section gives an introduction to the general concepts of
text/csv MIME entities and URI fragment identifiers and discusses the
need for fragment identifiers for text/csv and deployment issues.
Section 2 discusses the principles and methods on which this memo is
Show full document text