[16] enhancement: use new RFC 7464 JSON sequencing in i3bar protocol · Issue #1493 · i3/i3
( 版)
https://github.com/i3/i3/issues/1493
[17] ISSUE-20: Represent Collections using JSON Text Sequences (RFC 7464) - Social Web Working Group Tracker
( 版)
http://www.w3.org/Social/track/issues/20
The cat command concatenates the features of one or more datasets and prints them as a JSON text sequence of features. In other words: GeoJSON feature objects, possibly pretty printed, separated by ASCII RS (x1e) chars. LF-separated sequences with no pretty printing are optionally available using --x-json-seq-no-rs.
[21] RFC 7946 - The GeoJSON Format
()
https://tools.ietf.org/html/rfc7946#appendix-C
If such a representation is needed, a new media type is required that
has the ability to represent these sets or sequences. When defining
such a media type, it may be useful to base it on "JavaScript Object
Notation (JSON) Text Sequences" [RFC7464], leaving the foundations of
how to represent multiple JSON objects to that specification, and
only defining how it applies to GeoJSON objects.
[22]GeoJSON text sequences
[23] draft-wilde-json-seq-suffix-00 - A Media Type Structured Syntax Suffix for JSON Text Sequences
()
https://tools.ietf.org/html/draft-wilde-json-seq-suffix-00
[24] +json-seq should be a proper structured syntax suffix · Issue #19 · geojson/geojson-text-sequences
()
https://github.com/geojson/geojson-text-sequences/issues/19
[25] I-D/json-seq-suffix at master · dret/I-D
()
https://github.com/dret/I-D/tree/master/json-seq-suffix
[28] RFC 8091 - A Media Type Structured Syntax Suffix for JSON Text Sequences () https://tools.ietf.org/html/rfc8091
[36] GeoJSONSeq: sequence of GeoJSON features — GDAL documentation
(, )
https://gdal.org/drivers/vector/geojsonseq.html
RS=YES/NO: whether to start records with the RS=0x1E character, so as to be compatible with the RFC 8142 standard. Defaults to NO, unless the filename extension is “geojsons”