What it has done is get councils, well, some of them, seriously
interested in helping to keep our database up-to-date. Pressure
from local newspaper reporters is the usual route to cooperation!
We make sure that we explain the pitfalls in the data to the
reporters, and they usually get the point but publish the results
anyway...
Would still like to have our first XML-RPC link to a council
database, but I think that's some years off still. This looks
interesting: http://wiki.open311.org/GeoReport_v2
I haven't really followed this thread, but as someone helping to
coordinate the Open311 GeoReport spec I thought I'd give you an update
that the version 2 of the spec is being finalized over the next month
and should have at least two or three interoperable deployments in major
US cities shortly following (late winter or early spring). Some
companies that do CRM implementations throughout the world have also
been involved including Lagan which provides CRMs in cities throughout
the UK and Australia: http://www.lagan.com/Open_311.aspx
There have already been a few conversations between Lagan and MySociety
about this, but the spec needed finalization before much could really
happen.
As far as identifying the correct jurisdiction boundary authority to
route issues, this is something we've thought about, but haven't ironed
out a full solution. We developed a quick proof of concept called
GeoWebDNS <http://demo.geowebdns.org/> and the FCC's recent inquiry
about revising the 911 system in the US to include more IP based
communications (called NG911) references a similar concept called LoST
<http://tools.ietf.org/html/rfc5222>. I think there will still need to
be a bit of manual intervention for routing, but if things are standards
based then that should be made much easier. Routing issues within a
jurisdiction based on the issue type should be pretty trivial since
issue types are meant to be clearly defined.
Phil
--
Philip Ashlock
Open Government Program Manager
OpenPlans.org <http://www.openplans.org> | @philipashlock
<http://twitter.com/philipashlock> | (360) 389-2741
_______________________________________________
developers-public mailing list
[email protected]
https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
Unsubscribe:
https://secure.mysociety.org/admin/lists/mailman/options/developers-public/archive%40mail-archive.com
