<div dir="ltr">I prefer post-fix the content type since geoJSON is a subset of JSON<div><br></div><div> application/json+geo</div><div><br></div><div>For one, this makes it clear that it is `application/json` plus another thing '+geo'. Additionally this would permit multiple suffix (e.g. 'application/json+geo+ld'. Last, practically code can evaluate 'contenttype =~ /application\/json/ and it would account for subsets.</div>
<div><br></div><div>Andrew</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Nov 3, 2013 at 9:07 PM, Erik Wilde <span dir="ltr"><<a href="mailto:dret@berkeley.edu" target="_blank">dret@berkeley.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hello billy.<div class="im"><br>
<br>
On 2013-11-03, 17:03 , Billy Newman wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
To be 100% honest I am not sure why application/geojson+json would break<br>
compatibility. If you are serving GeoJSON and using application/json<br>
and change to server application/geojson+json you are still returning<br>
the same thing, in this case GeoJSON. Isn't application/geojson+json a<br>
sub-set of application/json?<br>
</blockquote>
<br></div>
logically it is and the structured suffix makes it look a little bit as if it were, but strictly speaking, media types have not hierarchy other than the type/subtype structure, so application/json and application/geojson+json are completely different things. whether over time the structured suffixes will create a defacto structure of registered media types that might eventually be codified is hard to tell, but as it stands now, when you ask for application/geojson+json, an old server would just say "no, i only have application/json", and there would be no matching process to connect those two in any way.<br>
<br>
thinking of it, maybe something like <a href="http://tools.ietf.org/html/rfc4647" target="_blank">http://tools.ietf.org/html/<u></u>rfc4647</a> should exist for media types as well, and then could take structured suffixes into account. but the problem also is that different communities have different practices around how they use media types. in RDF, for example, media types play a minimal role, just distinguishing between various serializations of the same generic metamodel, whereas other communities have adopted different practices, making media types more meaningful, semantically speaking. it might actually be pretty hard to unify all of those practices. which is not to say that it might not be a valuable exercise as an I-D, so that it's captured in one place. but it might turn to be an exercise where the end result is that there is no single simple unified model that could be used across all domains, so what remains would be the simple matching process as defined by HTTP.<br>
<br>
<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-22#section-5.3.2" target="_blank">http://tools.ietf.org/html/<u></u>draft-ietf-httpbis-p2-<u></u>semantics-22#section-5.3.2</a><div class="im HOEnZb"><br>
<br>
cheers,<br>
<br>
dret.<br>
<br>
-- <br>
erik wilde | mailto:<a href="mailto:dret@berkeley.edu" target="_blank">dret@berkeley.edu</a> - tel:<a href="tel:%2B1-510-2061079" value="+15102061079" target="_blank">+1-510-2061079</a> |<br>
| UC Berkeley - School of Information (ISchool) |<br>
| <a href="http://dret.net/netdret" target="_blank">http://dret.net/netdret</a> <a href="http://twitter.com/dret" target="_blank">http://twitter.com/dret</a> |<br></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<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/<u></u>listinfo.cgi/geojson-geojson.<u></u>org</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Andrew Turner<br>t: @ajturner<br>b: <a href="http://highearthorbit.com" target="_blank">http://highearthorbit.com</a><br>m: 248.982.3609<br>
</div>