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