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

[Ballot comment]
In Section 5 all references must include RFC number and don't just say "above". The whole section will be cut & pasted to IANA website, so it must be self contained.

[Ballot comment]
The last paragraph in section 1 seems out of place. Maybe it belongs i section 4?

Please expand JSON and GeoJSON on first mention.

[Ballot comment]
- section 1, last para: this seems to be out of
context, the para would be better in section 2.

- section 2, I think you need a normative
reference for ASCII (RFC20) or you should say
what hex values map to RS (0x1e) and LF (0x0a)
to help folks. (Providing the hex values would
allow you to make an ASCII ref informative if
you cared about that I guess;-)

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has completed its review of draft-ietf-geojson-text-sequence-03.txt. If any part of this review is inaccurate, please let us know.

The IANA Services Operator understands that, upon approval of this document, there is a single action which we must complete.

In the application namespace of the Media Types registry located at:

https://www.iana.org/assignments/media-types/

a single, new Media Type is to be registered as follows:

Name: geo+json-seq
Template: [ TBD-at-Registration ]
Reference: [ RFC-to-be ]

The IANA Services Operator understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: geojson-chairs@ietf.org, geojson@ietf.org, martin.thomson@gmail.com, alissa@cooperw.in, draft-ietf-geojson-text-sequence@ietf.org, "Martin Thomson"
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (GeoJSON Text Sequences) to Proposed Standard


The IESG has received a request from the Geographic JSON WG (geojson) to
consider the following document:
- 'GeoJSON Text Sequences'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2017-01-24. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  A proposed standard for geographic data that can be parsed and
  produced incrementally.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-geojson-text-sequence/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-geojson-text-sequence/ballot/


No IPR declarations have been submitted directly on this I-D.

Technical Summary

This proposed standard simply glues together the recently published geojson [RFC7946] and JSON text sequences [RFC7464].

Working Group Summary

  The document shepherd believes this to be ready.  It has good consensus; good discussion, little contention.

Document Quality

  Several reviews of the document were provided.  A media type review has been conducted.  I have checked references.

  Implementations:
https://github.com/mapbox/rasterio
https://github.com/Toblerity/Fiona
geojsonio
Turf
https://github.com/mapbox/cligj
 
Personnel

  Document Shepherd: Martin Thomson
  Responsible Area Director: Alissa Cooper <@usual address>

Each has author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed.