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

Note: This ballot was opened for revision 04 and is now closed.

Alvaro Retana No Objection

(Alissa Cooper; former steering group member) Yes

(Alexey Melnikov; former steering group member) No Objection

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.

(Alia Atlas; former steering group member) No Objection

(Ben Campbell; former steering group member) No Objection

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

Please expand JSON and GeoJSON on first mention.

(Deborah Brungard; former steering group member) No Objection

(Jari Arkko; former steering group member) No Objection

(Joel Jaeggli; former steering group member) No Objection

(Kathleen Moriarty; former steering group member) No Objection

(Mirja Kühlewind; former steering group member) No Objection

(Spencer Dawkins; former steering group member) No Objection

(Stephen Farrell; former steering group member) No Objection

- 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;-)

(Suresh Krishnan; former steering group member) No Objection

(Terry Manderson; former steering group member) No Objection