tdwg apis issues - Githubissues

tdwg / apis

Application programming interfaces (services and clients) for biodiversity information

9 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

develop or adopt existing standards and processes for notifying api end or api redirect notification practices

#70 debpaul opened 3 months ago
0
Decide about terminology: GUID or PID

#69 nickynicolson opened 2 years ago
7
Consider if an offline tool might also be useful

#68 nickynicolson opened 2 years ago
0
Import "registry" functionalities as issues

#67 nickynicolson closed 2 years ago
0
Connect with/support TAG regarding GUIDs

#66 nickynicolson opened 2 years ago
2
Develop standardized trust metrics for certification

#65 nickynicolson opened 2 years ago
1
Support the developer community to build good APIs

#64 nickynicolson opened 2 years ago
1
Display coverage (which standards used in which services)

#63 nickynicolson opened 2 years ago
1
Criteria for "certification" of TDWG compliant services

#62 nickynicolson opened 2 years ago
2
As a provider of services, I want to tell the world that these are validly formed. A badge would be nice.

#61 nickynicolson opened 2 years ago
0
As a provider of services, I want to leverage these to seek new collaborations.

#60 nickynicolson opened 2 years ago
0
TRUST principles for TDWG compliant services

#59 nickynicolson opened 2 years ago
1
As a provider of services, I want assurances that they are being used and to receive feedback on how to improve them.

#58 nickynicolson opened 2 years ago
1
Advocate for APIs to funders

#57 nickynicolson opened 2 years ago
1
Develop an API design guide

#56 nickynicolson opened 2 years ago
1
Move towards an environment that allows to create and share free TDWG- compliant APIs as elements of workflows that solve common problems

#55 nickynicolson opened 2 years ago
0
Establish protocols for services integration thereby establishing continuity across the community

#54 nickynicolson opened 2 years ago
0
Standardize APIs

#53 nickynicolson opened 2 years ago
0
Reduce heterogeneity

#52 nickynicolson opened 2 years ago
0
advance and expand the role of technology in the biodiversity data and wider scientific community

#51 nickynicolson opened 2 years ago
0
A free Marketplace to look for biodiversity API's with examples and solutions

#50 nickynicolson opened 2 years ago
0
providers should commit to a standardized API description like OpenAPI

#49 nickynicolson opened 2 years ago
0
A common service to discover biodiversity data that answer a consistent schema

#48 nickynicolson opened 2 years ago
0
Agreed blueprint for designing APIs

#47 nickynicolson opened 2 years ago
0
Provide a reference implementation

#46 DavidFichtmueller opened 2 years ago
1
Be transparent about rate limiting/throttling

#45 DavidFichtmueller opened 2 years ago
0
Make it fast

#44 DavidFichtmueller opened 2 years ago
0
For GET queries, include the query in the response

#43 DavidFichtmueller opened 2 years ago
0
Use your API to build your website or product

#42 DavidFichtmueller opened 2 years ago
1
Advertise your API and add it to lists or registries

#41 DavidFichtmueller opened 2 years ago
1
Provide a way for developers to subscribe to updates, downtimes, sunsetting etc

#40 DavidFichtmueller opened 2 years ago
0
Explain how users can provide feedback, submit issue reports etc

#39 DavidFichtmueller opened 2 years ago
0
If you're building a service wrapping somebody else's curated dataset, then talk to them about your plans

#38 DavidFichtmueller opened 2 years ago
0
Make sure the service does not already exist

#37 DavidFichtmueller opened 2 years ago
0
Keep it running

#36 DavidFichtmueller opened 2 years ago
0
Introduce performance parameters

#35 DavidFichtmueller opened 2 years ago
0
Use a framework for service testing

#34 DavidFichtmueller opened 2 years ago
0
Explicitly define the resources the API is built upon

#33 DavidFichtmueller opened 2 years ago
0
Enforce strict validation rules for request parameters

#32 DavidFichtmueller opened 2 years ago
0
Don't alter standard HTTP headers unless necessary

#31 DavidFichtmueller opened 2 years ago
0
Use only key value pairs for query parameters

#30 DavidFichtmueller opened 2 years ago
1
Use a consistent request structure

#29 DavidFichtmueller opened 2 years ago
0
Simple is sustainable

#28 DavidFichtmueller opened 2 years ago
0
Don't repeat response bodies

#27 DavidFichtmueller opened 2 years ago
0
Include GUID in responses

#26 DavidFichtmueller opened 2 years ago
0
Provide human-friendly descriptions and a beginners guide, like GBIF

#25 DavidFichtmueller opened 2 years ago
0
Provide test examples / templates

#24 DavidFichtmueller opened 2 years ago
0
Secure routes as necessary

#23 DavidFichtmueller opened 2 years ago
0
Use OpenAPI 3.x to document

#22 DavidFichtmueller opened 2 years ago
0
Monitor your API for uptime

#21 DavidFichtmueller opened 2 years ago
0