Shepherd writeup
rfc7946-04

As required by RFC 4858, this is the current template for the Document 
Shepherd Write-Up.

Changes are expected over time. This version is dated 24 February 2012.

(1) What type of RFC is being requested?

Proposed Standard.  This document specifies a protocol format.

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

   GeoJSON is a geospatial data interchange format based on JavaScript
   Object Notation (JSON).

Working Group Summary

  The working group had good discussion around the changes made
  to this version over the version that was widely deployed.  There was 
  good consensus for the changes made (these are summarized in
  Appendix B).

Document Quality

  GeoJSON is widely implemented and used already.  The changes made
  by the working group are largely formal in nature, though this includes
  a new media type (the "vnd." prefix has been dropped).  The media
  type change has been proposed and reviewed, see
  https://mailarchive.ietf.org/arch/msg/media-types/hUlxdmrz6nid3er1XXK86cgxIkA

  Considerable debate was had over the inclusion of the "crs" member.
  The working group has consensus around the text in -03.

Personnel

  Martin Thomson is the document shepherd.
  Alissa Cooper is the responsible AD.

--
  A technical and editorial review has been performed by the
  shepherd and media type (see
  https://mailarchive.ietf.org/arch/msg/media-types/hUlxdmrz6nid3er1XXK86cgxIkA)
  
  The working group has strong consensus to publish the document.
  Several of the changes made during the process were a little
  contentious, but there was consensus on the outcome of each issue.

  idnits shows only bogus warnings.
  References are correctly allocated to sections.
  A single media type is requested of IANA; this has been reviewed.
  There are no IPR disclosures and authors have acknowledged this.
  The examples in the document are valid JSON according to jsonlint.com
Back