blog/tags/open311/open311.rss

   1 <?xml version="1.0" encoding="utf-8"?>
   2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
   3         <channel>
   4                 <title>Petter Reinholdtsen - Entries tagged open311</title>
   5                 <description>Entries tagged open311</description>
   6                 <link>http://people.skolelinux.org/pere/blog/</link>
   7
   8
   9         <item>
  10                 <title>Initial notes on adding Open311 server API on FixMyStreet</title>
  11                 <link>http://people.skolelinux.org/pere/blog/Initial_notes_on_adding_Open311_server_API_on_FixMyStreet.html</link>
  12                 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Initial_notes_on_adding_Open311_server_API_on_FixMyStreet.html</guid>
  13                 <pubDate>Fri, 29 Apr 2011 10:00:00 +0200</pubDate>
  14                 <description>
  15 &lt;p&gt;The last few days I have spent some time trying to add support for
  16 the &lt;ahref=&quot;http://www.open311.org/&quot;&gt;Open311 API&lt;/a&gt; in the
  17 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;Norwegian FixMyStreet service&lt;/a&gt;.
  18 Earlier I believed Open311 would be a useful API to use to submit
  19 reports to the municipalities, but when I noticed that the
  20 &lt;a href=&quot;http://fixmystreet.org.nz/&quot;&gt;New Zealand version&lt;/a&gt; of
  21 FixMyStreet had implemented Open311 on the server side, it occurred to
  22 me that this was a nice way to allow the public, press and
  23 municipalities to do data mining directly in the FixMyStreet service.
  24 Thus I went to work implementing the Open311 specification for
  25 FixMyStreet.  The implementation is not yet ready, but I am starting
  26 to get a draft limping along.  In the process, I have discovered a few
  27 issues with the Open311 specification.&lt;/p&gt;
  28
  29 &lt;p&gt;One obvious missing feature is the lack of natural language
  30 handling in the specification.  The specification seem to assume all
  31 reports will be written in English, and do not provide a way for the
  32 receiving end to specify which languages are understood there.  To be
  33 able to use the same client and submit to several Open311 receivers,
  34 it would be useful to know which language to use when writing reports.
  35 I believe the specification should be extended to allow the receivers
  36 of problem reports to specify which language they accept, and the
  37 submitter to specify which language the report is written in.
  38 Language of a text can also be automatically guessed using statistical
  39 methods, but for multi-lingual persons like myself, it is useful to
  40 know which language to use when writing a problem report.  I suspect
  41 some lang=nb,nn kind of attribute would solve it.&lt;/p&gt;
  42
  43 &lt;p&gt;A key part of the Open311 API is the list of services provided,
  44 which is similar to the categories used by FixMyStreet.  One issue I
  45 run into is the need to specify both name and unique identifier for
  46 each category.  The specification do not state that the identifier
  47 should be numeric, but all example implementations have used numbers
  48 here.  In FixMyStreet, there is no number associated with each
  49 category.  As the specification do not forbid it, I will use the name
  50 as the unique identifier for now and see how open311 clients handle
  51 it.&lt;/p&gt;
  52
  53 &lt;p&gt;The report format in open311 and the report format in FixMyStreet
  54 differ in a key part.  FixMyStreet have a title and a description,
  55 while Open311 only have a description and lack the title.  I&#39;m not
  56 quite sure how to best handle this yet.  When asking for a FixMyStreet
  57 report in Open311 format, I just merge title an description into the
  58 open311 description, but this is not going to work if the open311 API
  59 should be used for submitting new reports to FixMyStreet.&lt;/p&gt;
  60
  61 &lt;p&gt;The search feature in Open311 is missing a way to ask for problems
  62 near a geographic location.  I believe this is important if one is to
  63 use Open311 as the query language for mobile units.  The specification
  64 should be extended to handle this, probably using some new lat=, lon=
  65 and range= options.&lt;/p&gt;
  66
  67 &lt;p&gt;The final challenge I see is that the FixMyStreet code handle
  68 several administrations in one interface, while the Open311 API seem
  69 to assume only one administration.  For FixMyStreet, this mean a
  70 report can be sent to several administrations, and the categories
  71 available depend on the location of the problem.  Not quite sure how
  72 to best handle this.  I&#39;ve noticed
  73 &lt;a href=&quot;http://seeclickfix.com/open311/&quot;&gt;SeeClickFix&lt;/a&gt; added
  74 latitude and longitude options to the services request, but it do not
  75 solve the problem of what to return when no location is specified.
  76 Will have to investigate this a bit more.&lt;/p&gt;
  77
  78 &lt;p&gt;My distaste for web forums have kept me from bringing these issues
  79 up with the open311 developer group.  I really wish they had a email
  80 list available via &lt;a href=&quot;http://www.gmane.org/&quot;&gt;Gmane&lt;/a&gt; to use for
  81 discussions instead of only
  82 &lt;a href=&quot;http://lists.open311.org/groups/discuss&quot;&gt;a forum&lt;a/&gt;.  Oh,
  83 well.  That will probably resolve itself, one way or another.  I&#39;ve
  84 also tried visiting the IRC channel #open311 on FreeNode, but no-one
  85 seem to reply to my questions there.  This make me wonder if I just
  86 fail to understand how the open311 community work.  It sure do not
  87 work like the free software project communities I am used to.&lt;/p&gt;
  88 </description>
  89         </item>
  90
  91         </channel>
  92 </rss>