< draft-ietf-geojson-text-sequence-03.txt		draft-ietf-geojson-text-sequence-04.txt >
	GeoJSON S. Gillies		GeoJSON S. Gillies
	Internet-Draft Mapbox		Internet-Draft Mapbox
	Intended status: Informational January 7, 2017		Intended status: Standards Track January 25, 2017
	Expires: July 11, 2017		Expires: July 29, 2017
	GeoJSON Text Sequences		GeoJSON Text Sequences
	draft-ietf-geojson-text-sequence-03		draft-ietf-geojson-text-sequence-04
	Abstract		Abstract
	A proposed standard for geographic data that can be parsed and		This document defines a format for geographic data that can be parsed
	produced incrementally.		and produced incrementally.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	provisions of BCP 78 and BCP 79.		provisions of BCP 78 and BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on July 11, 2017.		This Internet-Draft will expire on July 29, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2017 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 2, line 28 ¶		skipping to change at page 2, line 28 ¶
	1. Introduction		1. Introduction
	Large or never-ending sequences of values pose a problem for JSON		Large or never-ending sequences of values pose a problem for JSON
	that is well explained in the motivation for JSON Text Sequences		that is well explained in the motivation for JSON Text Sequences
	[RFC7464]. GeoJSON [RFC7946] faces the same kind of problem:		[RFC7464]. GeoJSON [RFC7946] faces the same kind of problem:
	geographic datasets often run to the tens of thousands or millions of		geographic datasets often run to the tens of thousands or millions of
	features. The problem is often amplified by the presence of large		features. The problem is often amplified by the presence of large
	arrays of coordinates for each of the features.		arrays of coordinates for each of the features.
	This document describes a specialization of JSON Text Sequences. A		This document describes a specialization of JSON Text Sequences. A
	GeoJSON Text Sequence is a document of possibly infinite size		GeoJSON Text Sequence is a document of arbitrarily large size
	containing one or more GeoJSON objects, e.g., multiple GeoJSON texts		containing one or more GeoJSON objects, e.g., multiple GeoJSON texts
	that can be parsed and produced incrementally, and not only a single		that can be parsed and produced incrementally, and not only a single
	GeoJSON FeatureCollection, Feature, or Geometry.		GeoJSON FeatureCollection, Feature, or Geometry.
	The advantage of using ASCII character RS "0x1e" to denote a text is		The advantage of using ASCII character RS "0x1e" to denote a text is
	that sequence producers and parsers need not enforce a canonical form		that sequence producers and parsers need not enforce a canonical form
	of GeoJSON. Any valid GeoJSON, pretty-printed or compact, can be		of GeoJSON. Any valid GeoJSON, pretty-printed or compact, can be
	used in a GeoJSON text sequence. Additionally, GeoJSON text		used in a GeoJSON text sequence. Additionally, GeoJSON text
	sequences inherit from the other [RFC7464] rules for consistent		sequences inherit from the other [RFC7464] rules for consistent
	processing of sequences with potentially corrupted texts.		processing of sequences with potentially corrupted texts.
	skipping to change at page 3, line 52 ¶		skipping to change at page 3, line 52 ¶
	Subtype name: geo+json-seq		Subtype name: geo+json-seq
	Required parameters: n/a		Required parameters: n/a
	Optional parameters: n/a		Optional parameters: n/a
	Encoding considerations: binary		Encoding considerations: binary
	Security considerations: See Section 3 above		Security considerations: See Section 3 above
	Interoperability considerations: See Section 4 abovee		Interoperability considerations: See Section 4 above
	Published specification: [[This document]]		Published specification: [[This document]]
	Applications that use this media type: No known applications		Applications that use this media type: No known applications
	currently use this media type. This media type is intended for		currently use this media type. This media type is intended for
	GeoJSON applications currently using colloquial line-delimited		GeoJSON applications currently using colloquial line-delimited
	variants of GeoJSON.		variants of GeoJSON.
	Additional information:		Additional information:
	Magic number(s): n/a		Magic number(s): n/a
End of changes. 6 change blocks.
	8 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/