RFC 7111 / CSV FRAGMENT GUIDE

Retrieve the table, then select

A URI fragment is the part after #. A supporting client interprets it after retrieving the CSV resource.

RFC 7111 · § 1.2EXAMPLE

4 / 4

Consider an older client

Separate case: a client without this fragment support uses the complete resource instead. Do not assume every browser highlights rows.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references

New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Helpful first, if these ideas are unfamiliar

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

RFC 7111 defines fragment identifiers for the text/csv media type; it does not define a server query language.
Fragment meaning depends on the retrieved media type, regardless of the URI scheme (§1.2).
An unsupported client behaves as if the complete resource were referenced (§1.3). A server cannot reliably detect whether a fragment was used.

DETAILS

Also RFC 7111 §§1.3, 4.2 and RFC 3986 §3.5. The example table is fictional; highlighted regions are client-side selections, not server filtering.