Open311

Wiki

Collaboration for an Open311 Standard
Personal tools

Difference between revisions of "Roadmap"

Collaboration for an Open311 Standard

Jump to: navigation, search
(Created page with '* Negotiate or mitigate inconsistencies with metadata (Service Request types) ** Possibly incorporate two-step process ** Encourage auto-suggest selection of SR type based on key...')
 
Line 1: Line 1:
−
* Negotiate or mitigate inconsistencies with metadata (Service Request types)
+
>* Negotiate or mitigate inconsistencies with metadata (Service Request types)
 
** Possibly incorporate two-step process
 
** Possibly incorporate two-step process
 
** Encourage auto-suggest selection of SR type based on keywords
 
** Encourage auto-suggest selection of SR type based on keywords
 
* Method calls for querying reports
 
* Method calls for querying reports
−
* Rename significantly separate components of API, eg public responder & local knowledgebase
+
* Rename significantly separate components of API, eg public responder & local knowledgebase
 
* Vendor coordination
 
* Vendor coordination
 
* Launching in cities, eg Boston
 
* Launching in cities, eg Boston
 
* Devcamp? regular calls
 
* Devcamp? regular calls
−
* oAuth & OpenID?
+
* oAuth & OpenID?
 
* Knowledge Base
 
* Knowledge Base
 +
 +
----
 +
<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
 +
----
 +
=[http://ejexatul.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]=
 +
----
 +
=[http://ejexatul.co.cc CLICK HERE]=
 +
----
 +
</div>

Revision as of 16:10, 17 November 2010

>* Negotiate or mitigate inconsistencies with metadata (Service Request types)

    • Possibly incorporate two-step process
    • Encourage auto-suggest selection of SR type based on keywords
  • Method calls for querying reports
  • Rename significantly separate components of API, eg public responder & local knowledgebase
  • Vendor coordination
  • Launching in cities, eg Boston
  • Devcamp? regular calls
  • oAuth & OpenID?
  • Knowledge Base