]> pere.pagekite.me Git - homepage.git/blob - blog/index.rss
Generated.
[homepage.git] / blog / index.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/' xmlns:atom="http://www.w3.org/2005/Atom">
3 <channel>
4 <title>Petter Reinholdtsen</title>
5 <description></description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
8
9 <item>
10 <title>Gatemagasinet =Oslo får konkurrent fra Folk er Folk</title>
11 <link>http://people.skolelinux.org/pere/blog/Gatemagasinet__Oslo_f_r_konkurrent_fra_Folk_er_Folk.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gatemagasinet__Oslo_f_r_konkurrent_fra_Folk_er_Folk.html</guid>
13 <pubDate>Tue, 19 Jun 2012 10:00:00 +0200</pubDate>
14 <description>&lt;p&gt;Aftenposten melder i dag at selgerne av
15 &lt;a href=&quot;http://www.erlikoslo.no/&quot;&gt;gatemagasinet =Oslo&lt;/a&gt; er
16 &lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/Oslo-selgerne-irritert-pa-nytt-gatemagasin-6850970.html&quot;&gt;irritert
17 på at det er kommet en konkurrent på banen&lt;/a&gt; fra organisasjonen
18 &lt;a href=&quot;http://oslo.folkerfolk.no/&quot;&gt;Folk er Folk&lt;/a&gt;,
19 som støtter “rumenerne”, de mest uglesette av tiggerne i Norge. Min
20 første tanke da jeg leste nyheten er at slik må =Oslo-selgerne tåle
21 når de nekter &quot;rumenerne&quot; og andre utenlandske tiggere å selge
22 gatemagasinet sitt. Det ble rapportert for noen år siden at
23 &lt;a href=&quot;http://www.aftenposten.no/nyheter/iriks/Ikke-rom-i-herberget-6677803.html&quot;&gt;utenlandske
24 tiggere ikke var velkomne som selgere&lt;/a&gt;, og å opprette en konkurrent
25 virker da for meg som et rasjonelt alternativ. Og at &quot;rumerene&quot;
26 utelukkes gjelder visst ikke bare i Oslo. I Adresseavisen fant jeg en
27 artikkel om at selgerne av
28 &lt;a href=&quot;http://www.gatemagasinetsorgenfri.no/&quot;&gt;gateavisen
29 Sorgenfri&lt;/a&gt; i Trondheim også
30 &lt;a href=&quot;http://www.adressa.no/nyheter/trondheim/article1122005.ece?index=20&quot;&gt;utelukker
31 utenlandske selgere&lt;/a&gt;.&lt;/p&gt;
32
33 &lt;p&gt;Men situasjonen er visst ikke så rett frem som opprinnelige
34 artikler kunne tyde på. Mens jeg søkte opp gamle artikler og
35 referanser om temaet, fant jeg et
36 &lt;a href=&quot;http://www.dagbladet.no/kultur/2008/07/29/542041.html&quot;&gt;leserbrev
37 fra en av stifterne av =Oslo&lt;/a&gt;, som protesterte på
38 &lt;a href=&quot;http://www.dagbladet.no/nyheter/2008/07/23/541530.html&quot;&gt;påstander
39 fra likestillingsombudet om diskriminering&lt;/a&gt; og forteller at =Oslo
40 krever at de som selger magasinet skal kunne kommunisere med kundene
41 for å kunne representere magasinet utad, og at &quot;rumererne&quot; ikke
42 ekskluderes for å være utlendinger men pga. at de ikke kan snakke
43 norsk. Det er jo ikke urimelig å kreve at en selger skal kunne
44 kommunisere med kundene, men som kjøper har jeg ikke snakket så mye
45 med =Oslo-selgerne at det ville vært et problem for meg om selgeren
46 ikke kunne snakke norsk. Jeg er dermed i tvil om hvorvidt
47 argumentasjonen holder når effekten er at de mest uglesette tiggerne i
48 Norge ekskluderes.&lt;/p&gt;
49
50 &lt;p&gt;Uansett tror jeg ikke markedet for gatemagasiner i Oslo er mettet.
51 Personlig kunne jeg godt tenkte meg å kjøpe flere, men gidder ikke
52 kjøpe den samme utgaven av =Oslo flere ganger. En konkurrent som Folk
53 er Folk kan dermed ende opp med å gjøre markedet større i stedet for å
54 spise av markedsandelene til =Oslo.&lt;/p&gt;
55 </description>
56 </item>
57
58 <item>
59 <title>SQL-database med anbud publisert på Doffin</title>
60 <link>http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html</link>
61 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html</guid>
62 <pubDate>Fri, 15 Jun 2012 13:30:00 +0200</pubDate>
63 <description>&lt;p&gt;&lt;a href=&quot;http://www.doffin.no/&quot;&gt;Doffin&lt;/a&gt; er det offentlige Norges
64 portal for annonsering av anbudsutlysninger. Nettstedet er mye brukt,
65 men rådataene er ikke enkelt tilgjengelig for almenheten. For å bøte
66 på det har jeg som et &lt;a href=&quot;htt://www.nuug.no/&quot;&gt;NUUG-prosjekt&lt;/a&gt;
67 laget en &lt;a href=&quot;http://scraperwiki.com/&quot;&gt;Scraperwiki&lt;/a&gt;-skraper som
68 lager en
69 &lt;a href=&quot;https://scraperwiki.com/scrapers/norwegian-doffin/&quot;&gt;SQL-database
70 med nøkkelinformasjonen fra Doffin&lt;/a&gt;, slik at det er mulig å søke og
71 analysere Doffin-oppføringene. Det publiseres mellom 900-1500 anbud
72 hver måned via Doffin. Jeg har ingen konkrete planer for analyse, men
73 håper enklere tilgjengelighet gjør at flere griper sjansen. På sikt
74 håper jeg å bruke denne databasen som grunnlag for å lage en database
75 over anbudsdokumenter, som i dag ikke er tilgjengelig fra doffin, men
76 må bestilles fra hver enkelt utlyser.&lt;/p&gt;
77
78 &lt;p&gt;Jeg var litt usikker på om det var rettighetsproblemer knyttet til
79 skraping av informasjon fra Doffin, men ser i
80 &lt;a href=&quot;http://www.doffin.no/sitehelp/help_terms.aspx&quot;&gt;vilkårene til
81 Doffin&lt;/a&gt; følgende:&lt;/p&gt;
82
83 &lt;p&gt;&lt;blockquote&gt;
84
85 &lt;p&gt;Opphavsrett mv&lt;/p&gt;
86
87 &lt;p&gt;Ved innleggig av kunngjøringer på Doffin aksepterer Oppdragsgiver
88 at opphavsrett og andre rettigheter til materialet overføres til
89 Fornyings- og administrasjonsdepartementet, eller den departementet
90 utnevner. Oppdragsgiver har imidlertid bruksrett til materialet, og
91 kan benytte det til de formål de måtte ønske.&lt;/p&gt;
92
93 &lt;/blockquote&gt;&lt;/p&gt;
94
95 &lt;p&gt;Hvis informasjonen er vernet av opphavsrettsloven (hvilket jeg
96 tviler på, gitt lovens begrensninger om informasjon fra det
97 offentlige), så er det FAD som har de immaterielle rettighetene. FAD
98 er en del av staten, som opererer på vegne av folket, og enhver borger
99 skulle dermed ha rett til å videreformidle informasjonen. Ingen av
100 offentlighetslovens unntak kommer til anvendelse, i og med at
101 informasjonen allerede er publisert.&lt;/p&gt;
102 </description>
103 </item>
104
105 <item>
106 <title>Debian Edu - some ideas for the future versions</title>
107 <link>http://people.skolelinux.org/pere/blog/Debian_Edu___some_ideas_for_the_future_versions.html</link>
108 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu___some_ideas_for_the_future_versions.html</guid>
109 <pubDate>Mon, 11 Jun 2012 14:30:00 +0200</pubDate>
110 <description>&lt;p&gt;During my work on
111 &lt;a href=&quot;http://www.debian.org/News/2012/20120311.nb.html&quot;&gt;Debian Edu
112 based on Squeeze&lt;/a&gt;, I came across some issues that should be
113 addressed in the Wheezy release. I finally found time to wrap up my
114 notes and provide quick summary of what I found, with a bit
115 explanation.&lt;/p&gt;
116
117 &lt;p&gt;&lt;ul&gt;
118
119 &lt;li&gt;We need to rewrite our package installation framework, as tasksel
120 changed from using tasksel tasks to using meta packages (aka packages
121 with dependencies like our education-* packages), and our installation
122 system depend on tasksel tasks in
123 /usr/share/tasksel/debian-edu-tasks.desc for package
124 installation.&lt;/li&gt;
125
126 &lt;li&gt;Enable Kerberos login for more services. Now with the Kerberos
127 foundation in place, we should use it to get single sign on with more
128 services, and avoiding unneeded password / login questions. We should
129 at least try to enable it for these services:
130 &lt;ul&gt;
131
132 &lt;li&gt;CUPS for admins to add/configure printers and users when using
133 quotas.&lt;/li&gt;
134 &lt;li&gt;Nagios for admins checking the system status.&lt;/li&gt;
135 &lt;li&gt;GOsa for admins updating LDAP and users changing their passwords.&lt;/li&gt;
136 &lt;li&gt;LDAP for admins updating LDAP.&lt;/li&gt;
137 &lt;li&gt;Squid for users when exam mode / filtering is active.&lt;/li&gt;
138 &lt;li&gt;ssh for admins and users to save a password prompt.&lt;/li&gt;
139
140 &lt;/ul&gt;&lt;/li&gt;
141
142 &lt;li&gt;When we move GOsa to use Kerberos instead of LDAP bind to
143 authenticate users, we should try to block or at least limit access to
144 use LDAP bind for authentication, to ensure Kerberos is used when it
145 is intended, and nothing fall back to using the less safe LDAP bind&lt;/li&gt;
146
147 &lt;li&gt;Merge debian-edu-config and debian-edu-install. The split made
148 sense when d-e-install did a lot more, but these days it is just an
149 inconvenience when we update the debconf preseeding values.&lt;/li&gt;
150
151 &lt;li&gt;Fix partman-auto to allow us to abort the installation before
152 touching the disk if the disk is too small. This is
153 &lt;a href=&quot;http://bugs.debian.org/653305&quot;&gt;BTS report #653305&lt;/a&gt; and the
154 d-i developers are fine with the patch and someone just need to apply
155 it and upload. After this is done we need to adjust
156 debian-edu-install to use this new hook.&lt;/li&gt;
157
158 &lt;li&gt;Adjust to new LTSP framework (boot time config instead of install
159 time config). LTSP changed its design, and our hooks to install
160 packages and update the configuration is most likely not going to work
161 in Wheezy.
162
163 &lt;li&gt;Consider switching to NBD instead of NFS for LTSP root, to allow
164 the Kernel to cache files in its normal file cache, possibly speeding
165 up KDE login on slow networks.&lt;/li&gt;
166
167 &lt;li&gt;Make it possible to create expired user passwords that need to
168 change on first login. This is useful when handing out password on
169 paper, to make sure only the user know the password. This require
170 fixes to the PAM handling of kdm and gdm.&lt;/li&gt;
171
172 &lt;li&gt;Make GUI for adding new machines automatically from sitesummary.
173 The current command line script is not very friendly to people most
174 familiar with GUIs. This should probably be integrated into GOsa to
175 have it available where the admin will be looking for it..&lt;/li&gt;
176
177 &lt;li&gt;We should find way for Nagios to check that the DHCP service
178 actually is working (as in handling out IP addresses). None of the
179 Nagios checks I have found so far have been working for me.&lt;/li&gt;
180
181 &lt;li&gt;We should switch from libpam-nss-ldapd to sssd for all profiles
182 using LDAP, and not only on for roaming workstations, to have less
183 packages to configure and consistent setup across all profiles.&lt;/li&gt;
184
185 &lt;li&gt;We should configure Kerberos to update LDAP and Samba password
186 when changing password using the Kerberos protocol. The hook was
187 requested in &lt;a href=&quot;http://bugs.debian.org/588968&quot;&gt;BTS report
188 #588968&lt;/a&gt; and is now available in Wheezy. We might need to write a
189 MIT Kerberos plugin in C to get this.&lt;/li&gt;
190
191 &lt;li&gt;We should clean up the set of applications installed by default.
192 &lt;ul&gt;
193
194 &lt;li&gt;reduce the number of chemistry visualisers&lt;/li&gt;
195 &lt;li&gt;consider dropping xpaint&lt;/li&gt;
196 &lt;li&gt;and probably more?&lt;/li&gt;
197 &lt;/ul&gt;&lt;/li&gt;
198
199 &lt;li&gt;Some hardware need external firmware to work properly. This is
200 mostly the case for WiFi network cards, but there are some other
201 examples too. For popular laptops to work out of the box, such
202 firmware need to be installed from non-free, and we should provide
203 some GUI to do this. Ubuntu already have this implemented, and we
204 could consider using their packages. At the moment we have some
205 command line script to do this (one for the running system, another
206 for the LTSP chroot).&lt;/li&gt;
207
208
209 &lt;li&gt;In Squeeze, we provide KDE, Gnome and LXDE as desktop options. We
210 should extend the list to Xfce and Sugar, and preferably find a way to
211 install several and allow the admin or the user to select which one to
212 use.&lt;/li&gt;
213
214 &lt;li&gt;The golearn tool from the goplay package make it easy to check out
215 interesting educational packages. We should work on the package
216 tagging in Debian to ensure it represent all the useful educational
217 packages, and extend the tool to allow it to use packagekit to install
218 new applications with a simple mouse click.&lt;/li&gt;
219
220 &lt;li&gt;The Squeeze version got half a exam solution already in place,
221 with the introduction of iptable based network blocking, but for it to
222 be a complete exam solution the Squid proxy need to enable
223 filtering/blocking as well when the exam mode is enabled. We should
224 implement a way to easily enable this for the schools that want it,
225 instead of the &quot;it is documented&quot; method of today.&lt;/li&gt;
226
227 &lt;li&gt;A feature used in several schools is the ability for a teacher to
228 &quot;take over&quot; the desktop of individual or all computers in the room.
229 There are at least three implementations,
230 &lt;a href=&quot;italc.sourceforge.net/&quot;&gt;italc&lt;/a&gt;,
231 &lt;a href=&quot;http://www.itais.net/help/en/&quot;&gt;controlaula&lt;/a&gt; og
232 &lt;a href=&quot;http://www.epoptes.org/&quot;&gt;epoptes&lt;/a&gt; and we should pick one of
233 them and make it trivial to set it up in a school. The challenges is
234 how to distribute crypto keys and how to group computers in one room
235 and how to set up which machine/user can control the machines in a
236 given room.&lt;/li&gt;
237
238 &lt;li&gt;Tablets and surf boards are getting more and more popular, and we
239 should look into providing a good solution for integrating these into
240 the Debian Edu network. Not quite sure how. Perhaps we should
241 provide a installation profile with better touch screen support for
242 them, or add some sync services to allow them to exchange
243 configuration and data with the central server. This should be
244 investigated.&lt;/li&gt;
245
246 &lt;/ul&gt;&lt;/p&gt;
247
248 &lt;p&gt;I guess we will discover more as we continue to work on the Wheezy
249 version.&lt;/p&gt;
250 </description>
251 </item>
252
253 <item>
254 <title>Litt statistikk fra Offentlig Elektronisk postjournal</title>
255 <link>http://people.skolelinux.org/pere/blog/Litt_statistikk_fra_Offentlig_Elektronisk_postjournal.html</link>
256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Litt_statistikk_fra_Offentlig_Elektronisk_postjournal.html</guid>
257 <pubDate>Sun, 10 Jun 2012 20:30:00 +0200</pubDate>
258 <description>&lt;p&gt;De siste månedene har jeg sammen med andre i NUUG jobbet med å
259 gjøre det enklere å få innsyn i offentlige dokumenter, og dette
260 inkluderer å gjøre postjournaler enklere tilgjengelig for maskinell
261 analyse og søk. I den forbindelse tok jeg i dag å tittet litt på
262 &lt;a href=&quot;http://www.oep.no/&quot;&gt;Offentlig Elektronisk Postjournal
263 (OEP)&lt;/a&gt;, FAD/DIFIs fellesløsning for departementer og statlige
264 etater.&lt;/p&gt;
265
266 &lt;p&gt;Her er antall oppføringer pr. måned det siste året,
267 &lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&amp;name=postliste-oep&amp;query=select%20strftime(%22%25Y-%25m%22%2C%20%60recordpublishdate%60)%20as%20oeppubmonth%2C%20count(*)%20from%20%60swdata%60%20group%20by%20oeppubmonth%20order%20by%20oeppubmonth&quot;&gt;summert
268 opp&lt;/a&gt; ved hjelp av
269 &lt;a href=&quot;https://scraperwiki.com/scrapers/postliste-oep/&quot;&gt;en
270 Scraperwiki-database&lt;/a&gt;. Merk at denne Scraperwikien har
271 ytelsesproblemer pga. mengden data. &lt;/p&gt;
272
273 &lt;p&gt;&lt;table border=&quot;1&quot;&gt;
274 &lt;tr&gt;&lt;th&gt;Måned&lt;/th&gt;&lt;th&gt;Antall&lt;/th&gt;&lt;/tr&gt;
275 &lt;tr&gt;&lt;td&gt;2011-07&lt;/td&gt;&lt;td&gt;164355&lt;/td&gt;&lt;/tr&gt;
276 &lt;tr&gt;&lt;td&gt;2011-08&lt;/td&gt;&lt;td&gt;153662&lt;/td&gt;&lt;/tr&gt;
277 &lt;tr&gt;&lt;td&gt;2011-09&lt;/td&gt;&lt;td&gt;173134&lt;/td&gt;&lt;/tr&gt;
278 &lt;tr&gt;&lt;td&gt;2011-10&lt;/td&gt;&lt;td&gt;170665&lt;/td&gt;&lt;/tr&gt;
279 &lt;tr&gt;&lt;td&gt;2011-11&lt;/td&gt;&lt;td&gt;198409&lt;/td&gt;&lt;/tr&gt;
280 &lt;tr&gt;&lt;td&gt;2011-12&lt;/td&gt;&lt;td&gt;175908&lt;/td&gt;&lt;/tr&gt;
281 &lt;tr&gt;&lt;td&gt;2012-01&lt;/td&gt;&lt;td&gt;206875&lt;/td&gt;&lt;/tr&gt;
282 &lt;tr&gt;&lt;td&gt;2012-02&lt;/td&gt;&lt;td&gt;202862&lt;/td&gt;&lt;/tr&gt;
283 &lt;tr&gt;&lt;td&gt;2012-03&lt;/td&gt;&lt;td&gt;204225&lt;/td&gt;&lt;/tr&gt;
284 &lt;tr&gt;&lt;td&gt;2012-04&lt;/td&gt;&lt;td&gt;207931&lt;/td&gt;&lt;/tr&gt;
285 &lt;tr&gt;&lt;td&gt;2012-05&lt;/td&gt;&lt;td&gt;223754&lt;/td&gt;&lt;/tr&gt;
286 &lt;/table&gt;&lt;/p&gt;
287
288 &lt;p&gt;Det er også interessant å se hvor ofte ulike etater sender inn sine
289 journaloppføringer til OEP. OEP inneholder en liste med sist
290 innrapporteringsdato for alle som sender til OEP, og ved å se når og
291 hvor ofte det blir sendt inn fra etatene kan
292 &lt;a href=&quot;https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&amp;name=postliste-oep-deliverydates&amp;query=select%20agency%2C%0A(julianday(datetime(&#39;now&#39;))%20-%20%0A%20julianday(min(%60deliverydate%60)))%2Fcount(*)%20as%20dayfreq%2C%0A%20count(*)%0Afrom%20%60swdata%60%20group%20by%20agency%20order%20by%20dayfreq%20desc&quot;&gt;frekvensen
293 beregnes&lt;/a&gt;. Her er bunnlista, dvs. de som leverer sjeldnere enn hver 10.
294 dag beregnet fra
295 &lt;a href=&quot;https://scraperwiki.com/scrapers/postliste-oep-deliverydates/&quot;&gt;en
296 Scraperwiki-database&lt;/a&gt;:&lt;/p&gt;
297
298 &lt;p&gt;&lt;table border=&quot;1&quot;&gt;
299
300 &lt;tr&gt; &lt;th&gt;Etat&lt;/th&gt; &lt;th&gt;Frekvens&lt;/th&gt; &lt;th&gt;Leveringer&lt;/th&gt; &lt;/tr&gt;
301 &lt;tr&gt; &lt;td&gt;Norges geologiske undersøkelse&lt;/td&gt; &lt;td&gt;83.7527546296&lt;/td&gt; &lt;td&gt;1&lt;/td&gt; &lt;/tr&gt;
302 &lt;tr&gt; &lt;td&gt;Medietilsynet&lt;/td&gt; &lt;td&gt;33.7527546296&lt;/td&gt; &lt;td&gt;1&lt;/td&gt; &lt;/tr&gt;
303 &lt;tr&gt; &lt;td&gt;Departementenes servicesenter&lt;/td&gt; &lt;td&gt;23.8763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
304 &lt;tr&gt; &lt;td&gt;Kunnskapsdepartementet&lt;/td&gt; &lt;td&gt;15.8763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
305 &lt;tr&gt; &lt;td&gt;Kompetansesenter for distriktsutvikling&lt;/td&gt; &lt;td&gt;15.3763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
306 &lt;tr&gt; &lt;td&gt;Toll- og avgiftsdirektoratet&lt;/td&gt; &lt;td&gt;15.3763773148&lt;/td&gt; &lt;td&gt;2&lt;/td&gt; &lt;/tr&gt;
307 &lt;tr&gt; &lt;td&gt;Fredskorpset&lt;/td&gt; &lt;td&gt;12.5842515432&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
308 &lt;tr&gt; &lt;td&gt;Statens legemiddelverk&lt;/td&gt; &lt;td&gt;12.1881886574&lt;/td&gt; &lt;td&gt;4&lt;/td&gt; &lt;/tr&gt;
309 &lt;tr&gt; &lt;td&gt;Utlendingsnemnda&lt;/td&gt; &lt;td&gt;11.5842515432&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
310 &lt;tr&gt; &lt;td&gt;Politidirektoratet&lt;/td&gt; &lt;td&gt;10.9175848765&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
311 &lt;tr&gt; &lt;td&gt;Skattedirektoratet&lt;/td&gt; &lt;td&gt;10.9175848765&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
312 &lt;tr&gt; &lt;td&gt;Statens innkrevingssentral&lt;/td&gt; &lt;td&gt;10.5842515432&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
313 &lt;tr&gt; &lt;td&gt;Barne-, ungdoms- og familiedirektoratet&lt;/td&gt; &lt;td&gt;10.2509182099&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
314 &lt;tr&gt; &lt;td&gt;Kunst i offentlige rom&lt;/td&gt; &lt;td&gt;10.2509182099&lt;/td&gt; &lt;td&gt;3&lt;/td&gt; &lt;/tr&gt;
315
316 &lt;/table&gt;&lt;/p&gt;
317
318 &lt;p&gt;En kan beregne lignende frekvenser ved å sammenligne
319 journalføringsdato med publiseringsdato for hver enkelt oppføring i
320 OEP, men den lenken legger jeg ikke ved her for å unngå at
321 søkemotorroboter begynner å overbelaste Scraperwiki-databasen.&lt;/p&gt;
322
323 &lt;p&gt;Jeg har spurt Norges geologiske undersøkelse om hvorfor de leverer
324 så sjelden, og det kommer av at de har problemer etter oppgradering av
325 arkivsystemet sitt og jobber med å fikse det slik at de kan gå tilbake
326 til å levere hver uke. Har ikke undersøkt noen av de andre.&lt;/p&gt;
327 </description>
328 </item>
329
330 <item>
331 <title>TV with face recognition, for improved viewer experience</title>
332 <link>http://people.skolelinux.org/pere/blog/TV_with_face_recognition__for_improved_viewer_experience.html</link>
333 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/TV_with_face_recognition__for_improved_viewer_experience.html</guid>
334 <pubDate>Sat, 9 Jun 2012 22:00:00 +0200</pubDate>
335 <description>&lt;p&gt;Slashdot got a story about Intel planning a
336 &lt;a href=&quot;http://entertainment.slashdot.org/story/12/06/09/0012247/intel-to-launch-tv-service-with-facial-recognition-by-end-of-the-year&quot;&gt;TV
337 with face recognition&lt;/a&gt; to recognise the viewer, and it occurred to
338 me that it would be more interesting to turn it around, and do face
339 recognition on the TV image itself. It could let the viewer know who
340 is present on the screen, and perhaps look up their credibility,
341 company affiliation, previous appearances etc for the viewer to better
342 evaluate what is being said and done. That would be a feature I would
343 be willing to pay for.&lt;/p&gt;
344
345 &lt;p&gt;I would not be willing to pay for a TV that point a camera on my
346 household, like the big brother feature apparently proposed by Intel.
347 It is the telescreen idea fetched straight out of the book
348 &lt;a href=&quot;http://gutenberg.net.au/ebooks01/0100021.txt&quot;&gt;1984 by George
349 Orwell&lt;/a&gt;.&lt;/p&gt;
350 </description>
351 </item>
352
353 <item>
354 <title>Web service to look up HP and Dell computer hardware support status</title>
355 <link>http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html</link>
356 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html</guid>
357 <pubDate>Wed, 6 Jun 2012 23:15:00 +0200</pubDate>
358 <description>&lt;p&gt;A few days ago
359 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html&quot;&gt;I
360 reported how to get&lt;/a&gt; the support status out of Dell using an
361 unofficial and undocumented SOAP API, which I since have found out was
362 &lt;a href=&quot;http://lists.us.dell.com/pipermail/linux-poweredge/2012-February/045959.html&quot;&gt;discovered
363 by Daniel De Marco in february&lt;/a&gt;. Combined with my web scraping
364 code for HP, Dell and IBM
365 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html&quot;&gt;from
366 2009&lt;/a&gt;, I got inspired and wrote
367 &lt;a href=&quot;https://views.scraperwiki.com/run/computer-hardware-support-status/&quot;&gt;a
368 web service&lt;/a&gt; based on Scraperwiki to make it easy to look up the
369 support status and get a machine readable result back.&lt;/p&gt;
370
371 &lt;p&gt;This is what it look like at the moment when asking for the JSON
372 output:
373
374 &lt;blockquote&gt;&lt;pre&gt;
375 % GET &lt;a href=&quot;https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&amp;vendor=Dell&amp;servicetag=2v1xwn1&quot;&gt;https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&amp;vendor=Dell&amp;servicetag=2v1xwn1&lt;/a&gt;
376 supportstatus({&quot;servicetag&quot;: &quot;2v1xwn1&quot;, &quot;warrantyend&quot;: &quot;2013-11-24&quot;, &quot;shipped&quot;: &quot;2010-11-24&quot;, &quot;scrapestamputc&quot;: &quot;2012-06-06T20:26:56.965847&quot;, &quot;scrapedurl&quot;: &quot;http://143.166.84.118/services/assetservice.asmx?WSDL&quot;, &quot;vendor&quot;: &quot;Dell&quot;, &quot;productid&quot;: &quot;&quot;})
377 %
378 &lt;/pre&gt;&lt;/blockquote&gt;
379
380 &lt;p&gt;It currently support Dell and HP, and I am hoping for help to add
381 support for other vendors. The python source is available on
382 Scraperwiki and I welcome help with adding more features.&lt;/p&gt;
383 </description>
384 </item>
385
386 <item>
387 <title>Kommentar til artikkel i Adresseavisa som omtaler FiksGataMi</title>
388 <link>http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html</link>
389 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html</guid>
390 <pubDate>Sat, 2 Jun 2012 19:30:00 +0200</pubDate>
391 <description>&lt;p&gt;Jeg oppdaget nylig en
392 &lt;a href=&quot;http://www.adressa.no/nyheter/trondheim/article1831198.ece&quot;&gt;artikkel
393 i Adresseavisa&lt;/a&gt; i Trondheim som nevner FiksGataMi, og der Trondheim
394 kommune ser ut til å fortelle at de ikke følger forvaltningslovens
395 krav ved mottak av meldinger sendt inn via FiksGataMi. La derfor
396 nettopp inn denne kommentaren til artikkelen:&lt;p&gt;
397
398 &lt;p&gt;&lt;blockquote&gt;
399
400 &lt;p&gt;Her er en liten faktaoppdatering om FiksGataMi-tjenesten, da noen
401 ser ut til å ha misforstått hvordan den fungerer.&lt;/p&gt;
402
403 &lt;p&gt;FiksGataMi er et privat initiativ opprettet og drevet av
404 medlemsforeningen NUUG. FiksGataMi tar imot meldinger om feil i
405 offentlig infrastruktur, og sender meldingen skriftlig videre på vegne
406 av innmelder til aktuell aktør i det offentlige, det være seg kommune,
407 fylke eller vegvesenregion. Offentlig etat blir valgt ut fra
408 geografisk plassering og kategori valgt av innsender. Offentlige
409 etater er i følge forvaltningsloven pliktig å følge opp og besvare
410 skriftlige henvendelser, og hvis noen av mottakerne ikke gjør dette
411 kan en klage på lovbrudd i det offentlige. FiksGataMi fungerer dermed
412 som en slags epostklient for innbyggerne der kopi av innsendte
413 meldinger gjøres tilgjengelig og knyttes til kartplassering for enkel
414 gjenfinning. Å sende inn nye problemrapporter via FiksGataMi er
415 dermed ikke avhengig av at kommunen aktivt må følge med på meldinger
416 hos FiksGataMi, da de får dem tilsendt på sine offisielle
417 epostmottakspunkter. Hvorvidt noe blir fikset og om innbyggerne er
418 opp til mottaker av meldingene. For Trondheim kommune er
419 mottaksadressen bydrift.vegdrift@trondheim.kommune.no, en adresse jeg
420 inntil jeg leste denne artikkelen trodde ble håndtert i henhold til
421 forvaltningslovens krav.&lt;/p&gt;
422
423 &lt;p&gt;Kan ellers fortelle at 57 kommuner lenker til FiksGataMi fra sine
424 nettsider, og at 37 % (4182 av 11266 ) av problemrapportene sendt inn
425 via FiksGataMi er markert som løst i løsningen. Trondheim kommune har
426 fått tilbud om å få rapportene levert på datamaskinlesbart format i
427 stedet for epost, men har ikke takket ja så langt.&lt;/p&gt;
428
429 &lt;p&gt;Vennlig hilsen Petter Reinholdtsen, en av NUUG-folkene bak FiksGataMi.no&lt;/p&gt;
430
431 &lt;/blockquote&gt;&lt;/p&gt;
432
433 &lt;p&gt;Det høres for meg ut som om innbyggerne i Trondheim burde klage på
434 kommunens potensielle lovbrudd.&lt;/p&gt;
435 </description>
436 </item>
437
438 <item>
439 <title>Debian Edu interview: Mike Gabriel</title>
440 <link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Mike_Gabriel.html</link>
441 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Mike_Gabriel.html</guid>
442 <pubDate>Sat, 2 Jun 2012 15:00:00 +0200</pubDate>
443 <description>&lt;p&gt;Back in 2010, Mike Gabriel showed up on the
444 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu and Skolelinux&lt;/a&gt;
445 mailing list. He quickly proved to be a valuable developer, and
446 thanks to his tireless effort we now have Kerberos integrated into the
447 &lt;a href=&quot;http://www.debian.org/News/2012/20120311.html&quot;&gt;Debian Edu
448 Squeeze&lt;/a&gt; version.&lt;/p&gt;
449
450 &lt;p&gt;&lt;strong&gt;Who are you, and how do you spend your days?&lt;/strong&gt;&lt;/p&gt;
451
452 &lt;p&gt;My name is Mike Gabriel, I am 38 years old and live near Kiel,
453 Schleswig-Holstein, Germany. I live together with a wonderful partner
454 (Angela Fuß) and two own children and two bonus children (contributed
455 by Angela).&lt;/p&gt;
456
457 &lt;p&gt;During the day I am part-time employed as a system administrator
458 and part-time working as an IT consultant. The consultancy work
459 touches free software topics wherever and whenever possible. During
460 the nights I am a free software developer. In the gaps I also train in
461 becoming an osteopath.&lt;/p&gt;
462
463 &lt;p&gt;Starting in 2010 we (Andreas Buchholz, Angela Fuß, Mike Gabriel)
464 have set up a free software project in the area of Kiel that aims at
465 introducing free software into schools. The project&#39;s name is
466 &quot;IT-Zukunft Schule&quot; (IT future for schools). The project links IT
467 skills with communication skills.&lt;/p&gt;
468
469 &lt;p&gt;&lt;strong&gt;How did you get in contact with the Skolelinux/Debian Edu
470 project?&lt;/strong&gt;&lt;/p&gt;
471
472 &lt;p&gt;While preparing our own customised Linux distribution for
473 &quot;IT-Zukunft Schule&quot; we were repeatedly asked if we really wanted to
474 reinvent the wheel. What schools really need is already available,
475 people said. From this impulse we started evaluating other Linux
476 distributions that target being used for school networks.&lt;/p&gt;
477
478 &lt;p&gt;At the end we short-listed two approaches and compared them: a
479 commercial Linux distribution developed by a company in Bremen,
480 Germany, and Skolelinux / Debian Edu. Between 12/2010 and 03/2011 we
481 went to several events and met people being responsible for marketing
482 and development of either of the distributions. Skolelinux / Debian
483 Edu was by far much more convincing compared to the other product that
484 got short-listed beforehand--across the full spectrum. What was most
485 attractive for me personally: the perspective of collaboration within
486 the developmental branch of the Debian Edu project itself.&lt;/p&gt;
487
488 &lt;p&gt;In parallel with this, we talked to many local and not-so-local
489 people. People teaching at schools, headmasters, politicians, data
490 protection experts, other IT professionals.&lt;/p&gt;
491
492 &lt;p&gt;We came to two conclusions:&lt;/p&gt;
493
494 &lt;p&gt;First, a technical conclusion: What schools need is available in
495 bits and pieces here and there, and none of the solutions really fit
496 by 100%. Any school we have seen has a very individual IT setup
497 whereas most of each school&#39;s requirements could mapped by a standard
498 IT solution. The requirement to this IT solution is flexibility and
499 customisability, so that individual adaptations here and there are
500 possible. In terms of re-distributing and rolling out such a
501 standardised IT system for schools (a system that is still to some
502 degree customisable) there is still a lot of work to do here
503 locally. Debian Edu / Skolelinux has been our choice as the starting
504 point.&lt;/p&gt;
505
506 &lt;p&gt;Second, a holistic conclusion: What schools need does not exist at
507 all (or we missed it so far). There are several technical solutions
508 for handling IT at schools that tend to make a good impression. What
509 has been missing completely here in Germany, though, is the enrolment
510 of people into using IT and teaching with IT. &quot;IT-Zukunft Schule&quot;
511 tries to provide an approach for this.&lt;/p&gt;
512
513 &lt;p&gt;Only some schools have some sort of a media concept which explains,
514 defines and gives guidance on how to use IT in class. Most schools in
515 Northern Germany do not have an IT service provider, the school&#39;s IT
516 equipment is managed by one or (if the school is lucky) two (admin)
517 teachers, most of the workload these admin teachers get done in there
518 spare time.&lt;/p&gt;
519
520 &lt;p&gt;We were surprised that only a very few admin teachers were
521 networked with colleagues from other schools. Basically, every school
522 here around has its individual approach of providing IT equipment to
523 teachers and students and the exchange of ideas has been quasi
524 non-existent until 2010/2011.&lt;/p&gt;
525
526 &lt;p&gt;Quite some (non-admin) teachers try to avoid using IT technology in
527 class as a learning medium completely. Several reasons for this
528 avoidance do exist.&lt;/p&gt;
529
530 &lt;p&gt;We discovered that no-one has ever taken a closer look at this
531 social part of IT management in schools, so far. On our quest journey
532 for a technical IT solution for schools, we discussed this issue with
533 several teachers, headmasters, politicians, other IT professionals and
534 they all confirmed: a holistic approach of considering IT management
535 at schools, an approach that includes the people in place, will be new
536 and probably a gain for all.&lt;/p&gt;
537
538 &lt;p&gt;&lt;strong&gt;What do you see as the advantages of Skolelinux/Debian
539 Edu?&lt;/strong&gt;&lt;/p&gt;
540
541 &lt;p&gt;There is a list of advantages: international context, openness to
542 any kind of contributions, do-ocracy policy, the closeness to Debian,
543 the different installation scenarios possible (from stand-alone
544 workstation to complex multi-server sites), the transparency within
545 project communication, honest communication within the group of
546 developers, etc.&lt;/p&gt;
547
548 &lt;p&gt;&lt;strong&gt;What do you see as the disadvantages of Skolelinux/Debian
549 Edu?&lt;/strong&gt;&lt;/p&gt;
550
551 &lt;p&gt;Every coin has two sides:&lt;/p&gt;
552
553 &lt;p&gt;Technically: &lt;a href=&quot;http://bugs.debian.org/311188&quot;&gt;BTS issue
554 #311188&lt;/a&gt;, tricky upgradability of a Debian Edu main server, network
555 client installations on top of a plain vanilla Debian installation
556 should become possible sometime in the near future, one could think
557 about splitting the very complex package debian-edu-config into
558 several portions (to make it easier for new developers to
559 contribute).&lt;/p&gt;
560
561 &lt;p&gt;Another issue I see is that we (as Debian Edu developers) should
562 find out more about the network of people who do the marketing for
563 Debian Edu / Skolelinux. There is a very active group in Germany
564 promoting Skolelinux on the bigger Linux Days within Germany. Are
565 there other groups like that in other countries? How can we bring
566 these marketing people together (marketing group A with group B and
567 all of them with the group of Debian Edu developers)? During the last
568 meeting of the German Skolelinux group, I got the impression of people
569 there being rather disconnected from the development department of
570 Debian Edu / Skolelinux.&lt;/p&gt;
571
572 &lt;p&gt;&lt;strong&gt;Which free software do you use daily?&lt;/strong&gt;&lt;/p&gt;
573
574 &lt;p&gt;For my daily business, I do not use commercial software at all.&lt;/p&gt;
575
576 &lt;p&gt;For normal stuff I use Iceweasel/Firefox, Libreoffice.org. For
577 serious text writing I prefer LaTeX. I use gimp, inkscape, scribus for
578 more artistic tasks. I run virtual machines in KVM and Virtualbox.&lt;/p&gt;
579
580 &lt;p&gt;I am one of the upstream developers of X2Go. In 2010 I started the
581 development of a Python based X2Go Client, called PyHoca-GUI.
582 PyHoca-GUI has brought forth a Python X2Go Client API that currently
583 is being integrated in Ubuntu&#39;s software center.&lt;/p&gt;
584
585 &lt;p&gt;For communications I have my own Kolab server running using Horde
586 as web-based groupware client. For IRC I love to use irssi, for Jabber
587 I have several clients that I use, mostly pidgin, though. I am also
588 the Debian maintainer of Coccinella, a Jabber-based interactive
589 whiteboard.&lt;/p&gt;
590
591 &lt;p&gt;My favourite terminal emulator is KDE&#39;s Yakuake.&lt;/p&gt;
592
593 &lt;p&gt;&lt;strong&gt;Which strategy do you believe is the right one to use to
594 get schools to use free software?&lt;/strong&gt;&lt;/p&gt;
595
596 &lt;p&gt;Communicate, communicate, communicate. Enrol people, enrol people,
597 enrol people.&lt;/p&gt;
598 </description>
599 </item>
600
601 <item>
602 <title>SOAP based webservice from Dell to check server support status</title>
603 <link>http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html</link>
604 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html</guid>
605 <pubDate>Fri, 1 Jun 2012 15:20:00 +0200</pubDate>
606 <description>&lt;p&gt;A few years ago I wrote
607 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html&quot;&gt;how
608 to extract support status&lt;/a&gt; for your Dell and HP servers. Recently
609 I have learned from colleges here at the
610 &lt;a href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; that Dell have
611 made this even easier, by providing a SOAP based web service. Given
612 the service tag, one can now query the Dell servers and get machine
613 readable information about the support status. This perl code
614 demonstrate how to do it:&lt;/p&gt;
615
616 &lt;p&gt;&lt;pre&gt;
617 use strict;
618 use warnings;
619 use SOAP::Lite;
620 use Data::Dumper;
621 my $GUID = &#39;11111111-1111-1111-1111-111111111111&#39;;
622 my $App = &#39;test&#39;;
623 my $servicetag = $ARGV[0] or die &quot;Please supply a servicetag. $!\n&quot;;
624 my ($deal, $latest, @dates);
625 my $s = SOAP::Lite
626 -&gt; uri(&#39;http://support.dell.com/WebServices/&#39;)
627 -&gt; on_action( sub { join &#39;&#39;, @_ } )
628 -&gt; proxy(&#39;http://xserv.dell.com/services/assetservice.asmx&#39;)
629 ;
630 my $a = $s-&gt;GetAssetInformation(
631 SOAP::Data-&gt;name(&#39;guid&#39;)-&gt;value($GUID)-&gt;type(&#39;&#39;),
632 SOAP::Data-&gt;name(&#39;applicationName&#39;)-&gt;value($App)-&gt;type(&#39;&#39;),
633 SOAP::Data-&gt;name(&#39;serviceTags&#39;)-&gt;value($servicetag)-&gt;type(&#39;&#39;),
634 );
635 print Dumper($a -&gt; result) ;
636 &lt;/pre&gt;&lt;/p&gt;
637
638 &lt;p&gt;The output can look like this:&lt;/p&gt;
639
640 &lt;p&gt;&lt;pre&gt;
641 $VAR1 = {
642 &#39;Asset&#39; =&gt; {
643 &#39;Entitlements&#39; =&gt; {
644 &#39;EntitlementData&#39; =&gt; [
645 {
646 &#39;EntitlementType&#39; =&gt; &#39;Expired&#39;,
647 &#39;EndDate&#39; =&gt; &#39;2009-07-29T00:00:00&#39;,
648 &#39;Provider&#39; =&gt; &#39;&#39;,
649 &#39;StartDate&#39; =&gt; &#39;2006-07-29T00:00:00&#39;,
650 &#39;DaysLeft&#39; =&gt; &#39;0&#39;
651 },
652 {
653 &#39;EntitlementType&#39; =&gt; &#39;Expired&#39;,
654 &#39;EndDate&#39; =&gt; &#39;2009-07-29T00:00:00&#39;,
655 &#39;Provider&#39; =&gt; &#39;&#39;,
656 &#39;StartDate&#39; =&gt; &#39;2006-07-29T00:00:00&#39;,
657 &#39;DaysLeft&#39; =&gt; &#39;0&#39;
658 },
659 {
660 &#39;EntitlementType&#39; =&gt; &#39;Expired&#39;,
661 &#39;EndDate&#39; =&gt; &#39;2007-07-29T00:00:00&#39;,
662 &#39;Provider&#39; =&gt; &#39;&#39;,
663 &#39;StartDate&#39; =&gt; &#39;2006-07-29T00:00:00&#39;,
664 &#39;DaysLeft&#39; =&gt; &#39;0&#39;
665 }
666 ]
667 },
668 &#39;AssetHeaderData&#39; =&gt; {
669 &#39;SystemModel&#39; =&gt; &#39;GX620&#39;,
670 &#39;ServiceTag&#39; =&gt; &#39;8DSGD2J&#39;,
671 &#39;SystemShipDate&#39; =&gt; &#39;2006-07-29T19:00:00-05:00&#39;,
672 &#39;Buid&#39; =&gt; &#39;2323&#39;,
673 &#39;Region&#39; =&gt; &#39;Europe&#39;,
674 &#39;SystemID&#39; =&gt; &#39;PLX_GX620&#39;,
675 &#39;SystemType&#39; =&gt; &#39;OptiPlex&#39;
676 }
677 }
678 };
679 &lt;/pre&gt;&lt;/p&gt;
680
681 &lt;p&gt;I have not been able to find any documentation from Dell about this
682 service outside the
683 &lt;a href=&quot;http://xserv.dell.com/services/assetservice.asmx?op=GetAssetInformation&quot;&gt;inline
684 documentation&lt;/a&gt;, and according to
685 &lt;a href=&quot;http://iboyd.net/index.php/2012/02/14/updated-dell-warranty-information-script/&quot;&gt;one
686 comment&lt;/a&gt; it can have stability issues, but it is a lot better than
687 scraping HTML pages. :)&lt;/p&gt;
688
689 &lt;p&gt;Wonder if HP and other server vendors have a similar service. If
690 you know of one, drop me an email. :)&lt;/p&gt;
691 </description>
692 </item>
693
694 <item>
695 <title>Veileder fra DIFI om publisering av offentlige data</title>
696 <link>http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html</link>
697 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html</guid>
698 <pubDate>Fri, 1 Jun 2012 10:40:00 +0200</pubDate>
699 <description>&lt;p&gt;På onsdag rakk jeg såvidt innom
700 &lt;a href=&quot;http://www.meetup.com/osloopendata/&quot;&gt;Oslo Open Data Forums&lt;/a&gt;
701 møte, og fikk lagt hendene mine på DIFIs helt nye veileder
702 &quot;&lt;a href=&quot;http://veileder.data.norge.no/&quot;&gt;Åpne data. Del og skap
703 verdier. Veileder i tilgjengeliggjøring av offentlig data&lt;/a&gt;&quot; (også
704 &lt;a href=&quot;http://www.difi.no/filearchive/veileder-i-tilgjengeliggjoring-av-offentlig-data-web.pdf&quot;&gt;tilgjengelig
705 som PDF&lt;/a&gt; fra DIFI).&lt;/p&gt;
706
707 &lt;p&gt;Veilederen er veldig bra, og nevner viktige problemstillinger og
708 skisserer f.eks. både verdiskapningspotensialet og formatmulighetene
709 som en bør ha i bakhodet når en publiserer offentlig informasjon på
710 maskinlesbart format. Kildekoden til veilederen er
711 &lt;a href=&quot;https://github.com/difi/veileder-opnedata&quot;&gt;tilgjengelig via
712 github&lt;/a&gt;, og en kan rapportere tilbakemeldinger og forslag til
713 forbedringer der (eller via epost og twitter for de som ønsker
714 det).&lt;/p&gt;
715
716 &lt;p&gt;Det eneste jeg virkelig savnet i veilederen var omtale av
717 &lt;a href=&quot;http://www.w3.org/DesignIssues/LinkedData.html&quot;&gt;w3cs
718 stjerneklassifisering&lt;/a&gt; av åpne datakilder, som jeg tror ville være
719 nyttige mentale knagger for de som vurderer å publisere sin
720 informasjon på som åpne data. Jeg har
721 &lt;a href=&quot;https://github.com/difi/veileder-opnedata/issues/1&quot;&gt;rapportert
722 en github-bug&lt;/a&gt; om dette, så får vi se hvordan den blir behandlet.&lt;/p&gt;
723
724 &lt;p&gt;Det slo meg at det var veldig lite konkret i veilederen om valg av
725 bruksvilkår ved publisering (aka lisens), men jeg er ikke sikker på om
726 det hører hjemme der, da det er et vanskelig tema som kanskje heller
727 hører hjemme i sin egen veileder. Uansett, anbefaler alle å ta en
728 titt på veilederen og sikre at alle offentlige etater en har kontakt
729 med får en kopi.&lt;/p&gt;
730 </description>
731 </item>
732
733 </channel>
734 </rss>