Please add best practices for API terms of use to guidelines
- Dominant language
- No language data
- Stars
- 34
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
It would be helpful for the guidelines to communicate best practices about API terms of use.
Specifically, the following terms of use are expected to be used for APIs that provide output under the Open Government License - British Columbia: https://www2.gov.bc.ca/gov/content/data/open-data/api-terms-of-use-for-ogl-information
Guidance might fit in the API Encoding and Metadata section and could stand alone, or perhaps be a bullet of “Publish to the BC Data Catalogue?”
Some examples of APIs that reference these terms of use are:
- Open511-DriveBC
- BC Address Geocoder
- WorkBC Job Postings-
Related to this, it is also a general best practice for externally accessible APIs to output open data so that API users do not need to ask the Intellectual Property Office for permission to use the outputs in other works. API outputs not published under OGL-BC are "Access Only", as described in B.C. government standard copyright. e.g., the Geocoder outputs the coordinates of a civic address as well as other information - all released under OGL-BC.
Thanks
Contributor guide
Assessment
This issue has not been assessed yet.