blog/tags/open311/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html>
   4  <head>
   5   <title>Petter Reinholdtsen: Entries Tagged open311</title>
   6   <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css">
   7   <link rel="alternate" title="RSS Feed" href="open311.rss" type="application/rss+xml">
   8  </head>
   9  <body>
  10
  11  <div class="title">
  12   <h1>
  13        <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  14
  15   </h1>
  16
  17  </div>
  18
  19  <p>Entries tagged "open311".</p>
  20
  21
  22
  23
  24 <div class="entry">
  25  <div class="title">
  26  <a href="http://people.skolelinux.org/pere/blog/Initial_notes_on_adding_Open311_server_API_on_FixMyStreet.html">Initial notes on adding Open311 server API on FixMyStreet</a>
  27  </div>
  28  <div class="date">
  29   2011-04-29 10:00
  30  </div>
  31
  32  <div class="body">
  33
  34 <p>The last few days I have spent some time trying to add support for
  35 the <a href="http://www.open311.org/">Open311 API</a> in the
  36 <a href="http://www.fiksgatami.no/">Norwegian FixMyStreet service</a>.
  37 Earlier I believed Open311 would be a useful API to use to submit
  38 reports to the municipalities, but when I noticed that the
  39 <a href="http://fixmystreet.org.nz/">New Zealand version</a> of
  40 FixMyStreet had implemented Open311 on the server side, it occurred to
  41 me that this was a nice way to allow the public, press and
  42 municipalities to do data mining directly in the FixMyStreet service.
  43 Thus I went to work implementing the Open311 specification for
  44 FixMyStreet.  The implementation is not yet ready, but I am starting
  45 to get a draft limping along.  In the process, I have discovered a few
  46 issues with the Open311 specification.</p>
  47
  48 <p>One obvious missing feature is the lack of natural language
  49 handling in the specification.  The specification seem to assume all
  50 reports will be written in English, and do not provide a way for the
  51 receiving end to specify which languages are understood there.  To be
  52 able to use the same client and submit to several Open311 receivers,
  53 it would be useful to know which language to use when writing reports.
  54 I believe the specification should be extended to allow the receivers
  55 of problem reports to specify which language they accept, and the
  56 submitter to specify which language the report is written in.
  57 Language of a text can also be automatically guessed using statistical
  58 methods, but for multi-lingual persons like myself, it is useful to
  59 know which language to use when writing a problem report.  I suspect
  60 some lang=nb,nn kind of attribute would solve it.</p>
  61
  62 <p>A key part of the Open311 API is the list of services provided,
  63 which is similar to the categories used by FixMyStreet.  One issue I
  64 run into is the need to specify both name and unique identifier for
  65 each category.  The specification do not state that the identifier
  66 should be numeric, but all example implementations have used numbers
  67 here.  In FixMyStreet, there is no number associated with each
  68 category.  As the specification do not forbid it, I will use the name
  69 as the unique identifier for now and see how open311 clients handle
  70 it.</p>
  71
  72 <p>The report format in open311 and the report format in FixMyStreet
  73 differ in a key part.  FixMyStreet have a title and a description,
  74 while Open311 only have a description and lack the title.  I'm not
  75 quite sure how to best handle this yet.  When asking for a FixMyStreet
  76 report in Open311 format, I just merge title an description into the
  77 open311 description, but this is not going to work if the open311 API
  78 should be used for submitting new reports to FixMyStreet.</p>
  79
  80 <p>The search feature in Open311 is missing a way to ask for problems
  81 near a geographic location.  I believe this is important if one is to
  82 use Open311 as the query language for mobile units.  The specification
  83 should be extended to handle this, probably using some new lat=, lon=
  84 and range= options.</p>
  85
  86 <p>The final challenge I see is that the FixMyStreet code handle
  87 several administrations in one interface, while the Open311 API seem
  88 to assume only one administration.  For FixMyStreet, this mean a
  89 report can be sent to several administrations, and the categories
  90 available depend on the location of the problem.  Not quite sure how
  91 to best handle this.  I've noticed
  92 <a href="http://seeclickfix.com/open311/">SeeClickFix</a> added
  93 latitude and longitude options to the services request, but it do not
  94 solve the problem of what to return when no location is specified.
  95 Will have to investigate this a bit more.</p>
  96
  97 <p>My distaste for web forums have kept me from bringing these issues
  98 up with the open311 developer group.  I really wish they had a email
  99 list available via <a href="http://www.gmane.org/">Gmane</a> to use for
 100 discussions instead of only
 101 <a href="http://lists.open311.org/groups/discuss">a forum<a/>.  Oh,
 102 well.  That will probably resolve itself, one way or another.  I've
 103 also tried visiting the IRC channel #open311 on FreeNode, but no-one
 104 seem to reply to my questions there.  This make me wonder if I just
 105 fail to understand how the open311 community work.  It sure do not
 106 work like the free software project communities I am used to.</p>
 107
 108  </div>
 109  <div class="tags">
 110
 111
 112
 113   Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami</a>, <a href="http://people.skolelinux.org/pere/blog/tags/open311">open311</a>.
 114
 115  </div>
 116 </div>
 117 <div class="padding"></div>
 118
 119 <div class="entry">
 120  <div class="title">
 121  <a href="http://people.skolelinux.org/pere/blog/Experimental_Open311_API_for_the_mySociety_fixmystreet_system.html">Experimental Open311 API for the mySociety fixmystreet system</a>
 122  </div>
 123  <div class="date">
 124   2011-04-30 17:20
 125  </div>
 126
 127  <div class="body">
 128
 129 <p>Today, the first draft implementation of an
 130 <a href="http://www.open311.org/">Open311 API</a> for the Norwegian
 131 service <a href="http://www.fiksgatami.no/">FiksGataMi</a> started to
 132 work.  It is only available on the developer server for now, and I
 133 have not tested it using any existing Open311 client (I lack the
 134 platforms needed to run the clients I have found so far), but it is
 135 able to query the database and extract a list of open and closed
 136 requests within a given category and reported to a given municipality.
 137 I believe that is a good start to create a useful service for those
 138 that want to do data mining on the requests submitted so far.</p>
 139
 140 <p>Where is it?  Visit
 141 <a href="http://fiksgatami-dev.nuug.no/open311.cgi/v2/">http://fiksgatami-dev.nuug.no/open311.cgi/v2/</a>
 142 to have a look.  Please send feedback to the
 143 <a href="http://lists.nuug.no/mailman/listinfo/fiksgatami">fiksgatami
 144 (at) nuug.no</a> mailing list.</p>
 145
 146  </div>
 147  <div class="tags">
 148
 149
 150
 151   Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami</a>, <a href="http://people.skolelinux.org/pere/blog/tags/open311">open311</a>.
 152
 153  </div>
 154 </div>
 155 <div class="padding"></div>
 156
 157  <p style="text-align: right;"><a href="open311.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14"></a></p>
 158
 159
 160
 161
 162 <div id="sidebar">
 163
 164 <h2>Archive</h2>
 165 <ul>
 166
 167 <li>2011
 168 <ul>
 169
 170 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 171
 172 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 173
 174 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 175
 176 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 177
 178 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 179
 180 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 181
 182 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (2)</a></li>
 183
 184 </ul></li>
 185
 186 <li>2010
 187 <ul>
 188
 189 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 190
 191 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 192
 193 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 194
 195 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 196
 197 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 198
 199 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 200
 201 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 202
 203 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 204
 205 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 206
 207 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 208
 209 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 210
 211 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 212
 213 </ul></li>
 214
 215 <li>2009
 216 <ul>
 217
 218 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 219
 220 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 221
 222 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 223
 224 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 225
 226 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 227
 228 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 229
 230 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 231
 232 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 233
 234 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 235
 236 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 237
 238 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 239
 240 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 241
 242 </ul></li>
 243
 244 <li>2008
 245 <ul>
 246
 247 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 248
 249 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 250
 251 </ul></li>
 252
 253 </ul>
 254
 255
 256
 257 <h2>Tags</h2>
 258 <ul>
 259
 260  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 261
 262  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 263
 264  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 265
 266  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
 267
 268  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (10)</a></li>
 269
 270  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (49)</a></li>
 271
 272  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (63)</a></li>
 273
 274  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (7)</a></li>
 275
 276  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (91)</a></li>
 277
 278  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (11)</a></li>
 279
 280  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (11)</a></li>
 281
 282  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (9)</a></li>
 283
 284  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (15)</a></li>
 285
 286  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
 287
 288  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
 289
 290  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 291
 292  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (12)</a></li>
 293
 294  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (127)</a></li>
 295
 296  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (118)</a></li>
 297
 298  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 299
 300  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (21)</a></li>
 301
 302  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (38)</a></li>
 303
 304  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 305
 306  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
 307
 308  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
 309
 310  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 311
 312  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
 313
 314  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (3)</a></li>
 315
 316  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (24)</a></li>
 317
 318  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
 319
 320  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (2)</a></li>
 321
 322  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (8)</a></li>
 323
 324  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (20)</a></li>
 325
 326  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
 327
 328  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (15)</a></li>
 329
 330 </ul>
 331
 332 </div>
 333 </body>
 334 </html>