blog/tags/digistan/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged digistan</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="https://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="digistan.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="https://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "digistan".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="https://people.skolelinux.org/pere/blog/_pen_og_gjennomsiktig_vedlikehold_av_spesifikasjonen_for_Noark_5_Tjenestegrensesnitt.html">Åpen og gjennomsiktig vedlikehold av spesifikasjonen for Noark 5 Tjenestegrensesnitt</a>
  26       </div>
  27       <div class="date">
  28         11th March 2019
  29       </div>
  30       <div class="body">
  31         <p>Et virksomhetsarkiv for meg, er et arbeidsverktøy der en enkelt kan
  32 finne informasjonen en trenger når en trenger det, og der
  33 virksomhetens samlede kunnskap er tilgjengelig. Det må være greit å
  34 finne frem i, litt som en bibliotek. Men der et bibliotek gjerne tar
  35 vare på offentliggjort informasjon som er tilgjengelig flere steder,
  36 tar et arkiv vare på virksomhetsintern og til tider personlig
  37 informasjon som ofte kun er tilgjengelig fra et sted.</p>
  38
  39 <p>Jeg mistenker den eneste måten å sikre at arkivet inneholder den
  40 samlede kunnskapen i en virksomhet, er å bruke det som virksomhetens
  41 kunnskapslager. Det innebærer å automatisk kopiere (brev, epost,
  42 SMS-er etc) inn i arkivet når de sendes og mottas, og der filtrere
  43 vekk det en ikke vil ta vare på, og legge på metadata om det som er
  44 samlet inn for enkel gjenfinning. En slik bruk av arkivet innebærer at
  45 arkivet er en del av daglig virke, ikke at det er siste hvilested for
  46 informasjon ingen lenger har daglig bruk for. For å kunne være en del
  47 av det daglige virket må arkivet enkelt kunne integreres med andre
  48 systemer.  I disse dager betyr det å tilby arkivet som en
  49 nett-tjeneste til hele virksomheten, tilgjengelig for både mennesker
  50 og datamaskiner.  Det betyr i tur å både tilby nettsider og et
  51 maskinlesbart grensesnitt.</p>
  52
  53 <p>For noen år siden erkjente visjonære arkivarer fordelene med et
  54 standardisert maskinlesbart grensesnitt til organisasjonens arkiv.  De
  55 gikk igang med å lage noe de kalte
  56 <a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">Noark
  57 5 Tjenestegrensesnitt</a>.  Gjort riktig, så åpner slike maskinlesbare
  58 grensesnitt for samvirke på tvers av uavhengige programvaresystemer.
  59 Gjort feil, vil det blokkere for samvirke og bidra til
  60 leverandørinnlåsing.  For å gjøre det riktig så må grensesnittet være
  61 klart og entydig beskrevet i en spesifikasjon som gjør at
  62 spesifikasjonen tolkes på samme måte uavhengig av hvem som leser den,
  63 og uavhengig av hvem som tar den i bruk.</p>
  64
  65 <p>For å oppnå klare og entydige beskrivelser i en spesifikasjon, som
  66 trengs for å kunne få en fri og åpen standard (se
  67 <a href="https://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">Digistan-definisjon</a>),
  68 så trengs det en åpen og gjennomsiktig inngangsport med lav terskel,
  69 der de som forsøker å ta den i bruk enkelt kan få inn korreksjoner,
  70 etterlyse klargjøringer og rapportere uklarheter i spesifikasjonen.
  71 En trenger også automatiserte datasystemer som måler og sjekker at et
  72 gitt grensesnitt fungerer i tråd med spesifikasjonen.</p>
  73
  74 <p>For Noark 5 Tjenestegrensesnittet er det nå etablert en slik åpen
  75 og gjennomsiktig inngangsport på prosjekttjenesten github.  Denne
  76 inngangsporten består først og fremst av en åpen portal som lar enhver
  77 se hva som er gjort av endringer i spesifikasjonsteksten over tid, men
  78 det hører også med et åpent &quot;diskusjonsforum&quot; der en kan
  79 komme med endringsforslag og forespørsler om klargjøringer.  Alle
  80 registrerte brukere på github kan bidra med innspill til disse
  81 henvendelsene.</p>
  82
  83 <p>I samarbeide med Arkivverket har jeg fått opprettet et git-depot
  84 med spesifikasjonsteksten for tjenestegrensesnittet, der det er lagt
  85 inn historikk for endringer i teksten de siste årene, samt lagt inn
  86 endringsforslag og forespørsler om klargjøring av teksten.  Bakgrunnen
  87 for at jeg bidro med dette er at jeg er involvert i
  88 <a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">Nikita-prosjektet</a>,
  89 som lager en fri programvare-utgave av Noark 5 Tjenestegrensesnitt.
  90 Det er først når en forsøker å lage noe i tråd med en spesifikasjon at
  91 en oppdager hvor mange detaljer som må beskrives i spesifikasjonen for
  92 å sikre samhandling.</p>
  93
  94 <p>Spesifikasjonen vedlikeholdes i et rent tekstformat, for å ha et
  95 format egnet for versjonskontroll via versjontrollsystemet git.  Dette
  96 gjør det både enkelt å se konkret hvilke endringer som er gjort når,
  97 samt gjør det praktisk mulig for enhver med github-konto å sende inn
  98 endringsforslag med formuleringer til spesifikasjonsteksten.  Dette
  99 tekstformatet vises frem som nettsider på github, slik at en ikke
 100 trenger spesielle verktøy for å se på siste utgave av
 101 spesifikasjonen.</p>
 102
 103 <p>Fra dette rene tekstformatet kan det så avledes ulike formater, som
 104 HTML for websider, PDF for utskrift på papir og ePub for lesing med
 105 ebokleser.  Avlednings-systemet (byggesystemet) bruker i dag
 106 verktøyene pandoc, latex, docbook-xsl og GNU make til
 107 transformasjonen.  Tekstformatet som brukes dag er
 108 <a href="https://www.markdownguide.org/">Markdown</a>, men det vurderes
 109 å
 110 <a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/9">endre
 111 til formatet RST</a> i fremtiden for bedre styring av utseende på
 112 PDF-utgaven.</p>
 113
 114 <p>Versjonskontrollsystemet git ble valgt da det er både fleksibelt,
 115 avansert og enkelt å ta i bruk. Github ble valgt (foran f.eks. Gitlab
 116 som vi bruker i Nikita), da Arkivverket allerede hadde tatt i bruk
 117 Github i andre sammenhenger.</p>
 118
 119 <p>Enkle endringer i teksten kan gjøres av priviligerte brukere
 120 direkte i nettsidene til Github, ved å finne aktuell fil som skal
 121 endres (f.eks. kapitler/03-konformitet.md), klikke på den lille
 122 bokstaven i høyre hjørne over teksten. Det kommer opp en nettside der
 123 en kan endre teksten slik en ønsker. Når en er fornøyd med endringen
 124 så må endringen &quot;sjekkes inn&quot; i historikken. Det gjøres ved
 125 å gi en kort beskrivelse av endringen (beskriv helst hvorfor endringen
 126 trengs, ikke hva som er endret), under overskriften &quot;Commit
 127 changes&quot;. En kan og bør legge inn en lengre forklaring i det
 128 større skrivefeltet, før en velger om endringen skal sendes direkte
 129 til 'master'-grenen (dvs. autorativ utgave av spesifikasjonen) eller
 130 om en skal lage en ny gren for denne endringen og opprette en
 131 endringsforespørsel (aka &quot;Pull Request&quot;/PR). Når alt dette
 132 er gjort kan en velge &quot;Commit changes&quot; for å sende inn
 133 endringen. Hvis den er lagt inn i &quot;master&quot;-grenen så er den
 134 en offisiell del av spesifikasjonen med en gang.  Hvis den derimot er
 135 en endringsforespørsel, så legges den inn i
 136 <a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/pulls">listen
 137 over forslag til endringer</a> som venter på korrekturlesing og
 138 godkjenning.</p>
 139
 140 <p>Større endringer (for eksempel samtidig endringer i flere filer)
 141 gjøres enklest ved å hente ned en kopi av git-depoet lokalt og gjøre
 142 endringene der før endringsforslaget sendes inn. Denne prosessen er
 143 godt beskrivet i dokumentasjon fra github.  Git-prosjektet som skal
 144 &quot;klones&quot; er
 145 <a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/</a>.</p>
 146
 147 <p>For å registrere nye utfordringer (issues) eller kommentere på
 148 eksisterende utfordringer benyttes nettsiden
 149 <a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues">https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues</a>.
 150 I skrivende stund er det 48 åpne og 11 avsluttede utfordringer.  Et
 151 forslag til hva som bør være med når en beskriver en utfordring er
 152 tilgjengelig som utfordring
 153 <a href="https://github.com/arkivverket/noark5-tjenestegrensesnitt-standard/issues/14">#14</a>.</p>
 154
 155 <p>For å bygge en PDF-utgave av spesifikasjonen så bruker jeg i dag en
 156 Debian GNU/Linux-maskin med en rekke programpakker installert.  Når
 157 dette er på plass, så holder det å kjøre kommandoen 'make pdf html' på
 158 kommandolinjen, vente ca. 20 sekunder, før spesifikasjon.pdf og
 159 spesifikasjon.html ligger klar på disken. Verktøyene for bygging av
 160 PDF, HTML og ePub-utgave er også tilgjengelig på Windows og
 161 MacOSX.</p>
 162
 163 <p>Github bidrar med rammeverket.  Men for at åpent vedlikehold av
 164 spesifikasjonen skal fungere, så trengs det folk som bidrar med sin
 165 tid og kunnskap.  Arkivverket har sagt de skal bidra med innspill og
 166 godkjenne forslag til endringer, men det blir størst suksess hvis alle
 167 som bruker og lager systemer basert på Noark 5 Tjenestegrensesnitt
 168 bidrar med sin kunnskap og kommer med forslag til forebedringer.  Jeg
 169 stiller.  Blir du med?</p>
 170
 171 <p>Det er viktig å legge til rette for åpen diskusjon blant alle
 172 interesserte, som ikke krever at en må godta lange kontrakter med
 173 vilkår for deltagelse. Inntil Arkivverket dukker opp på IRC har vi
 174 laget en IRC-kanal der interesserte enkelt kan orientere seg og
 175 diskutere tjenestegrensesnittet. Alle er velkommen til å ta turen
 176 innom
 177 <a href="https://webchat.freenode.net/?channels=nikita">#nikita</a>
 178 (f.eks. via irc.freenode.net) for å møte likesinnede.</p>
 179
 180 <p>Det holder dog ikke å ha en god spesifikasjon, hvis ikke de som tar
 181 den i bruk gjør en like god jobb. For å automatisk teste om et konkret
 182 tjenestegrensesnitt følger (min) forståelse av
 183 spesifikasjonsdokumentet, har jeg skrevet et program som kobler seg
 184 opp til et Noark 5v4 REST-tjeneste og tester alt den finner for å se
 185 om det er i henhold til min tolkning av spesifikasjonen.  Dette
 186 verktøyet er tilgjengelig fra
 187 <a href="https://github.com/petterreinholdtsen/noark5-tester">https://github.com/petterreinholdtsen/noark5-tester</a>,
 188 og brukes daglig mens vi utvikler Nikita for å sikre at vi ikke
 189 introduserer nye feil.  Hvis en skal sikre samvirke på tvers av ulike
 190 systemer er det helt essensielt å kunne raskt og automatisk sjekke at
 191 tjenestegrensesnittet oppfører seg som forventet.  Jeg håper andre som
 192 lager sin utgave av tjenestegrensesnittet vi bruke dette verktøyet,
 193 slik at vi tidlig og raskt kan oppdage hvor vi har tolket
 194 spesifikasjonen ulikt, og dermed få et godt grunnlag for å gjøre
 195 spesifikasjonsteksten enda klarere og bedre.</p>
 196
 197 <p>Dagens beskrivelse av Noark 5 Tjenestegrensesnitt er et svært godt
 198 utgangspunkt for å gjøre virksomhetens arkiv til et dynamisk og
 199 sentralt arbeidsverktøy i organisasjonen.  Blir du med å gjøre den
 200 enda bedre?</p>
 201
 202       </div>
 203       <div class="tags">
 204
 205
 206         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 207
 208
 209       </div>
 210     </div>
 211     <div class="padding"></div>
 212
 213     <div class="entry">
 214       <div class="title">
 215         <a href="https://people.skolelinux.org/pere/blog/Regjeringen__FAD_og_DIFI_g_r_inn_for___fjerne_ODF_som_obligatorisk_standard_i_det_offentlige.html">Regjeringen, FAD og DIFI går inn for å fjerne ODF som obligatorisk standard i det offentlige</a>
 216       </div>
 217       <div class="date">
 218         18th March 2013
 219       </div>
 220       <div class="body">
 221         <p>I
 222 <a href="http://standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">siste
 223 høring</a> om
 224 <a href="http://standard.difi.no/forvaltningsstandarder">referansekatalogen
 225 for IT-standarder i offentlig sektor</a>, med høringsfrist 2012-09-30
 226 (DIFI-sak 2012/498), ble det foreslått å fjerne ODF som obligatorisk
 227 standard når en publiserte dokumenter som skulle kunne redigeres
 228 videre av mottaker.  NUUG og andre protesterte på forslaget, som er et
 229 langt steg tilbake når det gjelder å sikre like rettigheter for alle
 230 når en kommuniserer med det offentlige.  For noen dager siden ble jeg
 231 oppmerksom på at Direktoratet for forvaltning og IKT (DIFI) og
 232 Fornyings-,administrasjons- og kirkedepartementet (FAD) har
 233 konkludert, og oversendt forslag til regjeringen i saken. FADs
 234 dokument
 235 <a href="http://www.oep.no/search/result.html?period=none&descType=both&caseNumber=2012%2F2168&senderType=both&documentType=all&list2=94&searchType=advanced&Search=S%C3%B8k+i+journaler">2012/2168</a>-8,
 236 «Utkast til endring av standardiseringsforskriften» datert 2013-02-06
 237 har følgende triste oppsummering fra høringen i saken:</p>
 238
 239 <p><blockquote>
 240 Det kom noen innvendinger på forslaget om å fjerne ODF som
 241 obligatorisk standard for redigerbare dokumenter. Innvendingene har
 242 ikke blitt ilagt avgjørende vekt.
 243 </blockquote></p>
 244
 245 <p>Ved å fjerne ODF som obligatorisk format ved publisering av
 246 redigerbare dokumenter setter en Norge tiår tilbake.  Det som vil skje
 247 er at offentlige etater går tilbake til kun å publisere dokumenter på
 248 et av de mange formatene til Microsoft Office, og alle som ikke
 249 aksepterer bruksvilkårene til Microsoft eller ikke har råd til å bruke
 250 penger på å få tilgang til Microsoft Office må igjen basere seg på
 251 verktøy fra utviklerne som er avhengig av å reversutvikle disse
 252 formatene.  I og med at ISO-spesifikasjonen for OOXML ikke komplett og
 253 korrekt spesifiserer formatene til MS Office (men er nyttige å titte i
 254 når en reversutvikler), er en tilbake til en situasjon der en ikke har
 255 <a href="https://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
 256 fri og åpen standard</a> å forholde seg til, men i stedet må springe
 257 etter Microsoft.  Alle andre leverandører enn Microsoft vil dermed ha
 258 en seriøs ulempe.  Det er som å fjerne krav om bruk av meter som
 259 måleenhet, og heretter aksepterer alle måleenheter som like gyldige,
 260 når en vet at den mest brukte enheten vil være armlengden til Steve
 261 Ballmer slik Microsoft måler den.</p>
 262
 263 <p>Jeg er ikke sikker på om forslaget er vedtatt av regjeringen ennå.
 264 Kristian Bergem hos DIFI nevnte på et møte forrige tirsdag at han
 265 trodde det var vedtatt i statsråd 8. mars, men jeg har ikke klart å
 266 finne en skriftlig kilde på regjeringen.no som bekrefter dette.
 267 Kanskje det ennå ikke er for sent...</p>
 268
 269 <p>Jeg ba i forrige uke om innsyn i dokument 6, 7 og 8 i FAD-saken, og
 270 har i dag fått innsyn i dokument 7 og 8.  Ble nektet innsyn i
 271 dokumentet med tittelen «Oppsummering av høring om endringer i
 272 forskrift om IT-standarder i offentlig forvaltning» med hjemmel i
 273 off. lovens §15.1, så det er vanskelig å vite hvordan argumentene fra
 274 høringen ble mottatt og forstått av saksbehandleren hos DIFI.  Lurer
 275 på hvordan jeg kan klage på at jeg ikke fikk se oppsummeringen.  Fikk
 276 tre PDFer tilsendt fra FAD,
 277 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/20130115%20Notat%20FAD%20-%20EHF.pdf%20(L)(889185).pdf">Endring av underversjon i EHF</a>,
 278 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/Bakgrunnsnotat%20knyttet%20til%20versjon%20av%20EHF%20standarden%20i%20Forskrift%20om%20IT-standarder%20i%20offentlig%20sektor.pdf">Bakgrunnsnotat knyttet til versjon av EHF standarden i Forskrift om IT-standarder i offentlig sektor</a> og
 279 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/Utkast%20Kongelig%20resolusjon.docx%20(L)(898064).pdf">Utkast til endring av standardiseringsforskriften</a>, hvis du vil ta en titt.</p>
 280
 281       </div>
 282       <div class="tags">
 283
 284
 285         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 286
 287
 288       </div>
 289     </div>
 290     <div class="padding"></div>
 291
 292     <div class="entry">
 293       <div class="title">
 294         <a href="https://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Trenger en avtale med MPEG-LA for å publisere og kringkaste H.264-video?</a>
 295       </div>
 296       <div class="date">
 297         21st June 2012
 298       </div>
 299       <div class="body">
 300         <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
 301 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
 302 <a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
 303 fri og åpen standard</a> i henhold til
 304 <a href="https://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
 305 til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
 306 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
 307 gjelder Norge.  Det ser uansett ut til å være en juridisk interessant
 308 problemstilling.  Men jeg tenkte her om dagen som så, at hvis det er
 309 nødvendig, så har store aktører som
 310 <a href="http://www.nrk.no/">NRK</a> og
 311 <a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
 312 slik avtale.  Jeg har derfor sendt forespørsel til begge (for
 313 regjeringen sin del er det Departementenes Servicesenter som gjør
 314 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
 315 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
 316 av MPEG-LA.  Her er kopi av eposten jeg har sendt til
 317 <a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
 318 Forespørselen til NRK er veldig lik.</p>
 319
 320 <p><blockquote>
 321
 322 <p>Date: Tue, 19 Jun 2012 15:18:33 +0200
 323 <br>From: Petter Reinholdtsen
 324 <br>To: postmottak@dss.dep.no
 325 <br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
 326
 327 <p>Hei.  Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
 328 til avtaler rundt bruk av videoformatene MPEG og H.264.  Jeg er
 329 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
 330 eller noen som representerer MPEG-LA i Norge.</p>
 331
 332 <p>MPEG og H.264 er videoformater som brukes både til kringkasting
 333 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
 334 via Adobe Flash.  MPEG-LA, &lt;URL:
 335 <a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> &gt;, er
 336 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
 337 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
 338 bruksrett for MPEG og H.264.</p>
 339
 340 <p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
 341 videoformater, og dette ser ut til å være organisert av DSS.  Jeg
 342 antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
 343
 344 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge &lt;URL:
 345 <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
 346 &gt;:</p>
 347
 348 <p><blockquote>
 349
 350   <p>6.17. AVC DISTRIBUTION. The following notice applies to software
 351   containing AVC import and export functionality: THIS PRODUCT IS
 352   LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
 353   NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
 354   WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
 355   WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
 356   ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
 357   LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
 358   IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
 359   FROM MPEG LA L.L.C. SEE
 360   <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
 361
 362 </blockquote></p>
 363
 364 <p>Her er det kun "non-commercial" og "personal and non-commercial"
 365 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
 366
 367 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
 368 følgende klausul i følge &lt;URL:
 369 <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
 370 &gt;:</p>
 371
 372 <p><blockquote>
 373
 374   <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
 375   funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
 376   kommersiell bruk ekstra lisensiering og følgende gjelder:
 377   AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
 378   FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
 379   KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
 380   OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
 381   PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
 382   FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
 383   AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
 384   FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
 385 </blockquote></p>
 386
 387 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
 388 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
 389 til å bruke programmet/utstyret hvis en skal lage noe annet enn
 390 private filmer og i ikke-kommersiell virksomhet.</p>
 391
 392 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
 393 ikke er begrenset av de generelle bruksvilkårene som gjelder for
 394 utstyr som bruker MPEG og/eller H.264.</p>
 395 </blockquote></p>
 396
 397 <p>Nå venter jeg spent på svaret.  Jeg planlegger å blogge om svaret
 398 her.</p>
 399
 400       </div>
 401       <div class="tags">
 402
 403
 404         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
 405
 406
 407       </div>
 408     </div>
 409     <div class="padding"></div>
 410
 411     <div class="entry">
 412       <div class="title">
 413         <a href="https://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html">HTC One X - Your video?  What do you mean?</a>
 414       </div>
 415       <div class="date">
 416         26th April 2012
 417       </div>
 418       <div class="body">
 419         <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
 420 article today</a> published by Computerworld Norway, the photographer
 421 <a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
 422 that the video editor application included with
 423 <a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
 424 X</a> have some quite surprising terms of use.  The article is mostly
 425 based on the twitter message from mister Urke, stating:
 426
 427 <p><blockquote>
 428 "<a href="http://twitter.com/urke/status/194062269724897280">Drøy
 429 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
 430 kan jeg KUN bruke dem privat.</a>"
 431 </blockquote></p>
 432
 433 <p>I quickly translated it to this English message:</p>
 434
 435 <p><blockquote>
 436 "Arrogant user agreement: HTC can use MY edited videos
 437 commercially.  Although I can ONLY use them privately."
 438 </blockquote></p>
 439
 440 <p>I've been unable to find the text of the license term myself, but
 441 suspect it is a variation of the MPEG-LA terms I
 442 <a href="https://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
 443 with my Canon IXUS 130</a>.  The HTC One X specification specifies that
 444 the recording format of the phone is .amr for audio and .mp3 for
 445 video.  AMR is
 446 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
 447 Multi-Rate audio codec</a> with patents which according to the
 448 Wikipedia article require an license agreement with
 449 <a href="http://www.voiceage.com/">VoiceAge</a>.  MP4 is
 450 <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
 451 H.264</a>, which according to Wikipedia require a licence agreement
 452 with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
 453
 454 <p>I know why I prefer
 455 <a href="http://www.digistan.org/open-standard:definition">free and open
 456 standards</a> also for video.</p>
 457
 458       </div>
 459       <div class="tags">
 460
 461
 462         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
 463
 464
 465       </div>
 466     </div>
 467     <div class="padding"></div>
 468
 469     <div class="entry">
 470       <div class="title">
 471         <a href="https://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html">What standards are Free and Open as defined by Digistan?</a>
 472       </div>
 473       <div class="date">
 474         30th December 2010
 475       </div>
 476       <div class="body">
 477         <p>After trying to
 478 <a href="https://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
 479 Ogg Theora</a> to
 480 <a href="http://www.digistan.org/open-standard:definition">the Digistan
 481 definition</a> of a free and open standard, I concluded that this need
 482 to be done for more standards and started on a framework for doing
 483 this.  As a start, I want to get the status for all the standards in
 484 the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
 485 JPEG, PNG, SVG and others.  But to be able to complete this in a
 486 reasonable time frame, I will need help.</p>
 487
 488 <p>If you want to help out with this work, please visit
 489 <a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
 490 wiki pages I have set up for this</a>, and let me know that you want
 491 to help out.  The IRC channel #nuug on irc.freenode.net is a good
 492 place to coordinate this for now, as it is the IRC channel for the
 493 NUUG association where I have created the framework (I am the leader
 494 of the Norwegian Unix User Group).</p>
 495
 496 <p>The framework is still forming, and a lot is left to do.  Do not be
 497 scared by the sketchy form of the current pages. :)</p>
 498
 499       </div>
 500       <div class="tags">
 501
 502
 503         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 504
 505
 506       </div>
 507     </div>
 508     <div class="padding"></div>
 509
 510     <div class="entry">
 511       <div class="title">
 512         <a href="https://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
 513       </div>
 514       <div class="date">
 515         27th December 2010
 516       </div>
 517       <div class="body">
 518         <p>One of the reasons I like the Digistan definition of
 519 "<a href="http://www.digistan.org/open-standard:definition">Free and
 520 Open Standard</a>" is that this is a new term, and thus the meaning of
 521 the term has been decided by Digistan.  The term "Open Standard" has
 522 become so misunderstood that it is no longer very useful when talking
 523 about standards.  One end up discussing which definition is the best
 524 one and with such frame the only one gaining are the proponents of
 525 de-facto standards and proprietary solutions.</p>
 526
 527 <p>But to give us an idea about the diversity of definitions of open
 528 standards, here are a few that I know about.  This list is not
 529 complete, but can be a starting point for those that want to do a
 530 complete survey.  More definitions are available on the
 531 <a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
 532 page</a>.</p>
 533
 534 <p>First off is my favourite, the definition from the European
 535 Interoperability Framework version 1.0.  Really sad to notice that BSA
 536 and others has succeeded in getting it removed from version 2.0 of the
 537 framework by stacking the committee drafting the new version with
 538 their own people.  Anyway, the definition is still available and it
 539 include the key properties needed to make sure everyone can use a
 540 specification on equal terms.</p>
 541
 542 <blockquote>
 543
 544 <p>The following are the minimal characteristics that a specification
 545 and its attendant documents must have in order to be considered an
 546 open standard:</p>
 547
 548 <ul>
 549
 550 <li>The standard is adopted and will be maintained by a not-for-profit
 551 organisation, and its ongoing development occurs on the basis of an
 552 open decision-making procedure available to all interested parties
 553 (consensus or majority decision etc.).</li>
 554
 555 <li>The standard has been published and the standard specification
 556 document is available either freely or at a nominal charge. It must be
 557 permissible to all to copy, distribute and use it for no fee or at a
 558 nominal fee.</li>
 559
 560 <li>The intellectual property - i.e. patents possibly present - of
 561 (parts of) the standard is made irrevocably available on a royalty-
 562 free basis.</li>
 563
 564 <li>There are no constraints on the re-use of the standard.</li>
 565
 566 </ul>
 567 </blockquote>
 568
 569 <p>Another one originates from my friends over at
 570 <a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
 571 support for <a href="http://www.aaben-standard.dk/">this
 572 definition</a> in 2004.  It even made it into the Danish parlament as
 573 <a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
 574 definition of a open standard</a>.  Another from a different part of
 575 the Danish government is available from the wikipedia page.</p>
 576
 577 <blockquote>
 578
 579 <p>En åben standard opfylder følgende krav:</p>
 580
 581 <ol>
 582
 583 <li>Veldokumenteret med den fuldstændige specifikation offentligt
 584 tilgængelig.</li>
 585
 586 <li>Frit implementerbar uden økonomiske, politiske eller juridiske
 587 begrænsninger på implementation og anvendelse.</li>
 588
 589 <li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
 590 "standardiseringsorganisation") via en åben proces.</li>
 591
 592 </ol>
 593
 594 </blockquote>
 595
 596 <p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
 597 definition</a> from Free Software Foundation Europe.</p>
 598
 599 <blockquote>
 600
 601 <p>An Open Standard refers to a format or protocol that is</p>
 602
 603 <ol>
 604
 605 <li>subject to full public assessment and use without constraints in a
 606 manner equally available to all parties;</li>
 607
 608 <li>without any components or extensions that have dependencies on
 609 formats or protocols that do not meet the definition of an Open
 610 Standard themselves;</li>
 611
 612 <li>free from legal or technical clauses that limit its utilisation by
 613 any party or in any business model;</li>
 614
 615 <li>managed and further developed independently of any single vendor
 616 in a process open to the equal participation of competitors and third
 617 parties;</li>
 618
 619 <li>available in multiple complete implementations by competing
 620 vendors, or as a complete implementation equally available to all
 621 parties.</li>
 622
 623 </ol>
 624
 625 </blockquote>
 626
 627 <p>A long time ago, SUN Microsystems, now bought by Oracle, created
 628 its
 629 <a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
 630 Standards Checklist</a> with a fairly detailed description.</p>
 631
 632 <blockquote>
 633 <p>Creation and Management of an Open Standard
 634
 635 <ul>
 636
 637 <li>Its development and management process must be collaborative and
 638   democratic:
 639
 640          <ul>
 641
 642          <li>Participation must be accessible to all those who wish to
 643             participate and can meet fair and reasonable criteria
 644             imposed by the organization under which it is developed
 645             and managed.</li>
 646
 647          <li>The processes must be documented and, through a known
 648             method, can be changed through input from all
 649             participants.</li>
 650
 651          <li>The process must be based on formal and binding commitments for
 652             the disclosure and licensing of intellectual property rights.</li>
 653
 654          <li>Development and management should strive for consensus,
 655             and an appeals process must be clearly outlined.</li>
 656
 657          <li>The standard specification must be open to extensive
 658             public review at least once in its life-cycle, with
 659             comments duly discussed and acted upon, if required.</li>
 660
 661          </ul>
 662
 663 </li>
 664
 665 </ul>
 666
 667 <p>Use and Licensing of an Open Standard</p>
 668 <ul>
 669
 670 <li>The standard must describe an interface, not an implementation,
 671   and the industry must be capable of creating multiple, competing
 672   implementations to the interface described in the standard without
 673   undue or restrictive constraints.  Interfaces include APIs,
 674   protocols, schemas, data formats and their encoding.</li>
 675
 676 <li> The standard must not contain any proprietary "hooks" that create
 677   a technical or economic barriers</li>
 678
 679 <li>Faithful implementations of the standard must
 680   interoperate. Interoperability means the ability of a computer
 681   program to communicate and exchange information with other computer
 682   programs and mutually to use the information which has been
 683   exchanged. This includes the ability to use, convert, or exchange
 684   file formats, protocols, schemas, interface information or
 685   conventions, so as to permit the computer program to work with other
 686   computer programs and users in all the ways in which they are
 687   intended to function.</li>
 688
 689 <li>It must be permissible for anyone to copy, distribute and read the
 690   standard for a nominal fee, or even no fee. If there is a fee, it
 691   must be low enough to not preclude widespread use.</li>
 692
 693 <li>It must be possible for anyone to obtain free (no royalties or
 694   fees; also known as "royalty free"), worldwide, non-exclusive and
 695   perpetual licenses to all essential patent claims to make, use and
 696   sell products based on the standard.  The only exceptions are
 697   terminations per the reciprocity and defensive suspension terms
 698   outlined below. Essential patent claims include pending, unpublished
 699   patents, published patents, and patent applications. The license is
 700   only for the exact scope of the standard in question.
 701
 702       <ul>
 703
 704       <li> May be conditioned only on reciprocal licenses to any of
 705         licensees' patent claims essential to practice that standard
 706         (also known as a reciprocity clause)</li>
 707
 708       <li> May be terminated as to any licensee who sues the licensor
 709         or any other licensee for infringement of patent claims
 710         essential to practice that standard (also known as a
 711         "defensive suspension" clause)</li>
 712
 713       <li> The same licensing terms are available to every potential
 714         licensor</li>
 715
 716       </ul>
 717 </li>
 718
 719 <li>The licensing terms of an open standards must not preclude
 720   implementations of that standard under open source licensing terms
 721   or restricted licensing terms</li>
 722
 723 </ul>
 724
 725 </blockquote>
 726
 727 <p>It is said that one of the nice things about standards is that
 728 there are so many of them.  As you can see, the same holds true for
 729 open standard definitions.  Most of the definitions have a lot in
 730 common, and it is not really controversial what properties a open
 731 standard should have, but the diversity of definitions have made it
 732 possible for those that want to avoid a level marked field and real
 733 competition to downplay the significance of open standards.  I hope we
 734 can turn this tide by focusing on the advantages of Free and Open
 735 Standards.</p>
 736
 737       </div>
 738       <div class="tags">
 739
 740
 741         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 742
 743
 744       </div>
 745     </div>
 746     <div class="padding"></div>
 747
 748     <div class="entry">
 749       <div class="title">
 750         <a href="https://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">Is Ogg Theora a free and open standard?</a>
 751       </div>
 752       <div class="date">
 753         25th December 2010
 754       </div>
 755       <div class="body">
 756         <p><a href="http://www.digistan.org/open-standard:definition">The
 757 Digistan definition</a> of a free and open standard reads like this:</p>
 758
 759 <blockquote>
 760
 761 <p>The Digital Standards Organization defines free and open standard
 762 as follows:</p>
 763
 764 <ol>
 765
 766 <li>A free and open standard is immune to vendor capture at all stages
 767 in its life-cycle. Immunity from vendor capture makes it possible to
 768 freely use, improve upon, trust, and extend a standard over time.</li>
 769
 770 <li>The standard is adopted and will be maintained by a not-for-profit
 771 organisation, and its ongoing development occurs on the basis of an
 772 open decision-making procedure available to all interested
 773 parties.</li>
 774
 775 <li>The standard has been published and the standard specification
 776 document is available freely. It must be permissible to all to copy,
 777 distribute, and use it freely.</li>
 778
 779 <li>The patents possibly present on (parts of) the standard are made
 780 irrevocably available on a royalty-free basis.</li>
 781
 782 <li>There are no constraints on the re-use of the standard.</li>
 783
 784 </ol>
 785
 786 <p>The economic outcome of a free and open standard, which can be
 787 measured, is that it enables perfect competition between suppliers of
 788 products based on the standard.</p>
 789 </blockquote>
 790
 791 <p>For a while now I have tried to figure out of Ogg Theora is a free
 792 and open standard according to this definition.  Here is a short
 793 writeup of what I have been able to gather so far.  I brought up the
 794 topic on the Xiph advocacy mailing list
 795 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
 796 July 2009</a>, for those that want to see some background information.
 797 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
 798 the Ogg Theora specification fulfils the Digistan definition.</p>
 799
 800 <p><strong>Free from vendor capture?</strong></p>
 801
 802 <p>As far as I can see, there is no single vendor that can control the
 803 Ogg Theora specification.  It can be argued that the
 804 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
 805 given that it is a non-profit foundation with the expressed goal
 806 making free and open protocols and standards available, it is not
 807 obvious that this is a real risk.  One issue with the Xiph
 808 foundation is that its inner working (as in board member list, or who
 809 control the foundation) are not easily available on the web.  I've
 810 been unable to find out who is in the foundation board, and have not
 811 seen any accounting information documenting how money is handled nor
 812 where is is spent in the foundation.  It is thus not obvious for an
 813 external observer who control The Xiph foundation, and for all I know
 814 it is possible for a single vendor to take control over the
 815 specification.  But it seem unlikely.</p>
 816
 817 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
 818
 819 <p>Assuming that the Xiph foundation is the organisation its web pages
 820 claim it to be, this point is fulfilled.  If Xiph foundation is
 821 controlled by a single vendor, it isn't, but I have not found any
 822 documentation indicating this.</p>
 823
 824 <p>According to
 825 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
 826 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
 827 government, the Xiph foundation is a non-commercial organisation and
 828 the development process is open, transparent and non-Discrimatory.
 829 Until proven otherwise, I believe it make most sense to believe the
 830 report is correct.</p>
 831
 832 <p><strong>Specification freely available?</strong></p>
 833
 834 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
 835 container format</a> and both the
 836 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
 837 <a href="http://theora.org/doc/">Theora</a> codeces are available on
 838 the web.  This are the terms in the Vorbis and Theora specification:
 839
 840 <blockquote>
 841
 842 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
 843 specifications, whether in private, public, or corporate
 844 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
 845 the right to set the Ogg [Vorbis/Theora] specification and certify
 846 specification compliance.
 847
 848 </blockquote>
 849
 850 <p>The Ogg container format is specified in IETF
 851 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
 852 this is the term:<p>
 853
 854 <blockquote>
 855
 856 <p>This document and translations of it may be copied and furnished to
 857 others, and derivative works that comment on or otherwise explain it
 858 or assist in its implementation may be prepared, copied, published and
 859 distributed, in whole or in part, without restriction of any kind,
 860 provided that the above copyright notice and this paragraph are
 861 included on all such copies and derivative works.  However, this
 862 document itself may not be modified in any way, such as by removing
 863 the copyright notice or references to the Internet Society or other
 864 Internet organizations, except as needed for the purpose of developing
 865 Internet standards in which case the procedures for copyrights defined
 866 in the Internet Standards process must be followed, or as required to
 867 translate it into languages other than English.</p>
 868
 869 <p>The limited permissions granted above are perpetual and will not be
 870 revoked by the Internet Society or its successors or assigns.</p>
 871 </blockquote>
 872
 873 <p>All these terms seem to allow unlimited distribution and use, an
 874 this term seem to be fulfilled.  There might be a problem with the
 875 missing permission to distribute modified versions of the text, and
 876 thus reuse it in other specifications.  Not quite sure if that is a
 877 requirement for the Digistan definition.</p>
 878
 879 <p><strong>Royalty-free?</strong></p>
 880
 881 <p>There are no known patent claims requiring royalties for the Ogg
 882 Theora format.
 883 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
 884 and
 885 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
 886 Jobs</a> in Apple claim to know about some patent claims (submarine
 887 patents) against the Theora format, but no-one else seem to believe
 888 them.  Both Opera Software and the Mozilla Foundation have looked into
 889 this and decided to implement Ogg Theora support in their browsers
 890 without paying any royalties.  For now the claims from MPEG-LA and
 891 Steve Jobs seem more like FUD to scare people to use the H.264 codec
 892 than any real problem with Ogg Theora.</p>
 893
 894 <p><strong>No constraints on re-use?</strong></p>
 895
 896 <p>I am not aware of any constraints on re-use.</p>
 897
 898 <p><strong>Conclusion</strong></p>
 899
 900 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
 901 depend on the governing structure of the Xiph foundation.  Given the
 902 background report used by the Norwegian government, I believe it is
 903 safe to assume the last two requirements are fulfilled too, but it
 904 would be nice if the Xiph foundation web site made it easier to verify
 905 this.</p>
 906
 907 <p>It would be nice to see other analysis of other specifications to
 908 see if they are free and open standards.</p>
 909
 910       </div>
 911       <div class="tags">
 912
 913
 914         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>.
 915
 916
 917       </div>
 918     </div>
 919     <div class="padding"></div>
 920
 921     <div class="entry">
 922       <div class="title">
 923         <a href="https://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html">The reply from Edgar Villanueva to Microsoft in Peru</a>
 924       </div>
 925       <div class="date">
 926         25th December 2010
 927       </div>
 928       <div class="body">
 929         <p>A few days ago
 930 <a href="http://www.idg.no/computerworld/article189879.ece">an
 931 article</a> in the Norwegian Computerworld magazine about how version
 932 2.0 of
 933 <a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
 934 Interoperability Framework</a> has been successfully lobbied by the
 935 proprietary software industry to remove the focus on free software.
 936 Nothing very surprising there, given
 937 <a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
 938 reports</a> on how Microsoft and others have stacked the committees in
 939 this work.  But I find this very sad.   The definition of
 940 <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
 941 open standard from version 1</a> was very good, and something I
 942 believe should be used also in the future, alongside
 943 <a href="http://www.digistan.org/open-standard:definition">the
 944 definition from Digistan</A>.  Version 2 have removed the open
 945 standard definition from its content.</p>
 946
 947 <p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
 948 Villanueva, congressman in Peru at the time, to Microsoft as a reply
 949 to Microsofts attack on his proposal regarding the use of free software
 950 in the public sector in Peru.  As the text was not available from a
 951 few of the URLs where it used to be available, I copy it here from
 952 <a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
 953 source</a> to ensure it is available also in the future.  Some
 954 background information about that story is available in
 955 <a href="http://www.linuxjournal.com/article/6099">an article</a> from
 956 Linux Journal in 2002.</p>
 957
 958 <blockquote>
 959 <p>Lima, 8th of April, 2002<br>
 960 To: Señor JUAN ALBERTO GONZÁLEZ<br>
 961 General Manager of Microsoft Perú</p>
 962
 963 <p>Dear Sir:</p>
 964
 965 <p>First of all, I thank you for your letter of March 25, 2002 in which you state the official position of Microsoft relative to Bill Number 1609, Free Software in Public Administration, which is indubitably inspired by the desire for Peru to find a suitable place in the global technological context. In the same spirit, and convinced that we will find the best solutions through an exchange of clear and open ideas, I will take this opportunity to reply to the commentaries included in your letter.</p>
 966
 967 <p>While acknowledging that opinions such as yours constitute a significant contribution, it would have been even more worthwhile for me if, rather than formulating objections of a general nature (which we will analyze in detail later) you had gathered solid arguments for the advantages that proprietary software could bring to the Peruvian State, and to its citizens in general, since this would have allowed a more enlightening exchange in respect of each of our positions.</p>
 968
 969 <p>With the aim of creating an orderly debate, we will assume that what you call "open source software" is what the Bill defines as "free software", since there exists software for which the source code is distributed together with the program, but which does not fall within the definition established by the Bill; and that what you call "commercial software" is what the Bill defines as "proprietary" or "unfree", given that there exists free software which is sold in the market for a price like any other good or service.</p>
 970
 971 <p>It is also necessary to make it clear that the aim of the Bill we are discussing is not directly related to the amount of direct savings that can by made by using free software in state institutions. That is in any case a marginal aggregate value, but in no way is it the chief focus of the Bill. The basic principles which inspire the Bill are linked to the basic guarantees of a state of law, such as:</p>
 972
 973 <p>
 974 <ul>
 975 <li>Free access to public information by the citizen. </li>
 976 <li>Permanence of public data. </li>
 977 <li>Security of the State and citizens.</li>
 978 </ul>
 979 </p>
 980
 981 <p>To guarantee the free access of citizens to public information, it is indispensable that the encoding of data is not tied to a single provider. The use of standard and open formats gives a guarantee of this free access, if necessary through the creation of compatible free software.</p>
 982
 983 <p>To guarantee the permanence of public data, it is necessary that the usability and maintenance of the software does not depend on the goodwill of the suppliers, or on the monopoly conditions imposed by them. For this reason the State needs systems the development of which can be guaranteed due to the availability of the source code.</p>
 984
 985 <p>To guarantee national security or the security of the State, it is indispensable to be able to rely on systems without elements which allow control from a distance or the undesired transmission of information to third parties. Systems with source code freely accessible to the public are required to allow their inspection by the State itself, by the citizens, and by a large number of independent experts throughout the world. Our proposal brings further security, since the knowledge of the source code will eliminate the growing number of programs with *spy code*. </p>
 986
 987 <p>In the same way, our proposal strengthens the security of the citizens, both in their role as legitimate owners of information managed by the state, and in their role as consumers. In this second case, by allowing the growth of a widespread availability of free software not containing *spy code* able to put at risk privacy and individual freedoms.</p>
 988
 989 <p>In this sense, the Bill is limited to establishing the conditions under which the state bodies will obtain software in the future, that is, in a way compatible with these basic principles.</p>
 990
 991
 992 <p>From reading the Bill it will be clear that once passed:<br>
 993 <li>the law does not forbid the production of proprietary software</li>
 994 <li>the law does not forbid the sale of proprietary software</li>
 995 <li>the law does not specify which concrete software to use</li>
 996 <li>the law does not dictate the supplier from whom software will be bought</li>
 997 <li>the law does not limit the terms under which a software product can be licensed.</li>
 998
 999 </p>
1000
1001 <p>What the Bill does express clearly, is that, for software to be acceptable for the state it is not enough that it is technically capable of fulfilling a task, but that further the contractual conditions must satisfy a series of requirements regarding the license, without which the State cannot guarantee the citizen adequate processing of his data, watching over its integrity, confidentiality, and accessibility throughout time, as these are very critical aspects for its normal functioning.</p>
1002
1003 <p>We agree, Mr. Gonzalez, that information and communication technology have a significant impact on the quality of life of the citizens (whether it be positive or negative). We surely also agree that the basic values I have pointed out above are fundamental in a democratic state like Peru. So we are very interested to know of any other way of guaranteeing these principles, other than through the use of free software in the terms defined by the Bill.</p>
1004
1005 <p>As for the observations you have made, we will now go on to analyze them in detail:</p>
1006
1007 <p>Firstly, you point out that: "1. The bill makes it compulsory for all public bodies to use only free software, that is to say open source software, which breaches the principles of equality before the law, that of non-discrimination and the right of free private enterprise, freedom of industry and of contract, protected by the constitution."</p>
1008
1009 <p>This understanding is in error. The Bill in no way affects the rights you list; it limits itself entirely to establishing conditions for the use of software on the part of state institutions, without in any way meddling in private sector transactions. It is a well established principle that the State does not enjoy the wide spectrum of contractual freedom of the private sector, as it is limited in its actions precisely by the requirement for transparency of public acts; and in this sense, the preservation of the greater common interest must prevail when legislating on the matter.</p>
1010
1011 <p>The Bill protects equality under the law, since no natural or legal person is excluded from the right of offering these goods to the State under the conditions defined in the Bill and without more limitations than those established by the Law of State Contracts and Purchasing (T.U.O. by Supreme Decree No. 012-2001-PCM).</p>
1012
1013 <p>The Bill does not introduce any discrimination whatever, since it only establishes *how* the goods have to be provided (which is a state power) and not *who* has to provide them (which would effectively be discriminatory, if restrictions based on national origin, race religion, ideology, sexual preference etc. were imposed). On the contrary, the Bill is decidedly antidiscriminatory. This is so because by defining with no room for doubt the conditions for the provision of software, it prevents state bodies from using software which has a license including discriminatory conditions.</p>
1014
1015 <p>It should be obvious from the preceding two paragraphs that the Bill does not harm free private enterprise, since the latter can always choose under what conditions it will produce software; some of these will be acceptable to the State, and others will not be since they contradict the guarantee of the basic principles listed above. This free initiative is of course compatible with the freedom of industry and freedom of contract (in the limited form in which the State can exercise the latter). Any private subject can produce software under the conditions which the State requires, or can refrain from doing so. Nobody is forced to adopt a model of production, but if they wish to provide software to the State, they must provide the mechanisms which guarantee the basic principles, and which are those described in the Bill.</p>
1016
1017 <p>By way of an example: nothing in the text of the Bill would prevent your company offering the State bodies an office "suite", under the conditions defined in the Bill and setting the price that you consider satisfactory. If you did not, it would not be due to restrictions imposed by the law, but to business decisions relative to the method of commercializing your products, decisions with which the State is not involved.</p>
1018
1019 <p>To continue; you note that:" 2. The bill, by making the use of open source software compulsory, would establish discriminatory and non competitive practices in the contracting and purchasing by public bodies..."</p>
1020
1021 <p>This statement is just a reiteration of the previous one, and so the response can be found above. However, let us concern ourselves for a moment with your comment regarding "non-competitive ... practices."</p>
1022
1023 <p>Of course, in defining any kind of purchase, the buyer sets conditions which relate to the proposed use of the good or service. From the start, this excludes certain manufacturers from the possibility of competing, but does not exclude them "a priori", but rather based on a series of principles determined by the autonomous will of the purchaser, and so the process takes place in conformance with the law. And in the Bill it is established that *no one* is excluded from competing as far as he guarantees the fulfillment of the basic principles.</p>
1024
1025 <p>Furthermore, the Bill *stimulates* competition, since it tends to generate a supply of software with better conditions of usability, and to better existing work, in a model of continuous improvement.</p>
1026
1027 <p>On the other hand, the central aspect of competivity is the chance to provide better choices to the consumer. Now, it is impossible to ignore the fact that marketing does not play a neutral role when the product is offered on the market (since accepting the opposite would lead one to suppose that firms' expenses in marketing lack any sense), and that therefore a significant expense under this heading can influence the decisions of the purchaser. This influence of marketing is in large measure reduced by the bill that we are backing, since the choice within the framework proposed is based on the *technical merits* of the product and not on the effort put into commercialization by the producer; in this sense, competitiveness is increased, since the smallest software producer can compete on equal terms with the most powerful corporations.</p>
1028
1029 <p>It is necessary to stress that there is no position more anti-competitive than that of the big software producers, which frequently abuse their dominant position, since in innumerable cases they propose as a solution to problems raised by users: "update your software to the new version" (at the user's expense, naturally); furthermore, it is common to find arbitrary cessation of technical help for products, which, in the provider's judgment alone, are "old"; and so, to receive any kind of technical assistance, the user finds himself forced to migrate to new versions (with non-trivial costs, especially as changes in hardware platform are often involved). And as the whole infrastructure is based on proprietary data formats, the user stays "trapped" in the need to continue using products from the same supplier, or to make the huge effort to change to another environment (probably also proprietary).</p>
1030
1031 <p>You add: "3. So, by compelling the State to favor a business model based entirely on open source, the bill would only discourage the local and international manufacturing companies, which are the ones which really undertake important expenditures, create a significant number of direct and indirect jobs, as well as contributing to the GNP, as opposed to a model of open source software which tends to have an ever weaker economic impact, since it mainly creates jobs in the service sector."</p>
1032
1033 <p>I do not agree with your statement. Partly because of what you yourself point out in paragraph 6 of your letter, regarding the relative weight of services in the context of software use. This contradiction alone would invalidate your position. The service model, adopted by a large number of companies in the software industry, is much larger in economic terms, and with a tendency to increase, than the licensing of programs.</p>
1034
1035 <p>On the other hand, the private sector of the economy has the widest possible freedom to choose the economic model which best suits its interests, even if this freedom of choice is often obscured subliminally by the disproportionate expenditure on marketing by the producers of proprietary software.</p>
1036
1037 <p>In addition, a reading of your opinion would lead to the conclusion that the State market is crucial and essential for the proprietary software industry, to such a point that the choice made by the State in this bill would completely eliminate the market for these firms. If that is true, we can deduce that the State must be subsidizing the proprietary software industry. In the unlikely event that this were true, the State would have the right to apply the subsidies in the area it considered of greatest social value; it is undeniable, in this improbable hypothesis, that if the State decided to subsidize software, it would have to do so choosing the free over the proprietary, considering its social effect and the rational use of taxpayers money.</p>
1038
1039 <p>In respect of the jobs generated by proprietary software in countries like ours, these mainly concern technical tasks of little aggregate value; at the local level, the technicians who provide support for proprietary software produced by transnational companies do not have the possibility of fixing bugs, not necessarily for lack of technical capability or of talent, but because they do not have access to the source code to fix it. With free software one creates more technically qualified employment and a framework of free competence where success is only tied to the ability to offer good technical support and quality of service, one stimulates the market, and one increases the shared fund of knowledge, opening up alternatives to generate services of greater total value and a higher quality level, to the benefit of all involved: producers, service organizations, and consumers.</p>
1040
1041 <p>It is a common phenomenon in developing countries that local software industries obtain the majority of their takings in the service sector, or in the creation of "ad hoc" software. Therefore, any negative impact that the application of the Bill might have in this sector will be more than compensated by a growth in demand for services (as long as these are carried out to high quality standards). If the transnational software companies decide not to compete under these new rules of the game, it is likely that they will undergo some decrease in takings in terms of payment for licenses; however, considering that these firms continue to allege that much of the software used by the State has been illegally copied, one can see that the impact will not be very serious. Certainly, in any case their fortune will be determined by market laws, changes in which cannot be avoided; many firms traditionally associated with proprietary software have already set out on the road (supported by copious expense) of providing services associated with free software, which shows that the models are not mutually exclusive.</p>
1042
1043 <p>With this bill the State is deciding that it needs to preserve certain fundamental values. And it is deciding this based on its sovereign power, without affecting any of the constitutional guarantees. If these values could be guaranteed without having to choose a particular economic model, the effects of the law would be even more beneficial. In any case, it should be clear that the State does not choose an economic model; if it happens that there only exists one economic model capable of providing software which provides the basic guarantee of these principles, this is because of historical circumstances, not because of an arbitrary choice of a given model.</p>
1044
1045 <p>Your letter continues: "4. The bill imposes the use of open source software without considering the dangers that this can bring from the point of view of security, guarantee, and possible violation of the intellectual property rights of third parties."</p>
1046
1047 <p>Alluding in an abstract way to "the dangers this can bring", without specifically mentioning a single one of these supposed dangers, shows at the least some lack of knowledge of the topic. So, allow me to enlighten you on these points.</p>
1048
1049 <p>On security:</p>
1050
1051 <p>National security has already been mentioned in general terms in the initial discussion of the basic principles of the bill. In more specific terms, relative to the security of the software itself, it is well known that all software (whether proprietary or free) contains errors or "bugs" (in programmers' slang). But it is also well known that the bugs in free software are fewer, and are fixed much more quickly, than in proprietary software. It is not in vain that numerous public bodies responsible for the IT security of state systems in developed countries require the use of free software for the same conditions of security and efficiency.</p>
1052
1053 <p>What is impossible to prove is that proprietary software is more secure than free, without the public and open inspection of the scientific community and users in general. This demonstration is impossible because the model of proprietary software itself prevents this analysis, so that any guarantee of security is based only on promises of good intentions (biased, by any reckoning) made by the producer itself, or its contractors.</p>
1054
1055 <p>It should be remembered that in many cases, the licensing conditions include Non-Disclosure clauses which prevent the user from publicly revealing security flaws found in the licensed proprietary product.</p>
1056
1057 <p>In respect of the guarantee:</p>
1058
1059 <p>As you know perfectly well, or could find out by reading the "End User License Agreement" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.</p>
1060
1061 <p>On Intellectual Property:</p>
1062
1063 <p>Questions of intellectual property fall outside the scope of this bill, since they are covered by specific other laws. The model of free software in no way implies ignorance of these laws, and in fact the great majority of free software is covered by copyright. In reality, the inclusion of this question in your observations shows your confusion in respect of the legal framework in which free software is developed. The inclusion of the intellectual property of others in works claimed as one's own is not a practice that has been noted in the free software community; whereas, unfortunately, it has been in the area of proprietary software. As an example, the condemnation by the Commercial Court of Nanterre, France, on 27th September 2001 of Microsoft Corp. to a penalty of 3 million francs in damages and interest, for violation of intellectual property (piracy, to use the unfortunate term that your firm commonly uses in its publicity).</p>
1064
1065 <p>You go on to say that: "The bill uses the concept of open source software incorrectly, since it does not necessarily imply that the software is free or of zero cost, and so arrives at mistaken conclusions regarding State savings, with no cost-benefit analysis to validate its position."</p>
1066
1067 <p>This observation is wrong; in principle, freedom and lack of cost are orthogonal concepts: there is software which is proprietary and charged for (for example, MS Office), software which is proprietary and free of charge (MS Internet Explorer), software which is free and charged for (Red Hat, SuSE etc GNU/Linux distributions), software which is free and not charged for (Apache, Open Office, Mozilla), and even software which can be licensed in a range of combinations (MySQL).</p>
1068
1069 <p>Certainly free software is not necessarily free of charge. And the text of the bill does not state that it has to be so, as you will have noted after reading it. The definitions included in the Bill state clearly *what* should be considered free software, at no point referring to freedom from charges. Although the possibility of savings in payments for proprietary software licenses are mentioned, the foundations of the bill clearly refer to the fundamental guarantees to be preserved and to the stimulus to local technological development. Given that a democratic State must support these principles, it has no other choice than to use software with publicly available source code, and to exchange information only in standard formats.</p>
1070
1071 <p>If the State does not use software with these characteristics, it will be weakening basic republican principles. Luckily, free software also implies lower total costs; however, even given the hypothesis (easily disproved) that it was more expensive than proprietary software, the simple existence of an effective free software tool for a particular IT function would oblige the State to use it; not by command of this Bill, but because of the basic principles we enumerated at the start, and which arise from the very essence of the lawful democratic State.</p>
1072
1073 <p>You continue: "6. It is wrong to think that Open Source Software is free of charge. Research by the Gartner Group (an important investigator of the technological market recognized at world level) has shown that the cost of purchase of software (operating system and applications) is only 8% of the total cost which firms and institutions take on for a rational and truly beneficial use of the technology. The other 92% consists of: installation costs, enabling, support, maintenance, administration, and down-time."</p>
1074
1075 <p>This argument repeats that already given in paragraph 5 and partly contradicts paragraph 3. For the sake of brevity we refer to the comments on those paragraphs. However, allow me to point out that your conclusion is logically false: even if according to Gartner Group the cost of software is on average only 8% of the total cost of use, this does not in any way deny the existence of software which is free of charge, that is, with a licensing cost of zero.</p>
1076
1077 <p>In addition, in this paragraph you correctly point out that the service components and losses due to down-time make up the largest part of the total cost of software use, which, as you will note, contradicts your statement regarding the small value of services suggested in paragraph 3. Now the use of free software contributes significantly to reduce the remaining life-cycle costs. This reduction in the costs of installation, support etc. can be noted in several areas: in the first place, the competitive service model of free software, support and maintenance for which can be freely contracted out to a range of suppliers competing on the grounds of quality and low cost. This is true for installation, enabling, and support, and in large part for maintenance. In the second place, due to the reproductive characteristics of the model, maintenance carried out for an application is easily replicable, without incurring large costs (that is, without paying more than once for the same thing) since modifications, if one wishes, can be incorporated in the common fund of knowledge. Thirdly, the huge costs caused by non-functioning software ("blue screens of death", malicious code such as virus, worms, and trojans, exceptions, general protection faults and other well-known problems) are reduced considerably by using more stable software; and it is well known that one of the most notable virtues of free software is its stability.</p>
1078
1079 <p>You further state that: "7. One of the arguments behind the bill is the supposed freedom from costs of open-source software, compared with the costs of commercial software, without taking into account the fact that there exist types of volume licensing which can be highly advantageous for the State, as has happened in other countries."</p>
1080
1081 <p>I have already pointed out that what is in question is not the cost of the software but the principles of freedom of information, accessibility, and security. These arguments have been covered extensively in the preceding paragraphs to which I would refer you.</p>
1082
1083 <p>On the other hand, there certainly exist types of volume licensing (although unfortunately proprietary software does not satisfy the basic principles). But as you correctly pointed out in the immediately preceding paragraph of your letter, they only manage to reduce the impact of a component which makes up no more than 8% of the total.</p>
1084
1085 <p>You continue: "8. In addition, the alternative adopted by the bill (I) is clearly more expensive, due to the high costs of software migration, and (II) puts at risk compatibility and interoperability of the IT platforms within the State, and between the State and the private sector, given the hundreds of versions of open source software on the market."</p>
1086
1087 <p>Let us analyze your statement in two parts. Your first argument, that migration implies high costs, is in reality an argument in favor of the Bill. Because the more time goes by, the more difficult migration to another technology will become; and at the same time, the security risks associated with proprietary software will continue to increase. In this way, the use of proprietary systems and formats will make the State ever more dependent on specific suppliers. Once a policy of using free software has been established (which certainly, does imply some cost) then on the contrary migration from one system to another becomes very simple, since all data is stored in open formats. On the other hand, migration to an open software context implies no more costs than migration between two different proprietary software contexts, which invalidates your argument completely.</p>
1088
1089 <p>The second argument refers to "problems in interoperability of the IT platforms within the State, and between the State and the private sector" This statement implies a certain lack of knowledge of the way in which free software is built, which does not maximize the dependence of the user on a particular platform, as normally happens in the realm of proprietary software. Even when there are multiple free software distributions, and numerous programs which can be used for the same function, interoperability is guaranteed as much by the use of standard formats, as required by the bill, as by the possibility of creating interoperable software given the availability of the source code.</p>
1090
1091 <p>You then say that: "9. The majority of open source code does not offer adequate levels of service nor the guarantee from recognized manufacturers of high productivity on the part of the users, which has led various public organizations to retract their decision to go with an open source software solution and to use commercial software in its place."</p>
1092
1093 <p>This observation is without foundation. In respect of the guarantee, your argument was rebutted in the response to paragraph 4. In respect of support services, it is possible to use free software without them (just as also happens with proprietary software), but anyone who does need them can obtain support separately, whether from local firms or from international corporations, again just as in the case of proprietary software.</p>
1094
1095 <p>On the other hand, it would contribute greatly to our analysis if you could inform us about free software projects *established* in public bodies which have already been abandoned in favor of proprietary software. We know of a good number of cases where the opposite has taken place, but not know of any where what you describe has taken place.</p>
1096
1097 <p>You continue by observing that: "10. The bill discourages the creativity of the Peruvian software industry, which invoices 40 million US$/year, exports 4 million US$ (10th in ranking among non-traditional exports, more than handicrafts) and is a source of highly qualified employment. With a law that encourages the use of open source, software programmers lose their intellectual property rights and their main source of payment."</p>
1098
1099 <p>It is clear enough that nobody is forced to commercialize their code as free software. The only thing to take into account is that if it is not free software, it cannot be sold to the public sector. This is not in any case the main market for the national software industry. We covered some questions referring to the influence of the Bill on the generation of employment which would be both highly technically qualified and in better conditions for competition above, so it seems unnecessary to insist on this point.</p>
1100
1101 <p>What follows in your statement is incorrect. On the one hand, no author of free software loses his intellectual property rights, unless he expressly wishes to place his work in the public domain. The free software movement has always been very respectful of intellectual property, and has generated widespread public recognition of its authors. Names like those of Richard Stallman, Linus Torvalds, Guido van Rossum, Larry Wall, Miguel de Icaza, Andrew Tridgell, Theo de Raadt, Andrea Arcangeli, Bruce Perens, Darren Reed, Alan Cox, Eric Raymond, and many others, are recognized world-wide for their contributions to the development of software that is used today by millions of people throughout the world. On the other hand, to say that the rewards for authors rights make up the main source of payment of Peruvian programmers is in any case a guess, in particular since there is no proof to this effect, nor a demonstration of how the use of free software by the State would influence these payments.</p>
1102
1103 <p>You go on to say that: "11. Open source software, since it can be distributed without charge, does not allow the generation of income for its developers through exports. In this way, the multiplier effect of the sale of software to other countries is weakened, and so in turn is the growth of the industry, while Government rules ought on the contrary to stimulate local industry."</p>
1104
1105 <p>This statement shows once again complete ignorance of the mechanisms of and market for free software. It tries to claim that the market of sale of non- exclusive rights for use (sale of licenses) is the only possible one for the software industry, when you yourself pointed out several paragraphs above that it is not even the most important one. The incentives that the bill offers for the growth of a supply of better qualified professionals, together with the increase in experience that working on a large scale with free software within the State will bring for Peruvian technicians, will place them in a highly competitive position to offer their services abroad.</p>
1106
1107 <p>You then state that: "12. In the Forum, the use of open source software in education was discussed, without mentioning the complete collapse of this initiative in a country like Mexico, where precisely the State employees who founded the project now state that open source software did not make it possible to offer a learning experience to pupils in the schools, did not take into account the capability at a national level to give adequate support to the platform, and that the software did not and does not allow for the levels of platform integration that now exist in schools."</p>
1108
1109 <p>In fact Mexico has gone into reverse with the Red Escolar (Schools Network) project. This is due precisely to the fact that the driving forces behind the Mexican project used license costs as their main argument, instead of the other reasons specified in our project, which are far more essential. Because of this conceptual mistake, and as a result of the lack of effective support from the SEP (Secretary of State for Public Education), the assumption was made that to implant free software in schools it would be enough to drop their software budget and send them a CD ROM with Gnu/Linux instead. Of course this failed, and it couldn't have been otherwise, just as school laboratories fail when they use proprietary software and have no budget for implementation and maintenance. That's exactly why our bill is not limited to making the use of free software mandatory, but recognizes the need to create a viable migration plan, in which the State undertakes the technical transition in an orderly way in order to then enjoy the advantages of free software.</p>
1110
1111 <p>You end with a rhetorical question: "13. If open source software satisfies all the requirements of State bodies, why do you need a law to adopt it? Shouldn't it be the market which decides freely which products give most benefits or value?"</p>
1112
1113 <p>We agree that in the private sector of the economy, it must be the market that decides which products to use, and no state interference is permissible there. However, in the case of the public sector, the reasoning is not the same: as we have already established, the state archives, handles, and transmits information which does not belong to it, but which is entrusted to it by citizens, who have no alternative under the rule of law. As a counterpart to this legal requirement, the State must take extreme measures to safeguard the integrity, confidentiality, and accessibility of this information. The use of proprietary software raises serious doubts as to whether these requirements can be fulfilled, lacks conclusive evidence in this respect, and so is not suitable for use in the public sector.</p>
1114
1115 <p>The need for a law is based, firstly, on the realization of the fundamental principles listed above in the specific area of software; secondly, on the fact that the State is not an ideal homogeneous entity, but made up of multiple bodies with varying degrees of autonomy in decision making. Given that it is inappropriate to use proprietary software, the fact of establishing these rules in law will prevent the personal discretion of any state employee from putting at risk the information which belongs to citizens. And above all, because it constitutes an up-to-date reaffirmation in relation to the means of management and communication of information used today, it is based on the republican principle of openness to the public.</p>
1116
1117 <p>In conformance with this universally accepted principle, the citizen has the right to know all information held by the State and not covered by well- founded declarations of secrecy based on law. Now, software deals with information and is itself information. Information in a special form, capable of being interpreted by a machine in order to execute actions, but crucial information all the same because the citizen has a legitimate right to know, for example, how his vote is computed or his taxes calculated. And for that he must have free access to the source code and be able to prove to his satisfaction the programs used for electoral computations or calculation of his taxes.</p>
1118
1119 <p>I wish you the greatest respect, and would like to repeat that my office will always be open for you to expound your point of view to whatever level of detail you consider suitable.</p>
1120
1121 <p>Cordially,<br>
1122 DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
1123 Congressman of the Republic of Perú.</p>
1124 </blockquote>
1125
1126       </div>
1127       <div class="tags">
1128
1129
1130         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1131
1132
1133       </div>
1134     </div>
1135     <div class="padding"></div>
1136
1137     <div class="entry">
1138       <div class="title">
1139         <a href="https://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">Best å ikke fortelle noen at streaming er nedlasting...</a>
1140       </div>
1141       <div class="date">
1142         30th October 2010
1143       </div>
1144       <div class="body">
1145         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
1146 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
1147 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
1148 filmene NRK la ut ikke var tilgjengelig i et
1149 <a href="http://www.digistan.org/open-standard:definition">fritt og
1150 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
1151
1152 <p><blockquote>
1153 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
1154 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
1155 som dette, vet at det stort sett er mulig å lure ut ting med den
1156 nødvendige forkunnskapen."</p>
1157
1158 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
1159 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
1160 er å forlede leseren.</p>
1161
1162 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
1163 vil tillate streaming men ikke nedlasting meningsløs.</p>
1164
1165 <p>Anbefaler forresten å lese
1166 <a href="http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm">http://blogs.computerworlduk.com/simon-says/2010/10/drm-is-toxic-to-culture/index.htm</a>
1167 om hva som ville være konsekvensen hvis digitale avspillingssperrer
1168 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
1169 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
1170 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
1171 opp under.</p>
1172 </blockquote></p>
1173
1174 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
1175 NRKBeta:</p>
1176
1177 <p><blockquote>
1178 <p>From: Anders Hofseth &lt;XXX@gmail.com>
1179 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
1180 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
1181 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
1182 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
1183
1184 <p>Hei Petter.
1185 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
1186 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
1187 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1188 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
1189
1190 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
1191 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1192 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
1193
1194 <p>Med hilsen,
1195 <br>-anders</p>
1196
1197 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
1198 </blockquote></p>
1199
1200 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
1201 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
1202 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
1203 Har fjernet epostadresser og telefonnummer til de involverte, for å
1204 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
1205
1206 <p><blockquote>
1207 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
1208 <br>To: Anders Hofseth &lt;XXX@gmail.com>
1209 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
1210 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
1211 <br>        Henrik Lied &lt;XXX@gmail.com>
1212 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
1213 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
1214
1215 <p>[Anders Hofseth]
1216 <br>> Hei Petter.</p>
1217
1218 <p>Hei.</p>
1219
1220 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
1221 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
1222 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1223 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
1224
1225 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
1226 vil nok fortsette en stund til.  :)</p>
1227
1228 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
1229 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
1230 fortsette å legge ut arkivmateriale.</p>
1231
1232 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
1233 faktum, som er at streaming er det samme som nedlasting, og at innhold
1234 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
1235 det.</p>
1236
1237 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
1238 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
1239 Det er ikke et argument som holder vann. :)</p>
1240
1241 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
1242 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1243 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
1244
1245 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
1246 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
1247 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
1248 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
1249 skal sendes skal være uten bruksbegresninger og kan publiseres i
1250 formater som heller ikke har bruksbegresninger (bruksbegresningene til
1251 H.264 burde få varselbjellene i NRK til å ringe).</p>
1252
1253 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
1254 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
1255 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
1256
1257 <p>Anbefaler &lt;URL:<a href="http://webmink.com/2010/09/03/h-264-and-foss/">http://webmink.com/2010/09/03/h-264-and-foss/</a>> og en
1258 titt på
1259 &lt;URL: <a href="https://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">https://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</a> >.
1260 for å se hva slags bruksbegresninger H.264 innebærer.</p>
1261
1262 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1263 kan brukes før rettighetshaverene også innser at de er med på å skade
1264 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1265 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1266 langt på overtid.</p>
1267
1268 <p>> Ring meg om noe er uklart: XXX</p>
1269
1270 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1271 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1272 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1273 for videre diskusjon hadde dere i mine øyne kommet fra det med
1274 ryggraden på plass.</p>
1275
1276 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
1277
1278 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1279 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
1280 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
1281 NRK1. :)</p>
1282
1283 <p>Vennlig hilsen,
1284 <br>--
1285 <br>Petter Reinholdtsen</p>
1286
1287       </div>
1288       <div class="tags">
1289
1290
1291         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1292
1293
1294       </div>
1295     </div>
1296     <div class="padding"></div>
1297
1298     <div class="entry">
1299       <div class="title">
1300         <a href="https://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">Terms of use for video produced by a Canon IXUS 130 digital camera</a>
1301       </div>
1302       <div class="date">
1303          9th September 2010
1304       </div>
1305       <div class="body">
1306         <p>A few days ago I had the mixed pleasure of bying a new digital
1307 camera, a Canon IXUS 130.  It was instructive and very disturbing to
1308 be able to verify that also this camera producer have the nerve to
1309 specify how I can or can not use the videos produced with the camera.
1310 Even thought I was aware of the issue, the options with new cameras
1311 are limited and I ended up bying the camera anyway.  What is the
1312 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
1313 MPEG-LA that is the problem, and our right to record our experiences
1314 without asking for permissions that is at risk.
1315
1316 <p>On page 27 of the Danish instruction manual, this section is
1317 written:</p>
1318
1319 <blockquote>
1320 <p>This product is licensed under AT&T patents for the MPEG-4 standard
1321 and may be used for encoding MPEG-4 compliant video and/or decoding
1322 MPEG-4 compliant video that was encoded only (1) for a personal and
1323 non-commercial purpose or (2) by a video provider licensed under the
1324 AT&T patents to provide MPEG-4 compliant video.</p>
1325
1326 <p>No license is granted or implied for any other use for MPEG-4
1327 standard.</p>
1328 </blockquote>
1329
1330 <p>In short, the camera producer have chosen to use technology
1331 (MPEG-4/H.264) that is only provided if I used it for personal and
1332 non-commercial purposes, or ask for permission from the organisations
1333 holding the knowledge monopoly (patent) for technology used.</p>
1334
1335 <p>This issue has been brewing for a while, and I recommend you to
1336 read
1337 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
1338 Our Civilization's Video Art and Culture is Threatened by the
1339 MPEG-LA</a>" by Eugenia Loli-Queru and
1340 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
1341 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
1342 the issue.  The solution is to support the
1343 <a href="http://www.digistan.org/open-standard:definition">free and
1344 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
1345 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
1346
1347       </div>
1348       <div class="tags">
1349
1350
1351         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="https://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="https://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="https://people.skolelinux.org/pere/blog/tags/web">web</a>.
1352
1353
1354       </div>
1355     </div>
1356     <div class="padding"></div>
1357
1358     <div class="entry">
1359       <div class="title">
1360         <a href="https://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">Fri og åpen standard, slik Digistan ser det</a>
1361       </div>
1362       <div class="date">
1363         31st January 2009
1364       </div>
1365       <div class="body">
1366         <p>Det er mange ulike definisjoner om hva en åpen standard er for noe,
1367 og NUUG hadde <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">en
1368 pressemelding om dette sommeren 2005</a>.  Der ble definisjonen til
1369 <a href="http://www.aaben-standard.dk/">DKUUG</a>,
1370 <a href="http://europa.eu.int/idabc/servlets/Doc?id=19529">EU-kommissionens
1371 European Interoperability Framework ( side 9)</a> og
1372 <a href="http://www.teknologiradet.no/files/7polert_copy.htm">teknologirådet</a> omtalt.</p>
1373
1374 <p>Siden den gang har regjeringens standardiseringsråd dukket opp, og de
1375 ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
1376 <a href="http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=476407">sin
1377 arbeidsmetodikk</a>.  Personlig synes jeg det er en god ide, da
1378 kravene som stilles der gjør at alle markedsaktører får like vilkår,
1379 noe som kommer kundene til gode ved hjelp av økt konkurranse.</p>
1380
1381 <p>I sommer kom det en ny definisjon på banen.
1382 <a href="https://web.archive.org/web/20160618103850/http://www.digistan.org/">Digistan</a> lanserte
1383 <a href="https://web.archive.org/web/20160618103850/http://www.digistan.org/open-standard:definition">en
1384 definisjon på en fri og åpen standard</a>.  Jeg liker måten de bryter
1385 ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
1386 ved å legge på et ord og poengtere at en standard som er både åpen og
1387 fri har noen spesielle krav.  Her er den definisjonen etter rask
1388 oversettelse fra engelsk til norsk av meg:</p>
1389
1390 <blockquote>
1391 <p><strong>Definisjonen av en fri og åpen standard</strong></p>
1392
1393 <p>Den digitale standardorganisasjonen definierer fri og åpen standard
1394 som følger:</p>
1395 <ul>
1396 <li>En fri og åpen standard er immun for leverandørinnlåsing i alle
1397 stadier av dens livssyklus.  Immuniteten fra leverandørinnlåsing gjør
1398 det mulig å fritt bruke, forbedre, stole på og utvide en standard over
1399 tid.</li>
1400 <li>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
1401 organisasjon, og dens pågående utvikling gjøres med en åpen
1402 beslutningsprosedyre som er tilgjengelig for alle som er interessert i
1403 å delta.</li>
1404 <li>Standarden er publisert og spesifikasjonsdokumentet er fritt
1405 tilgjengelig.  Det må være tillatt for alle å kopiere, distribuere og
1406 bruke den uten begresninger.</li>
1407 <li>Patentene som muligens gjelder (deler av) standarden er gjort
1408 ugjenkallelig tilgjengelig uten krav om betaling.</li>
1409 <li>Det er ingen begresninger i gjenbruk av standarden.</li>
1410 </ul>
1411 <p>Det økonomiske resultatet av en fri og åpen standard, som kan
1412 måles, er at det muliggjør perfekt konkurranse mellom leverandører av
1413 produkter basert på standarden.</p>
1414 </blockquote>
1415
1416 <p>(Tar gjerne imot forbedringer av oversettelsen.)</p>
1417
1418       </div>
1419       <div class="tags">
1420
1421
1422         Tags: <a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="https://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1423
1424
1425       </div>
1426     </div>
1427     <div class="padding"></div>
1428
1429     <p style="text-align: right;"><a href="digistan.rss"><img src="https://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
1430     <div id="sidebar">
1431
1432
1433
1434 <h2>Archive</h2>
1435 <ul>
1436
1437 <li>2024
1438 <ul>
1439
1440 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/01/">January (1)</a></li>
1441
1442 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/02/">February (1)</a></li>
1443
1444 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/03/">March (2)</a></li>
1445
1446 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/04/">April (3)</a></li>
1447
1448 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/05/">May (1)</a></li>
1449
1450 <li><a href="https://people.skolelinux.org/pere/blog/archive/2024/06/">June (1)</a></li>
1451
1452 </ul></li>
1453
1454 <li>2023
1455 <ul>
1456
1457 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/01/">January (3)</a></li>
1458
1459 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/02/">February (1)</a></li>
1460
1461 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/04/">April (2)</a></li>
1462
1463 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/05/">May (3)</a></li>
1464
1465 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/06/">June (1)</a></li>
1466
1467 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/08/">August (1)</a></li>
1468
1469 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/09/">September (1)</a></li>
1470
1471 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/10/">October (1)</a></li>
1472
1473 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/11/">November (4)</a></li>
1474
1475 <li><a href="https://people.skolelinux.org/pere/blog/archive/2023/12/">December (1)</a></li>
1476
1477 </ul></li>
1478
1479 <li>2022
1480 <ul>
1481
1482 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/02/">February (1)</a></li>
1483
1484 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/03/">March (3)</a></li>
1485
1486 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/04/">April (2)</a></li>
1487
1488 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/06/">June (2)</a></li>
1489
1490 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/07/">July (1)</a></li>
1491
1492 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/09/">September (1)</a></li>
1493
1494 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/10/">October (1)</a></li>
1495
1496 <li><a href="https://people.skolelinux.org/pere/blog/archive/2022/12/">December (1)</a></li>
1497
1498 </ul></li>
1499
1500 <li>2021
1501 <ul>
1502
1503 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/01/">January (2)</a></li>
1504
1505 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/02/">February (1)</a></li>
1506
1507 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/05/">May (1)</a></li>
1508
1509 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/06/">June (1)</a></li>
1510
1511 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/07/">July (3)</a></li>
1512
1513 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/08/">August (1)</a></li>
1514
1515 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/09/">September (1)</a></li>
1516
1517 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/10/">October (1)</a></li>
1518
1519 <li><a href="https://people.skolelinux.org/pere/blog/archive/2021/12/">December (1)</a></li>
1520
1521 </ul></li>
1522
1523 <li>2020
1524 <ul>
1525
1526 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/02/">February (2)</a></li>
1527
1528 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/03/">March (2)</a></li>
1529
1530 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/04/">April (2)</a></li>
1531
1532 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/05/">May (3)</a></li>
1533
1534 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/06/">June (2)</a></li>
1535
1536 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/07/">July (1)</a></li>
1537
1538 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/09/">September (1)</a></li>
1539
1540 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/10/">October (1)</a></li>
1541
1542 <li><a href="https://people.skolelinux.org/pere/blog/archive/2020/11/">November (1)</a></li>
1543
1544 </ul></li>
1545
1546 <li>2019
1547 <ul>
1548
1549 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
1550
1551 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
1552
1553 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/03/">March (3)</a></li>
1554
1555 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/05/">May (2)</a></li>
1556
1557 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/06/">June (5)</a></li>
1558
1559 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/07/">July (2)</a></li>
1560
1561 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/08/">August (1)</a></li>
1562
1563 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/09/">September (1)</a></li>
1564
1565 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/11/">November (1)</a></li>
1566
1567 <li><a href="https://people.skolelinux.org/pere/blog/archive/2019/12/">December (4)</a></li>
1568
1569 </ul></li>
1570
1571 <li>2018
1572 <ul>
1573
1574 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
1575
1576 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
1577
1578 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
1579
1580 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
1581
1582 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
1583
1584 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
1585
1586 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
1587
1588 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
1589
1590 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
1591
1592 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
1593
1594 <li><a href="https://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
1595
1596 </ul></li>
1597
1598 <li>2017
1599 <ul>
1600
1601 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
1602
1603 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
1604
1605 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
1606
1607 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
1608
1609 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
1610
1611 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
1612
1613 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
1614
1615 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
1616
1617 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
1618
1619 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
1620
1621 <li><a href="https://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
1622
1623 </ul></li>
1624
1625 <li>2016
1626 <ul>
1627
1628 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1629
1630 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1631
1632 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1633
1634 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1635
1636 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1637
1638 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1639
1640 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1641
1642 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1643
1644 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1645
1646 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1647
1648 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
1649
1650 <li><a href="https://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
1651
1652 </ul></li>
1653
1654 <li>2015
1655 <ul>
1656
1657 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1658
1659 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1660
1661 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1662
1663 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1664
1665 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1666
1667 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1668
1669 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1670
1671 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1672
1673 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1674
1675 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1676
1677 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1678
1679 <li><a href="https://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1680
1681 </ul></li>
1682
1683 <li>2014
1684 <ul>
1685
1686 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1687
1688 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1689
1690 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1691
1692 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1693
1694 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1695
1696 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1697
1698 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1699
1700 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1701
1702 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1703
1704 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1705
1706 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1707
1708 <li><a href="https://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1709
1710 </ul></li>
1711
1712 <li>2013
1713 <ul>
1714
1715 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1716
1717 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1718
1719 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1720
1721 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1722
1723 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1724
1725 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1726
1727 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1728
1729 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1730
1731 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1732
1733 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1734
1735 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1736
1737 <li><a href="https://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1738
1739 </ul></li>
1740
1741 <li>2012
1742 <ul>
1743
1744 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1745
1746 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1747
1748 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1749
1750 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1751
1752 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1753
1754 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1755
1756 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1757
1758 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1759
1760 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1761
1762 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1763
1764 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1765
1766 <li><a href="https://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1767
1768 </ul></li>
1769
1770 <li>2011
1771 <ul>
1772
1773 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1774
1775 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1776
1777 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1778
1779 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1780
1781 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1782
1783 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1784
1785 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1786
1787 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1788
1789 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1790
1791 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1792
1793 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1794
1795 <li><a href="https://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1796
1797 </ul></li>
1798
1799 <li>2010
1800 <ul>
1801
1802 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1803
1804 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1805
1806 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1807
1808 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1809
1810 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1811
1812 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1813
1814 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1815
1816 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1817
1818 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1819
1820 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1821
1822 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1823
1824 <li><a href="https://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1825
1826 </ul></li>
1827
1828 <li>2009
1829 <ul>
1830
1831 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1832
1833 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1834
1835 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1836
1837 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1838
1839 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1840
1841 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1842
1843 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1844
1845 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1846
1847 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1848
1849 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1850
1851 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1852
1853 <li><a href="https://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1854
1855 </ul></li>
1856
1857 <li>2008
1858 <ul>
1859
1860 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1861
1862 <li><a href="https://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1863
1864 </ul></li>
1865
1866 </ul>
1867
1868
1869
1870 <h2>Tags</h2>
1871 <ul>
1872
1873  <li><a href="https://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (19)</a></li>
1874
1875  <li><a href="https://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1876
1877  <li><a href="https://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1878
1879  <li><a href="https://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1880
1881  <li><a href="https://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (9)</a></li>
1882
1883  <li><a href="https://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (13)</a></li>
1884
1885  <li><a href="https://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
1886
1887  <li><a href="https://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1888
1889  <li><a href="https://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (3)</a></li>
1890
1891  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian">debian (200)</a></li>
1892
1893  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (159)</a></li>
1894
1895  <li><a href="https://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (9)</a></li>
1896
1897  <li><a href="https://people.skolelinux.org/pere/blog/tags/digistan">digistan (11)</a></li>
1898
1899  <li><a href="https://people.skolelinux.org/pere/blog/tags/dld">dld (18)</a></li>
1900
1901  <li><a href="https://people.skolelinux.org/pere/blog/tags/docbook">docbook (33)</a></li>
1902
1903  <li><a href="https://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1904
1905  <li><a href="https://people.skolelinux.org/pere/blog/tags/english">english (462)</a></li>
1906
1907  <li><a href="https://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1908
1909  <li><a href="https://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
1910
1911  <li><a href="https://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (34)</a></li>
1912
1913  <li><a href="https://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1914
1915  <li><a href="https://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
1916
1917  <li><a href="https://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1918
1919  <li><a href="https://people.skolelinux.org/pere/blog/tags/intervju">intervju (43)</a></li>
1920
1921  <li><a href="https://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (18)</a></li>
1922
1923  <li><a href="https://people.skolelinux.org/pere/blog/tags/kart">kart (23)</a></li>
1924
1925  <li><a href="https://people.skolelinux.org/pere/blog/tags/kodi">kodi (6)</a></li>
1926
1927  <li><a href="https://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1928
1929  <li><a href="https://people.skolelinux.org/pere/blog/tags/lego">lego (5)</a></li>
1930
1931  <li><a href="https://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1932
1933  <li><a href="https://people.skolelinux.org/pere/blog/tags/linuxcnc">linuxcnc (6)</a></li>
1934
1935  <li><a href="https://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1936
1937  <li><a href="https://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1938
1939  <li><a href="https://people.skolelinux.org/pere/blog/tags/madewithcc">madewithcc (3)</a></li>
1940
1941  <li><a href="https://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1942
1943  <li><a href="https://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (46)</a></li>
1944
1945  <li><a href="https://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (15)</a></li>
1946
1947  <li><a href="https://people.skolelinux.org/pere/blog/tags/noark5">noark5 (25)</a></li>
1948
1949  <li><a href="https://people.skolelinux.org/pere/blog/tags/norsk">norsk (325)</a></li>
1950
1951  <li><a href="https://people.skolelinux.org/pere/blog/tags/nuug">nuug (199)</a></li>
1952
1953  <li><a href="https://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (41)</a></li>
1954
1955  <li><a href="https://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1956
1957  <li><a href="https://people.skolelinux.org/pere/blog/tags/opensnitch">opensnitch (4)</a></li>
1958
1959  <li><a href="https://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (76)</a></li>
1960
1961  <li><a href="https://people.skolelinux.org/pere/blog/tags/personvern">personvern (114)</a></li>
1962
1963  <li><a href="https://people.skolelinux.org/pere/blog/tags/raid">raid (4)</a></li>
1964
1965  <li><a href="https://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1966
1967  <li><a href="https://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1968
1969  <li><a href="https://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1970
1971  <li><a href="https://people.skolelinux.org/pere/blog/tags/robot">robot (17)</a></li>
1972
1973  <li><a href="https://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1974
1975  <li><a href="https://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
1976
1977  <li><a href="https://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1978
1979  <li><a href="https://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (60)</a></li>
1980
1981  <li><a href="https://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1982
1983  <li><a href="https://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1984
1985  <li><a href="https://people.skolelinux.org/pere/blog/tags/standard">standard (76)</a></li>
1986
1987  <li><a href="https://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (7)</a></li>
1988
1989  <li><a href="https://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (14)</a></li>
1990
1991  <li><a href="https://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (65)</a></li>
1992
1993  <li><a href="https://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (5)</a></li>
1994
1995  <li><a href="https://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1996
1997  <li><a href="https://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
1998
1999  <li><a href="https://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (22)</a></li>
2000
2001  <li><a href="https://people.skolelinux.org/pere/blog/tags/video">video (80)</a></li>
2002
2003  <li><a href="https://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
2004
2005  <li><a href="https://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
2006
2007 </ul>
2008
2009
2010     </div>
2011     <p style="text-align: right">
2012  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
2013 </p>
2014
2015   </body>
2016 </html>