GeoJSON Text Sequences
draft-ietf-geojson-text-sequence-04

The information below is for an old version of the document
Document Type Active Internet-Draft (geojson WG)
Last updated 2017-02-02 (latest revision 2017-01-24)
Replaces draft-gillies-geojson-text-seq
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Martin Thomson
Shepherd write-up Show (last changed 2016-09-19)
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alissa Cooper
Send notices to "Martin Thomson" <martin.thomson@gmail.com>
IANA IANA review state IANA OK - Actions Needed
GeoJSON                                                       S. Gillies
Internet-Draft                                                    Mapbox
Intended status: Standards Track                        January 25, 2017
Expires: July 29, 2017

                         GeoJSON Text Sequences
                  draft-ietf-geojson-text-sequence-04

Abstract

   This document defines a format for geographic data that can be parsed
   and produced incrementally.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 29, 2017.

Copyright Notice

   Copyright (c) 2017 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.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Gillies                   Expires July 29, 2017                 [Page 1]
Internet-Draft                 GeoJSONSeq                   January 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  GeoJSON Text Sequence Format  . . . . . . . . . . . . . . . .   2
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  Interoperability Considerations . . . . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Large or never-ending sequences of values pose a problem for JSON
   that is well explained in the motivation for JSON Text Sequences
   [RFC7464].  GeoJSON [RFC7946] faces the same kind of problem:
   geographic datasets often run to the tens of thousands or millions of
   features.  The problem is often amplified by the presence of large
   arrays of coordinates for each of the features.

   This document describes a specialization of JSON Text Sequences.  A
   GeoJSON Text Sequence is a document of arbitrarily large size
   containing one or more GeoJSON objects, e.g., multiple GeoJSON texts
   that can be parsed and produced incrementally, and not only a single
   GeoJSON FeatureCollection, Feature, or Geometry.

   The advantage of using ASCII character RS "0x1e" to denote a text is
   that sequence producers and parsers need not enforce a canonical form
   of GeoJSON.  Any valid GeoJSON, pretty-printed or compact, can be
   used in a GeoJSON text sequence.  Additionally, GeoJSON text
   sequences inherit from the other [RFC7464] rules for consistent
   processing of sequences with potentially corrupted texts.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

2.  GeoJSON Text Sequence Format

   Defined in prose, following [RFC7464]: a GeoJSON text sequence is any
   number of GeoJSON [RFC7946] texts, each encoded in UTF-8 [RFC3629],
   each preceded by one ASCII RS character, and each followed by a line
   feed (LF).

Gillies                   Expires July 29, 2017                 [Page 2]
Internet-Draft                 GeoJSONSeq                   January 2017

   The GeoJSON Text Sequence Format conforms to all the rules of
   [RFC7464] and adds the following constraint: each JSON text MUST
   contain a single GeoJSON object as defined in [RFC7946].

   Heterogeneous sequences containing a mix of GeoJSON Geometry,
   Feature, and FeatureCollection objects are permitted.  How producers
   and parsers of GeoJSON text sequences communicate rules for allowed
Show full document text