Add documentation about our support for /data.json and Project Open Data

[chrismetcalf]

[chrismetcalf]

I should be tackling this today.

[philipashlock]

It looks like there's some coverage of this at http://www.socrata.com/open-data-mandate/ but you could also have something separate that explains this is also applicable for non-federal publishers. /cc @ianjkalin

[ianjkalin]

@chrismetcalf We also just pushed our data.json fixes to production. So there is brand new functionality that non-Federal publishers can take advantage of for @ProjectOpenData integration.

[chrismetcalf]

Whoops, mis-tagged a commit. Reopening.

[haileypate]

+1 -- As someone who recently became a Socrata admin for the first time in a new city, it's been frustrating to not be able to find API documentation all in one place. When playing with the API, I found calls that returned interesting data (ie dcat.json, data.json) but I found nothing at dev.socrata.com to explain where the results came from and why they returned different record counts.

I could try and guess what's happening by profiling these response objects and pattern-seeking, but I don't have enough time. Overall, the portal product seems to be heading in a good direction, but I feel the lack of comprehensive API documentation (api/search, api/users, api/views, etc) is one of Socrata's biggest opportunities.