In order for applications to work seamlessly across multiple jurisdictions that support Open311, the applications need to be able to discovery the API endpoint for the jurisdiction serving that location.
Rather than discovering individual Open311 API endpoints directly, applications would probably first be directed to the Service Discovery for the jurisdiction and then be routed to the specific Open311 endpoint from there.
There was a basic proposal for this called GeoWebDNS and there is also work on a specification called LoST that is designed for a broad range of use cases including Next Generation 911 Services (NG911). Information on these can be found at http://wiki.open311.org/GeoWeb_DNS
In order for applications to work seamlessly across multiple jurisdictions that support Open311, the applications need to be able to discovery the API endpoint for the jurisdiction serving that location.
Rather than discovering individual Open311 API endpoints directly, applications would probably first be directed to the Service Discovery for the jurisdiction and then be routed to the specific Open311 endpoint from there.
There was a basic proposal for this called GeoWebDNS and there is also work on a specification called LoST that is designed for a broad range of use cases including Next Generation 911 Services (NG911). Information on these can be found at http://wiki.open311.org/GeoWeb_DNS