(→GeoReport v2: added link to service discovery mechanism) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
=Open311 APIs= | =Open311 APIs= | ||
| Line 48: | Line 45: | ||
Client libraries make it easier to build client applications that work with the spec. | Client libraries make it easier to build client applications that work with the spec. | ||
* http://rubygems.org/gems/open311 | * http://rubygems.org/gems/open311 | ||
| + | * https://github.com/mheadd/CSharpOpen311-v2 | ||
==GeoReport v1== | ==GeoReport v1== | ||
Here is a proposal for doing specifying metadata about Open311 endpoints. It is expected that a version of this will be included in v2. Service Discovery
Servers receive and manage reports on behalf of a jurisdiction
| Name | Status | API Key | Dev API | Production API |
|---|---|---|---|---|
| San Francisco | Development Ready | Request Key | Dev URL | Production URL |
| Washington D.C. | Development Ready | Request Key | Dev URL | Production URL |
Server applications can receive and manage reports
Client applications can send and view reports
Test suites are used to verify that a server is compliant with the specification.
Client libraries make it easier to build client applications that work with the spec.
| Name | Status | API Key | Dev API | Production API |
|---|---|---|---|---|
| City of San Francisco | Production Ready | Request Key | Dev URL | Production URL |