Views
Difference between revisions of "San Francisco"
Collaboration for an Open311 Standard
(→General Description) |
|||
| Line 5: | Line 5: | ||
311 twitter integration, exciting about participating in Open311 api, been considering for a while. Agrees with not just looking at request, but also disseminating information. Happy to focus just on requests for now, but then getting to how to answer questsion. Draft api is modeled after DC api. Fast tracking this, next few months . Using Lagan system, the vision is to route that to departments that do the work. Have a middleware system, using Oracle, thinking of changing that model, so 311 is a central hub, so other depts poll system. rather than pushing data out, just wnt to make sure that information will flow out. Very optimistic | 311 twitter integration, exciting about participating in Open311 api, been considering for a while. Agrees with not just looking at request, but also disseminating information. Happy to focus just on requests for now, but then getting to how to answer questsion. Draft api is modeled after DC api. Fast tracking this, next few months . Using Lagan system, the vision is to route that to departments that do the work. Have a middleware system, using Oracle, thinking of changing that model, so 311 is a central hub, so other depts poll system. rather than pushing data out, just wnt to make sure that information will flow out. Very optimistic | ||
| − | [http://apps.sfgov.org/Open311API/ Information | + | [http://apps.sfgov.org/Open311API/ Information on San Francisco's Open311 implementation] |
| + | |||
| + | |||
| + | === Interested in our Open311 Efforts=== | ||
| + | |||
| + | We’d like to invite anyone interested in moving the Open311 API forward to this public meeting. So we have an idea of your areas of interest and some background we ask that you fill out a [http://apps.sfgov.org/Open311API/?page_id=448 simple form]. | ||
| + | |||
| + | Here are the details: | ||
| + | When: Dec 3rd, 5:30PM PST | ||
| + | Where: 641.715.3625 Pin: 813951# | ||
| + | |||
| + | Agenda: | ||
| + | 1. Present to the public our [http://apps.sfgov.org/Open311API/?page_id=382 draft design spec] | ||
| + | 2. Identify gaps in design | ||
| + | 3. Brainstorm | ||
Revision as of 14:57, 3 December 2009
This page is a stub. If you have more content to add, please edit this page.
This was taken from the Notes from Cities portion of the Open311 DevCamp Etherpad
General Description
311 twitter integration, exciting about participating in Open311 api, been considering for a while. Agrees with not just looking at request, but also disseminating information. Happy to focus just on requests for now, but then getting to how to answer questsion. Draft api is modeled after DC api. Fast tracking this, next few months . Using Lagan system, the vision is to route that to departments that do the work. Have a middleware system, using Oracle, thinking of changing that model, so 311 is a central hub, so other depts poll system. rather than pushing data out, just wnt to make sure that information will flow out. Very optimistic
Information on San Francisco's Open311 implementation
Interested in our Open311 Efforts
We’d like to invite anyone interested in moving the Open311 API forward to this public meeting. So we have an idea of your areas of interest and some background we ask that you fill out a simple form.
Here are the details: When: Dec 3rd, 5:30PM PST Where: 641.715.3625 Pin: 813951#
Agenda: 1. Present to the public our draft design spec 2. Identify gaps in design 3. Brainstorm
