From nobody Fri Oct 2 10:50:02 2015 Return-Path: X-Original-To: geopriv@ietfa.amsl.com Delivered-To: geopriv@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0555A1B3009 for ; Fri, 2 Oct 2015 10:50:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e1NYElAt4I5l for ; Fri, 2 Oct 2015 10:49:58 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEAE31B2E0E for ; Fri, 2 Oct 2015 10:49:57 -0700 (PDT) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id DFF842056C for ; Fri, 2 Oct 2015 13:49:56 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 02 Oct 2015 13:49:56 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= content-type:date:from:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=5rWwgjMmQkn3SaXq iZGFPkFLHmY=; b=hTBjC/1GjxYWpbejwRT0CiJSU7NJaO56T4bruToFaTrUvsbl FLKJzZYayGMin1UCacNUvUZqlyZjrCi+Mggf1NdqBcjVINv/eQJXjAmrsCg4ETge yiFKP9Zr5WdHGOC1G0wJGpWCL9hVCtW8YGgBqhg0cEzCrKMEas0FI3RoDcQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:references:subject:to:x-sasl-enc:x-sasl-enc; s= smtpout; bh=5rWwgjMmQkn3SaXqiZGFPkFLHmY=; b=DezA7b3J8+6hxk90jrAa GTOJ1lrwb7TBxGjCkMM+Rnc1Mp/2ISwBhfV5C4KvAKGTQr5vQtVXgVPm1A+Vddof 67kWyYoXSqqtlIF2SQPeNwl/sZIZo+jtz0L6LizfMnXwIhFZ68hurAjrZaFbj2Um pZIeFABWKTmhCtkTX9iIFzI= X-Sasl-enc: MQA/KoWXwUJj0gT2kdrSilE/84ix48u4kqnPygNtXPYG 1443808196 Received: from dhcp-171-68-20-103.cisco.com (dhcp-171-68-20-103.cisco.com [171.68.20.103]) by mail.messagingengine.com (Postfix) with ESMTPA id 54E7EC00023; Fri, 2 Oct 2015 13:49:56 -0400 (EDT) From: Alissa Cooper Content-Type: multipart/alternative; boundary="Apple-Mail=_F5E9DCEC-5B4E-4D9A-A859-325EB766CADD" Date: Fri, 2 Oct 2015 10:49:55 -0700 References: <20151002163548.13742.44075.idtracker@ietfa.amsl.com> To: dispatch@ietf.org, geopriv mailing list Message-Id: <1B66F091-6880-4832-B63D-F47FFB6F9B0C@cooperw.in> Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) Archived-At: Subject: [Geopriv] Fwd: WG Action: Formed Geographic JSON (geojson) X-BeenThere: geopriv@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Geographic Location/Privacy List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2015 17:50:00 -0000 --Apple-Mail=_F5E9DCEC-5B4E-4D9A-A859-325EB766CADD Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii FYI > Begin forwarded message: > > From: The IESG > Subject: WG Action: Formed Geographic JSON (geojson) > Date: October 2, 2015 at 9:35:48 AM PDT > To: "IETF-Announce" > Cc: geojson WG > Reply-To: ietf@ietf.org > > A new IETF working group has been formed in the Applications and > Real-Time Area. For additional information please contact the Area > Directors or the WG Chairs. > > Geographic JSON (geojson) > ------------------------------------------------ > Current Status: Proposed WG > > Chairs: > Erik Wilde > Martin Thomson > > Assigned Area Director: > Alissa Cooper > > Mailing list > Address: geojson@ietf.org > To Subscribe: https://www.ietf.org/mailman/listinfo/geojson > Archive: https://mailarchive.ietf.org/arch/search/?email_list=geojson > > 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 (JSON Text Sequences) 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, An Architecture for Location and Location > Privacy in Internet Applications. 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: > > --Apple-Mail=_F5E9DCEC-5B4E-4D9A-A859-325EB766CADD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii FYI

Begin forwarded message:

From: = The IESG <iesg-secretary@ietf.org>
Subject: = WG Action: Formed = Geographic JSON (geojson)
Date: = October 2, 2015 at 9:35:48 AM = PDT
To: = "IETF-Announce" <ietf-announce@ietf.org>
Cc: geojson WG <geojson@ietf.org>
Reply-To: = ietf@ietf.org

A new IETF working group has been formed in = the Applications and
Real-Time Area. For additional = information please contact the Area
Directors or the WG = Chairs.

Geographic JSON (geojson)
------------------------------------------------
Current Status: Proposed WG

Chairs:
 Erik Wilde <dret@berkeley.edu>
 Martin Thomson <martin.thomson@gmail.com>

Assigned Area Director:
 Alissa Cooper = <alissa@cooperw.in>

Mailing = list
 Address: geojson@ietf.org
 To Subscribe: https://www.ietf.org/mailman/listinfo/geojson
 Archive: https://mailarchive.ietf.org/arch/search/?email_list=3Dgeojson<= /a>

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 = (JSON Text Sequences) 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, An Architecture for = Location and Location
Privacy in Internet Applications. = 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:



= --Apple-Mail=_F5E9DCEC-5B4E-4D9A-A859-325EB766CADD--