Giters
opengeospatial
/
OGC-Web-API-Guidelines
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
28
Watchers:
23
Issues:
46
Forks:
7
opengeospatial/OGC-Web-API-Guidelines Issues
Pagination
Closed
3 years ago
Comments count
10
Example checklists
Updated
3 years ago
Comments count
1
Define Default behavior if parameters are not there.
Closed
3 years ago
Comments count
2
Replace felxible -> flexible
Closed
3 years ago
Comments count
1
Change reference to Web Feature Service 3.0 to something more modern
Closed
3 years ago
Resolve comments from Carl Reed
Closed
3 years ago
Comments count
3
Description of OGC Architectural Philosophy
Updated
3 years ago
Don’t Reinvent
Closed
3 years ago
Comments count
1
Great APIs are testable
Closed
3 years ago
Comments count
1
Ensure discover resources mechanism.
Closed
3 years ago
Comments count
2
common design principles in main-stream IT
Closed
3 years ago
Comments count
1
Addition of HTTP status code 302 to Option Set 2 in Principle #8 - HTTP Status Codes
Closed
3 years ago
Comments count
1
Bulk operations
Closed
3 years ago
Comments count
1
Are all principles equal ?
Closed
3 years ago
Comments count
1
Register geospatial relation types in the IANA register
Closed
3 years ago
Comments count
2
Reference to obsolete RFC 2616
Closed
3 years ago
Comments count
3
URIs and link references should be predictable
Closed
3 years ago
Comments count
2
Metadata - Guideline 13
Closed
3 years ago
Comments count
1
Reorganize Principles 7 and 8
Closed
3 years ago
Comments count
1
Rewrite Principle #17 (geospatial relations -> geospatial elements)
Closed
3 years ago
Comments count
1
Tiles are not always equally divided. Therefore, it is not always assigned to a simple matrix.
Closed
5 years ago
Comments count
3
Non-functional links in README
Closed
5 years ago
Comments count
2
"OGC Web API" is misleading
Closed
5 years ago
Comments count
3
Hard to identify what is meant to be normative or informative in the text
Closed
5 years ago
Comments count
1
Principle #17a - Use IANA well-known identifiers
Closed
5 years ago
Comments count
7
Consolidate the SecureDimensions branch in the master. Focus on WebAPI or in RESTful resources?
Closed
5 years ago
Comments count
4
Principle 17b - Use OGC services reserved URIs
Closed
5 years ago
Comments count
3
Principle 19 - Make use of geospatial relations
Closed
5 years ago
Comments count
4
Plurals to return collections in Principle #5 – Don’t mix Singular and Plural
Closed
5 years ago
Comments count
1
Principle 17 - Use Well-Known URL Templates and Access Paths
Closed
5 years ago
Comments count
3
Principle #3a - Use Well-Known Resource Classes
Closed
5 years ago
Comments count
8
Principle #15 – Miscellaneous
Closed
5 years ago
Comments count
1
Principle #14 – Security
Closed
5 years ago
Comments count
1
Principle #13 – Metadata
Closed
5 years ago
Comments count
6
Principle #12 – Not Accessing Resources
Closed
5 years ago
Comments count
3
Principle #11 – Partial Responses
Closed
5 years ago
Comments count
4
Principle #9 – Use of HTTP Header
Closed
5 years ago
Comments count
2
Principle #8 – HTTP Status Codes
Closed
5 years ago
Comments count
2
Principle #7 – Error Handling
Closed
5 years ago
Comments count
3
Principle #6 – Put Complexity behind the ‘?’
Closed
5 years ago
Comments count
2
Principle #5 – Don’t mix Singular and Plural
Closed
5 years ago
Comments count
5
Principle #4 – Use CRUD
Closed
5 years ago
Comments count
3
Principle #3b – Keep the Base URL Simple
Closed
5 years ago
Comments count
3
Principle #2 – Keep It Simple and Intuitive
Closed
5 years ago
Comments count
1
OGC Web API Design Principles
Closed
5 years ago
Comments count
3
Change requirements to recommendations
Closed
5 years ago
Comments count
1