Make a public plan on future of occ api re: JSON keys, query parameters, versioning

14023
Reporter: feedback bot
Type: Task
Summary: Make a public plan on future of occ api re: JSON keys, query parameters, versioning
Priority: Major
Resolution: WontFix
Status: Closed
Created: 2013-09-22 03:16:55.841
Updated: 2014-06-24 10:58:01.592
Resolved: 2014-06-24 10:58:01.561
        
        
Description: Am contemplating using the GBIF API but am reluctant to do so at the moment because I am not certain of the stability of the response signature. In particular, why are the JSON keys and query parameters not using Darwin Core terms when these clearly should be. Including a version in the API path would boost my confidence because I'd see that you will probably have a newer version at some point with an expected period of grace for users who have designed applications using your a then older version of your API.

*Reporter*: David Shorthouse
*E-mail*: [mailto:david.shorthouse@umontreal.ca]]]>