<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about geosjon)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/geosjon.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:22 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>IETF GeoJSON</title><link>https://sgillies.net/2015/12/05/ietf-geojson.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Having busted up my technical/administrative blogjam, I'm going to try to catch
up on the news from my little corner of the world. The new IETF GeoJSON
working group that I've been incubating finally hatched on October 1. The
chairs are Martin Thomson and Erik Wilde and I'm playing the role of lead
editor. All but one of the original format spec authors are participating in
the working group along others from the original email list and a bunch of
IETF folks. We're going to ship two documents: a GeoJSON format specification
(with clarifications and extension guidance) and a document describing a format
for a streamable sequence of GeoJSON texts (as I've sketched out in this blog
&lt;a class="reference external" href="https://sgillies.net/2014/10/05/unix-style-spatial-etl-with-fio-cat-collect-and-load.html"&gt;previously&lt;/a&gt;).&lt;/p&gt;
&lt;p&gt;The IETF GeoJSON WG will operate out of the existing
&lt;a class="reference external" href="https://github.com/geojson/draft-geojson"&gt;https://github.com/geojson/draft-geojson&lt;/a&gt; repo and use an IETF GeoJSON mailing
list &lt;a class="reference external" href="https://www.ietf.org/mailman/listinfo/geojson"&gt;https://www.ietf.org/mailman/listinfo/geojson&lt;/a&gt; for discussion and
announcements. See
&lt;a class="reference external" href="https://github.com/geojson/draft-geojson/blob/master/CONTRIBUTING.md"&gt;https://github.com/geojson/draft-geojson/blob/master/CONTRIBUTING.md&lt;/a&gt; for all
the details about contributing. The WG's draft is &lt;a class="reference external" href="https://datatracker.ietf.org/doc/draft-ietf-geojson/"&gt;https://datatracker.ietf.org/doc/draft-ietf-geojson/&lt;/a&gt; and replaces the old &lt;a class="reference external" href="https://datatracker.ietf.org/doc/draft-butler-geojson/"&gt;https://datatracker.ietf.org/doc/draft-butler-geojson/&lt;/a&gt; draft that we've been iterating on for a year or so. This is to say
that the IETF GeoJSON WG has adopted the draft of the independent GeoJSON
working group and that the independent GeoJSON working group has become the
IETF GeoJSON WG.&lt;/p&gt;
&lt;p&gt;To get to the next revision of draft-ietf-geojson, I'm going through the
outstanding issues in the tracker, summarizing them to the discussion list,
and trying to reach consensus on whether to add text to the spec, remove
text from the spec, or leave it alone. Some of these are more contentious than
others, such as if and how GeoJSON should be extended. So far we have
consensus that there is extensibility, but no consensus that there is a
capital E Extension Framework.&lt;/p&gt;
&lt;p&gt;If you've ever felt that the GeoJSON specification wasn't clear enough on
something or is out of step with recent technological advances, this is the
time to jump in and help improve it.&lt;/p&gt;</description><category>geosjon</category><category>ietf</category><category>work</category><guid>https://sgillies.net/2015/12/05/ietf-geojson.html</guid><pubDate>Sat, 05 Dec 2015 07:00:00 GMT</pubDate></item></channel></rss>