(sorry this is a crosspost also here for the CitySDK folks:
http://dev.hel.fi/node/218 ,but I guess it also needs to be discussed in a wide
range)
Hi,
as I mentioned earlier, we are planning to implement the open311 Georeport v2 /
CitySDK issue reporting API to our participation Project www.klarschiff-hro.de
(aka 'clean ship rostock'). But now we struggle: Our properietary HTTP API
supports esp. various aspects, that we currently don't see in CitySDK nor in
Open311:
- internal notes - submit issues and add non-public information (e.g. plate)
- comments - let users comment to (3rd party) issues
- voting - let users vote/support ideas or problems
- abuse - let user report vandalism on your platform
- staff edits - let logged on users edit issues, add notes, ...
I think each of the aspect is quiet modular and might make sense also for all
other instances. But I'm not sure how we might develop and add such support to
the official standard. For example is there a formal way (proposal, RFC, draft,
final, ..) on how to add extensions to open311? And how to add support for the
addons, without breaking existing solutions? Maybe it's just a something
similar like the CitySDK Helsinki extensions at the beginning? So just switch
from a boolean to enumeration:
https://asiointi.hel.fi/palautews/rest/v1/services.json?extensions=voting...,...
regards,
Matthias
http://dev.hel.fi/node/218 ,but I guess it also needs to be discussed in a wide
range)
Hi,
as I mentioned earlier, we are planning to implement the open311 Georeport v2 /
CitySDK issue reporting API to our participation Project www.klarschiff-hro.de
(aka 'clean ship rostock'). But now we struggle: Our properietary HTTP API
supports esp. various aspects, that we currently don't see in CitySDK nor in
Open311:
- internal notes - submit issues and add non-public information (e.g. plate)
- comments - let users comment to (3rd party) issues
- voting - let users vote/support ideas or problems
- abuse - let user report vandalism on your platform
- staff edits - let logged on users edit issues, add notes, ...
I think each of the aspect is quiet modular and might make sense also for all
other instances. But I'm not sure how we might develop and add such support to
the official standard. For example is there a formal way (proposal, RFC, draft,
final, ..) on how to add extensions to open311? And how to add support for the
addons, without breaking existing solutions? Maybe it's just a something
similar like the CitySDK Helsinki extensions at the beginning? So just switch
from a boolean to enumeration:
https://asiointi.hel.fi/palautews/rest/v1/services.json?extensions=voting...,...
regards,
Matthias