Feedback sent via API Guidelines from Yammer (GIS CoP):
William Burt (FLNRORD, Regional Geomatics Specialist, Kootenay Boundary Region)
–
This guidance looks great. Likely I won't be developing an api anytime soon but perhaps I would be a consumer. Many of bcgov api are purpose built for and limited to one application. To animate the new data story line that is being presented access needs to be open to other consumers with un-forcasted use cases.
Here are some questions I expect this COP would have:- Are our APIs catalogued and documented like data? If I need documentation, an api key or authentication where would someone go?
Feedback sent via API Guidelines from Yammer (GIS CoP): William Burt (FLNRORD, Regional Geomatics Specialist, Kootenay Boundary Region) – This guidance looks great. Likely I won't be developing an api anytime soon but perhaps I would be a consumer. Many of bcgov api are purpose built for and limited to one application. To animate the new data story line that is being presented access needs to be open to other consumers with un-forcasted use cases. Here are some questions I expect this COP would have:- Are our APIs catalogued and documented like data? If I need documentation, an api key or authentication where would someone go?