You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've created a new page on the wiki at http://wiki.open311.org/GeoReport_v2/Extensions/ to document where the GeoReport v2 specification is being used in the wild with additional features, fields, parameters, or other customizations that extend the core v2 spec. This issue is simply being used to provide notes about documenting this before adding everything to the page on the wiki. It will also serve as an index to existing issues here on the issue tracker around specific extensions
I think the Extensions page should be organized similarly to the existing GeoReport_v2 page on the wiki around headings for the different GET/POST resources where they've been extended, plus headings for entirely new resources where they've been added. Under each of these headings there should be documentation for the feature in the same format as the main spec documentation and then a list of endpoints and/or providers that implement the extension.
In Helsinki, a service request may contain reference to a service object. Service object is typically an item like public toilet and it is referenced by unique service_object_id and service_object_type.
We've created a new page on the wiki at http://wiki.open311.org/GeoReport_v2/Extensions/ to document where the GeoReport v2 specification is being used in the wild with additional features, fields, parameters, or other customizations that extend the core v2 spec. This issue is simply being used to provide notes about documenting this before adding everything to the page on the wiki. It will also serve as an index to existing issues here on the issue tracker around specific extensions
I think the Extensions page should be organized similarly to the existing GeoReport_v2 page on the wiki around headings for the different GET/POST resources where they've been extended, plus headings for entirely new resources where they've been added. Under each of these headings there should be documentation for the feature in the same format as the main spec documentation and then a list of endpoints and/or providers that implement the extension.
There's already been some good discussion of many of these extension on the mailing list at http://lists.open311.org/groups/discuss/messages/topic/1dIPOwaKyRitCWJ6C6jIlW and here are a few to start off with:
Media Handling (see also #9)
Comments (see also #10)
Editing (see also #11)
Others:
non-standard
label provided by endpoints like the Connected Bits service in Chicago: http://dev.cityofchicago.org/docs/api/service_requestsThe text was updated successfully, but these errors were encountered: