Re: [Geopriv] Forming and chartering a GeoJSON WG

Alissa Cooper <alissa@cooperw.in> Thu, 12 February 2015 21:36 UTC

Return-Path: <alissa@cooperw.in>
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 DEC391A702B for <geopriv@ietfa.amsl.com>; Thu, 12 Feb 2015 13:36:34 -0800 (PST)
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 LyieqdSCl8Iy for <geopriv@ietfa.amsl.com>; Thu, 12 Feb 2015 13:36:31 -0800 (PST)
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 E5FD81A1B65 for <geopriv@ietf.org>; Thu, 12 Feb 2015 13:36:28 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2395A20834 for <geopriv@ietf.org>; Thu, 12 Feb 2015 16:36:28 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 12 Feb 2015 16:36:28 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h= x-sasl-enc:content-type:mime-version:subject:from:in-reply-to :date:cc:message-id:references:to; s=mesmtp; bh=geDBAvt1uBxa4a5m m+mmeCdMik0=; b=UMKWyKHDtnpzsk7gUfXl49nhj+BJL3BVv2u6aKOgyuSb0gI0 dfs+B2e8eFyKrIjpytu6L1fsC5/BMUNN4SBxsEY4trPh72+asuWVCVPAaAeJfum8 MywCNpsTLxHFriKuKToKNlDKKAYwEjg9t6nulW9uBXnwWE0gaBpAQ3cpOdk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:content-type:mime-version :subject:from:in-reply-to:date:cc:message-id:references:to; s= smtpout; bh=geDBAvt1uBxa4a5mm+mmeCdMik0=; b=C/Hkl/Gw2OPTfohJQaCF FQr30KsCFLw4LHOiQ1vUu0sRoX2DofmHJPYhmz3V24Q0l7HhlQkMm0nPJ/p6X8Zj ERQ1gBqRPF6asq0VSiaumhpNquha6XTDdAsF6jPhLNq/KGJCS5Kd6Xpi6EtE+H38 A4TWYMWw+6vFYJhzdiI8ju8=
X-Sasl-enc: lFv2W+ZKJ/0q+8pE9ygHqDWbafeluemV6ZKnwJYGL9Ez 1423776987
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.239.233]) by mail.messagingengine.com (Postfix) with ESMTPA id 651BCC00295; Thu, 12 Feb 2015 16:36:27 -0500 (EST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5A9BA0FD-14E6-4BE7-9700-E62EDC0DD86E"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <54DCBBF9.8010705@gmail.com>
Date: Thu, 12 Feb 2015 13:36:26 -0800
Message-Id: <7036DD56-A189-48AB-AF5D-0D00DFA69C14@cooperw.in>
References: <54D3AF68.4070803@berkeley.edu> <625863E8-3AE1-4ABB-879E-946C958DC1C7@cooperw.in> <54DCBBF9.8010705@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/geopriv/xCzjSugi6PN32hctxzaYwpgO2aM>
Cc: geopriv@ietf.org
Subject: Re: [Geopriv] Forming and chartering a GeoJSON WG
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv/>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 21:36:35 -0000

Please send your comments to dispatch@ietf.org.

On Feb 12, 2015, at 6:43 AM, Alexandru Petrescu <alexandru.petrescu@gmail.com>; wrote:

> The abstract of this draft-butler-geojson-05 says:
>> This document recommends a single coordinate reference system based
>>   on WGS 84.  Other coordinate reference systems are not recommended.
> 
> I think the draft should be revised in this sense.
> 
> JSON/IP will reach a number of reference systems in wide use, non-WGS-84, which deserve direct use instead of through conversion.
> 
> Alex
> 
> 
> Le 10/02/2015 22:45, Alissa Cooper a écrit :
>> Folks who may have thoughts about this should send them on the dispatch
>> list ...
>> 
>> Begin forwarded message:
>> 
>>> *From: *Erik Wilde <dret@berkeley.edu <mailto:dret@berkeley.edu>>
>>> *Subject: **Re: Forming and chartering a GeoJSON WG*
>>> *Date: *February 5, 2015 at 9:59:04 AM PST
>>> *To: *dispatch@ietf.org <mailto:dispatch@ietf.org>
>>> *Cc: *Richard Barnes <rlb@ipv.sx <mailto:rlb@ipv.sx>>, Sean Gillies
>>> <sean.gillies@gmail.com <mailto:sean.gillies@gmail.com>>, Alissa
>>> Cooper <alissa@cooperw.in <mailto:alissa@cooperw.in>>, Barry Leiba
>>> <barryleiba@computer.org <mailto:barryleiba@computer.org>>, Pete
>>> Resnick <presnick@qti.qualcomm.com
>>> <mailto:presnick@qti.qualcomm.com>>, metazool@fastmail.net
>>> <mailto:metazool@fastmail.net>
>>> 
>>> hello.
>>> 
>>> On 2015-02-03 16:40 , Richard Barnes wrote:
>>>> Sorry for the delay here.  It looks like the next step here is to send a
>>>> charter proposal to the DISPATCH mailing list, dispatch@ietf.org
>>>> <mailto:dispatch@ietf.org>
>>> 
>>> we have had conversations about establishing an IETF WG for GeoJSON,
>>> which would be chartered with taking the current GeoJSON definition,
>>> and turning it into an IETF RFC. the next step in this process seems
>>> to be proposing a charter. please find the proposed charter in this
>>> email to dispatch@ietf.org <mailto:dispatch@ietf.org>, and it also is
>>> available online here:
>>> 
>>> https://github.com/geojson/draft-geojson/blob/master/charter.md
>>> 
>>> ==============================================================
>>> 
>>> Proposed GeoJSON WG Charter
>>> 
>>> GeoJSON
>>> 
>>> GeoJSON is a geospatial data interchange format based on JavaScript
>>> Object Notation (JSON). It was published at http://geojson.org in
>>> 2008. It has succeeded in streamlining geographic information system
>>> standards and making them accessible to practitioners of modern web
>>> development. GeoJSON today plays an important role in many spatial
>>> databases, web APIs, and open data platforms.
>>> 
>>> This WG will work on a GeoJSON Format RFC that specifies the format
>>> more precisely and serves as a better guide for implementers. The work
>>> will start from an Internet-Draft written by the original authors.
>>> This I-D, draft-butler-geojson-04, substantially improves the format
>>> specification. The remaining tasks of the WG are:
>>> 
>>> * Further clarification of the GeoJSON format specification.
>>> * Addition of implementation advice based on lessons learned since 2008.
>>> * geoAddition of more explicit extension advice to the specification.
>>> 
>>> The addition of new features to the GeoJSON format is not within the
>>> scope of this WG. One possible exception to this (depending on WG
>>> consensus) is the adoption of JSON Text Sequences as an alternative
>>> way of serializing sets of GeoJSON objects.
>>> 
>>> ==============================================================
>>> 
>>> thanks a lot and kind regards,
>>> 
>>> dret.
>>> 
>>> --
>>> erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
>>>          | UC Berkeley  -  School of Information (ISchool) |
>>>          | http://dret.net/netdret http://twitter.com/dret |
>> 
>> 
>> 
>> _______________________________________________
>> Geopriv mailing list
>> Geopriv@ietf.org
>> https://www.ietf.org/mailman/listinfo/geopriv
>> 
> 
> 
> _______________________________________________
> Geopriv mailing list
> Geopriv@ietf.org
> https://www.ietf.org/mailman/listinfo/geopriv