<div dir="ltr">I like it. HAL was the model I was thinking of mimicking.<div><br></div><div><div>Thanks,</div><div>Chris</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 7, 2014 at 1:55 PM, Sean Gillies <span dir="ltr"><<a href="mailto:sean.gillies@gmail.com" target="_blank">sean.gillies@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Update: based on a look at HAL and JSON API, I've come up with a draft for fields to go into the IANA's registration form: <br>
<br><a href="https://github.com/geojson/draft-geojson/blob/master/media-type/registration.md" target="_blank">https://github.com/geojson/draft-geojson/blob/master/media-type/registration.md</a><br>
<a href="https://github.com/geojson/draft-geojson/issues/24" target="_blank">https://github.com/geojson/draft-geojson/issues/24</a><br></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">
On Wed, May 7, 2014 at 12:55 PM, Sean Gillies <span dir="ltr"><<a href="mailto:sean.gillies@gmail.com" target="_blank">sean.gillies@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hi Chris,<br><br></div>application/json+geojson would go against the grain of media types that are already out there:<br>
<br></div> application/vnd.github+json (GitHub)<br></div>
application/vnd.api+json (JSON API)<br></div> application/vnd.collection+json (<a href="http://amundsen.com/media-types/collection/" target="_blank">http://amundsen.com/media-types/collection/</a>)<br><br></div>We could register application/vnd.geo+json with IANA (following instructions at <a href="http://tools.ietf.org/html/rfc6838" target="_blank">http://tools.ietf.org/html/rfc6838</a>) which looks straightforward. We could add application/geo+json to the geojson I-D (<a href="http://datatracker.ietf.org/doc/draft-butler-geojson/" target="_blank">http://datatracker.ietf.org/doc/draft-butler-geojson/</a>) but then we're blocked until that makes it to RFC. I think I prefer the former. <br>
<br></div>Any advice on the above, Erik?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Wed, May 7, 2014 at 11:58 AM, Chris Metcalf <span dir="ltr"><<a href="mailto:chris.metcalf@socrata.com" target="_blank">chris.metcalf@socrata.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div>We're building out an API that outputs both our own JSON format as well as GeoJSON, and we allow clients to negotiate formats using the HTTP Accept header.</div>
<div><br></div><div>However, since most implementations seem to use application/json as the mimetype for GeoJSON, we would not properly be able to differentiate a client's desires using headers alone.</div>
<div><br></div><div>It looks like there has been some discussion around defining a mimetype or profile for GeoJSON. Has that gotten anywhere?</div><div><br></div><a href="http://lists.geojson.org/htdig.cgi/geojson-geojson.org/2013-June/000808.html" target="_blank">http://lists.geojson.org/htdig.cgi/geojson-geojson.org/2013-June/000808.html</a><br>
<div><a href="http://lists.geojson.org/htdig.cgi/geojson-geojson.org/2013-June/000809.html" target="_blank">http://lists.geojson.org/htdig.cgi/geojson-geojson.org/2013-June/000809.html</a><br></div><div><a href="http://lists.geojson.org/htdig.cgi/geojson-geojson.org/2012-October/000683.html" target="_blank">http://lists.geojson.org/htdig.cgi/geojson-geojson.org/2012-October/000683.html</a><br>
</div><div><br></div><div>We're currently planning on using "application/json+geojson" for GeoJSON output, but I'd prefer to go with whatever already has more adoption.</div><div><br></div><div><div><br>
</div><div>Thanks,</div><div><br></div><div>Chris Metcalf</div><div>Director of Platform</div><div>chris.metcalf (at) <a href="http://socrata.com" target="_blank">socrata.com</a></div></div></div>
<br></div></div><div>_______________________________________________<br>
GeoJSON mailing list<br>
<a href="mailto:GeoJSON@lists.geojson.org" target="_blank">GeoJSON@lists.geojson.org</a><br>
<a href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org" target="_blank">http://lists.geojson.org/listinfo.cgi/geojson-geojson.org</a><br>
<br></div></blockquote></div><span><font color="#888888"><br><br clear="all"><br>-- <br>Sean Gillies
</font></span></div>
</blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br>Sean Gillies
</font></span></div>
<br>_______________________________________________<br>
GeoJSON mailing list<br>
<a href="mailto:GeoJSON@lists.geojson.org">GeoJSON@lists.geojson.org</a><br>
<a href="http://lists.geojson.org/listinfo.cgi/geojson-geojson.org" target="_blank">http://lists.geojson.org/listinfo.cgi/geojson-geojson.org</a><br>
<br></blockquote></div><br></div>