Re: FW: WG Review: Geographic JSON (geojson)

Very much so ! Thanks Lars

ed


On Tue, 15 Sep 2015 at 09:01 Svensson, Lars <L.Svensson@dnb.de> wrote:

> Most likely of interest to this group.
>
> Best,
>
> Lars
>
> *** Lesen. Hören. Wissen. Deutsche Nationalbibliothek ***
> --
> Dr. Lars G. Svensson
> Deutsche Nationalbibliothek
> Informationsinfrastruktur und Bestanderhaltung
> Adickesallee 1
> D-60322 Frankfurt am Main
> Telefon: +49-69-1525-1752
> Telefax: +49-69-1525-1799
> mailto:l.svensson@dnb.de
> http://www.dnb.de
>
> > -----Original Message-----
> > From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of
> > The IESG
> > Sent: Monday, September 14, 2015 6:47 PM
> > To: IETF-Announce
> > Subject: WG Review: Geographic JSON (geojson)
> >
> > A new IETF working group has been proposed in the Applications and
> > Real-Time Area. The IESG has not made any determination yet. The
> > following draft charter was submitted, and is provided for informational
> > purposes only. Please send your comments to the IESG mailing list (iesg
> > at ietf.org) by 2015-09-24.
> >
> > Geographic JSON (geojson)
> > ------------------------------------------------
> > Current Status: Proposed WG
> >
> > Assigned Area Director:
> >   Alissa Cooper <alissa@cooperw.in>
> >
> >
> > Charter:
> >
> > GeoJSON is a format for encoding data about geographic features using
> > JavaScript Object Notation (JSON) [RFC7159]. Geographic features need not
> > be physical things; any thing with properties that are bounded in space
> > may be considered a feature. GeoJSON provides a means of representing
> > both the properties and spatial extent of features.
> >
> > The GeoJSON format specification was published at http://geojson.org in
> > 2008. GeoJSON today plays an important and growing role in many spatial
> > databases, web APIs, and open data platforms. Consequently the
> > implementers increasingly demand formal standardization, improvements in
> > the specification, guidance on extensibility, and the means to utilize
> > larger GeoJSON datasets.
> >
> > This WG will work on a GeoJSON Format RFC that specifies the format more
> > precisely, serves as a better guide for implementers, and improves
> > extensibility of the format. The work will start from an Internet-Draft
> > written by the original GeoJSON authors: draft-butler-geojson [1].
> >
> > This WG will work on GeoJSON mappings of 'geo' URIs, reinforcing the use
> > of RFC 5870.
> >
> > This WG will work on a format for a streamable sequence of GeoJSON texts
> > based on RFC 7464 to address the difficulties in serializing very large
> > sequences of features or feature sequences of indeterminate length.
> >
> > GeoJSON objects represent geographic features only and do not specify
> > associations between geographic features and particular devices, users,
> > or facilities. Any association with a particular device, user, or
> > facility requires another protocol. When a GeoJSON object is used in a
> > context where it identifies the location of a device, user, or facility,
> > it becomes subject to the architectural, security, and privacy
> > considerations in RFC 6280. The application of those considerations is
> > specific to protocols that make use of GeoJSON objects and is out of
> > scope for the GeoJSON WG. Although the WG is chartered to improve the
> > extensibility of the format, extensions that would allow GeoJSON objects
> > to specify associations between geographic features and particular
> > devices, users, or facilities are not expected to be defined in the WG.
> > Should that be needed, re-chartering will be required.
> >
> > Deliverables:
> >
> > * A GeoJSON format specification document including mappings of 'geo'
> > URIs
> > * A document describing a format for a streamable sequence of GeoJSON
> > texts
> >
> > [1] https://tools.ietf.org/html/draft-butler-geojson
> >
> > Milestones:
> >
> > TBD
>
>
> --

*Ed Parsons*
Geospatial Technologist, Google

Google Voice +44 (0)20 7881 4501
www.edparsons.com @edparsons

Received on Tuesday, 15 September 2015 09:26:44 UTC