< draft-ietf-geojson-text-sequence-02.txt		draft-ietf-geojson-text-sequence-03.txt >
	GeoJSON S. Gillies		GeoJSON S. Gillies
	Internet-Draft Mapbox		Internet-Draft Mapbox
	Intended status: Informational September 19, 2016		Intended status: Informational January 7, 2017
	Expires: March 23, 2017		Expires: July 11, 2017
	GeoJSON Text Sequences		GeoJSON Text Sequences
	draft-ietf-geojson-text-sequence-02		draft-ietf-geojson-text-sequence-03
	Abstract		Abstract
	A proposed standard for geographic data that can be parsed and		A proposed standard for geographic data that can be parsed and
	produced incrementally.		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.
	skipping to change at page 1, line 31 ¶		skipping to change at page 1, line 31 ¶
	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 March 23, 2017.		This Internet-Draft will expire on July 11, 2017.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 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
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	described in the Simplified BSD License.		described in the Simplified BSD License.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
	1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2		1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
	2. GeoJSON Text Sequence Format . . . . . . . . . . . . . . . . 2		2. GeoJSON Text Sequence Format . . . . . . . . . . . . . . . . 2
	3. Security Considerations . . . . . . . . . . . . . . . . . . . 3		3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
	4. Interoperability Considerations . . . . . . . . . . . . . . . 3		4. Interoperability Considerations . . . . . . . . . . . . . . . 3
	5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
	6. Normative References . . . . . . . . . . . . . . . . . . . . 4		6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
	Appendix A. Contributors . . . . . . . . . . . . . . . . . . . . 5		6.1. Normative References . . . . . . . . . . . . . . . . . . 4
			6.2. Informative References . . . . . . . . . . . . . . . . . 5
	Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5		Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
	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.
	skipping to change at page 3, line 36 ¶		skipping to change at page 3, line 36 ¶
	GeoJSON texts with no internal newlines are more interoperable with		GeoJSON texts with no internal newlines are more interoperable with
	existing non-standardized parsers.		existing non-standardized parsers.
	In a distributed system where order and exactly-once delivery of		In a distributed system where order and exactly-once delivery of
	messages are difficult to achieve, GeoJSON text sequences that do not		messages are difficult to achieve, GeoJSON text sequences that do not
	rely on order of texts for extra semantics are more interoperable		rely on order of texts for extra semantics are more interoperable
	than those that do.		than those that do.
	5. IANA Considerations		5. IANA Considerations
	The MIME media type for GeoJSON feature sequences is application/		The MIME media type for GeoJSON feature sequences is "application/
	geo+json-seq.		geo+json-seq". This uses the suffix established in
			[I-D.wilde-json-seq-suffix].
	Type name: application		Type name: application
	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
	skipping to change at page 4, line 28 ¶		skipping to change at page 4, line 28 ¶
	Object Identifiers: n/a		Object Identifiers: n/a
	Person to contact for further information: Sean Gillies		Person to contact for further information: Sean Gillies
	(sean.gillies@gmail.com)		(sean.gillies@gmail.com)
	Intended usage: COMMON		Intended usage: COMMON
	Restrictions on usage: none		Restrictions on usage: none
	6. Normative References		6. References
			6.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO		[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
	10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November		10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
	2003, <http://www.rfc-editor.org/info/rfc3629>.		2003, <http://www.rfc-editor.org/info/rfc3629>.
	[RFC7159] Bray, T., "The JavaScript Object Notation (JSON) Data
	Interchange Format", RFC 7159, March 2014.
	[RFC7464] Williams, N., "JavaScript Object Notation (JSON) Text		[RFC7464] Williams, N., "JavaScript Object Notation (JSON) Text
	Sequences", RFC 7464, DOI 10.17487/RFC7464, February 2015,		Sequences", RFC 7464, DOI 10.17487/RFC7464, February 2015,
	<http://www.rfc-editor.org/info/rfc7464>.		<http://www.rfc-editor.org/info/rfc7464>.
	[RFC7946] Butler, H., Daly, M., Doyle, A., Gillies, S., Hagen, S.,		[RFC7946] Butler, H., Daly, M., Doyle, A., Gillies, S., Hagen, S.,
	and T. Schaub, "The GeoJSON Format", RFC 7946,		and T. Schaub, "The GeoJSON Format", RFC 7946,
	DOI 10.17487/RFC7946, August 2016,		DOI 10.17487/RFC7946, August 2016,
	<http://www.rfc-editor.org/info/rfc7946>.		<http://www.rfc-editor.org/info/rfc7946>.
	Appendix A. Contributors		6.2. Informative References
	TODO.		[I-D.wilde-json-seq-suffix]
			Wilde, E., "A Media Type Structured Syntax Suffix for JSON
			Text Sequences", December 2016.
	Author's Address		Author's Address
	S. Gillies		S. Gillies
	Mapbox		Mapbox
	Email: sean.gillies@gmail.com		Email: sean.gillies@gmail.com
	URI: http://sgillies.net		URI: http://sgillies.net
End of changes. 10 change blocks.
	15 lines changed or deleted		18 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/