(→Servers) |
(→Client Libraries (API Wrappers)) |
||
| Line 46: | Line 46: | ||
====Client Libraries (API Wrappers)==== | ====Client Libraries (API Wrappers)==== | ||
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 Ruby Gem] by Dan Melton et al |
| − | * https://github.com/mheadd/CSharpOpen311-v2 | + | * [https://github.com/mheadd/node-open311 Node.js] by Mark Headd |
| + | * [https://github.com/mheadd/CSharpOpen311-v2 C Sharp] by Mark Headd | ||
==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.
Note that the URLs require a method and jurisdiction_id at the end, the root URL is not intended to be accessed directly.
| Name | Status | API Key | Dev API | Production API |
|---|---|---|---|---|
| San Francisco | Development Ready | Request Key | Dev URL | Production URL |
| Washington D.C. | Development Ready | - | - | 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 |