--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+ <head>
+ <title>Petter Reinholdtsen: Entries Tagged open311</title>
+ <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css">
+ <link rel="alternate" title="RSS Feed" href="open311.rss" type="application/rss+xml">
+ </head>
+ <body>
+
+ <div class="title">
+ <h1>
+ <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
+
+ </h1>
+
+ </div>
+
+ <p>Entries tagged "open311".</p>
+
+
+
+
+<div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 2011-04-29 10:00
+ </div>
+
+ <div class="body">
+
+<p>The last few days I have spent some time trying to add support for
+the <ahref="http://www.open311.org/">Open311 API</a> in the
+<a href="http://www.fiksgatami.no/">Norwegian FixMyStreet service</a>.
+Earlier I believed Open311 would be a useful API to use to submit
+reports to the municipalities, but when I noticed that the
+<a href="http://fixmystreet.org.nz/">New Zealand version</a> of
+FixMyStreet had implemented Open311 on the server side, it occurred to
+me that this was a nice way to allow the public, press and
+municipalities to do data mining directly in the FixMyStreet service.
+Thus I went to work implementing the Open311 specification for
+FixMyStreet. The implementation is not yet ready, but I am starting
+to get a draft limping along. In the process, I have discovered a few
+issues with the Open311 specification.</p>
+
+<p>One obvious missing feature is the lack of natural language
+handling in the specification. The specification seem to assume all
+reports will be written in English, and do not provide a way for the
+receiving end to specify which languages are understood there. To be
+able to use the same client and submit to several Open311 receivers,
+it would be useful to know which language to use when writing reports.
+I believe the specification should be extended to allow the receivers
+of problem reports to specify which language they accept, and the
+submitter to specify which language the report is written in.
+Language of a text can also be automatically guessed using statistical
+methods, but for multi-lingual persons like myself, it is useful to
+know which language to use when writing a problem report. I suspect
+some lang=nb,nn kind of attribute would solve it.</p>
+
+<p>A key part of the Open311 API is the list of services provided,
+which is similar to the categories used by FixMyStreet. One issue I
+run into is the need to specify both name and unique identifier for
+each category. The specification do not state that the identifier
+should be numeric, but all example implementations have used numbers
+here. In FixMyStreet, there is no number associated with each
+category. As the specification do not forbid it, I will use the name
+as the unique identifier for now and see how open311 clients handle
+it.</p>
+
+<p>The report format in open311 and the report format in FixMyStreet
+differ in a key part. FixMyStreet have a title and a description,
+while Open311 only have a description and lack the title. I'm not
+quite sure how to best handle this yet. When asking for a FixMyStreet
+report in Open311 format, I just merge title an description into the
+open311 description, but this is not going to work if the open311 API
+should be used for submitting new reports to FixMyStreet.</p>
+
+<p>The search feature in Open311 is missing a way to ask for problems
+near a geographic location. I believe this is important if one is to
+use Open311 as the query language for mobile units. The specification
+should be extended to handle this, probably using some new lat=, lon=
+and range= options.</p>
+
+<p>The final challenge I see is that the FixMyStreet code handle
+several administrations in one interface, while the Open311 API seem
+to assume only one administration. For FixMyStreet, this mean a
+report can be sent to several administrations, and the categories
+available depend on the location of the problem. Not quite sure how
+to best handle this. I've noticed
+<a href="http://seeclickfix.com/open311/">SeeClickFix</a> added
+latitude and longitude options to the services request, but it do not
+solve the problem of what to return when no location is specified.
+Will have to investigate this a bit more.</p>
+
+<p>My distaste for web forums have kept me from bringing these issues
+up with the open311 developer group. I really wish they had a email
+list available via <a href="http://www.gmane.org/">Gmane</a> to use for
+discussions instead of only
+<a href="http://lists.open311.org/groups/discuss">a forum<a/>. Oh,
+well. That will probably resolve itself, one way or another. I've
+also tried visiting the IRC channel #open311 on FreeNode, but no-one
+seem to reply to my questions there. This make me wonder if I just
+fail to understand how the open311 community work. It sure do not
+work like the free software project communities I am used to.</p>
+
+ </div>
+ <div class="tags">
+
+
+
+ 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>.
+
+ </div>
+</div>
+<div class="padding"></div>
+
+ <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>
+
+
+
+
+<div id="sidebar">
+
+<h2>Archive</h2>
+<ul>
+
+<li>2011
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (6)</a></li>
+
+</ul></li>
+
+<li>2010
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
+
+</ul></li>
+
+<li>2009
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
+
+</ul></li>
+
+<li>2008
+<ul>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
+
+</ul></li>
+
+</ul>
+
+
+
+<h2>Tags</h2>
+<ul>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (10)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (49)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (63)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (7)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (89)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (9)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (11)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (9)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (14)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (12)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (121)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (116)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (20)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (38)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (3)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (24)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (8)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (20)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (15)</a></li>
+
+</ul>
+
+</div>
+</body>
+</html>
--- /dev/null
+<?xml version="1.0" encoding="utf-8"?>
+<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
+ <channel>
+ <title>Petter Reinholdtsen - Entries tagged open311</title>
+ <description>Entries tagged open311</description>
+ <link>http://people.skolelinux.org/pere/blog/</link>
+
+
+ <item>
+ <title>Initial notes on adding Open311 server API on FixMyStreet</title>
+ <link>http://people.skolelinux.org/pere/blog/Initial_notes_on_adding_Open311_server_API_on_FixMyStreet.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Initial_notes_on_adding_Open311_server_API_on_FixMyStreet.html</guid>
+ <pubDate>Fri, 29 Apr 2011 10:00:00 +0200</pubDate>
+ <description>
+<p>The last few days I have spent some time trying to add support for
+the <ahref="http://www.open311.org/">Open311 API</a> in the
+<a href="http://www.fiksgatami.no/">Norwegian FixMyStreet service</a>.
+Earlier I believed Open311 would be a useful API to use to submit
+reports to the municipalities, but when I noticed that the
+<a href="http://fixmystreet.org.nz/">New Zealand version</a> of
+FixMyStreet had implemented Open311 on the server side, it occurred to
+me that this was a nice way to allow the public, press and
+municipalities to do data mining directly in the FixMyStreet service.
+Thus I went to work implementing the Open311 specification for
+FixMyStreet. The implementation is not yet ready, but I am starting
+to get a draft limping along. In the process, I have discovered a few
+issues with the Open311 specification.</p>
+
+<p>One obvious missing feature is the lack of natural language
+handling in the specification. The specification seem to assume all
+reports will be written in English, and do not provide a way for the
+receiving end to specify which languages are understood there. To be
+able to use the same client and submit to several Open311 receivers,
+it would be useful to know which language to use when writing reports.
+I believe the specification should be extended to allow the receivers
+of problem reports to specify which language they accept, and the
+submitter to specify which language the report is written in.
+Language of a text can also be automatically guessed using statistical
+methods, but for multi-lingual persons like myself, it is useful to
+know which language to use when writing a problem report. I suspect
+some lang=nb,nn kind of attribute would solve it.</p>
+
+<p>A key part of the Open311 API is the list of services provided,
+which is similar to the categories used by FixMyStreet. One issue I
+run into is the need to specify both name and unique identifier for
+each category. The specification do not state that the identifier
+should be numeric, but all example implementations have used numbers
+here. In FixMyStreet, there is no number associated with each
+category. As the specification do not forbid it, I will use the name
+as the unique identifier for now and see how open311 clients handle
+it.</p>
+
+<p>The report format in open311 and the report format in FixMyStreet
+differ in a key part. FixMyStreet have a title and a description,
+while Open311 only have a description and lack the title. I'm not
+quite sure how to best handle this yet. When asking for a FixMyStreet
+report in Open311 format, I just merge title an description into the
+open311 description, but this is not going to work if the open311 API
+should be used for submitting new reports to FixMyStreet.</p>
+
+<p>The search feature in Open311 is missing a way to ask for problems
+near a geographic location. I believe this is important if one is to
+use Open311 as the query language for mobile units. The specification
+should be extended to handle this, probably using some new lat=, lon=
+and range= options.</p>
+
+<p>The final challenge I see is that the FixMyStreet code handle
+several administrations in one interface, while the Open311 API seem
+to assume only one administration. For FixMyStreet, this mean a
+report can be sent to several administrations, and the categories
+available depend on the location of the problem. Not quite sure how
+to best handle this. I've noticed
+<a href="http://seeclickfix.com/open311/">SeeClickFix</a> added
+latitude and longitude options to the services request, but it do not
+solve the problem of what to return when no location is specified.
+Will have to investigate this a bit more.</p>
+
+<p>My distaste for web forums have kept me from bringing these issues
+up with the open311 developer group. I really wish they had a email
+list available via <a href="http://www.gmane.org/">Gmane</a> to use for
+discussions instead of only
+<a href="http://lists.open311.org/groups/discuss">a forum<a/>. Oh,
+well. That will probably resolve itself, one way or another. I've
+also tried visiting the IRC channel #open311 on FreeNode, but no-one
+seem to reply to my questions there. This make me wonder if I just
+fail to understand how the open311 community work. It sure do not
+work like the free software project communities I am used to.</p>
+</description>
+ </item>
+
+ </channel>
+</rss>
projects / homepage.git / commitdiff