Generated.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 1a378f7b23eace0f05f2c253c80aaa78b82cf097..09b2e131101252e11822d20b181f7e291c1c1073 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,33 +7,62 @@
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>

-               <title>Oppdatert Noark 5 Tjenestegrenesnitt versjon 1.0 for Noark 5.5.0</title>
-               <link>http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Oppdatert_Noark_5_Tjenestegrenesnitt_versjon_1_0_for_Noark_5_5_0.html</guid>
-                <pubDate>Fri, 5 Jul 2019 17:20:00 +0200</pubDate>
-               <description>&lt;p&gt;Jeg er veldig glad for å kunne fortelle at i går ble ny versjon av
-&lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/noark-standarden/noark-5/tjenestegrensesnitt-noark5&quot;&gt;API-spesifikasjonen
-for Noark 5 Tjenestegrensesnitt&lt;/a&gt; gitt ut.  Det så lenge mørkt ut
-for sjansene for å få inn nødvendige korreksjoner i
-spesifikasjonsteksten innen rimelig tid, men takket være intens og god
-innsats fra Mona og Anne Sofie hos Arkivverket de siste ukene, så ble
-resultatet som ble gitt ut på USAs frigjøringsdag mye bedre enn jeg
-fryktet.&lt;/p&gt;
-
-&lt;p&gt;Spesifikasjonen er
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;tilgjengelig
-som markdown-filer i Arkivverkets github-prosjekt for dette&lt;/a&gt;, og de
-aller fleste av forslagene til forbedringer fra oss som holder på med
-&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;Nikita-prosjektet&lt;/a&gt;
-kom med i denne nye og oppdaterte spesifikasjonsteksten.  Det er
-fortsatt mye som gjenstår før den er entydig, klar og sikrer samvirke
-på tvers av leverandører, men utgangspunktet er veldig mye bedre enn
-forrige versjon fra 2016.  Ta gjerne en titt.&lt;/p&gt;
-
-&lt;p&gt;Ellers må jeg jo si at det var hyggelig å se at min forrige
-bloggpost om tjenestegrensesnittet fikk en
-&lt;a href=&quot;https://beta.arkivverket.no/post/186020592045/noark-5-versjon-50-tjenestegrensesnitt-10&quot;&gt;lenke
-fra Arkivverket Beta&lt;/a&gt;.&lt;/p&gt;
+               <title>Bompenge-Norge, med noen tall fra bompengekalkulator</title>
+               <link>http://people.skolelinux.org/pere/blog/Bompenge_Norge__med_noen_tall_fra_bompengekalkulator.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bompenge_Norge__med_noen_tall_fra_bompengekalkulator.html</guid>
+                <pubDate>Mon, 1 Jun 2020 14:50:00 +0200</pubDate>
+               <description>&lt;p&gt;Det er tett med sensorstasjoner langs veinettet i Norge, som
+registrerer hvilke kjøretøy som passerer eller tar bilde av de som
+drar forbi.  I følge
+&lt;a href=&quot;https://vegkart.atlas.vegvesen.no/&quot;&gt;Vegvesenets nasjonale
+veidatabank (NVDB)&lt;/a&gt;, er det 353 bomstasjoner langs det norske
+veinettet.  21 i nordnorge, 48 i trøndelagsområdet, 13 på
+nordvestlandet, 91 i bergenstraktene og 180 på østlandsområdet.  I
+tillegg finnes det et utall overvåkningskamera og noen titalls
+RFID-avlesere for bompengebrikker som samler inn informasjon om hvilke
+biler som befinner seg hvor i landet.  For ikke å glemme alle
+mobilbasestasjoner som registrerer hvor brukere av mobilnettverket
+befinner seg.  De er ikke tema i dag.&lt;/p&gt;
+
+&lt;p&gt;De som kjører mye har interesse av å vite hvor mye bompenger det vil
+koste å kjøre fra et sted til et annet, og dette behovet har aktørene
+bak &lt;a href=&quot;https://bompengekalkulator.no/&quot;&gt;Bompengekalkulatoren&lt;/a&gt;
+tatt sikte på å tilby i markedet.  Fornuftig nok har de også en
+gratistjeneste, slik at de får frivillige til å gi innspill om feil i
+datagrunnlaget.  Jeg ble nylig nysgjerring på hvor mye det til koste å
+kjøre på kryss og tvers i Norge, og valgte meg ut en teststrekning fra
+Oslo til Tromsø for å se hvilke beløp som gjelder.&lt;/p&gt;
+
+&lt;p&gt;Bompengekalkulatoren viser frem flere rutealternativer for et gitt
+reisesøk, og i dette tilfellet, for reise fra Oslo Sentralstasjon til
+Tromsø sentrum, viser den tre alternativ.  Merk, disse tallene gjelder
+bensindrevet personbil.  En kan velge takstkategori i
+webgrensesnittet.  Det ene rutealternativet er E6 gjennom Norge, de to
+andre er E45 og E4 gjennom sverige.  E45 er innlandsruten i Sverige,
+motorvei gjennom store skoger som i følge kalkulatoren skal ta 22
+timer og 26 minutter med norsk bompengebeløp på 164 kroner.  Jeg har
+mine tvil til om datasettet til Bompengekalkulatoren har svenske
+bomstasjoner, så ta dette beløpet med en klype salt.  E4 er veien
+langs Bottenviken og mer befolket område, og skal ta 22 timer og 50
+minutter til en norsk bompengebeløp på 71 kroner.  Den norske ruten
+langs E6 skal derimot ta 23 timer og 16 minutter og beløpe seg til 664
+kroner.  Beløpene er uten autopass-brikke, slik at en slipper å få
+bilens posisjon registrert i alle bompengeavleserne som ikke også er
+bomstasjoner.  For trailere er bompengekostnaden 2-3 ganger så høy som
+for personbil.  I tillegg til pengebeløpet, som faktureres
+etterskuddsvis og de siste årene har blitt umulig å gjøre opp kontant
+på stedet, så kommer kostnaden med å få sine personopplysninger samlet
+inn, lagret og gjort tilgjengelig for fremmede på ubestemt tid.  Jeg
+ser på den kostnaden som mye høyere en pengebeløpet som
+faktureres.&lt;/p&gt;
+
+&lt;p&gt;For en tilsvarende tur fra Oslo til Bergen, så forteller
+kalkulatoren at raskeste vei er riksvei 7 på 7 timer 4 minutter med
+bompengebeløp 409 kroner.  Alternativene listet opp er E134 på 8 timer
+37 minutter med bompengebeløp 318 kroner og fylkesivei 40 på 7 timer
+30 minutter med beløp 331.  Det kan kanskje være greit å sjekke ut før
+en setter seg i bilen hvor ens personopplysninger vil bli samlet inn
+og lagret 5 fem år, når en velger hvilken rute en går for.&lt;/p&gt;

 
 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
 
 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner


@@ -44,39 +73,31 @@ Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Teach kids to protect their privacy - the EDRi way</title>
-               <link>http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teach_kids_to_protect_their_privacy___the_EDRi_way.html</guid>
-                <pubDate>Thu, 4 Jul 2019 19:10:00 +0200</pubDate>
-               <description>&lt;p&gt;Childs need to learn how to guard their privacy too.  To help them,
-&lt;a href=&quot;https://edri.org/&quot;&gt;European Digital Rights (EDRi)&lt;/a&gt; created
-a colorful booklet providing information on several privacy related topics,
-and tips on how to protect ones privacy in the digital age.&lt;/p&gt;
-
-&lt;p&gt;The 24 page booklet titled Digital Defenders is
-&lt;a href=&quot;https://edri.org/digital-defenders-help-kids-defend-their-privacy-around-europe&quot;&gt;available
-in several languages&lt;/a&gt;.  Thanks to the valuable contributions from
-members of &lt;a href=&quot;https://efn.no/&quot;&gt;the Electronic Foundation Norway
-(EFN)&lt;/a&gt; and others, it is also available in Norwegian Bokmål.
-If you would like to have it available in your language too,
-&lt;a href=&quot;https://hosted.weblate.org/projects/efn/privacy4kids/&quot;&gt;contribute
-via Weblate&lt;/a&gt; and get in touch.&lt;/p&gt;
-
-&lt;p&gt;But a funny, well written and good looking PDF do not have much
-impact, unless it is read by the right audience.  To increase the
-chance of kids reading it, I am currently assisting EFN in getting
-copies printed on paper to distribute on the street and in class
-rooms.  Print the booklet was made possible thanks to a small et of
-great sponsors.  Thank you very much to each and every one of them!  I
-hope to have the printed booklet ready to hand out on Tuesday, when
-&lt;a href=&quot;https://www.nuug.no/&gt;&quot;&gt;the Norwegian Unix Users Group&lt;/a&gt; is
-organizing &lt;a href=&quot;https://wiki.nuug.no/sommerfest2019&quot;&gt;its yearly
-barbecue for geeks and free software zealots in the Oslo area&lt;/a&gt;.  If
-you are nearby, feel free to come by and check out the party and the
-booklet.&lt;/p&gt;
-
-&lt;p&gt;If the booklet prove to be a success, it would be great to get
-more sponsoring and distribute it to every kid in the country. :)&lt;/p&gt;
+               <title>More reliable vlc bittorrent plugin in Debian (version 2.9)</title>
+               <link>http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_reliable_vlc_bittorrent_plugin_in_Debian__version_2_9_.html</guid>
+                <pubDate>Sun, 24 May 2020 17:00:00 +0200</pubDate>
+               <description>&lt;p&gt;I am very happy to report that a more reliable
+&lt;a href=&quot;https://tracker.debian.org/pkg/vlc-plugin-bittorrent&quot;&gt;VLC
+bittorrent plugin&lt;/a&gt; was just uploaded into debian.  This fixes a
+couple of crash bugs in the plugin, hopefully making the VLC
+experience even better when streaming directly from a bittorrent
+source.  The package is currently in Debian unstable, but should be
+available in Debian testing in two days.  To test it, simply install
+it like this:&lt;/p&gt;
+
+&lt;p&gt;&lt;pre&gt;
+apt install vlc-plugin-bittorrent
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;After it is installed, you can try to use it to play a file
+downloaded live via bittorrent like this:
+
+&lt;p&gt;&lt;pre&gt;
+vlc https://archive.org/download/Glass_201703/Glass_201703_archive.torrent
+&lt;/pre&gt;&lt;/p&gt;
+
+&lt;p&gt;It also support magnet links and local .torrent files.&lt;/p&gt;

 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address


@@ -85,289 +106,227 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Nikita og Noark 5 tjenestegrensesnittet tilbyr ny måte å tenke arkivering</title>
-               <link>http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_og_Noark_5_tjenestegrensesnittet_tilbyr_ny_m_te___tenke_arkivering.html</guid>
-                <pubDate>Fri, 21 Jun 2019 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;em&gt;av Thomas Sødring (OsloMet) og Petter Reinholdtsen (foreningen
-NUUG)&lt;/em&gt;&lt;/p&gt;
-
-&lt;p&gt;Nikita Noark 5-kjerne er et fri programvareprosjekt som tar i bruk
-Arkivverkets spesifikasjonen for Noark 5 Tjenestegrensesnitt og tilbyr
-et maskinlesbart grensesnitt (arkiv-API) til datasystemer som trenger å
-arkivere dokumenter og informasjon.  I tillegg tilbyr Nikita et
-nettleserbasert brukergrensesnitt for brukere av arkivet.  Dette
-brukergrensesnittet benytter det maskinlesbare grensesnittet.  Noark 5
-Tjenestegrensesnitt er en ny måte å tenke arkivering, med fokus på
-automatisering og maskinell behandling av arkivmateriale, i stedet for
-å fokusere på brukergrensesnitt.  En kan tenke på
-tjenestegrensesnittet som arkivet uten brukergrensesnitt, der flere
-aktører kan koble til ulike brukergrensesnitt, tilpasset ulike
-behov.&lt;/p&gt;
-
-&lt;p&gt;Historisk sett gjorde Noark standarden en veldig bra jobb med
-overgangen fra
-papir til digital saksbehandling, men det har kommet til kort på andre
-områder. Den teknologiske utviklingen har brakt oss ditt at vi kan og
-skal forvente langt mer fra en arkivkjerne enn før, men det offentlig
-er ofte konservativ når det gjelder nytenking. For lengst skulle
-begreper som samvirke mellom datasystemer, metadata, prosess og
-tjenestegrensesnitt (API) vært dominerende når systemer kjøpes
-inn. Dessverre er det slik at ikke alle ønsker samvirke mellom
-datasystemer velkommen, og det kan være trygt å kjøpe «svarte bokser»
-der du slipper å ta stilling til hvordan man skal få flere systemer
-til å virke sammen. Men IT-arkitektur er et begrep arkivfolk også
-begynner å ta inn over seg.&lt;/p&gt;
-
-&lt;p&gt;Slike systemer for å organisere metadata bør ha nettbaserte
-tjenestegrensesnitt der brukergrensesnitt er tydelig adskilt fra
-bakenforliggende system. Det finnes mange rapporter som snakker om å
-bryte ned siloer i forvaltningen og standardiserte tjenestegrensesnitt
-er det viktigste virkemiddel mot datasiloer og legger til rette for
-økt samvirke mellom systemer. Et standardisert tjenestegrensesnitt er
-et viktig middel for å få systemer til å samhandle da det sikrer at
-ulike produsenters systemer kan snakke sammen på tvers. Samfunnet
-fungerer ikke uten standardisering. Vi har alle samme strømstyrke og
-kontakter i veggene og kjører alle på høyre side av veien i Norge.  Det er i en slik
-sammenheng at prosjektet «Noark 5 Tjenestegrensesnitt» er veldig
-viktig. Hvis alle leverandører av arkivsystemer forholdt seg til et
-standardisert tjenestegrensesnitt kunne kostnadene for arkivering
-reduseres.  Tenk deg at du er en kommune som ønsker et fagsystem integrert
-med arkivløsningen din. I dag må fagsystemleverandøren vite og
-tilpasse seg den spesifikke versjonen og varianten av arkivløsningen
-du har. Hvis vi antar at alle leverandører av arkivkjerner har solgt
-inn enten SOAP eller REST-grensesnitt til kunder de siste 10 årene og
-det kommer endret versjon av grensesnittet innimellom, så gir det
-veldig mange forskjellige tjenestegrensesnitt en fagsystemleverandør
-må forholde seg til. Med 12 leverandører og kvartalsvise oppdateringer
-kan det potensielt bli 96 ulike varianter hvert eneste år.  Det sier
-seg selv at det blir dyrt. Men det blir faktisk verre. Hvis du senere
-ønsker å bytte ut arkivsystemet med et annet så er du avhengig å få
-alle integrasjonene dine laget på nytt. Dette kan gjøre at du velger å
-forbli hos en dårlig leverandør framfor å skaffe nytt system, fordi
-det blir for vanskelig og dyrt å bytte. Dermed etableres det «små»
-monopolsituasjoner som er vanskelig å bryte ut av. Dårlige valg i dag
-kan ha uante kostander på sikt. I Nikita-prosjektet har vi kun jobbet
-opp mot Noark 5 Tjenestegrensesnittet.  Det har tatt en god del
-ressurser å sette seg inn i spesifikasjonen og ta den i bruk, spesielt
-på grunn av uklarheter i spesifikasjonen. Hvis vi måtte gjøre det
-samme for alle versjoner og varianter av de forskjellige
-tjenestegrensesnittene ville det blitt veldig tidkrevende og
-kostbart.&lt;/p&gt;
-
-&lt;p&gt;For deg som arkivar er digitalisering og systemer som skal virke
-sammen en del av den nye hverdagen. Du har kanskje blitt skånet for
-det ved å kjøpe svarte bokser, men du risikerer at du gjør deg selv en
-bjørnetjeneste. Det kan oppleves som kjedelig å fortelle kolleger at
-du skal sette deg inn i et tjenestegrensesnitt, men dette er faktisk
-veldig spennende. Tjenestegrensesnittet er på en måte blitt levende og
-det er spesielt et begrep du bør merke deg: OData.  Å trekke inn deler
-av OData-standarden som en måte å filtrere entitetsøk i et arkivsystem
-var et nyttig trekk i prosjektet.  Følgende eksempel er en
-OData-spørring det går an å sende inn til en standardisert
-arkivkjerne:&lt;/p&gt;
+               <title>Debian Edu interview: Yvan Masson</title>
+               <link>http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Yvan_Masson.html</guid>
+                <pubDate>Tue, 12 May 2020 06:30:00 +0200</pubDate>
+               <description>&lt;p&gt;It has been way too long since my last interview, but as the
+&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt;
+community is still active, and new people keep showing up on the IRC
+channel &lt;a href=&quot;irc://irc.debian.org/#debian-edu&quot;&gt;#debian-edu&lt;/a&gt; and
+&lt;a href=&quot;https://lists.debian.org/debian-edu/&quot;&gt;the debian-edu mailing
+list&lt;/a&gt;, I decided to give it another go.  I was hoping someone else
+might pick up the idea and run with it, but this has not happened as
+far as I can tell, so here we are… This time the announcement of a new
+free software tool to
+&lt;a href=&quot;https://framagit.org/Yvan-Masson/WhosWho&quot;&gt;create a school year
+book&lt;/a&gt; triggered my interest, and I decided to learn more about its
+author.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Who are you, and how do you spend your days?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;My name is Yvan MASSON, I live in France. I have my own one person
+business in computer services.  The work consist of visiting my
+customers (person&#39;s home, local authority, small business) to give
+advise, install computers and software, fix issues, and provide
+computing usage training.  I spend the rest of my time enjoying my
+family and promoting free software.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;What is your approach for promoting free
+software?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;When I think that free software could be suitable for someone, I
+explain what it is, with simple words, give a few known examples, and
+explain that while there is no fee it is a viable alternative in many
+situations. Most people are receptive when you explain how it is
+better (I simplify arguments here, I know that it is not so simple):
+Linux works on older hardware, there are no viruses, and the software
+can be audited to ensure user is not spied upon. I think the most
+important is to keep a clear but moderated speech: when you try to
+convince too much, people feel attacked and stop listening.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;How did you get in contact with the Skolelinux / Debian Edu
+project?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;I can not remember how I first heard of Skolelinux / Debian Edu,
+but probably on planet.debian.org. As I have been working for a
+school, I have interest in this type of project.
+
+&lt;p&gt;The school I am involved in is a school for &quot;children&quot; between 14
+and 18 years old.  The French government has recommended free software
+since 2012, but they do not always use free software themselves.  The
+school computers are still using the Windows operating system, but all
+of them have the classic set of free software: Firefox ESR,
+LibreOffice (with the excellent extension Grammalecte that indicates
+French grammatical errors), SumatraPDF, Audacity, 7zip, KeePass2, VLC,
+GIMP, Inkscape…
+
+&lt;p&gt;&lt;strong&gt;What do you see as the advantages of Skolelinux / Debian
+Edu?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;It is free software! Built on Debian, I am sure that users are not
+spied upon, and that it can run on low end hardware.  This last point
+is very important, because we really need to improve &quot;green IT&quot;.  I do
+not know enough about Skolelinux / Debian Edu to tell how it is better
+than another free software solution, but what I like is the &quot;all in
+one&quot; solution: everything has been thought of and prepared to ease
+installation and usage.&lt;/p&gt;
+
+&lt;p&gt;I like Free Software because I hate using something that I can not
+understand. I do not say that I can understand everything nor that I
+want to understand everything, but knowing that someone / some company
+intentionally prevents me from understanding how things work is really
+unacceptable to me.&lt;/p&gt;
+
+&lt;p&gt;Secondly, and more importantly, free software is a requirement to
+prevent abuses regarding human rights and environmental care.
+Humanity can not rely on tools that are in the hands of small group of
+people.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;What do you see as the disadvantages of Skolelinux / Debian
+Edu?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;Again, I don&#39;t know this project enough. Maybe a dedicated website?
+Debian wiki works well for documentation, but is not very appealing to
+someone discovering the project. Also, as Skolelinux / Debian Edu uses
+OpenLDAP, it probably means that Windows workstations cannot use
+centralized authentication. Maybe the project could use Samba as an
+Active Directory domain controller instead, allowing Windows desktop
+usage when necessary.&lt;/p&gt;
+
+&lt;p&gt;(Editors note: In fact Windows workstations can
+&lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Buster/HowTo/Samba&quot;&gt;use
+the centralized authentication in a Debian Edu setup&lt;/a&gt;, at least for
+some versions of Windows, but the fact that this is not well known can
+be seen as an indication of the need for better documentation and
+marketing. :)&lt;/p&gt;
+     
+&lt;p&gt;&lt;strong&gt;Which free software do you use daily?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;Nothing original: Debian testing/sid with Gnome desktop, Firefox,
+Thunderbird, LibreOffice…&lt;/p&gt;
+     
+&lt;p&gt;&lt;strong&gt;Which strategy do you believe is the right one to use to
+get schools to use free software?&lt;/strong&gt;&lt;/p&gt;
+
+&lt;p&gt;Every effort to spread free software into schools is important,
+whatever it is. But I think, at least where I live, that IT
+professionals maintaining schools networks are still very &quot;Microsoft
+centric&quot;.  Schools will use any working solution, but they need people
+to install and maintain it.  How to make these professionals sensitive
+about free software and train them with solutions like Debian Edu /
+Skolelinux is a really good question :-)&lt;/p&gt;
+</description>
+       </item>
+       
+       <item>
+               <title>Jami as a Zoom client, a trick for password protected rooms...</title>
+               <link>http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
+                <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
+               <description>&lt;p&gt;Half a year ago,
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
+wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
+client&lt;/a&gt;, capable of peer-to-peer encrypted communication.  It
+handle both messages, audio and video.  It uses distributed hash
+tables instead of central infrastructure to connect its users to each
+other, which in my book is a plus.  I mentioned briefly that it could
+also work as a SIP client, which came in handy when the higher
+educational sector in Norway started to promote Zoom as its video
+conferencing solution.  I am reluctant to use the official Zoom client
+software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
+license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
+to check the security) and benchmark it, and thus prefer to connect to
+Zoom meetings with free software clients.&lt;/p&gt;
+
+&lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
+password set on the room.  The Jami daemon leak memory like crazy
+(approximately 1 GiB a minute) when I am connected to the video
+conference, so I had to restart the client every 7-10 minutes, which
+is not a great.  I tried to get other SIP Linux clients to work
+without success, so I decided I would have to live with this wart
+until someone managed to fix the leak in the dring code base.  But
+another problem showed up once the rooms were password protected.  I
+could not get my dial tone signaling through from Jami to Zoom, and
+dial tone signaling is used to enter the password when connecting to
+Zoom.  I tried a lot of different permutations with my Jami and
+Asterisk setup to try to figure out why the signaling did not get
+through, only to finally discover that the fundamental problem seem to
+be that Zoom is simply not able to receive dial tone signaling when
+connecting via SIP.  There seem to be nothing wrong with the Jami and
+Asterisk end, it is simply broken in the Zoom end.  I got help from a
+very skilled VoIP engineer figuring out this last part.  And being a
+very skilled engineer, he was also able to locate a solution for me.
+Or to be exact, a workaround that solve my initial problem of
+connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
+
+&lt;p&gt;So, how do you do this, I am sure you are wondering by now.  The
+trick is already
+&lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
+from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
+password.  What is most surprising about this is that the
+automatically generated email from Zoom with instructions on how to
+connect via SIP do not mention this.  The SIP address to use normally
+consist of the room ID (a number), an @ character and the IP address
+of the Zoom SIP gateway.  But Zoom understand a lot more than just the
+room ID in front of the at sign.  The format is &quot;&lt;tt&gt;[Meeting
+ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can hear see how you
+can both enter password, control the layout (full screen, active
+presence and gallery) and specify the host key to start the meeting.
+The full SIP address entered into Jami to provide the password will
+then look like this (all using made up numbers):&lt;/p&gt;

 
 &lt;p&gt;&lt;blockquote&gt;
 
 &lt;p&gt;&lt;blockquote&gt;

-.../sakarkiv/journalpost?filter=contains(tittel, &#39;nabovarsel&#39;)
+&lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;

 &lt;/blockquote&gt;&lt;/p&gt;
 
 &lt;/blockquote&gt;&lt;/p&gt;
 

-&lt;p&gt;Spørringen over vil hente en liste av alle dine journalposter der
-tittelen til journalposten inneholder ordet &#39;nabovarsel&#39;. Alle
-leverandører som implementerer tjenestegrensesnittet vil måtte tilby
-dette.  Det betyr at hvis du lærer dette språket for et system, vil det
-være gjeldende for alle. Dette er egentlig en ny måte å søke i
-arkivdatabasen på og vil være svært nyttig, for eksempel kan søk i
-tjenestegrensesnittet antagelig brukes til å hente ut offentlig
-postjournal. I arkivverden pleier vi å like teknologier som er
-menneskelesbart, da vet vi det er enkelt og nyttig! OData er også
-viktig fordi det kan bli en ny måte å svare innsynsforespørsler på i
-tråd med offentlighetsloven § 9, der retten til å kreve innsyn i
-sammenstilling fra databaser er nedfelt. I dag ser vi
-forvaltningsorganer som avviser slike krav fordi det «ikke kan gjøres
-med enkle framgangsmåter». Bruken av OData i tjenestegrensesnittet,
-sammen med maskinlesbar markeringsformater kan være et viktig bidrag
-til å åpne arkivene i tråd med prinsippene om en åpen og transparent
-forvaltning.&lt;/p&gt;
-
-&lt;p&gt;Standardisering er viktig fordi det &lt;em&gt;kan&lt;/em&gt; sikre samvirke.
-Men den effekten kommer kun hvis standardiseringen sikrer at alle
-forstår standarden på samme måte, dvs. at den er entydig og klar.  En
-god måte å sikre en entydig og klar spesifikasjon er ved å kreve at
-det finnes minst to ulike implementasjoner som følger spesifikasjonen
-og som kan snakke sammen, det vil si at de snakker samme språk, slik
-IETF krever for alle sine standarder, før spesifikasjonen anses å være
-ferdig. Tilbakemelding fra miljøet forteller at både leverandører og
-kunder har et avslappet forhold til Noark 5 Tjenestegrensesnitt og det
-er så langt kun Evry som har visst offentlig at de har en
-implementasjon av tjenestegrensesnittet.  Evry, HK Data og Fredrikstad
-kommune er igang med et pilotprosjekt på Noark 5
-Tjenestegrensesnitt. For å redusere kostnadene for samvirkende
-datasystemer betraktelig, er det veldig viktig at vi kommer i en
-situasjon der alle leverandører har sine egne implementasjoner av
-tjenestegrensesnittet, og at disse oppfører seg likt og i tråd med det
-som er beskrevet i spesifikasjonen.&lt;/p&gt;
-
-&lt;p&gt;Det er her fri programvare spiller en viktig rolle. Med en uklar
-standard blir det som en polsk riksdag, der ingenting fungerer. Nikita
-er en fri programvareimplementasjon av tjenestegrensesnitt og kan
-fungere som teknisk referanse slik at leverandører enklere kan se og
-forstå hvordan standarden skal tolkes. Vi har i Nikitaprosjektet
-erfart å ende opp med vidt forskjellige tolkninger når
-prosjektmedlemmene leser spesifikasjonsteksten, en effekt av en uklar
-spesifikasjon. Men Nikitaprosjektet har også utviklet et test-program
-som sjekker om et tjenestegrensesnitt er i samsvar med standarden, og
-prosjektet bruker det hele tiden for å sikre at endringer og
-forbedringer fungerer. Egenerklæringsskjemaenes dager kan være talte!
-Snart vil du selv kunne teste hver oppdatering av arkivsystemet med en
-uavhengig sjekk.&lt;/p&gt;
-
-&lt;p&gt;Fri programvare representerer en demokratisering av kunnskap der
-tolkning- og innlåsingsmakt flyttes fra leverandør til allmenheten.
-Med fri programvare har du en litt annerledes verdikjede, der selve
-produktet ikke holdes hemmelig for å tjene penger, slik en gjør med
-ufri programvare og skytjenester som ikke bruker fri programvare, men
-du kan tjene penger på andre deler av verdikjeden. Med fri programvare
-kan samfunnet betale for å videreutvikle nyttig
-fellesfunksjonalitet.&lt;/p&gt;
-
-&lt;p&gt;Nikita er en fri programvareimplementasjon av tjenestegrensesnittet og
-kan fungere som en referanseimplementasjon dersom det er ønskelig.
-Alle har lik tilgang til koden og det koster ingenting å ta den i bruk
-og utforske det. Nikitaprosjektet ønsker tjenestegrensesnittet
-velkommen og stiller veldig gjerne opp i diskusjoner om tolkning av
-tjenestegrensesnittet. Nikita er bygget på moderne
-programmeringsrammeverk og utviklet i full åpenhet. Men Nikita er ikke
-noe du kan kjøpe. Nikita er først og fremst et verktøy for forsking og
-utvikling laget for å fremme forskning på arkivfeltet.  Systemer som
-virker sammen har alltid vært hovedfokus og vil være det fremover.
-Det brukes som undervisningsverktøy der studentene ved OsloMet lærer
-om administrativt oppsett, saksbehandling, uttrekk og samvirkende
-datasystemer.  Det brukes også som forskningsobjekt der vi ser på
-import av dokumentsamlinger, bruk av blokkjede og andre nyskapende
-måter å tenke arkiv på. Det er dog helt greit om andre tar Nikita og
-pakker det for å selge det som produkt.  Forvaltningsorganer med
-sterke drift- og utviklingsmiljøer kan også se på Nikita og utforske
-hva som er mulig. Dette kan de gjøre uten å måtte betale for
-bruksrettigheter eller tilgang til konsulenter.  Men arkivering blir
-ikke gratis på grunn av Nikita.  Det trengs fortsatt folk med
-kompetanse og tid til å ta i bruk Nikita.&lt;/p&gt;
-
-&lt;p&gt;Nikita har nylig kommet med en ny utgave, den sjette i rekken.
-Systemet er ikke ferdig, mest på grunn av at API-spesifikasjonen for
-Noark 5 Tjenestegrensesnitt ikke er ferdig, men allerede i dag kan en
-bruke Nikita som arkiv.  Vi har laget eksempelsystem for å importere
-data fra deponi-XML og slik gjøre eksisterende arkivdata tilgjengelig
-via et API.  Vi har også laget en testklient som importerer epost inn
-i arkivet med vedlegg der epostenes trådinformasjon brukes til å legge
-eposttråder i samme arkivmappe, og en annen testklient som henter
-epost ut av en arkivmappe på mbox-format slik at en vanlig epostklient
-kan brukes til å lese igjennom og svare på epostene i en
-arkivmappe. De som vil ta en titt på Nikita kan besøke
-&lt;a href=&quot;https://nikita.oslomet.no&quot;&gt;https://nikita.oslomet.no&lt;/a&gt; og
-logge inn med brukernavn «admin@example.com» og passord «password».
-Dette gir tilgang til det forenklede brukergrensesnittet som brukes
-til undervisning.  De som heller vil ta en titt under panseret kan
-besøke
-&lt;a href=&quot;https://nikita.oslomet.no/browse.html&quot;&gt;https://nikita.oslomet.no/browse.html&lt;/a&gt;
-og der se hvordan API-et fungerer mer i detalj.  Innloggingsdetaljer
-her er det samme som for brukergrensesnittet.&lt;/p&gt;
-
-&lt;p&gt;Fremover er fokuset på forbedring av spesifikasjonen Noark 5
-Tjenestegrensesnitt. De som skrev tjenestegrensesnittet gjorde et
-interessant og framtidsrettet grep, de skilte sak fra arkiv.
-Tjenestegrensesnittet består av flere &quot;pakker&quot;, der noen er
-grunnleggende mens andre bygger på de grunnleggende pakkene. Pakkene
-som er beskrevet så langt heter «arkivstruktur», «sakarkiv»,
-«administrasjon», «loggogsporing» og «moeter» (dessverre
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pull/120&quot;&gt;planlagt
-fjernet&lt;/a&gt; i første utgave).  Etter hvert håper vi å utforske
-prosses- og metadatabeskrivelser til flere fagområder og bidra til at
-tjenestegrensesnittet kan legge til flere pakker som «byggarkiv»,
-«barnevern», «personal», «barnehage», der arkivfaglig metadata- og
-dokumentasjonsbehov er kartlagt og standardisert.&lt;/p&gt;
-
-&lt;p&gt;Nikita utvikles av en liten prosjektgruppe, og vi er alltid
-interessert å bli flere. Hvis en åpen, fri og standardisert tilnærming
-til arkivering høres interessant ut, bli med oss på veien videre.  Vi
-er tilstede på IRC-kanalen #nikita hos FreeNode (tilgjengelig via
-nettleser på
-&lt;a href=&quot;https://webchat.freenode.net?channels=#nikita&quot;&gt;https://webchat.freenode.net?channels=#nikita&lt;/a&gt;),
-og har en e-postliste nikita-noark@nuug.no hos NUUG (tilgjengelig for
-påmelding og arkiv på
-&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;https://lists.nuug.no/mailman/listinfo/nikita-noark&lt;/a&gt;)
-der en kan følge med eller være med oss på den spennende veien videre.
-Spesifikasjonen for Noark 5 Tjenestegrensesnitt vedlikeholdes på
-github,
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Now if only jami would reduce its memory usage, I could even
+recommend this setup to others. :)&lt;/p&gt;

 
 

-&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
-det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
-til min adresse
+&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
+activities, please send Bitcoin donations to my address

 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 </description>
        </item>
        
        <item>
 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 </description>
        </item>
        
        <item>

-               <title>Jami/Ring, finally functioning peer to peer communication client</title>
-               <link>http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
-                <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
-               <description>&lt;p&gt;Some years ago, in 2016, I
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;wrote
-for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
-It would provide messaging without any central server coordinating the
-system and without requiring all users to register a phone number or
-own a mobile phone.  Back then, I could not get it to work, and put it
-aside until it had seen more development.  A few days ago I decided to
-give it another try, and am happy to report that this time I am able
-to not only send and receive messages, but also place audio and video
-calls.  But only if UDP is not blocked into your network.&lt;/p&gt;
-
-&lt;p&gt;The Ring system changed name earlier this year to
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;.  I
-tried doing web search for &#39;ring&#39; when I discovered it for the first
-time, and can only applaud this change as it is impossible to find
-something called Ring among the noise of other uses of that word.  Now
-you can search for &#39;jami&#39; and this client and
-&lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
-least on duckduckgo.&lt;/p&gt;
-
-&lt;p&gt;Jami will by default encrypt messages as well as audio and video
-calls, and try to send them directly between the communicating parties
-if possible.  If this proves impossible (for example if both ends are
-behind NAT), it will use a central SIP TURN server maintained by the
-Jami project.  Jami can also be a normal SIP client.  If the SIP
-server is unencrypted, the audio and video calls will also be
-unencrypted.  This is as far as I know the only case where Jami will
-do anything without encryption.&lt;/p&gt;
-
-&lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
-Android, iOS, and Android TV.  It is included in Debian already.  Jami
-also work for those using F-Droid without any Google connections,
-while Signal do not.
-&lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
-protocol&lt;/a&gt; is described in the Ring project wiki.  The system uses a
-distributed hash table (DHT) system (similar to BitTorrent) running
-over UDP.  On one of the networks I use, I discovered Jami failed to
-work.  I tracked this down to the fact that incoming UDP packages
-going to ports 1-49999 were blocked, and the DHT would pick a random
-port and end up in the low range most of the time.  After talking to
-the developers, I solved this by enabling the dhtproxy in the
-settings, thus using TCP to talk to a central DHT proxy instead of
-
-peering directly with others.  I&#39;ve been told the developers are
-working on allowing DHT to use TCP to avoid this problem.  I also ran
-into a problem when trying to talk to the version of Ring included in
-Debian Stable (Stretch).  Apparently the protocol changed between
-beta2 and the current version, making these clients incompatible.
-Hopefully the protocol will not be made incompatible in the
-future.&lt;/p&gt;
-
-&lt;p&gt;It is worth noting that while looking at Jami and its features, I
-came across another communication platform I have not tested yet.  The
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
-and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;.  It might
-become the topic of a future blog post.&lt;/p&gt;
+               <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
+               <link>http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
+                <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
+               <description>&lt;p&gt;The curiosity got the better of me when
+&lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
+reported&lt;/a&gt; that New Jersey was desperately looking for
+&lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
+and a few days later it was reported that
+&lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
+tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;I thus decided to have a look at free software alternatives to
+learn COBOL, and had the pleasure to find
+&lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
+already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
+Debian&lt;/a&gt;.  It used to be called Open Cobol, and is a &quot;compiler&quot;
+transforming COBOL code to C or C++ before giving it to GCC or Visual
+Studio to build binaries.&lt;/p&gt;
+
+&lt;p&gt;I managed to get in touch with upstream, and was impressed with the
+quick response, and also was happy to see a new Debian maintainer
+taking over when the original one recently asked to be replaced.  A
+new Debian upload was done as recently as yesterday.&lt;/p&gt;
+
+&lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
+introduction and make and run simple COBOL programs.  It was fun to
+learn a new programming language.  If you want to test for yourself,
+&lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
+page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
+
+&lt;p&gt;As I do not have much experience with COBOL, I do not know how
+standard compliant it is, but it claim to pass most tests from COBOL
+test suite, which sound good to me.  It is nice to know it is possible
+to learn COBOL using software without any usage restrictions, and I am
+very happy such nice free software project as this is available.  If
+you as me is curious about COBOL, check it out.&lt;/p&gt;

 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address


@@ -376,247 +335,160 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>More sales number for my Free Culture paper editions (2019-edition)</title>
-               <link>http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_sales_number_for_my_Free_Culture_paper_editions__2019_edition_.html</guid>
-                <pubDate>Tue, 11 Jun 2019 16:05:00 +0200</pubDate>
-               <description>&lt;p&gt;The first book I published,
-&lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free Culture by Lawrence
-Lessig&lt;/a&gt;, is still selling a few copies.  Not a lot, but enough to
-have contributed slightly over $500 to the &lt;a
-href=&quot;https://creativecommons.org/&quot;&gt;Creative Commons Corporation&lt;/a&gt;
-so far.  All the profit is sent there. Most books are still sold via
-Amazon (83 copies), with Ingram second (49) and Lulu (12) and Machette (7) as
-minor channels.  Bying directly from Lulu bring the largest cut to
-Creative Commons.  The English Edition sold 80 copies so far, the
-French 59 copies, and Norwegian only 8 copies.  Nothing impressive,
-but nice to see the work we put down is still being appreciated.  The
-ebook edition is available for free from
-&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
-
-&lt;table border=&quot;0&quot;&gt;
-&lt;tr&gt;&lt;th rowspan=&quot;2&quot; valign=&quot;bottom&quot;&gt;Title / language&lt;/th&gt;
-&lt;th colspan=&quot;7&quot;&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;
-&lt;th&gt;2016 jan-jun&lt;/th&gt;
-&lt;th&gt;2016 jul-dec&lt;/th&gt;
-&lt;th&gt;2017 jan-jun&lt;/th&gt;
-&lt;th&gt;2017 jul-dec&lt;/th&gt;
-&lt;th&gt;2018 jan-jun&lt;/th&gt;
-&lt;th&gt;2018 jul-dec&lt;/th&gt;
-&lt;th&gt;2019 jan-may&lt;/th&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;19&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;11&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;1&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;27&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;16&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;9&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;tr&gt;
-  &lt;td&gt;Total&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;24&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;34&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;35&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;20&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;10&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;13&lt;/td&gt;
-  &lt;td align=&quot;right&quot;&gt;10&lt;/td&gt;
-&lt;/tr&gt;
-
-&lt;/table&gt;
-
-&lt;p&gt;It is fun to see the French edition being more popular than the
-English one.&lt;/p&gt;
-
-&lt;p&gt;If you would like to translate and publish the book in your native
-language, I would be happy to help make it happen.  Please get in
-touch.&lt;/p&gt;
-</description>
-       </item>
-       
-       <item>
-               <title>Official MIME type &quot;text/vnd.sosi&quot; for SOSI map data</title>
-               <link>http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Official_MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
-                <pubDate>Tue, 4 Jun 2019 09:20:00 +0200</pubDate>
-               <description>&lt;p&gt;Just 15 days ago,
-&lt;ahref=&quot;http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html&quot;&gt;I
-mentioned&lt;/a&gt; my submission to IANA to register an official MIME type
-for the SOSI vector map format.  This morning, just an hour ago, I was
-notified that
-&lt;a href=&quot;https://www.iana.org/assignments/media-types/text/vnd.sosi&quot;&gt;the
-MIME type &quot;text/vnd.sosi&quot;&lt;/a&gt; is registered for this format.  In
-addition to this registration, my
-&lt;a href=&quot;https://github.com/file/file/blob/master/magic/Magdir/sosi&quot;&gt;file(1)
-patch for a pattern matching rule for SOSI files&lt;/a&gt; has been accepted
-into the official source of that program (pending a new release), and
-I&#39;ve been told by the team behind
-&lt;a href=&quot;https://www.nationalarchives.gov.uk/PRONOM/&quot;&gt;PRONOM&lt;/a&gt; that
-the SOSI format will be included in the next release of PRONOM, which
-they plan to release this summer around July.&lt;/p&gt;
-
-&lt;p&gt;I am very happy to see all of this fall into place, for use by
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;the
-Noark 5 Tjenestegrensesnitt&lt;/a&gt; implementations.&lt;/p&gt;
+               <title>Totalovervåkning av innbyggernes bevegelser - nei takk!</title>
+               <link>http://people.skolelinux.org/pere/blog/Totaloverv_kning_av_innbyggernes_bevegelser___nei_takk_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Totaloverv_kning_av_innbyggernes_bevegelser___nei_takk_.html</guid>
+                <pubDate>Thu, 16 Apr 2020 20:30:00 +0200</pubDate>
+               <description>&lt;p&gt;Jeg er blitt spurt hva jeg synes om lansering av smittestopp-appen,
+overvåkningsløsningen lansert av Folkehelseinstituttet,
+Simula-senteret og Regjeringen i dag, fulgt av klare trusler fra
+regjeringen om konsekvenser hvis befolkningen ikke tar den i bruk.
+Rekker ikke skrive noe fyldig om temaet, men det er klart for meg at
+den utraderer retten til privatliv samt utgjør en personlig
+sikkerhetsrisiko for alle som tar den i bruk.  Bare det er nok til at
+det fremstår som en svært dårlig ide å bli med på denne &quot;dugnaden&quot;.
+Det finnes andre og bedre tilnærminger enn den valgt av FHI.  Har de
+valgt sin tilnærming for å sikre seg nok et datasett i den fremtidige
+ehelse-portalen?  Potensialet for misbruk av informasjon samlet inn av
+appen er for stort, effekten på neste krise for klar og gevinsten for
+liten.&lt;/p&gt;
+
+&lt;p&gt;For å si det med forhenværende leder i Datatilsynet, Georg Apenes,
+som skrev i en kronikk den gang Datatilsynet vernet
+privatsfæren at
+«&lt;a href=&quot;https://www.dagbladet.no/kultur/rent-mel-i-bilen/66333882&quot;&gt;SENTRALT
+I en liberal forestillingsverden finner vi aksept av borgerens rett
+til å kunne velge å være i fred; å være u-iakttatt, uregistrert og
+anonym&lt;/a&gt;».  Det er ikke uten grunn han startet kronikken med
+«Personvern et fremmedord i enkelte av de statsorganene som samler
+inn, oppbevarer og bruker personopplysninger».  Der har nok
+statsorganene bare blitt dårligere på 13 år.&lt;/p&gt;
+
+&lt;p&gt;Det er jo også verdt å merke seg at personvernrådet i EU (EDPB)
+mener smittestopp-appen
+&lt;a href=&quot;https://nrkbeta.no/2020/04/16/personvernrad-i-eu-mener-norsk-app-bryter-med-viktig-personvernprinsipp/&quot;&gt;opererer
+i strid med prinsippet om dataminimering&lt;/a&gt;.  Også de ser at det
+finnes mye bedre måter å gjøre dette på.&lt;/p&gt;

 
 

-&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+
+&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
+det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
+til min adresse
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
+Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>The space rover coquine, or how I ended up on the dark side of the moon</title>
-               <link>http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html</guid>
-                <pubDate>Sun, 2 Jun 2019 23:55:00 +0200</pubDate>
-               <description>&lt;p&gt;A while back a college and friend from Debian and the Skolelinux /
-Debian Edu project approached me, asking if I knew someone that might
-be interested in helping out with a technology project he was running
-as a teacher at &lt;a href=&quot;https://www.ecolefrancodanoise.dk/&quot;&gt;L&#39;école
-franco-danoise&lt;/a&gt; - the Danish-French school and kindergarden.  The
-kids were building robots, rovers.  The story behind it is to build a
-rover for use
-&lt;a href=&quot;http://blog.ecolefrancodanoise.dk/first-week-on-the-dark-side&quot;&gt;on
-the dark side of the moon&lt;/a&gt;, and remote control it.  As travel cost
-was a bit high for the final destination, and they wanted to test the
-concept first, he was looking for volunteers to host a rover for the
-kids to control in a foreign country.  I ended up volunteering as a
-host, and last week the rover arrived.  It took a while to arrive
-after &lt;a href=&quot;http://blog.ecolefrancodanoise.dk/model-moms&quot;&gt;it was
-built and shipped&lt;/a&gt;, because of customs confusion.  Luckily we were
-able fix it quickly with help from my colleges at work.&lt;/p&gt;
-
-&lt;p&gt;This is what it looked like when the rover arrived.  Note the cute
-eyes looking up on me from the wrapping&lt;/p&gt;
-
-&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-esken-med-det-rare-i.jpeg&quot; width=&quot;32%&quot; style=&quot;clear:left&quot;/&gt;
-&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-den-ser-meg.jpeg&quot; width=&quot;32%&quot; style=&quot;clear:left&quot;/&gt;
-&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-en-skrue-loes.jpeg&quot; width=&quot;32%&quot; style=&quot;clear:left&quot;/&gt;
-
-&lt;p style=&quot;text-align:left&quot;&gt;Once the robot arrived, we needed to track
-down batteries and figure out how to build custom firmware for it with
-the appropriate wifi settings.  I asked a friend if I could get two
-18650 batteries from his pile of Tesla batteries (he had them from the
-wrack of a crashed Tesla), so now the rover is running on Tesla
-batteries.&lt;/p&gt;
-
-&lt;p&gt;Building
-&lt;a href=&quot;https://gitlab.com/ecolefrancodanoise/arduino-efd/&quot;&gt;the rover
-firmware&lt;/a&gt; proved a bit harder, as the code did not work out of the
-box with the Arduino IDE package in Debian Buster.  I suspect this is
-due to a unsolved
-&lt;a href=&quot;https://github.com/arduino/Arduino/pull/2703&quot;&gt; license problem
-with arduino&lt;/a&gt; blocking Debian from upgrading to the latest version.
-In the end we gave up debugging why the IDE failed to find the
-required libraries, and ended up using the Arduino Makefile from the
-&lt;a href=&quot;https://tracker.debian.org/pkg/arduino-mk&quot;&gt;arduino-mk Debian
-package&lt;/a&gt; instead.  Unfortunately the camera library is missing from
-the Arduino environment in Debian, so we disabled the camera support
-for the first firmware build, to get something up and running.  With
-this reduced firmware, the robot could be controlled via the
-controller server, driving around and measuring distance using its
-internal acoustic sensor.&lt;/p&gt;
-
-&lt;p&gt;Next, With some help from my friend in Denmark, which checked in the
-camera library into the gitlab repository for me to use, we were able
-to build a new and more complete version of the firmware, and the
-robot is now up and running.  This is what the &quot;commander&quot; web page
-look like after taking a measurement and a snapshot:&lt;/p&gt;
-
-&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2019-06-02-robot-dark-side-of-moon-commander.png&quot; width=&quot;40%&quot; border=&quot;1&quot; align=&quot;center&quot;/&gt;
-
-&lt;p&gt;If you want to learn more about this project, you can check out the
-&lt;a href=&quot;https://hackaday.io/project/164082-the-dark-side-challenge&quot;&gt;The
-Dark Side Challenge&lt;/a&gt; Hackaday web pages.&lt;/p&gt;
+               <title>Ny URL til den frie norske stavekontrollen</title>
+               <link>http://people.skolelinux.org/pere/blog/Ny_URL_til_den_frie_norske_stavekontrollen.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ny_URL_til_den_frie_norske_stavekontrollen.html</guid>
+                <pubDate>Sat, 21 Mar 2020 08:00:00 +0100</pubDate>
+               <description>&lt;p&gt;Det er lenge siden jeg har sett på den norske stavekontrollen, sist
+jeg skrev om temaet var i 2016, og i mellomtiden har nettstedet
+no.speling.org forsvunnet, og både git-depotet på Alioth og
+mailman-tjenesten som hadde epostlistene for oversettelser blitt lagt
+ned.  Men bokmål og nynorsk trenger fortsatt stavekontroll, så etter
+et par purringer fra en som har lyst til å forbedre stavekontrollen
+har jeg endelig fått lagt ut ny offentlig kopi av git-depotet.  Jeg
+valgte gitlab foran github..  Siste utgave av stavekontrollen kan
+hentes ned fra
+&lt;a href=&quot;https://gitlab.com/norwegian-language-tools/spell-norwegian&quot;&gt;https://gitlab.com/norwegian-language-tools/spell-norwegian&lt;/a&gt;.
+Ingen ny versjon i denne omgang altså, bare et nytt sted å samle
+forbedringer til den frie norske stavekontrollen. :)

 
 

-&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
+det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
+til min adresse
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
+Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Nikita version 0.4 released - free software archive API server</title>
-               <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_4_released___free_software_archive_API_server.html</guid>
-                <pubDate>Wed, 22 May 2019 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;This morning,  a new release of 
-&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
-Noark 5 core project&lt;/a&gt; was
-&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2019-May/000468.html&quot;&gt;announced
+               <title>Nikita version 0.5 released - updated free software archive API server</title>
+               <link>http://people.skolelinux.org/pere/blog/Nikita_version_0_5_released___updated_free_software_archive_API_server.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Nikita_version_0_5_released___updated_free_software_archive_API_server.html</guid>
+                <pubDate>Mon, 2 Mar 2020 19:00:00 +0100</pubDate>
+               <description>&lt;p&gt;Today, after many months of development, a new release of
+&lt;ahref=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
+Noark 5 core project&lt;/a&gt; was finally
+&lt;ahref=&quot;https://lists.nuug.no/pipermail/nikita-noark/2020-March/000519.html&quot;&gt;announced

 on the project mailing list&lt;/a&gt;.  The Nikita free software solution is
 an implementation of the Norwegian archive standard Noark 5 used by
 on the project mailing list&lt;/a&gt;.  The Nikita free software solution is
 an implementation of the Norwegian archive standard Noark 5 used by

-government offices in Norway.  These were the changes in version 0.4
-since version 0.3, see the email link above for links to a demo site:&lt;/p&gt;
+government offices in Norway.  These were the changes in version 0.5
+since version 0.4, see the email link above for links to a demo
+site:&lt;/p&gt;

 
 &lt;ul&gt;
 
 
 &lt;ul&gt;
 

-  &lt;li&gt;Roll out OData handling to all endpoints where applicable&lt;/li&gt;
-  &lt;li&gt;Changed the relation key for &quot;ny-journalpost&quot; to the official one.&lt;/li&gt;
-  &lt;li&gt;Better link generation on outgoing links.&lt;/li&gt;
-  &lt;li&gt;Tidy up code and make code and approaches more consistent throughout
-   the codebase&lt;/li&gt;
-  &lt;li&gt;Update rels to be in compliance with updated version in the
-   interface standard&lt;/li&gt;
-  &lt;li&gt;Avoid printing links on empty objects as they can&#39;t have links&lt;/li&gt;
-  &lt;li&gt;Small bug fixes and improvements&lt;/li&gt;
-  &lt;li&gt;Start moving generation of outgoing links to @Service layer so access
-   control can be used when generating links&lt;/li&gt;
-  &lt;li&gt;Log exception that was being swallowed so it&#39;s traceable&lt;/li&gt;
-  &lt;li&gt;Fix name mapping problem&lt;/li&gt;
-  &lt;li&gt;Update templated printing so templated should only be printed if it
-   is set true. Requires more work to roll out across entire
-   application.&lt;/li&gt;
-  &lt;li&gt;Remove Record-&gt;DocumentObject as per domain model of n5v4&lt;/li&gt;
-  &lt;li&gt;Add ability to delete lists filtered with OData&lt;/li&gt;
-  &lt;li&gt;Return NO_CONTENT (204) on delete as per interface standard&lt;/li&gt;
-  &lt;li&gt;Introduce support for ConstraintViolationException exception&lt;/li&gt;
-  &lt;li&gt;Make Service classes extend NoarkService&lt;/li&gt;
-  &lt;li&gt;Make code base respect X-Forwarded-Host, X-Forwarded-Proto and
-   X-Forwarded-Port&lt;/li&gt;
-  &lt;li&gt;Update CorrespondencePart* code to be more in line with Single
-   Responsibility Principle&lt;/li&gt;
-  &lt;li&gt;Make package name follow directory structure&lt;/li&gt;
-  &lt;li&gt;Make sure Document number starts at 1, not 0&lt;/li&gt;
-  &lt;li&gt;Fix isues discovered by FindBugs&lt;/li&gt;
-  &lt;li&gt;Update from Date to ZonedDateTime&lt;/li&gt;
-  &lt;li&gt;Fix wrong tablename&lt;/li&gt;
-  &lt;li&gt;Introduce Service layer tests&lt;/li&gt;
-  &lt;li&gt;Improvements to CorrespondencePart&lt;/li&gt;
-  &lt;li&gt;Continued work on Class / Classificationsystem&lt;/li&gt;
-  &lt;li&gt;Fix feature where authors were stored as storageLocations&lt;/li&gt;
-  &lt;li&gt;Update HQL builder for OData&lt;/li&gt;
-  &lt;li&gt;Update OData search capability from webpage&lt;/li&gt;
-  
+  &lt;li&gt;Updated to Noark 5 versjon 5.0 API specification.
+    &lt;ul&gt;
+      &lt;li&gt;Changed formatting of _links from [] to {} to match IETF draft
+      on JSON HAL.&lt;/li&gt;
+      &lt;li&gt;Merged Registrering og Basisregistrering in version 4 to
+      combined Registrering.&lt;/li&gt;
+      &lt;li&gt;DokumentObjekt is now subtype of ArkivEnhet.&lt;/li&gt;
+      &lt;li&gt;Introducing new entity Arkivnotat.&lt;/li&gt;
+      &lt;li&gt;Changed all relation keys to use /v5/ instead of /v4/.&lt;/li&gt;
+      &lt;li&gt;Corrected to use new official relation keys when possible.&lt;/li&gt;
+      &lt;li&gt;Renamed Sakspart to Part and connect it to Mappe, Registrering
+      and Dokumentbeskrivelse instead of only Saksmappe.&lt;/li&gt;
+      &lt;li&gt;Moved Korrespondansepart connection from Journalpost to
+      Registrering.&lt;/li&gt;
+      &lt;li&gt;Moved Part and Korrespondansepart from package sakarkiv to
+      arkivstruktur.&lt;/li&gt;
+      &lt;li&gt;Renamed presedensstatus to presedensStatus.&lt;/li&gt;
+      &lt;li&gt;Use new JSON content-type &quot;application/vnd.noark5+json&quot;.&lt;/li&gt;
+      &lt;li&gt;Updated prepopulated format list to use PRONOM codes.&lt;/li&gt;
+      &lt;li&gt;Implemented endpoint for system information.&lt;/li&gt;
+      &lt;li&gt;Implemented national identifiers for both file and record.&lt;/li&gt;
+      &lt;li&gt;Implemented comments.&lt;/li&gt;
+      &lt;li&gt;implemented sign off.&lt;/li&gt;
+      &lt;li&gt;implemented conversion.&lt;/li&gt;
+    &lt;/ul&gt;&lt;/li&gt;
+  &lt;li&gt;Improved/implemented OData search and paging support for more entities.&lt;/li&gt;
+  &lt;li&gt;No longer exposes attribute Dokumentobjekt.referanseDokumentfil,
+   one should use the relation in _links instead.&lt;/li&gt;
+  &lt;li&gt;Corrected relation keys under
+   https://rel.arkivverket.no/noark5/v5/api/administrasjon/, replacing
+   &#39;administrasjon&#39; with &#39;admin&#39;.&lt;/li&gt;
+  &lt;li&gt;Fixed several security and stability issues discovered by Coverity.&lt;/li&gt;
+  &lt;li&gt;Corrected handling ETag errors, now return code 409.&lt;/li&gt;
+  &lt;li&gt;Improved handling of Kryssreferanse.&lt;/li&gt;
+  &lt;li&gt;Changed internal database model to use UUID/SystemID as primary keys
+   in tables.&lt;/li&gt;
+  &lt;li&gt;Changed internal database table names to use package prefix.&lt;/li&gt;
+  &lt;li&gt;Changed time zone handling for date and datetime attributes, to be
+   more according to the new definition in the API specification.&lt;/li&gt;
+  &lt;li&gt;Change revoke-token to only drop token on POST requests, not GET.&lt;/li&gt;
+  &lt;li&gt;Updated to newer Spring version.&lt;/li&gt;
+  &lt;li&gt;Changed primary key and URL component for metadata code lists to
+   use the &#39;kode&#39; value instead of a SystemID.&lt;/li&gt;
+  &lt;li&gt;Corrected implementation of Part and Sakspart.&lt;/li&gt;
+  &lt;li&gt;Changed instance lists with subtypes (like .../registrering/ and
+   .../mappe/) to include the attributes and _links entries for the
+   subtype in the supertype lists.&lt;/li&gt;
+  &lt;li&gt;Adjusted _links relations to make it possible to figure out the
+   entity of an instance using the self-&gt;href-&gt;relation key lookup
+   method.&lt;/li&gt;
+  &lt;li&gt;Fixed several end points to make sure GET, PUT, POST and DELETE
+   match each other.&lt;/li&gt;
+  &lt;li&gt;Updated DELETE endpoints to work with UUID based entity
+   identifiers.&lt;/li&gt;
+  &lt;li&gt;Restructured code to use more common URL related constants in entry
+   point values and replace @RequestMapping with method specific
+   annotations.&lt;/li&gt;
+  &lt;li&gt;Added first unit test code.&lt;/li&gt;
+  &lt;li&gt;Updated web GUI to work with the updated API.&lt;/li&gt;
+  &lt;li&gt;Changed integer fields, enforce them as numeric.&lt;/li&gt;
+  &lt;li&gt;Rewrote and simplify metadata handling to use common service and
+   controller code instead of duplicating for each type.&lt;/li&gt;
+  &lt;li&gt;Implemented the remaining metadata types.&lt;/li&gt;
+  &lt;li&gt;Changed Country list source from Wikipedia to Debian iso-codes and
+   updated the list of Countries.&lt;/li&gt;
+  &lt;li&gt;Many many corrections and improvements.&lt;/li&gt;
+

 &lt;/ul&gt;
 
 &lt;p&gt;If free and open standardized archiving API sound interesting to
 &lt;/ul&gt;
 
 &lt;p&gt;If free and open standardized archiving API sound interesting to


@@ -633,206 +505,80 @@ activities, please send Bitcoin donations to my address
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>MIME type &quot;text/vnd.sosi&quot; for SOSI map data</title>
-               <link>http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/MIME_type__text_vnd_sosi__for_SOSI_map_data.html</guid>
-                <pubDate>Mon, 20 May 2019 08:35:00 +0200</pubDate>
-               <description>&lt;p&gt;As part of my involvement in the work to
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard&quot;&gt;standardise
-a REST based API for Noark 5&lt;/a&gt;, the Norwegian archiving standard, I
-spent some time the last few months to try to register a
-&lt;a href=&quot;https://www.iana.org/assignments/media-types/&quot;&gt;MIME type&lt;/a&gt;
-and &lt;a href=&quot;https://www.nationalarchives.gov.uk/PRONOM/&quot;&gt;PRONOM
-code&lt;/a&gt; for the SOSI file format.  The background is that there is a
-set of formats approved for long term storage and archiving in Norway,
-and among these formats, SOSI is the only format missing a MIME type
-and PRONOM code.&lt;/p&gt;
-
-&lt;p&gt;What is SOSI, you might ask?  To quote Wikipedia: SOSI is short for
-Samordnet Opplegg for Stedfestet Informasjon (literally &quot;Coordinated
-Approach for Spatial Information&quot;, but more commonly expanded in
-English to Systematic Organization of Spatial Information).  It is a
-text based file format for geo-spatial vector information used in
-Norway.  Information about the SOSI format can be found in English
-from &lt;a href=&quot;https://en.wikipedia.org/wiki/SOSI&quot;&gt;Wikipedia&lt;/a&gt;.  The
-specification is available in Norwegian from
-&lt;a href=&quot;https://www.kartverket.no/geodataarbeid/Standarder/SOSI/&quot;&gt;the
-Norwegian mapping authority&lt;/a&gt;.  The SOSI standard, which originated
-in the beginning of nineteen eighties, was the inspiration and formed the
-basis for the XML based
-&lt;a href=&quot;https://en.wikipedia.org/wiki/Geography_Markup_Language&quot;&gt;Geography
-Markup Language&lt;/a&gt;.&lt;/p&gt;
-
-&lt;p&gt;I have so far written
-&lt;a href=&quot;https://github.com/file/file/pull/67&quot;&gt;a pattern matching
-rule&lt;/a&gt; for the file(1) unix tool to recognize SOSI files, submitted
-a request to the PRONOM project to have a PRONOM ID assigned to the
-format (reference TNA1555078202S60), and today send a request to IANA
-to register the &quot;text/vnd.sosi&quot; MIME type for this format (referanse
-&lt;a href=&quot;https://tools.iana.org/public-view/viewticket/1143144&quot;&gt;IANA
-#1143144&lt;/a&gt;).  If all goes well, in a few months, anyone implementing
-the Noark 5 Tjenestegrensesnitt API spesification should be able to
-use an official MIME type and PRONOM code for SOSI files.  In
-addition, anyone using SOSI files on Linux should be able to
-automatically recognise the format and web sites handing out SOSI
-files can begin providing a more specific MIME type.  So far, SOSI
-files has been handed out from web sites using the
-&quot;application/octet-stream&quot; MIME type, which is just a nice way of
-stating &quot;I do not know&quot;.  Soon, we will know. :)&lt;/p&gt;
+               <title>Blockchain and IoT articles accepted into Records Management Journal</title>
+               <link>http://people.skolelinux.org/pere/blog/Blockchain_and_IoT_articles_accepted_into_Records_Management_Journal.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Blockchain_and_IoT_articles_accepted_into_Records_Management_Journal.html</guid>
+                <pubDate>Thu, 27 Feb 2020 09:05:00 +0100</pubDate>
+               <description>&lt;p&gt;On Tuesday, two scietific articles we have been working on for a
+while, was finally accepted for publication into
+&lt;a href=&quot;https://www.emerald.com/insight/publication/issn/0956-5698&quot;&gt;Records
+Management Journal&lt;/a&gt;.  Still waiting for the assigned DOI urls to
+start working, but you can have a look at the LaTeX originals here.&lt;/p&gt;
+
+&lt;p&gt;The first article is
+&quot;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2020-02-25-rmj-iot-record-keeping.pdf&quot;&gt;A
+record-keeping approach to managing IoT-data for government
+agencies&lt;/a&gt;&quot; (&lt;a href=&quot;https://doi.org/10.1108/RMJ-09-2019-0050&quot;&gt;DOI
+10.1108/RMJ-09-2019-0050&lt;a/&gt;) by Thomas Sødring, Petter Reinholdtsen
+and David Massey, and sketches some approaches for storing measurement
+data (aka Internet of Things sensor data) in a archive, thus providing
+a well defined mechanism for screening and deletion of the information &lt;/p&gt;
+
+&lt;p&gt;The second article is
+&quot;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2020-02-25-rmj-block-chain-record-keeping.pdf&quot;&gt;Publishing
+and using record-keeping structural information in a blockchain&lt;/a&gt;&quot;
+(&lt;a href=&quot;https://doi.org/10.1108/RMJ-09-2019-0056&quot;&gt;DOI
+10.1108/RMJ-09-2019-0056&lt;/a&gt;) by Thomas Sødring, Petter Reinholdtsen
+and Svein Ølnes, where we describe a way for third parties to validate
+authenticity and thus improve trust in the records kept in a
+archive.&lt;/p&gt;

 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
 
 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
 activities, please send Bitcoin donations to my address
 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;

+
+&lt;p&gt;&lt;strong&gt;Update 2020-04-26&lt;/strong&gt;: Initially managed to swap the
+DOI numbers.  Fixed it.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>PlantUML for text based UML diagram modelling - nice free software</title>
-               <link>http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PlantUML_for_text_based_UML_diagram_modelling___nice_free_software.html</guid>
-                <pubDate>Mon, 25 Mar 2019 09:35:00 +0100</pubDate>
-               <description>&lt;p&gt;As part of my involvement with the
-&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita
-Noark 5 core project&lt;/a&gt;, I have been proposing improvements to the
-API specification created by &lt;a href=&quot;https://www.arkivverket.no/&quot;&gt;The
-National Archives of Norway&lt;/a&gt; and helped migrating the text from a
-version control system unfriendly binary format (docx) to Markdown in
-git.  Combined with the migration to a public git repository (on
-github), this has made it possible for anyone to suggest improvement
-to the text.&lt;/p&gt;
-
-&lt;p&gt;The specification is filled with UML diagrams.  I believe the
-original diagrams were modelled using Sparx Systems Enterprise
-Architect, and exported as EMF files for import into docx.  This
-approach make it very hard to track changes using a version control
-system.  To improve the situation I have been looking for a good text
-based UML format with associated command line free software tools on
-Linux and Windows, to allow anyone to send in corrections to the UML
-diagrams in the specification.  The tool must be text based to work
-with git, and command line to be able to run it automatically to
-generate the diagram images.  Finally, it must be free software to
-allow anyone, even those that can not accept a non-free software
-license, to contribute.&lt;/p&gt;
-
-&lt;p&gt;I did not know much about free software UML modelling tools when I
-started.  I have used dia and inkscape for simple modelling in the
-past, but neither are available on Windows, as far as I could tell.  I
-came across a nice
-&lt;a href=&quot;https://modeling-languages.com/text-uml-tools-complete-list/&quot;&gt;list
-of text mode uml tools&lt;/a&gt;, and tested out a few of the tools listed
-there.  &lt;a href=&quot;http://plantuml.com/&quot;&gt;The PlantUML tool&lt;/a&gt; seemed
-most promising.  After verifying that the packages
-&lt;a href=&quot;https://tracker.debian.org/pkg/plantuml&quot;&gt;is available in
-Debian&lt;/a&gt; and found &lt;a href=&quot;https://github.com/plantuml/plantuml&quot;&gt;its
-Java source&lt;/a&gt; under a GPL license on github, I set out to test if it
-could represent the diagrams we needed, ie the ones currently in
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/&quot;&gt;the
-Noark 5 Tjenestegrensesnitt specification&lt;/a&gt;.  I am happy to report
-that it could represent them, even thought it have a few warts here
-and there.&lt;/p&gt;
-
-&lt;p&gt;After a few days of modelling I completed the task this weekend.  A
-temporary link to the complete set of diagrams (original and from
-PlantUML) is available in
-&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/76&quot;&gt;the
-github issue discussing the need for a text based UML format&lt;/a&gt;, but
-please note I lack a sensible tool to convert EMF files to PNGs, so
-the &quot;original&quot; rendering is not as good as the original was in the
-publised PDF.&lt;/p&gt;
-
-&lt;p&gt;Here is an example UML diagram, showing the core classes for
-keeping metadata about archived documents:&lt;/p&gt;
-
-&lt;pre&gt;
-@startuml
-skinparam classAttributeIconSize 0
-
-!include media/uml-class-arkivskaper.iuml
-!include media/uml-class-arkiv.iuml
-!include media/uml-class-klassifikasjonssystem.iuml
-!include media/uml-class-klasse.iuml
-!include media/uml-class-arkivdel.iuml
-!include media/uml-class-mappe.iuml
-!include media/uml-class-merknad.iuml
-!include media/uml-class-registrering.iuml
-!include media/uml-class-basisregistrering.iuml
-!include media/uml-class-dokumentbeskrivelse.iuml
-!include media/uml-class-dokumentobjekt.iuml
-!include media/uml-class-konvertering.iuml
-!include media/uml-datatype-elektronisksignatur.iuml
-
-Arkivstruktur.Arkivskaper &quot;+arkivskaper 1..*&quot; &lt;-o &quot;+arkiv 0..*&quot; Arkivstruktur.Arkiv
-Arkivstruktur.Arkiv o--&gt; &quot;+underarkiv 0..*&quot; Arkivstruktur.Arkiv
-Arkivstruktur.Arkiv &quot;+arkiv 1&quot; o--&gt; &quot;+arkivdel 0..*&quot; Arkivstruktur.Arkivdel
-Arkivstruktur.Klassifikasjonssystem &quot;+klassifikasjonssystem [0..1]&quot; &lt;--o &quot;+arkivdel 1..*&quot; Arkivstruktur.Arkivdel
-Arkivstruktur.Klassifikasjonssystem &quot;+klassifikasjonssystem [0..1]&quot; o--&gt; &quot;+klasse 0..*&quot; Arkivstruktur.Klasse
-Arkivstruktur.Arkivdel &quot;+arkivdel 0..1&quot; o--&gt; &quot;+mappe 0..*&quot; Arkivstruktur.Mappe
-Arkivstruktur.Arkivdel &quot;+arkivdel 0..1&quot; o--&gt; &quot;+registrering 0..*&quot; Arkivstruktur.Registrering
-Arkivstruktur.Klasse &quot;+klasse 0..1&quot; o--&gt; &quot;+mappe 0..*&quot; Arkivstruktur.Mappe
-Arkivstruktur.Klasse &quot;+klasse 0..1&quot; o--&gt; &quot;+registrering 0..*&quot; Arkivstruktur.Registrering
-Arkivstruktur.Mappe --&gt; &quot;+undermappe 0..*&quot; Arkivstruktur.Mappe
-Arkivstruktur.Mappe &quot;+mappe 0..1&quot; o--&gt; &quot;+registrering 0..*&quot; Arkivstruktur.Registrering
-Arkivstruktur.Merknad &quot;+merknad 0..*&quot; &lt;--* Arkivstruktur.Mappe
-Arkivstruktur.Merknad &quot;+merknad 0..*&quot; &lt;--* Arkivstruktur.Dokumentbeskrivelse
-Arkivstruktur.Basisregistrering -|&gt; Arkivstruktur.Registrering
-Arkivstruktur.Merknad &quot;+merknad 0..*&quot; &lt;--* Arkivstruktur.Basisregistrering
-Arkivstruktur.Registrering &quot;+registrering 1..*&quot; o--&gt; &quot;+dokumentbeskrivelse 0..*&quot; Arkivstruktur.Dokumentbeskrivelse
-Arkivstruktur.Dokumentbeskrivelse &quot;+dokumentbeskrivelse 1&quot; o-&gt; &quot;+dokumentobjekt 0..*&quot; Arkivstruktur.Dokumentobjekt
-Arkivstruktur.Dokumentobjekt *-&gt; &quot;+konvertering 0..*&quot; Arkivstruktur.Konvertering
-Arkivstruktur.ElektroniskSignatur -[hidden]-&gt; Arkivstruktur.Dokumentobjekt
-@enduml
-&lt;/pre&gt;
-
-&lt;p&gt;&lt;a href=&quot;http://plantuml.com/class-diagram&quot;&gt;The format&lt;/a&gt; is quite
-compact, with little redundant information.  The text expresses
-entities and relations, and there is little layout related fluff.  One
-can reuse content by using include files, allowing for consistent
-naming across several diagrams.  The include files can be standalone
-PlantUML too.  Here is the content of
-&lt;tt&gt;media/uml-class-arkivskaper.iuml&lt;tt&gt;:&lt;/p&gt;
-
-&lt;pre&gt;
-@startuml
-class Arkivstruktur.Arkivskaper &lt;Arkivenhet&gt; {
-  +arkivskaperID : string
-  +arkivskaperNavn : string
-  +beskrivelse : string [0..1]
-}
-@enduml
-&lt;/pre&gt;
-
-&lt;p&gt;This is what the complete diagram for the PlantUML notation above
-look like:&lt;/p&gt;
-
-&lt;p&gt;&lt;img width=&quot;80%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2019-03-25-noark5-plantuml-diagrameksempel.png&quot;&gt;&lt;/p&gt;
-
-&lt;p&gt;A cool feature of PlantUML is that the generated PNG files include
-the entire original source diagram as text.  The source (with include
-statements expanded) can be extracted using for example
-&lt;tt&gt;exiftool&lt;/tt&gt;.  Another cool feature is that parts of the entities
-can be hidden after inclusion.  This allow to use include files with
-all attributes listed, even for UML diagrams that should not list any
-attributes.&lt;/p&gt;
-
-&lt;p&gt;The diagram also show some of the warts.  Some times the layout
-engine place text labels on top of each other, and some times it place
-the class boxes too close to each other, not leaving room for the
-labels on the relationship arrows.  The former can be worked around by
-placing extra newlines in the labes (ie &quot;\n&quot;).  I did not do it here
-to be able to demonstrate the issue.  I have not found a good way
-around the latter, so I normally try to reduce the problem by changing
-from vertical to horizontal links to improve the layout.&lt;/p&gt;
-
-&lt;p&gt;All in all, I am quite happy with PlantUML, and very impressed with
-how quickly its lead developer responds to questions.  So far I got an
-answer to my questions in a few hours when I send an email.  I
-definitely recommend looking at PlantUML if you need to make UML
-diagrams.  Note, PlantUML can draw a lot more than class relations.
-Check out the documention for a complete list. :)&lt;/p&gt;
+               <title>Redaksjon på plass for Noark 5 tjenestegrensesnitt</title>
+               <link>http://people.skolelinux.org/pere/blog/Redaksjon_p__plass_for_Noark_5_tjenestegrensesnitt.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Redaksjon_p__plass_for_Noark_5_tjenestegrensesnitt.html</guid>
+                <pubDate>Wed, 5 Feb 2020 14:45:00 +0100</pubDate>
+               <description>&lt;p&gt;Arbeidet med å lage et godt, fritt og åpent standardisert maskinelt
+grensesnitt for arkivering, med tilhørende fri
+programvareimplementasjon fortsetter.  Jeg snakker om
+&lt;a href=&quot;https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard&quot;&gt;Noark
+5 Tjenestegrensesnitt&lt;/a&gt; og
+&lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core/&quot;&gt;Nikita&lt;/a&gt;.
+Siste nytt etter
+&lt;a href=&quot;https://www.nuug.no/aktiviteter/20200127-noark-seminar/&quot;&gt;seminaret
+for noen dager siden&lt;/a&gt;, er vi i Nikita-prosjektet har fått beskjed
+fra Arkivverket at det blir satt ned en redaksjon for å videreutvikle
+spesifikasjonen.  Redaksjonen består av Mona Danielsen og Anne Sofie
+Knutsen ved arkivverket, Thomas Sødring ved OsloMet, og meg selv fra
+NUUG.  De to sistenevnte tar seg av de åpenbare forbedringene, mens
+hele redaksjonen diskuterer tvilstilfeller.  Jeg håper dette vil bidra
+til at vi lykkes i å gjøre denne protokollspesifikasjonen så entydig
+og klar at den vil bidra til et velfungerende marked for
+arkivsystemer, og sikre at programmer som trenger å snakke med
+arkivsystemet kan snakke med enhver implementasjon av
+API-spesifikasjonen.  Nikita er den første implementasjonen, men det
+bør blir flere.&lt;/p&gt;
+
+&lt;p&gt;Det gjenstår riktig nok endel før vi er i mål, selv om svært mye
+allerede er på plass.  Med innspill og forslag til forbedringer fra
+alle som vil ha et leverandøruavhengig og fullstendig
+datamaskinlesbart grensesnitt til arkivet, så tror jeg vi vil
+lykkes.&lt;/p&gt;

 
 

-&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
+&lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
+det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
+til min adresse
+&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
+Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;

 </description>
        </item>
        
 </description>
        </item>