blog/tags/standard/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 standard</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="standard.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21     <h3>Entries tagged "standard".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/ODF_bruk_i_staten__ikke_helt_p__plass.html">ODF-bruk i staten, ikke helt på plass</a>
  26       </div>
  27       <div class="date">
  28         22nd January 2009
  29       </div>
  30       <div class="body">
  31         <p>I går publiserte
  32 <a href="http://universitas.no/nyhet/52776/">Universitas</a>,
  33 <a href="http://www.dagensit.no/trender/article1588462.ece">Dagens-IT</a>
  34 og <a href="http://www.idg.no/computerworld/article118622.ece">Computerworld
  35 Norge</a> en sak om at de ansatte ved Universitetet i Oslo ikke følger
  36 regjeringens pålegg om å publisere i HTML, PDF eller ODF.  Det er bra
  37 at det kommer litt fokus på dette, og jeg håper noen journalister tar
  38 en titt på de andre statlige instansene også.</p>
  39
  40 <p>Skulle ønske det var en enkel måte å sjekke om ODF-dokumenter er i
  41 henholdt til ODF-spesifikasjonen, og en måte å teste om programmer som
  42 hevder å støtte ODF forstår alle delene av ODF-spesifikasjonen.
  43 Kjenner kun til ufullstendige løsninger for slikt.</p>
  44
  45       </div>
  46       <div class="tags">
  47
  48
  49         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
  50
  51
  52       </div>
  53     </div>
  54     <div class="padding"></div>
  55
  56     <div class="entry">
  57       <div class="title">
  58         <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">Fri og åpen standard, slik Digistan ser det</a>
  59       </div>
  60       <div class="date">
  61         31st January 2009
  62       </div>
  63       <div class="body">
  64         <p>Det er mange ulike definisjoner om hva en åpen standard er for noe,
  65 og NUUG hadde <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">en
  66 pressemelding om dette sommeren 2005</a>.  Der ble definisjonen til
  67 <a href="http://www.aaben-standard.dk/">DKUUG</a>,
  68 <a href="http://europa.eu.int/idabc/servlets/Doc?id=19529">EU-kommissionens
  69 European Interoperability Framework ( side 9)</a> og
  70 <a href="http://www.teknologiradet.no/files/7polert_copy.htm">teknologirådet</a> omtalt.</p>
  71
  72 <p>Siden den gang har regjeringens standardiseringsråd dukket opp, og de
  73 ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
  74 <a href="http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=476407">sin
  75 arbeidsmetodikk</a>.  Personlig synes jeg det er en god ide, da
  76 kravene som stilles der gjør at alle markedsaktører får like vilkår,
  77 noe som kommer kundene til gode ved hjelp av økt konkurranse.</p>
  78
  79 <p>I sommer kom det en ny definisjon på banen.
  80 <a href="http://www.digistan.org/">Digistan</a> lanserte
  81 <a href="http://www.digistan.org/open-standard:definition">en
  82 definisjon på en fri og åpen standard</a>.  Jeg liker måten de bryter
  83 ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
  84 ved å legge på et ord og poengtere at en standard som er både åpen og
  85 fri har noen spesielle krav.  Her er den definisjonen etter rask
  86 oversettelse fra engelsk til norsk av meg:</p>
  87
  88 <blockquote>
  89 <p><strong>Definisjonen av en fri og åpen standard</strong></p>
  90
  91 <p>Den digitale standardorganisasjonen definierer fri og åpen standard
  92 som følger:</p>
  93 <ul>
  94 <li>En fri og åpen standard er immun for leverandørinnlåsing i alle
  95 stadier av dens livssyklus.  Immuniteten fra leverandørinnlåsing gjør
  96 det mulig å fritt bruke, forbedre, stole på og utvide en standard over
  97 tid.</li>
  98 <li>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
  99 organisasjon, og dens pågående utvikling gjøres med en åpen
 100 beslutningsprosedyre som er tilgjengelig for alle som er interessert i
 101 å delta.</li>
 102 <li>Standarden er publisert og spesifikasjonsdokumentet er fritt
 103 tilgjengelig.  Det må være tillatt for alle å kopiere, distribuere og
 104 bruke den uten begresninger.</li>
 105 <li>Patentene som muligens gjelder (deler av) standarden er gjort
 106 ugjenkallelig tilgjengelig uten krav om betaling.</li>
 107 <li>Det er ingen begresninger i gjenbruk av standarden.</li>
 108 </ul>
 109 <p>Det økonomiske resultatet av en fri og åpen standard, som kan
 110 måles, er at det muliggjør perfekt konkurranse mellom leverandører av
 111 produkter basert på standarden.</p>
 112 </blockquote>
 113
 114 <p>(Tar gjerne imot forbedringer av oversettelsen.)</p>
 115
 116       </div>
 117       <div class="tags">
 118
 119
 120         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 121
 122
 123       </div>
 124     </div>
 125     <div class="padding"></div>
 126
 127     <div class="entry">
 128       <div class="title">
 129         <a href="http://people.skolelinux.org/pere/blog/Hva_er_egentlig_en__pen_standard_.html">Hva er egentlig en åpen standard?</a>
 130       </div>
 131       <div class="date">
 132         28th March 2009
 133       </div>
 134       <div class="body">
 135         <p>Jeg møter alle slags interessante mennesker på min vei, og et møte
 136 jeg lærte mye av var å treffe på en svært kompetent IT-fyr som
 137 benektet ting jeg anser som åpenbart og selvfølgelig når det gjelder
 138 standarder.  Det var interessant, da det fikk meg til å tenke litt
 139 nøyere på hvilke mekanismer som ligger til grunn for at noe oppfattes
 140 som en standard.  Det hele startet med arbeid rundt integrering av NSS
 141 LDAP mot Active Directory, og problemer som oppstår pga. at Active
 142 Directory ikke følger LDAP-spesifikasjonen som dokumentert i RFCer fra
 143 IETF (konkret, AD returnerer kun et subset av attributter hvis det er
 144 mer enn 1500 atributter av en gitt type i et LDAP-objekt, og en må be
 145 om resten i bolker av 1500).  Jeg hevdet måten dette ble gjort på brøt
 146 med LDAP-spesifikasjonen, og henviste til hvor i LDAP-spesifikasjonen
 147 fra IETF det sto at oppførselen til AD ikke fulgte
 148 LDAP-spesifikasjonen.  AD-spesialisten overrasket meg da ved å
 149 fortelle at IETF var ikke de som definerte LDAP-spesifikasjonen, og at
 150 Active Directory ikke brøt den virkelige LDAP-spesifikasjonen som han
 151 mente lå til grunn.  Jeg ble spesielt overrasket over denne
 152 tilnærmingen til problemstillingen, da til og med Microsoft så vidt
 153 jeg kan se anerkjenner IETF som organisasjonen som definerer
 154 LDAP-spesifikasjonen.  Jeg fikk aldri spurt hvem han mente sto bak den
 155 egentlige LDAP-spesifikasjonen, da det var irrelevant for problemet vi
 156 måtte løse (få Linux og AD til å fungere sammen).  Dette møtet
 157 fortalte meg uansett at det ikke er gitt at alle aktører er enige om
 158 hva en standard er, og hva som er kilden til en gitt standard.  Det er
 159 vanskelig å enes om felles standarder før en først enes om hvem som
 160 bestemmer hva en gitt standard innebærer.</p>
 161
 162 <p>Hva er så en standard?  I sin abstrakte form er det noe å samles
 163 om.  På engelsk er en av betydningene fane brukt i krig, du vet, den
 164 type fane en samlet seg rundt på kamplassen i riddertiden.  En
 165 standard definerer altså et felleskap, noen som har noe felles.  Det
 166 er naturligvis mange måter å utgjøre et felleskap på.  En kan
 167 f.eks. enes om å gjøre alt slik som Ole gjør det, og dermed si at Oles
 168 oppførsel er standard.  Hver gang Ole endrer oppførsel endrer også
 169 standarden seg uten noe mer organisering og prosedyre.  En variant av
 170 dette er å gjøre slik som Ole har gjort det i stedet for slik Ole til
 171 enhver til gjør noe.  Dette er ofte litt enklere å forholde seg til,
 172 da en slipper å sjekke med Ole hver gang for å vite hvordan ting skal
 173 gjøres nå, men hvis det Ole gjorde noe dumt den gang en bestemte seg
 174 for å følge Ole, så er det vanskeligere å få endret oppførsel for å
 175 unngå dette dumme.</p>
 176
 177 <p>En kan også ta det et skritt videre, og istedet for å basere seg på
 178 enkeltpersoners oppførsel sette seg ned og bli enige om hvordan en
 179 skal gjøre ting, dvs. lage et felleskap basert på konsensus.  Dette
 180 tar naturligvis litt mer tid (en må diskutere ting i forkant før en
 181 kan sette igang), men det kan bidra til at den oppførselen en
 182 planlegger å benytte seg av er mer gjennomtenkt.  Det ender også
 183 typisk opp med en beskrivelse av ønsket oppførsel som flere kan forstå
 184 - da flere har vært involvert i å utarbeide beskrivelsen.</p>
 185
 186 <p>Dette er dessverre ikke alt som trengs for å forstå hva en åpen
 187 standard er for noe.  Der alle kan se på hvordan folk oppfører seg, og
 188 dermed har valget om de vil oppføre seg likt eller ikke, så er det
 189 endel juridiske faktorer som gjør det hele mer komplisert -
 190 opphavsretten og patentlovgivningen for å være helt konkret.  For å gi
 191 et eksempel. Hvis noen blir enige om å alltid plystre en bestemt
 192 melodi når de møtes, for å identifisere hverandre, så kan
 193 opphavsretten brukes til å styre hvem som får lov til å gjøre dette.
 194 De har standardisert hvordan de kjenner igjen alle som følger denne
 195 standarden, men ikke alle har nødvendigvis lov til å følge den.
 196 Musikk er opphavsrettsbeskyttet, og fremføring av musikk i
 197 offentligheten er opphavsmannens enerett (dvs. et monopol).  Det vil i
 198 sin ytterste konsekvens si at alle som skal plystre en
 199 opphavsrettsbeskyttet melodi i det offentlige rom må ha godkjenning
 200 fra opphavsmannen.  Har en ikke dette, så bryter en loven og kan
 201 straffes.  Det er dermed mulig for opphavsmannen å kontrollere hvem
 202 som får lov til å benytte seg av denne standarden.  En annen variant
 203 er hvis en standard er dokumentert, så er dokumentet som definerer
 204 standarden (spesifikasjonen) beskyttet av opphavsretten, og det er
 205 dermed mulig for rettighetsinnehaver å begrense tilgang til
 206 spesifikasjonen, og slik styre hvem som kan ta i bruk standarden på
 207 den måten.</p>
 208
 209 <p>Der opphavsretten innvilger et monopol på kunstneriske uttrykk med
 210 verkshøyde, innvilger patentlovgivningen monopol på ideer.  Hvis en
 211 slik patentert idé (fortrinnsvis uttrykt i en teknisk innretning, men
 212 det er kompliserende faktorer som gjør at det ikke er et krav) trengs
 213 for å ta i bruk en standard, så vil den som innehar patent kunne styre
 214 hvem som får ta i bruk standarden.  Det er dermed ikke gitt at alle
 215 kan delta i et standard-felleskap, og hvis de kan delta, så er det
 216 ikke sikkert at det er på like vilkår.  F.eks. kan rettighetsinnehaver
 217 sette vilkår som gjør at noen faller utenfor, det være seg av
 218 finansielle, avtalemessige eller prinsipielle årsaker.  Vanlige slike
 219 vilkår er "må betale litt for hver kunde/bruker" som utelukker de som
 220 gir bort en løsning gratis og "må gi fra seg retten til å håndheve
 221 sine egne patentrettigheter ovenfor rettighetshaver" som utelukker
 222 alle som ønsker å beholde den muligheten.</p>
 223
 224 <p>En åpen standard innebærer for meg at alle kan få innsikt i en
 225 komplett beskrivelse av oppførsel som standarden skal dekke, og at
 226 ingen kan nektes å benytte seg av standarden.  Noen mener at det
 227 holder at alle med tilstrekkelig finansiering kan få tilgang til
 228 spesifikasjonen og at en kun har finansielle krav til bruk.
 229 Pga. denne konflikten har et nytt begrep spredt seg de siste årene,
 230 nemlig fri og åpen standard, der en har gjort det klart at alle må ha
 231 komplett og lik tilgang til spesifikasjoner og retten til å gjøre bruk
 232 av en standard for at en standard skal kunne kalles fri og åpen.</p>
 233
 234       </div>
 235       <div class="tags">
 236
 237
 238         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 239
 240
 241       </div>
 242     </div>
 243     <div class="padding"></div>
 244
 245     <div class="entry">
 246       <div class="title">
 247         <a href="http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html">Standardize on protocols and formats, not vendors and applications</a>
 248       </div>
 249       <div class="date">
 250         30th March 2009
 251       </div>
 252       <div class="body">
 253         <p>Where I work at the University of Oslo, one decision stand out as a
 254 very good one to form a long lived computer infrastructure.  It is the
 255 simple one, lost by many in todays computer industry: Standardize on
 256 open network protocols and open exchange/storage formats, not applications.
 257 Applications come and go, while protocols and files tend to stay, and
 258 thus one want to make it easy to change application and vendor, while
 259 avoiding conversion costs and locking users to a specific platform or
 260 application.</p>
 261
 262 <p>This approach make it possible to replace the client applications
 263 independently of the server applications.  One can even allow users to
 264 use several different applications as long as they handle the selected
 265 protocol and format.  In the normal case, only one client application
 266 is recommended and users only get help if they choose to use this
 267 application, but those that want to deviate from the easy path are not
 268 blocked from doing so.</p>
 269
 270 <p>It also allow us to replace the server side without forcing the
 271 users to replace their applications, and thus allow us to select the
 272 best server implementation at any moment, when scale and resouce
 273 requirements change.</p>
 274
 275 <p>I strongly recommend standardizing - on open network protocols and
 276 open formats, but I would never recommend standardizing on a single
 277 application that do not use open network protocol or open formats.</p>
 278
 279       </div>
 280       <div class="tags">
 281
 282
 283         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 284
 285
 286       </div>
 287     </div>
 288     <div class="padding"></div>
 289
 290     <div class="entry">
 291       <div class="title">
 292         <a href="http://people.skolelinux.org/pere/blog/Hvorfor_jeg_ikke_bruker_eFaktura.html">Hvorfor jeg ikke bruker eFaktura</a>
 293       </div>
 294       <div class="date">
 295         23rd April 2009
 296       </div>
 297       <div class="body">
 298         <p>Telenors annonsering om å kreve 35 kroner i gebyr fra alle som
 299 ønsker papirfaktura har satt sinnene i kok, og pressedekningen så
 300 langt snakker om at eldre og folk som ikke behersker data vil få en
 301 urimelig ekstrakostnad.  Jeg tror ikke jeg passer inn i noen av de
 302 kategoriene, men velger å holde meg unna eFaktura - som er det
 303 Telenor ønsker å få folk over på - pga. systemets egenskaper.</p>
 304
 305 <p>Slik jeg har sett eFaktura til forbrukere så langt, så sender
 306 selger en elektronisk beskjed til kundens bank, som legger ut
 307 informasjon om fakturaen i nettbanken for godkjenning.  Personlig
 308 ville jeg sett det som mer naturlig at det gikk en elektronisk beskjed
 309 fra selger til kunde, dvs meg, og at jeg så kunne bruke den videre
 310 mot banken eller andre hvis jeg ønsket dette.  Mine innkjøp og
 311 regninger er jo en sak mellom meg og mine leverandører, ikke en sak
 312 mellom min bank og mine leverandører.  Kun hvis jeg ønsker å betale
 313 fakturaen skal banken involveres.  En faktura bør jo inn i
 314 regnskapet, og jeg ønsker mulighet til å legge det inn der.  Når
 315 fakturaen sendes til banken i stedet for meg, blir det vanskeligere.
 316 Hele eFaktura-modellen virker på meg som en umyndiggjøring av meg
 317 som kunde.</p>
 318
 319 <p>I tillegg har jeg ikke vært i stand til å finne
 320 eFaktura-formatets spesifikasjon, og det ser ut til at utsending av
 321 slike krever dyre avtaler med bankene for å få lov til å sende ut
 322 eFaktura til kunder.  Jeg ser vel helst at fakturering på
 323 elektroniske formater kan gjøres f.eks. via epost eller HTTP uten å
 324 måtte betale mellommenn for retten til å lever ut en faktura, og
 325 liker rett og slett ikke dagens faktureringsmodeller.</p>
 326
 327       </div>
 328       <div class="tags">
 329
 330
 331         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 332
 333
 334       </div>
 335     </div>
 336     <div class="padding"></div>
 337
 338     <div class="entry">
 339       <div class="title">
 340         <a href="http://people.skolelinux.org/pere/blog/Standarder_fungerer_best_n_r_en_samler_seg_rundt_dem.html">Standarder fungerer best når en samler seg rundt dem</a>
 341       </div>
 342       <div class="date">
 343         19th May 2009
 344       </div>
 345       <div class="body">
 346         <p>En standard er noe man samler seg rundt, ut fra ideen om at en får
 347 fordeler når mange står sammen.  Jo flere som står sammen, jo
 348 bedre.  Når en vet dette, blir det litt merkelig å lese noen av
 349 uttalelsene som er kommet inn til
 350 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2/horingsuttalelser.html?id=549423">høringen
 351 om versjon 2 av statens referansekatalog over standarder</a>.  Blant
 352 annet Abelia, NHO og Microsoft tror det er lurt med flere standarder
 353 innenfor samme område.  Det blir som å si at det er fint om Norge
 354 standardiserte både på A4- og Letter-størrelser på arkene, ulik
 355 sporvidde på jernbaneskinnene, meter og fot som lengemål, eller
 356 høyre- og venstrekjøring - slik at en kan konkurrere på hvilken
 357 standard som er best.  De fleste forstår heldigvis at dette ikke
 358 bidrar positivt.</p>
 359
 360       </div>
 361       <div class="tags">
 362
 363
 364         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 365
 366
 367       </div>
 368     </div>
 369     <div class="padding"></div>
 370
 371     <div class="entry">
 372       <div class="title">
 373         <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
 374       </div>
 375       <div class="date">
 376         26th June 2009
 377       </div>
 378       <div class="body">
 379         <p>I
 380 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
 381 sin høringsuttalelse</a> til
 382 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
 383 til versjon 2 av statens referansekatalog over standarder</a>, lirer
 384 de av seg følgende FUD-perle:</p>
 385
 386 <p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
 387   spesifikasjoner overordnet styrt av xiph.org, som er en
 388   ikke-kommersiell organisasjon.  Etablerte og anerkjente
 389   standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
 390   innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
 391   Det er derimot helt opp til hver enkelt organisasjon å bestemme
 392   hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
 393   spesifikasjonene bør derfor ikke defineres som åpne
 394   standarder."</blockquote></p>
 395
 396 <p>De vokter seg vel for å nevne den anerkjente
 397 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
 398 IP og det meste av protokoller på Internet, og RFC-standardene som
 399 IETF står bak.  Ogg er spesifisert i
 400 <a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
 401 tvil å anse som en åpen standard.  Vorbis er
 402 <a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>.  Theora er
 403
 404 under standardisering via IETF, med
 405 <a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
 406 utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
 407 skrevet i stein ennå, men det blir neppe endringer som ikke er
 408 bakoverkompatibel).  De kan være inne på noe når det gjelder FLAC da
 409 jeg ikke finner tegn til at <a
 410 href="http://flac.sourceforge.net/format.html">spesifikasjonen
 411 tilgjengelig på web</a> er på tur via noen
 412 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
 413 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
 414 bort fra at også den organiseres via IETF.  Jeg kjenner personlig lite
 415 til FLAC.</p>
 416
 417 <p>Uredelig argumentasjon bør en holde seg for god til å komme med,
 418 spesielt når det er så enkelt i dagens Internet-hverdag å gå
 419 misvisende påstander etter i sømmene.</p>
 420
 421       </div>
 422       <div class="tags">
 423
 424
 425         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 426
 427
 428       </div>
 429     </div>
 430     <div class="padding"></div>
 431
 432     <div class="entry">
 433       <div class="title">
 434         <a href="http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html">Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon 2</a>
 435       </div>
 436       <div class="date">
 437          6th July 2009
 438       </div>
 439       <div class="body">
 440         <p>Jeg ble glad da regjeringen
 441 <a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
 442 versjon 2 av
 443 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
 444 referansekatalog over standarder</a>, men trist da jeg leste hva som
 445 faktisk var vedtatt etter
 446 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
 447 De fleste av de valgte åpne standardene er gode og vil bidra til at
 448 alle kan delta på like vilkår i å lage løsninger for staten, men
 449 noen av dem blokkerer for de som ikke har anledning til å benytte
 450 spesifikasjoner som krever betaling for bruk (såkalt
 451 royalty-betaling).  Det gjelder spesifikt for H.264 for video og MP3
 452 for lyd.  Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
 453 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
 454 fra statens websider gjøre dette uten å måtte bruke programmer der
 455 betaling for bruk var nødvendig.  Når det nå er gjort valgfritt for
 456 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
 457 Vorbis), så vil en bli tvunget til å forholde seg til
 458 royalty-belastede standarder for å få tilgang til videoen og
 459 lyden.</p>
 460
 461 <p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
 462 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
 463 være uten royalty-betaling.  Jeg håper det ikke betyr at en har mistet
 464 all forståelse for hvilke prinsipper som må følges for å oppnå
 465 likeverdig konkurranse mellom aktørene i IT-bransjen.  NUUG advarte
 466 mot dette i
 467 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
 468 høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
 469
 470 <p>Oppdatering 2012-06-29: Kom over <ahref="
 471 http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">en
 472 rapport til FAD</a> fra da versjon 1 av katalogen ble vedtatt, og der
 473 er det tydelig at problemstillingen var kjent og forstått.</p>
 474
 475       </div>
 476       <div class="tags">
 477
 478
 479         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 480
 481
 482       </div>
 483     </div>
 484     <div class="padding"></div>
 485
 486     <div class="entry">
 487       <div class="title">
 488         <a href="http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html">Regjerningens oppsummering av høringen om standardkatalogen versjon 2</a>
 489       </div>
 490       <div class="date">
 491          9th July 2009
 492       </div>
 493       <div class="body">
 494         <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
 495 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
 496 for regjeringen da de tok sin avgjørelse.  De er nå lagt ut på NUUGs
 497 wiki, direkte tilgjengelig via "<a
 498 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
 499 v2.0 - Oppsummering av høring</a>" og "<a
 500 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
 501 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
 502 UTKAST</a>".</p>
 503
 504 <p>Det er tre ting jeg merker meg i oppsummeringen fra
 505 høringsuttalelsen da jeg skummet igjennom den.  Det første er at
 506 forståelsen av hvordan programvarepatenter påvirker fri
 507 programvareutvikling også i Norge når en argumenterer med at
 508 royalty-betaling ikke er et relevant problem i Norge.  Det andre er at
 509 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
 510 standard innenfor hvert område.  Det siste er at påstander i
 511 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
 512 Microsoft om hvordan Ogg blir standardisert og påstanden fra
 513 politidirektoratet om patentproblemer i Theora).</p>
 514
 515       </div>
 516       <div class="tags">
 517
 518
 519         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 520
 521
 522       </div>
 523     </div>
 524     <div class="padding"></div>
 525
 526     <div class="entry">
 527       <div class="title">
 528         <a href="http://people.skolelinux.org/pere/blog/ISO_still_hope_to_fix_OOXML.html">ISO still hope to fix OOXML</a>
 529       </div>
 530       <div class="date">
 531          8th August 2009
 532       </div>
 533       <div class="body">
 534         <p>According to <a
 535 href="http://twerner.blogspot.com/2009/08/defects-of-office-open-xml.html">a
 536 blog post from Torsten Werner</a>, the current defect report for ISO
 537 29500 (ISO OOXML) is 809 pages.  His interesting point is that the
 538 defect report is 71 pages more than the full ODF 1.1 specification.
 539 Personally I find it more interesting that ISO still believe ISO OOXML
 540 can be fixed in ISO.  Personally, I believe it is broken beyon repair,
 541 and I completely lack any trust in ISO for being able to get anywhere
 542 close to solving the problems.  I was part of the Norwegian committee
 543 involved in the OOXML fast track process, and was not impressed with
 544 Standard Norway and ISO in how they handled it.</p>
 545
 546 <p>These days I focus on ODF instead, which seem like a specification
 547 with the future ahead of it.  We are working in NUUG to organise a ODF
 548 seminar this autumn.</p>
 549
 550       </div>
 551       <div class="tags">
 552
 553
 554         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 555
 556
 557       </div>
 558     </div>
 559     <div class="padding"></div>
 560
 561     <div class="entry">
 562       <div class="title">
 563         <a href="http://people.skolelinux.org/pere/blog/Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html">Relative popularity of document formats (MS Office vs. ODF)</a>
 564       </div>
 565       <div class="date">
 566         12th August 2009
 567       </div>
 568       <div class="body">
 569         <p>Just for fun, I did a search right now on Google for a few file ODF
 570 and MS Office based formats (not to be mistaken for ISO or ECMA
 571 OOXML), to get an idea of their relative usage.  I searched using
 572 'filetype:odt' and equvalent terms, and got these results:</P>
 573
 574 <table>
 575 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
 576 <tr><td>Tekst</td> <td>odt:282000</td> <td>docx:308000</td></tr>
 577 <tr><td>Presentasjon</td> <td>odp:75600</td> <td>pptx:183000</td></tr>
 578 <tr><td>Regneark</td> <td>ods:26500     </td> <td>xlsx:145000</td></tr>
 579 </table>
 580
 581 <p>Next, I added a 'site:no' limit to get the numbers for Norway, and
 582 got these numbers:</p>
 583
 584 <table>
 585 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
 586 <tr><td>Tekst</td> <td>odt:2480 </td> <td>docx:4460</td></tr>
 587 <tr><td>Presentasjon</td> <td>odp:299   </td> <td>pptx:741</td></tr>
 588 <tr><td>Regneark</td> <td>ods:187       </td> <td>xlsx:372</td></tr>
 589 </table>
 590
 591 <p>I wonder how these numbers change over time.</p>
 592
 593 <p>I am aware of Google returning different results and numbers based
 594 on where the search is done, so I guess these numbers will differ if
 595 they are conduced in another country.  Because of this, I did the same
 596 search from a machine in California, USA, a few minutes after the
 597 search done from a machine here in Norway.</p>
 598
 599
 600 <table>
 601 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
 602 <tr><td>Tekst</td> <td>odt:129000</td> <td>docx:308000</td></tr>
 603 <tr><td>Presentasjon</td> <td>odp:44200</td> <td>pptx:93900</td></tr>
 604 <tr><td>Regneark</td> <td>ods:26500     </td> <td>xlsx:82400</td></tr>
 605 </table>
 606
 607 <p>And with 'site:no':
 608
 609 <table>
 610 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
 611 <tr><td>Tekst</td> <td>odt:2480</td> <td>docx:3410</td></tr>
 612 <tr><td>Presentasjon</td> <td>odp:175</td> <td>pptx:604</td></tr>
 613 <tr><td>Regneark</td> <td>ods:186       </td> <td>xlsx:296</td></tr>
 614 </table>
 615
 616 <p>Interesting difference, not sure what to conclude from these
 617 numbers.</p>
 618
 619       </div>
 620       <div class="tags">
 621
 622
 623         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 624
 625
 626       </div>
 627     </div>
 628     <div class="padding"></div>
 629
 630     <div class="entry">
 631       <div class="title">
 632         <a href="http://people.skolelinux.org/pere/blog/Danmark_g_r_for_ODF_.html">Danmark går for ODF?</a>
 633       </div>
 634       <div class="date">
 635         29th January 2010
 636       </div>
 637       <div class="body">
 638         <p>Ble nettopp gjort oppmerksom på en
 639 <a href="http://www.version2.dk/artikel/13690-breaking-odf-vinder-dokumentformat-krigen ">nyhet fra Version2</a>
 640 fra Danmark, der det hevdes at Folketinget har vedtatt at ODF skal
 641 brukes som dokumentutvekslingsformat i Staten.</p>
 642
 643 <p>Hyggelig lesning, spesielt hvis det viser seg at de av vedtatt
 644 kravlisten for hva som skal aksepteres som referert i kommentarfeltet
 645 til artikkelen og
 646 <a href="http://www.version2.dk/artikel/13693-er-ooxml-doemt-ude-her-er-kravene-til-en-offentlig-dokumentstandard">en
 647 annen artikkel</a> i samme nett-avis.  Liker spesielt godt denne:</p>
 648
 649 <p><blockquote> Det skal demonstreres, at standarden i sin helhed kan
 650 implementeres af alle direkte i sin helhed på flere
 651 platforme.</blockquote></p>
 652
 653 <p>Noe slikt burde være et krav også i Norge.</p>
 654
 655       </div>
 656       <div class="tags">
 657
 658
 659         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 660
 661
 662       </div>
 663     </div>
 664     <div class="padding"></div>
 665
 666     <div class="entry">
 667       <div class="title">
 668         <a href="http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html">A manual for standards wars...</a>
 669       </div>
 670       <div class="date">
 671          6th June 2010
 672       </div>
 673       <div class="body">
 674         <p>Via the
 675 <a href="http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html">blog
 676 of Rob Weir</a> I came across the very interesting essay named
 677 <a href="http://faculty.haas.berkeley.edu/shapiro/wars.pdf">The Art of
 678 Standards Wars</a> (PDF 25 pages).  I recommend it for everyone
 679 following the standards wars of today.</p>
 680
 681       </div>
 682       <div class="tags">
 683
 684
 685         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 686
 687
 688       </div>
 689     </div>
 690     <div class="padding"></div>
 691
 692     <div class="entry">
 693       <div class="title">
 694         <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">Officeshots taking shape</a>
 695       </div>
 696       <div class="date">
 697         13th June 2010
 698       </div>
 699       <div class="body">
 700         <p>For those of us caring about document exchange and
 701 interoperability, <a href="http://www.officeshots.org/">OfficeShots</a>
 702 is a great service.  It is to ODF documents what
 703 <a href="http://browsershots.org/">BrowserShots</a> is for web
 704 pages.</p>
 705
 706 <p>A while back, I was contacted by Knut Yrvin at the part of Nokia
 707 that used to be Trolltech, who wanted to help the OfficeShots project
 708 and wondered if the University of Oslo where I work would be
 709 interested in supporting the project.  I helped him to navigate his
 710 request to the right people at work, and his request was answered with
 711 a spot in the machine room with power and network connected, and Knut
 712 arranged funding for a machine to fill the spot.  The machine is
 713 administrated by the OfficeShots people, so I do not have daily
 714 contact with its progress, and thus from time to time check back to
 715 see how the project is doing.</p>
 716
 717 <p>Today I had a look, and was happy to see that the Dell box in our
 718 machine room now is the host for several virtual machines running as
 719 OfficeShots factories, and the project is able to render ODF documents
 720 in 17 different document processing implementation on Linux and
 721 Windows.  This is great.</p>
 722
 723       </div>
 724       <div class="tags">
 725
 726
 727         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 728
 729
 730       </div>
 731     </div>
 732     <div class="padding"></div>
 733
 734     <div class="entry">
 735       <div class="title">
 736         <a href="http://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>
 737       </div>
 738       <div class="date">
 739          9th September 2010
 740       </div>
 741       <div class="body">
 742         <p>A few days ago I had the mixed pleasure of bying a new digital
 743 camera, a Canon IXUS 130.  It was instructive and very disturbing to
 744 be able to verify that also this camera producer have the nerve to
 745 specify how I can or can not use the videos produced with the camera.
 746 Even thought I was aware of the issue, the options with new cameras
 747 are limited and I ended up bying the camera anyway.  What is the
 748 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
 749 MPEG-LA that is the problem, and our right to record our experiences
 750 without asking for permissions that is at risk.
 751
 752 <p>On page 27 of the Danish instruction manual, this section is
 753 written:</p>
 754
 755 <blockquote>
 756 <p>This product is licensed under AT&T patents for the MPEG-4 standard
 757 and may be used for encoding MPEG-4 compliant video and/or decoding
 758 MPEG-4 compliant video that was encoded only (1) for a personal and
 759 non-commercial purpose or (2) by a video provider licensed under the
 760 AT&T patents to provide MPEG-4 compliant video.</p>
 761
 762 <p>No license is granted or implied for any other use for MPEG-4
 763 standard.</p>
 764 </blockquote>
 765
 766 <p>In short, the camera producer have chosen to use technology
 767 (MPEG-4/H.264) that is only provided if I used it for personal and
 768 non-commercial purposes, or ask for permission from the organisations
 769 holding the knowledge monopoly (patent) for technology used.</p>
 770
 771 <p>This issue has been brewing for a while, and I recommend you to
 772 read
 773 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
 774 Our Civilization's Video Art and Culture is Threatened by the
 775 MPEG-LA</a>" by Eugenia Loli-Queru and
 776 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
 777 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
 778 the issue.  The solution is to support the
 779 <a href="http://www.digistan.org/open-standard:definition">free and
 780 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
 781 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
 782
 783       </div>
 784       <div class="tags">
 785
 786
 787         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 788
 789
 790       </div>
 791     </div>
 792     <div class="padding"></div>
 793
 794     <div class="entry">
 795       <div class="title">
 796         <a href="http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html">Standardkrav inn i anbudstekster?</a>
 797       </div>
 798       <div class="date">
 799         17th October 2010
 800       </div>
 801       <div class="body">
 802         <p>Hvis det å følge standarder skal ha noen effekt overfor
 803 leverandører, så må slike krav og ønsker komme inn i anbudstekster når
 804 systemer kjøpes inn.  Har ikke sett noen slike formuleringer i anbud
 805 så langt, men har tenkt litt på hva som bør inn.  Her er noen ideer og
 806 forslag.  Min drøm er at en kan sette krav til slik støtte i
 807 anbudstekster, men så langt er det nok mer sannsynlig at en må nøye
 808 seg med å skrive at det er en fordel om slik støtte er tilstede i
 809 leveranser.</p>
 810
 811 <p>Som systemadministrator på Universitetet er det typisk to områder
 812 som er problematiske for meg.  Det ene er admin-grensesnittene på
 813 tjenermaskiner, som vi ønsker å bruke via ssh.  Det andre er nettsider
 814 som vi ønsker å bruke via en nettleser.  For begge deler er det viktig
 815 at protokollene og formatene som brukes følger standarder våre verktøy
 816 støtter.</p>
 817
 818 <p>De fleste har nå støtte for SSH som overføringsprotkoll for
 819 admin-grensesnittet, men det er ikke tilstrekkelig for å kunne stille
 820 inn f.eks BIOS og RAID-kontroller via ssh-forbindelsen.  Det er flere
 821 aktuelle protokoller for fremvisning av BIOS-oppsett og
 822 oppstartmeldinger, og min anbefaling ville være å kreve
 823 VT100-kompatibel protokoll, for å sikre at flest mulig
 824 terminalemulatorer kan forstå hva som kommer fra admin-grensesnittet
 825 via ssh.  Andre aktuelle alternativer er ANSI-terminalemulering og
 826 VT220.  Kanskje en formulering ala dette i anbudsutlysninger vil
 827 fungere:</p>
 828
 829 <p><blockquote>
 830 BIOS og oppstartmeldinger i administrasjonsgrensesnittet til maskinen
 831 bør/skal være tilgjengelig via SSH-protokollen som definert av IETF
 832 (RFC 4251 mfl.) og følge terminalfremvisningprotokollen VT100 (ref?)
 833 når en kobler seg til oppstart via ssh.
 834 </blockquote></p>
 835
 836 <p>Har ikke lykkes med å finne en god referanse for
 837 VT100-spesifikasjonen.</p>
 838
 839 <p>Når det gjelder nettsider, så er det det HTML, CSS og
 840 JavaScript-spesifikasjonen til W3C som gjelder.</p>
 841
 842 <p><blockquote>
 843 Alle systemets nettsider bør/skal være i henhold til statens
 844 standardkatalogs krav om nettsider og følge HTML-standarden som
 845 definert av W3C, og validere uten feil hos W3Cs HTML-validator
 846 (http://validator.w3.org).  Hvis det brukes CSS så bør/skal denne
 847 validere uten feil hos W3Cs CSS-validator
 848 (http://jigsaw.w3.org/css-validator/).  Eventuelle JavaScript skal
 849 være i henhold til EcmaScript-standarden.  I tillegg til å følge de
 850 overnevnte standardene skal websidene fungere i nettleserne (fyll inn
 851 relevant liste for organisasjonen) Firefox 3.5, Internet Explorer 8,
 852 Opera 9, etc.
 853 </blockquote></p>
 854
 855 <p>Vil et slikt avsnitt være konkret nok til å få leverandørene til å
 856 lage nettsider som følger standardene og fungerer i flere
 857 nettlesere?</p>
 858
 859 <p>Tar svært gjerne imot innspill på dette temaet til aktive (at)
 860 nuug.no, og er spesielt interessert i hva andre skriver i sine anbud
 861 for å oppmuntre leverandører til å følge standardene.  Kanskje NUUG
 862 burde lage et dokument med forslag til standardformuleringer å ta med
 863 i anbudsutlysninger?</p>
 864
 865 <p>Oppdatering 2010-12-03: I følge Wikipedias oppføring om
 866 <a href="http://en.wikipedia.org/wiki/ANSI_escape_code">ANSI escape
 867 code</a>, så bruker VT100-terminaler ECMA-48-spesifikasjonen som
 868 basis for sin oppførsel.  Det kan dermed være et alternativ når en
 869 skal spesifisere hvordan seriell-konsoll skal fungere.</p>
 870
 871       </div>
 872       <div class="tags">
 873
 874
 875         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 876
 877
 878       </div>
 879     </div>
 880     <div class="padding"></div>
 881
 882     <div class="entry">
 883       <div class="title">
 884         <a href="http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html">Best å ikke fortelle noen at streaming er nedlasting...</a>
 885       </div>
 886       <div class="date">
 887         30th October 2010
 888       </div>
 889       <div class="body">
 890         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
 891 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
 892 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
 893 filmene NRK la ut ikke var tilgjengelig i et
 894 <a href="http://www.digistan.org/open-standard:definition">fritt og
 895 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
 896
 897 <p><blockquote>
 898 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
 899 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
 900 som dette, vet at det stort sett er mulig å lure ut ting med den
 901 nødvendige forkunnskapen."</p>
 902
 903 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
 904 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
 905 er å forlede leseren.</p>
 906
 907 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
 908 vil tillate streaming men ikke nedlasting meningsløs.</p>
 909
 910 <p>Anbefaler forresten å lese
 911 <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>
 912 om hva som ville være konsekvensen hvis digitale avspillingssperrer
 913 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
 914 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
 915 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
 916 opp under.</p>
 917 </blockquote></p>
 918
 919 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
 920 NRKBeta:</p>
 921
 922 <p><blockquote>
 923 <p>From: Anders Hofseth &lt;XXX@gmail.com>
 924 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
 925 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
 926 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
 927 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
 928
 929 <p>Hei Petter.
 930 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
 931 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
 932 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
 933 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
 934
 935 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
 936 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
 937 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
 938
 939 <p>Med hilsen,
 940 <br>-anders</p>
 941
 942 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
 943 </blockquote></p>
 944
 945 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
 946 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
 947 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
 948 Har fjernet epostadresser og telefonnummer til de involverte, for å
 949 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
 950
 951 <p><blockquote>
 952 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
 953 <br>To: Anders Hofseth &lt;XXX@gmail.com>
 954 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
 955 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
 956 <br>        Henrik Lied &lt;XXX@gmail.com>
 957 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
 958 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
 959
 960 <p>[Anders Hofseth]
 961 <br>> Hei Petter.</p>
 962
 963 <p>Hei.</p>
 964
 965 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
 966 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
 967 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
 968 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
 969
 970 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
 971 vil nok fortsette en stund til.  :)</p>
 972
 973 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
 974 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
 975 fortsette å legge ut arkivmateriale.</p>
 976
 977 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
 978 faktum, som er at streaming er det samme som nedlasting, og at innhold
 979 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
 980 det.</p>
 981
 982 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
 983 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
 984 Det er ikke et argument som holder vann. :)</p>
 985
 986 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
 987 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
 988 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
 989
 990 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
 991 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
 992 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
 993 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
 994 skal sendes skal være uten bruksbegresninger og kan publiseres i
 995 formater som heller ikke har bruksbegresninger (bruksbegresningene til
 996 H.264 burde få varselbjellene i NRK til å ringe).</p>
 997
 998 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
 999 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
1000 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
1001
1002 <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
1003 titt på
1004 &lt;URL: <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html</a> >.
1005 for å se hva slags bruksbegresninger H.264 innebærer.</p>
1006
1007 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1008 kan brukes før rettighetshaverene også innser at de er med på å skade
1009 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1010 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1011 langt på overtid.</p>
1012
1013 <p>> Ring meg om noe er uklart: XXX</p>
1014
1015 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1016 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1017 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1018 for videre diskusjon hadde dere i mine øyne kommet fra det med
1019 ryggraden på plass.</p>
1020
1021 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
1022
1023 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1024 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
1025 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
1026 NRK1. :)</p>
1027
1028 <p>Vennlig hilsen,
1029 <br>--
1030 <br>Petter Reinholdtsen</p>
1031
1032       </div>
1033       <div class="tags">
1034
1035
1036         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
1037
1038
1039       </div>
1040     </div>
1041     <div class="padding"></div>
1042
1043     <div class="entry">
1044       <div class="title">
1045         <a href="http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html">Officeshots still going strong</a>
1046       </div>
1047       <div class="date">
1048         25th December 2010
1049       </div>
1050       <div class="body">
1051         <p>Half a year ago I
1052 <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">wrote
1053 a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
1054 a web service to allow anyone to test how ODF documents are handled by
1055 the different programs reading and writing the ODF format.</p>
1056
1057 <p>I just had a look at the service, and it seem to be going strong.
1058 Very interesting to see the results reported in the gallery, how
1059 different Office implementations handle different ODF features.  Sad
1060 to see that KOffice was not doing it very well, and happy to see that
1061 LibreOffice has been tested already (but sadly not listed as a option
1062 for OfficeShots users yet).  I am glad to see that the ODF community
1063 got such a great test tool available.</p>
1064
1065       </div>
1066       <div class="tags">
1067
1068
1069         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1070
1071
1072       </div>
1073     </div>
1074     <div class="padding"></div>
1075
1076     <div class="entry">
1077       <div class="title">
1078         <a href="http://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>
1079       </div>
1080       <div class="date">
1081         25th December 2010
1082       </div>
1083       <div class="body">
1084         <p>A few days ago
1085 <a href="http://www.idg.no/computerworld/article189879.ece">an
1086 article</a> in the Norwegian Computerworld magazine about how version
1087 2.0 of
1088 <a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
1089 Interoperability Framework</a> has been successfully lobbied by the
1090 proprietary software industry to remove the focus on free software.
1091 Nothing very surprising there, given
1092 <a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
1093 reports</a> on how Microsoft and others have stacked the committees in
1094 this work.  But I find this very sad.   The definition of
1095 <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
1096 open standard from version 1</a> was very good, and something I
1097 believe should be used also in the future, alongside
1098 <a href="http://www.digistan.org/open-standard:definition">the
1099 definition from Digistan</A>.  Version 2 have removed the open
1100 standard definition from its content.</p>
1101
1102 <p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
1103 Villanueva, congressman in Peru at the time, to Microsoft as a reply
1104 to Microsofts attack on his proposal regarding the use of free software
1105 in the public sector in Peru.  As the text was not available from a
1106 few of the URLs where it used to be available, I copy it here from
1107 <a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
1108 source</a> to ensure it is available also in the future.  Some
1109 background information about that story is available in
1110 <a href="http://www.linuxjournal.com/article/6099">an article</a> from
1111 Linux Journal in 2002.</p>
1112
1113 <blockquote>
1114 <p>Lima, 8th of April, 2002<br>
1115 To: Señor JUAN ALBERTO GONZÁLEZ<br>
1116 General Manager of Microsoft Perú</p>
1117
1118 <p>Dear Sir:</p>
1119
1120 <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>
1121
1122 <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>
1123
1124 <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>
1125
1126 <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>
1127
1128 <p>
1129 <ul>
1130 <li>Free access to public information by the citizen. </li>
1131 <li>Permanence of public data. </li>
1132 <li>Security of the State and citizens.</li>
1133 </ul>
1134 </p>
1135
1136 <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>
1137
1138 <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>
1139
1140 <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>
1141
1142 <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>
1143
1144 <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>
1145
1146
1147 <p>From reading the Bill it will be clear that once passed:<br>
1148 <li>the law does not forbid the production of proprietary software</li>
1149 <li>the law does not forbid the sale of proprietary software</li>
1150 <li>the law does not specify which concrete software to use</li>
1151 <li>the law does not dictate the supplier from whom software will be bought</li>
1152 <li>the law does not limit the terms under which a software product can be licensed.</li>
1153
1154 </p>
1155
1156 <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>
1157
1158 <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>
1159
1160 <p>As for the observations you have made, we will now go on to analyze them in detail:</p>
1161
1162 <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>
1163
1164 <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>
1165
1166 <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>
1167
1168 <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>
1169
1170 <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>
1171
1172 <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>
1173
1174 <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>
1175
1176 <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>
1177
1178 <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>
1179
1180 <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>
1181
1182 <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>
1183
1184 <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>
1185
1186 <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>
1187
1188 <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>
1189
1190 <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>
1191
1192 <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>
1193
1194 <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>
1195
1196 <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>
1197
1198 <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>
1199
1200 <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>
1201
1202 <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>
1203
1204 <p>On security:</p>
1205
1206 <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>
1207
1208 <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>
1209
1210 <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>
1211
1212 <p>In respect of the guarantee:</p>
1213
1214 <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>
1215
1216 <p>On Intellectual Property:</p>
1217
1218 <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>
1219
1220 <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>
1221
1222 <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>
1223
1224 <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>
1225
1226 <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>
1227
1228 <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>
1229
1230 <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>
1231
1232 <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>
1233
1234 <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>
1235
1236 <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>
1237
1238 <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>
1239
1240 <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>
1241
1242 <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>
1243
1244 <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>
1245
1246 <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>
1247
1248 <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>
1249
1250 <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>
1251
1252 <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>
1253
1254 <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>
1255
1256 <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>
1257
1258 <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>
1259
1260 <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>
1261
1262 <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>
1263
1264 <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>
1265
1266 <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>
1267
1268 <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>
1269
1270 <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>
1271
1272 <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>
1273
1274 <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>
1275
1276 <p>Cordially,<br>
1277 DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
1278 Congressman of the Republic of Perú.</p>
1279 </blockquote>
1280
1281       </div>
1282       <div class="tags">
1283
1284
1285         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1286
1287
1288       </div>
1289     </div>
1290     <div class="padding"></div>
1291
1292     <div class="entry">
1293       <div class="title">
1294         <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">Is Ogg Theora a free and open standard?</a>
1295       </div>
1296       <div class="date">
1297         25th December 2010
1298       </div>
1299       <div class="body">
1300         <p><a href="http://www.digistan.org/open-standard:definition">The
1301 Digistan definition</a> of a free and open standard reads like this:</p>
1302
1303 <blockquote>
1304
1305 <p>The Digital Standards Organization defines free and open standard
1306 as follows:</p>
1307
1308 <ol>
1309
1310 <li>A free and open standard is immune to vendor capture at all stages
1311 in its life-cycle. Immunity from vendor capture makes it possible to
1312 freely use, improve upon, trust, and extend a standard over time.</li>
1313
1314 <li>The standard is adopted and will be maintained by a not-for-profit
1315 organisation, and its ongoing development occurs on the basis of an
1316 open decision-making procedure available to all interested
1317 parties.</li>
1318
1319 <li>The standard has been published and the standard specification
1320 document is available freely. It must be permissible to all to copy,
1321 distribute, and use it freely.</li>
1322
1323 <li>The patents possibly present on (parts of) the standard are made
1324 irrevocably available on a royalty-free basis.</li>
1325
1326 <li>There are no constraints on the re-use of the standard.</li>
1327
1328 </ol>
1329
1330 <p>The economic outcome of a free and open standard, which can be
1331 measured, is that it enables perfect competition between suppliers of
1332 products based on the standard.</p>
1333 </blockquote>
1334
1335 <p>For a while now I have tried to figure out of Ogg Theora is a free
1336 and open standard according to this definition.  Here is a short
1337 writeup of what I have been able to gather so far.  I brought up the
1338 topic on the Xiph advocacy mailing list
1339 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
1340 July 2009</a>, for those that want to see some background information.
1341 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
1342 the Ogg Theora specification fulfils the Digistan definition.</p>
1343
1344 <p><strong>Free from vendor capture?</strong></p>
1345
1346 <p>As far as I can see, there is no single vendor that can control the
1347 Ogg Theora specification.  It can be argued that the
1348 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
1349 given that it is a non-profit foundation with the expressed goal
1350 making free and open protocols and standards available, it is not
1351 obvious that this is a real risk.  One issue with the Xiph
1352 foundation is that its inner working (as in board member list, or who
1353 control the foundation) are not easily available on the web.  I've
1354 been unable to find out who is in the foundation board, and have not
1355 seen any accounting information documenting how money is handled nor
1356 where is is spent in the foundation.  It is thus not obvious for an
1357 external observer who control The Xiph foundation, and for all I know
1358 it is possible for a single vendor to take control over the
1359 specification.  But it seem unlikely.</p>
1360
1361 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
1362
1363 <p>Assuming that the Xiph foundation is the organisation its web pages
1364 claim it to be, this point is fulfilled.  If Xiph foundation is
1365 controlled by a single vendor, it isn't, but I have not found any
1366 documentation indicating this.</p>
1367
1368 <p>According to
1369 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
1370 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
1371 government, the Xiph foundation is a non-commercial organisation and
1372 the development process is open, transparent and non-Discrimatory.
1373 Until proven otherwise, I believe it make most sense to believe the
1374 report is correct.</p>
1375
1376 <p><strong>Specification freely available?</strong></p>
1377
1378 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
1379 container format</a> and both the
1380 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
1381 <a href="http://theora.org/doc/">Theora</a> codeces are available on
1382 the web.  This are the terms in the Vorbis and Theora specification:
1383
1384 <blockquote>
1385
1386 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
1387 specifications, whether in private, public, or corporate
1388 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
1389 the right to set the Ogg [Vorbis/Theora] specification and certify
1390 specification compliance.
1391
1392 </blockquote>
1393
1394 <p>The Ogg container format is specified in IETF
1395 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
1396 this is the term:<p>
1397
1398 <blockquote>
1399
1400 <p>This document and translations of it may be copied and furnished to
1401 others, and derivative works that comment on or otherwise explain it
1402 or assist in its implementation may be prepared, copied, published and
1403 distributed, in whole or in part, without restriction of any kind,
1404 provided that the above copyright notice and this paragraph are
1405 included on all such copies and derivative works.  However, this
1406 document itself may not be modified in any way, such as by removing
1407 the copyright notice or references to the Internet Society or other
1408 Internet organizations, except as needed for the purpose of developing
1409 Internet standards in which case the procedures for copyrights defined
1410 in the Internet Standards process must be followed, or as required to
1411 translate it into languages other than English.</p>
1412
1413 <p>The limited permissions granted above are perpetual and will not be
1414 revoked by the Internet Society or its successors or assigns.</p>
1415 </blockquote>
1416
1417 <p>All these terms seem to allow unlimited distribution and use, an
1418 this term seem to be fulfilled.  There might be a problem with the
1419 missing permission to distribute modified versions of the text, and
1420 thus reuse it in other specifications.  Not quite sure if that is a
1421 requirement for the Digistan definition.</p>
1422
1423 <p><strong>Royalty-free?</strong></p>
1424
1425 <p>There are no known patent claims requiring royalties for the Ogg
1426 Theora format.
1427 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
1428 and
1429 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
1430 Jobs</a> in Apple claim to know about some patent claims (submarine
1431 patents) against the Theora format, but no-one else seem to believe
1432 them.  Both Opera Software and the Mozilla Foundation have looked into
1433 this and decided to implement Ogg Theora support in their browsers
1434 without paying any royalties.  For now the claims from MPEG-LA and
1435 Steve Jobs seem more like FUD to scare people to use the H.264 codec
1436 than any real problem with Ogg Theora.</p>
1437
1438 <p><strong>No constraints on re-use?</strong></p>
1439
1440 <p>I am not aware of any constraints on re-use.</p>
1441
1442 <p><strong>Conclusion</strong></p>
1443
1444 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
1445 depend on the governing structure of the Xiph foundation.  Given the
1446 background report used by the Norwegian government, I believe it is
1447 safe to assume the last two requirements are fulfilled too, but it
1448 would be nice if the Xiph foundation web site made it easier to verify
1449 this.</p>
1450
1451 <p>It would be nice to see other analysis of other specifications to
1452 see if they are free and open standards.</p>
1453
1454       </div>
1455       <div class="tags">
1456
1457
1458         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1459
1460
1461       </div>
1462     </div>
1463     <div class="padding"></div>
1464
1465     <div class="entry">
1466       <div class="title">
1467         <a href="http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
1468       </div>
1469       <div class="date">
1470         27th December 2010
1471       </div>
1472       <div class="body">
1473         <p>One of the reasons I like the Digistan definition of
1474 "<a href="http://www.digistan.org/open-standard:definition">Free and
1475 Open Standard</a>" is that this is a new term, and thus the meaning of
1476 the term has been decided by Digistan.  The term "Open Standard" has
1477 become so misunderstood that it is no longer very useful when talking
1478 about standards.  One end up discussing which definition is the best
1479 one and with such frame the only one gaining are the proponents of
1480 de-facto standards and proprietary solutions.</p>
1481
1482 <p>But to give us an idea about the diversity of definitions of open
1483 standards, here are a few that I know about.  This list is not
1484 complete, but can be a starting point for those that want to do a
1485 complete survey.  More definitions are available on the
1486 <a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
1487 page</a>.</p>
1488
1489 <p>First off is my favourite, the definition from the European
1490 Interoperability Framework version 1.0.  Really sad to notice that BSA
1491 and others has succeeded in getting it removed from version 2.0 of the
1492 framework by stacking the committee drafting the new version with
1493 their own people.  Anyway, the definition is still available and it
1494 include the key properties needed to make sure everyone can use a
1495 specification on equal terms.</p>
1496
1497 <blockquote>
1498
1499 <p>The following are the minimal characteristics that a specification
1500 and its attendant documents must have in order to be considered an
1501 open standard:</p>
1502
1503 <ul>
1504
1505 <li>The standard is adopted and will be maintained by a not-for-profit
1506 organisation, and its ongoing development occurs on the basis of an
1507 open decision-making procedure available to all interested parties
1508 (consensus or majority decision etc.).</li>
1509
1510 <li>The standard has been published and the standard specification
1511 document is available either freely or at a nominal charge. It must be
1512 permissible to all to copy, distribute and use it for no fee or at a
1513 nominal fee.</li>
1514
1515 <li>The intellectual property - i.e. patents possibly present - of
1516 (parts of) the standard is made irrevocably available on a royalty-
1517 free basis.</li>
1518
1519 <li>There are no constraints on the re-use of the standard.</li>
1520
1521 </ul>
1522 </blockquote>
1523
1524 <p>Another one originates from my friends over at
1525 <a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
1526 support for <a href="http://www.aaben-standard.dk/">this
1527 definition</a> in 2004.  It even made it into the Danish parlament as
1528 <a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
1529 definition of a open standard</a>.  Another from a different part of
1530 the Danish government is available from the wikipedia page.</p>
1531
1532 <blockquote>
1533
1534 <p>En åben standard opfylder følgende krav:</p>
1535
1536 <ol>
1537
1538 <li>Veldokumenteret med den fuldstændige specifikation offentligt
1539 tilgængelig.</li>
1540
1541 <li>Frit implementerbar uden økonomiske, politiske eller juridiske
1542 begrænsninger på implementation og anvendelse.</li>
1543
1544 <li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
1545 "standardiseringsorganisation") via en åben proces.</li>
1546
1547 </ol>
1548
1549 </blockquote>
1550
1551 <p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
1552 definition</a> from Free Software Foundation Europe.</p>
1553
1554 <blockquote>
1555
1556 <p>An Open Standard refers to a format or protocol that is</p>
1557
1558 <ol>
1559
1560 <li>subject to full public assessment and use without constraints in a
1561 manner equally available to all parties;</li>
1562
1563 <li>without any components or extensions that have dependencies on
1564 formats or protocols that do not meet the definition of an Open
1565 Standard themselves;</li>
1566
1567 <li>free from legal or technical clauses that limit its utilisation by
1568 any party or in any business model;</li>
1569
1570 <li>managed and further developed independently of any single vendor
1571 in a process open to the equal participation of competitors and third
1572 parties;</li>
1573
1574 <li>available in multiple complete implementations by competing
1575 vendors, or as a complete implementation equally available to all
1576 parties.</li>
1577
1578 </ol>
1579
1580 </blockquote>
1581
1582 <p>A long time ago, SUN Microsystems, now bought by Oracle, created
1583 its
1584 <a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
1585 Standards Checklist</a> with a fairly detailed description.</p>
1586
1587 <blockquote>
1588 <p>Creation and Management of an Open Standard
1589
1590 <ul>
1591
1592 <li>Its development and management process must be collaborative and
1593   democratic:
1594
1595          <ul>
1596
1597          <li>Participation must be accessible to all those who wish to
1598             participate and can meet fair and reasonable criteria
1599             imposed by the organization under which it is developed
1600             and managed.</li>
1601
1602          <li>The processes must be documented and, through a known
1603             method, can be changed through input from all
1604             participants.</li>
1605
1606          <li>The process must be based on formal and binding commitments for
1607             the disclosure and licensing of intellectual property rights.</li>
1608
1609          <li>Development and management should strive for consensus,
1610             and an appeals process must be clearly outlined.</li>
1611
1612          <li>The standard specification must be open to extensive
1613             public review at least once in its life-cycle, with
1614             comments duly discussed and acted upon, if required.</li>
1615
1616          </ul>
1617
1618 </li>
1619
1620 </ul>
1621
1622 <p>Use and Licensing of an Open Standard</p>
1623 <ul>
1624
1625 <li>The standard must describe an interface, not an implementation,
1626   and the industry must be capable of creating multiple, competing
1627   implementations to the interface described in the standard without
1628   undue or restrictive constraints.  Interfaces include APIs,
1629   protocols, schemas, data formats and their encoding.</li>
1630
1631 <li> The standard must not contain any proprietary "hooks" that create
1632   a technical or economic barriers</li>
1633
1634 <li>Faithful implementations of the standard must
1635   interoperate. Interoperability means the ability of a computer
1636   program to communicate and exchange information with other computer
1637   programs and mutually to use the information which has been
1638   exchanged. This includes the ability to use, convert, or exchange
1639   file formats, protocols, schemas, interface information or
1640   conventions, so as to permit the computer program to work with other
1641   computer programs and users in all the ways in which they are
1642   intended to function.</li>
1643
1644 <li>It must be permissible for anyone to copy, distribute and read the
1645   standard for a nominal fee, or even no fee. If there is a fee, it
1646   must be low enough to not preclude widespread use.</li>
1647
1648 <li>It must be possible for anyone to obtain free (no royalties or
1649   fees; also known as "royalty free"), worldwide, non-exclusive and
1650   perpetual licenses to all essential patent claims to make, use and
1651   sell products based on the standard.  The only exceptions are
1652   terminations per the reciprocity and defensive suspension terms
1653   outlined below. Essential patent claims include pending, unpublished
1654   patents, published patents, and patent applications. The license is
1655   only for the exact scope of the standard in question.
1656
1657       <ul>
1658
1659       <li> May be conditioned only on reciprocal licenses to any of
1660         licensees' patent claims essential to practice that standard
1661         (also known as a reciprocity clause)</li>
1662
1663       <li> May be terminated as to any licensee who sues the licensor
1664         or any other licensee for infringement of patent claims
1665         essential to practice that standard (also known as a
1666         "defensive suspension" clause)</li>
1667
1668       <li> The same licensing terms are available to every potential
1669         licensor</li>
1670
1671       </ul>
1672 </li>
1673
1674 <li>The licensing terms of an open standards must not preclude
1675   implementations of that standard under open source licensing terms
1676   or restricted licensing terms</li>
1677
1678 </ul>
1679
1680 </blockquote>
1681
1682 <p>It is said that one of the nice things about standards is that
1683 there are so many of them.  As you can see, the same holds true for
1684 open standard definitions.  Most of the definitions have a lot in
1685 common, and it is not really controversial what properties a open
1686 standard should have, but the diversity of definitions have made it
1687 possible for those that want to avoid a level marked field and real
1688 competition to downplay the significance of open standards.  I hope we
1689 can turn this tide by focusing on the advantages of Free and Open
1690 Standards.</p>
1691
1692       </div>
1693       <div class="tags">
1694
1695
1696         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1697
1698
1699       </div>
1700     </div>
1701     <div class="padding"></div>
1702
1703     <div class="entry">
1704       <div class="title">
1705         <a href="http://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>
1706       </div>
1707       <div class="date">
1708         30th December 2010
1709       </div>
1710       <div class="body">
1711         <p>After trying to
1712 <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
1713 Ogg Theora</a> to
1714 <a href="http://www.digistan.org/open-standard:definition">the Digistan
1715 definition</a> of a free and open standard, I concluded that this need
1716 to be done for more standards and started on a framework for doing
1717 this.  As a start, I want to get the status for all the standards in
1718 the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
1719 JPEG, PNG, SVG and others.  But to be able to complete this in a
1720 reasonable time frame, I will need help.</p>
1721
1722 <p>If you want to help out with this work, please visit
1723 <a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
1724 wiki pages I have set up for this</a>, and let me know that you want
1725 to help out.  The IRC channel #nuug on irc.freenode.net is a good
1726 place to coordinate this for now, as it is the IRC channel for the
1727 NUUG association where I have created the framework (I am the leader
1728 of the Norwegian Unix User Group).</p>
1729
1730 <p>The framework is still forming, and a lot is left to do.  Do not be
1731 scared by the sketchy form of the current pages. :)</p>
1732
1733       </div>
1734       <div class="tags">
1735
1736
1737         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1738
1739
1740       </div>
1741     </div>
1742     <div class="padding"></div>
1743
1744     <div class="entry">
1745       <div class="title">
1746         <a href="http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html">Chrome plan to drop H.264 support for HTML5 &lt;video&gt;</a>
1747       </div>
1748       <div class="date">
1749         12th January 2011
1750       </div>
1751       <div class="body">
1752         <p>Today I discovered
1753 <a href="http://www.digi.no/860070/google-dropper-h264-stotten-i-chrome">via
1754 digi.no</a> that the Chrome developers, in a surprising announcement,
1755 <a href="http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html">yesterday
1756 announced</a> plans to drop H.264 support for HTML5 &lt;video&gt; in
1757 the browser.  The argument used is that H.264 is not a "completely
1758 open" codec technology.  If you believe H.264 was free for everyone
1759 to use, I recommend having a look at the essay
1760 "<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
1761 Free That Matters</a>".  It is not free of cost for creators of video
1762 tools, nor those of us that want to publish on the Internet, and the
1763 terms provided by MPEG-LA excludes free software projects from
1764 licensing the patents needed for H.264.  Some background information
1765 on the Google announcement is available from
1766 <a href="http://www.osnews.com/story/24243/Google_To_Drop_H264_Support_from_Chrome">OSnews</a>.
1767 A good read. :)</p>
1768
1769 <p>Personally, I believe it is great that Google is taking a stand to
1770 promote equal terms for everyone when it comes to video publishing on
1771 the Internet.  This can only be done by publishing using free and open
1772 standards, which is only possible if the web browsers provide support
1773 for these free and open standards.  At the moment there seem to be two
1774 camps in the web browser world when it come to video support.  Some
1775 browsers support H.264, and others support
1776 <a href="http://www.theora.org/">Ogg Theora</a> and
1777 <a href="http://www.webmproject.org/">WebM</a>
1778 (<a href="http://www.diracvideo.org/">Dirac</a> is not really an option
1779 yet), forcing those of us that want to publish video on the Internet
1780 and which can not accept the terms of use presented by MPEG-LA for
1781 H.264 to not reach all potential viewers.
1782 Wikipedia keep <a href="http://en.wikipedia.org/wiki/HTML5_video">an
1783 updated summary</a> of the current browser support.</p>
1784
1785 <p>Not surprising, several people would prefer Google to keep
1786 promoting H.264, and John Gruber
1787 <a href="http://daringfireball.net/2011/01/simple_questions">presents
1788 the mind set</a> of these people quite well.  His rhetorical questions
1789 provoked a reply from Thom Holwerda with another set of questions
1790 <a href="http://www.osnews.com/story/24245/10_Questions_for_John_Gruber_Regarding_H_264_WebM">presenting
1791 the issues with H.264</a>. Both are worth a read.</p>
1792
1793 <p>Some argue that if Google is dropping H.264 because it isn't free,
1794 they should also drop support for the Adobe Flash plugin.  This
1795 argument was covered by Simon Phipps in
1796 <a href="http://blogs.computerworlduk.com/simon-says/2011/01/google-and-h264---far-from-hypocritical/index.htm">todays
1797 blog post</a>, which I find to put the issue in context.  To me it
1798 make perfect sense to drop native H.264 support for HTML5 in the
1799 browser while still allowing plugins.</p>
1800
1801 <p>I suspect the reason this announcement make so many people protest,
1802 is that all the users and promoters of H.264 suddenly get an uneasy
1803 feeling that they might be backing the wrong horse.  A lot of TV
1804 broadcasters have been moving to H.264 the last few years, and a lot
1805 of money has been invested in hardware based on the belief that they
1806 could use the same video format for both broadcasting and web
1807 publishing.  Suddenly this belief is shaken.</p>
1808
1809 <p>An interesting question is why Google is doing this.  While the
1810 presented argument might be true enough, I believe Google would only
1811 present the argument if the change make sense from a business
1812 perspective.  One reason might be that they are currently negotiating
1813 with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
1814 feeling that dropping H.264 completely from Chroome, Youtube and
1815 Google Video would improve the negotiation position of Google.
1816 Another reason might be that Google want to save money by not having
1817 to pay the video tax to MPEG-LA at all, and thus want to move to a
1818 video format not requiring royalties at all.  A third reason might be
1819 that the Chrome development team simply want to avoid the
1820 Chrome/Chromium split to get more help with the development of Chrome.
1821 I guess time will tell.</p>
1822
1823 <p>Update 2011-01-15: The Google Chrome team provided
1824 <a href="http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html">more
1825 background and information on the move</a> it a blog post yesterday.</p>
1826
1827       </div>
1828       <div class="tags">
1829
1830
1831         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1832
1833
1834       </div>
1835     </div>
1836     <div class="padding"></div>
1837
1838     <div class="entry">
1839       <div class="title">
1840         <a href="http://people.skolelinux.org/pere/blog/The_video_format_most_supported_in_web_browsers_.html">The video format most supported in web browsers?</a>
1841       </div>
1842       <div class="date">
1843         16th January 2011
1844       </div>
1845       <div class="body">
1846         <p>The video format struggle on the web continues, and the three
1847 contenders seem to be Ogg Theora, H.264 and WebM.  Most video sites
1848 seem to use H.264, while others use Ogg Theora.  Interestingly enough,
1849 the comments I see give me the feeling that a lot of people believe
1850 H.264 is the most supported video format in browsers, but according to
1851 the Wikipedia article on
1852 <a href="http://en.wikipedia.org/wiki/HTML5_video">HTML5 video</a>,
1853 this is not true.  Check out the nice table of supprted formats in
1854 different browsers there.  The format supported by most browsers is
1855 Ogg Theora, supported by released versions of Mozilla Firefox, Google
1856 Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
1857 BOLT browser, while not supported by Internet Explorer nor Safari.
1858 The runner up is WebM supported by released versions of Google Chrome
1859 Chromium Opera and Origyn Web Browser, and test versions of Mozilla
1860 Firefox.  H.264 is supported by released versions of Safari, Origyn
1861 Web Browser and BOLT browser, and the test version of Internet
1862 Explorer.  Those wanting Ogg Theora support in Internet Explorer and
1863 Safari can install plugins to get it.</p>
1864
1865 <p>To me, the simple conclusion from this is that to reach most users
1866 without any extra software installed, one uses Ogg Theora with the
1867 HTML5 video tag.   Of course to reach all those without a browser
1868 handling HTML5, one need fallback mechanisms.  In
1869 <a href="http://www.nuug.no/">NUUG</a>, we provide first fallback to a
1870 plugin capable of playing MPEG1 video, and those without such support
1871 we have a second fallback to the Cortado java applet playing Ogg
1872 Theora.  This seem to work quite well, as can be seen in an <a
1873 href="http://www.nuug.no/aktiviteter/20110111-semantic-web/">example
1874 from last week</a>.</p>
1875
1876 <p>The reason Ogg Theora is the most supported format, and H.264 is
1877 the least supported is simple.  Implementing and using H.264
1878 require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
1879 are incompatible with free software licensing.  If you believed H.264
1880 was without royalties and license terms, check out
1881 "<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
1882 Free That Matters</a>" by Simon Phipps.</p>
1883
1884 <p>A incomplete list of sites providing video in Ogg Theora is
1885 available from
1886 <a href="http://wiki.xiph.org/index.php/List_of_Theora_videos">the
1887 Xiph.org wiki</a>, if you want to have a look.  I'm not aware of a
1888 similar list for WebM nor H.264.</p>
1889
1890 <p>Update 2011-01-16 09:40: A question from Tollef on IRC made me
1891 realise that I failed to make it clear enough this text is about the
1892 &lt;video&gt; tag support in browsers and not the video support
1893 provided by external plugins like the Flash plugins.</p>
1894
1895       </div>
1896       <div class="tags">
1897
1898
1899         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1900
1901
1902       </div>
1903     </div>
1904     <div class="padding"></div>
1905
1906     <div class="entry">
1907       <div class="title">
1908         <a href="http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html">RAND terms - non-reasonable and discriminatory</a>
1909       </div>
1910       <div class="date">
1911         19th April 2012
1912       </div>
1913       <div class="body">
1914         <p>Here in Norway, the
1915 <a href="http://www.regjeringen.no/nb/dep/fad.html?id=339"> Ministry of
1916 Government Administration, Reform and Church Affairs</a> is behind
1917 a <a href="http://standard.difi.no/forvaltningsstandarder">directory of
1918 standards</a> that are recommended or mandatory for use by the
1919 government.  When the directory was created, the people behind it made
1920 an effort to ensure that everyone would be able to implement the
1921 standards and compete on equal terms to supply software and solutions
1922 to the government.  Free software and non-free software could compete
1923 on the same level.</p>
1924
1925 <p>But recently, some standards with RAND
1926 (<a href="http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing">Reasonable
1927 And Non-Discriminatory</a>) terms have made their way into the
1928 directory.  And while this might not sound too bad, the fact is that
1929 standard specifications with RAND terms often block free software from
1930 implementing them.  The reasonable part of RAND mean that the cost per
1931 user/unit is low,and the non-discriminatory part mean that everyone
1932 willing to pay will get a license.  Both sound great in theory.  In
1933 practice, to get such license one need to be able to count users, and
1934 be able to pay a small amount of money per unit or user.  By
1935 definition, users of free software do not need to register their use.
1936 So counting users or units is not possible for free software projects.
1937 And given that people will use the software without handing any money
1938 to the author, it is not really economically possible for a free
1939 software author to pay a small amount of money to license the rights
1940 to implement a standard when the income available is zero.  The result
1941 in these situations is that free software are locked out from
1942 implementing standards with RAND terms.</p>
1943
1944 <p>Because of this, when I see someone claiming the terms of a
1945 standard is reasonable and non-discriminatory, all I can think of is
1946 how this really is non-reasonable and discriminatory.  Because free
1947 software developers are working in a global market, it does not really
1948 help to know that software patents are not supposed to be enforceable
1949 in Norway.  The patent regimes in other countries affect us even here.
1950 I really hope the people behind the standard directory will pay more
1951 attention to these issues in the future.</p>
1952
1953 <p>You can find more on the issues with RAND, FRAND and RAND-Z terms
1954 from Simon Phipps
1955 (<a href="http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/">RAND:
1956 Not So Reasonable?</a>).</p>
1957
1958 <p>Update 2012-04-21: Just came across a
1959 <a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm">blog
1960 post from Glyn Moody</a> over at Computer World UK warning about the
1961 same issue, and urging people to speak out to the UK government.  I
1962 can only urge Norwegian users to do the same for
1963 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder">the
1964 hearing taking place at the moment</a> (respond before 2012-04-27).
1965 It proposes to require video conferencing standards including
1966 specifications with RAND terms.</p>
1967
1968       </div>
1969       <div class="tags">
1970
1971
1972         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
1973
1974
1975       </div>
1976     </div>
1977     <div class="padding"></div>
1978
1979     <div class="entry">
1980       <div class="title">
1981         <a href="http://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>
1982       </div>
1983       <div class="date">
1984         26th April 2012
1985       </div>
1986       <div class="body">
1987         <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
1988 article today</a> published by Computerworld Norway, the photographer
1989 <a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
1990 that the video editor application included with
1991 <a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
1992 X</a> have some quite surprising terms of use.  The article is mostly
1993 based on the twitter message from mister Urke, stating:
1994
1995 <p><blockquote>
1996 "<a href="http://twitter.com/urke/status/194062269724897280">Drøy
1997 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
1998 kan jeg KUN bruke dem privat.</a>"
1999 </blockquote></p>
2000
2001 <p>I quickly translated it to this English message:</p>
2002
2003 <p><blockquote>
2004 "Arrogant user agreement: HTC can use MY edited videos
2005 commercially.  Although I can ONLY use them privately."
2006 </blockquote></p>
2007
2008 <p>I've been unable to find the text of the license term myself, but
2009 suspect it is a variation of the MPEG-LA terms I
2010 <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
2011 with my Canon IXUS 130</a>.  The HTC One X specification specifies that
2012 the recording format of the phone is .amr for audio and .mp3 for
2013 video.  AMR is
2014 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
2015 Multi-Rate audio codec</a> with patents which according to the
2016 Wikipedia article require an license agreement with
2017 <a href="http://www.voiceage.com/">VoiceAge</a>.  MP4 is
2018 <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
2019 H.264</a>, which according to Wikipedia require a licence agreement
2020 with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
2021
2022 <p>I know why I prefer
2023 <a href="http://www.digistan.org/open-standard:definition">free and open
2024 standards</a> also for video.</p>
2025
2026       </div>
2027       <div class="tags">
2028
2029
2030         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2031
2032
2033       </div>
2034     </div>
2035     <div class="padding"></div>
2036
2037     <div class="entry">
2038       <div class="title">
2039         <a href="http://people.skolelinux.org/pere/blog/NUUGs_leverer_h_ringsuttalelse_om_v3_1_av_statens_referansekatalog.html">NUUGs leverer høringsuttalelse om v3.1 av statens referansekatalog</a>
2040       </div>
2041       <div class="date">
2042         27th April 2012
2043       </div>
2044       <div class="body">
2045         <p>NUUG-styremedlem Hans-Petter Fjeld
2046 <a href="https://plus.google.com/u/0/110394259537201279374/posts/AGzRmAuFdW1">meldte
2047 nettopp</a> at han har sendt inn <a href="http://www.nuug.no/">NUUG</a>s
2048 høringsuttalelse angående Difi sin standardkatalog v3.1.  Jeg er veldig
2049 glad for at så mange bidro og sikret at vår stemme blir hørt i denne
2050 høringen.  Anbefaler alle å lese våre
2051 <a href="http://wiki.nuug.no/uttalelser/201204-standardkatalog-v3.1">to
2052 sider med innspill</a>.</p>
2053
2054       </div>
2055       <div class="tags">
2056
2057
2058         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
2059
2060
2061       </div>
2062     </div>
2063     <div class="padding"></div>
2064
2065     <div class="entry">
2066       <div class="title">
2067         <a href="http://people.skolelinux.org/pere/blog/OpenOffice_org_fungerer_da_fint_for_blinde_.html">OpenOffice.org fungerer da fint for blinde?</a>
2068       </div>
2069       <div class="date">
2070         21st May 2012
2071       </div>
2072       <div class="body">
2073         <p>De siste dagene har høringsuttalelsene om DIFIs forslag til
2074 standardkatalog v3.1 blitt
2075 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder?tab=comments">publisert
2076 på DIFIs nettside</a>, og jeg kunne der glede meg over at
2077 <a href="http://wiki.nuug.no/uttalelser/201204-standardkatalog-v3.1">NUUGs</a>
2078 uttalelse er kommet med.  En uttalelse som overrasker og forvirrer meg
2079 er
2080 <a href="http://www.standard.difi.no/filearchive/norges-blindeforbund.pdf">den
2081 fra Norges Blindeforbund</a>, som 5 år etter at Klaus Knopper sammen
2082 med sin blinde kone blant annet
2083 <a href="http://www.nuug.no/aktiviteter/20071211-accessibility/">demonstrerte
2084 høyttalende OpenOffice.org på nynorsk for blinde</a> på et NUUG-møte.</p>
2085
2086 <p><a href="https://www.blindeforbundet.no/">Norges Blindeforbund</a>
2087 skriver følgende, som for meg virker å være formulert på sviktende
2088 grunnlag:</p>
2089
2090 <p><blockquote>
2091 <p>Bruk av fri programvare
2092
2093 <p>I FRIPROGSENTERET, RAPPORT 2009-02: Universell utforming
2094 <a href="http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf">http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf</a>
2095 sies det "Det finnes i dag ikke mange fri programvare-rammeverk eller
2096 generelle løsninger som støtter tilgjengelighet eller som er
2097 universelt utformet."</p>
2098
2099 <p>Til tross for at det gjennom prinsippene i fri programvare åpnes
2100 for større frihet til selv å påvirke programvareløsninger i retning av
2101 universell utforming viser praksis at virkeligheten er en annen.
2102 Mange av de mest alminnelige frie programvarepakkene mangler delvis
2103 eller fullstendig tilgjengelighet for mennesker med nedsatt
2104 syn. Eksempler på dette er OpenOffice og LibreOffice m.fl.</p>
2105
2106 <p>En annen utfordring ved bruk av fri programvare kan være manglende
2107 kundestøtte og muligheter til opplæring i bruk av løsningen. Svaksynte
2108 og blinde har et høyere behov for denne typen støtte enn andre brukere
2109 ettersom mange av dem har behov for tilleggsprogramvare som skal
2110 fungere sammen med den opprinnelige programvaren, og ettersom man ikke
2111 har de samme muligheter for overblikk over grensesnittet som en seende
2112 bruker. I tillegg til dette kommer de mer tilgjengelighetstekniske
2113 utfordringene som ofte må løses i samarbeid med
2114 programvareleverandør/produsent.</p>
2115
2116 <p>Fri programvare er ikke på samme måte underlagt lovgivning gjennom
2117 for eksempel diskriminerings og tilgjengelighetsloven ettersom det
2118 ikke alltid finnes en produsent/tilbyder av tjenesten eller produktet.</p>
2119
2120 <p>Norges Blindeforbund krever at universell utforming og
2121 brukskvalitet tas med som viktige hensyn i utredninger som ligger til
2122 grunn for valg av standarder som primært leder brukeren mot fri
2123 programvare. Et eksempel på dette er bruk av dokumentformatet ODF som
2124 leder brukeren i retning av OpenOffice, som er helt eller delvis
2125 utilgjengelig for svaksynte og blinde – noe avhengig av plattform og
2126 hjelpemiddelprogramvare.</p>
2127
2128 </blockquote></p>
2129
2130 <p>Jeg håper noen involvert i OpenOffice.org og/eller LibreOffice tar
2131 kontakt med Norges Blindeforbund og oppklarer det som for meg virker å
2132 være en misforståelse, i og med at OpenOffice.org så vidt jeg vet
2133 fungerer fint også for blinde.</p>
2134
2135 <p>Jeg ble minnet på problemstillingen da jeg leste Slashdot-saken om
2136 "<a href="http://linux.slashdot.org/story/12/05/21/1417221/the-state-of-linux-accessibility">The
2137 State of Linux Accessibility</a>", som også hevder at Linux fungerer
2138 utmerket for blinde.</p>
2139
2140       </div>
2141       <div class="tags">
2142
2143
2144         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
2145
2146
2147       </div>
2148     </div>
2149     <div class="padding"></div>
2150
2151     <div class="entry">
2152       <div class="title">
2153         <a href="http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html">The cost of ODF and OOXML</a>
2154       </div>
2155       <div class="date">
2156         26th May 2012
2157       </div>
2158       <div class="body">
2159         <p>I just come across a blog post from Glyn Moody reporting the
2160 claimed cost from Microsoft on requiring ODF to be used by the UK
2161 government.  I just sent him an email to let him know that his
2162 assumption are most likely wrong.  Sharing it here in case some of my
2163 blog readers have seem the same numbers float around in the UK.</p>
2164
2165 <p><blockquote> <p>Hi.  I just noted your
2166 <a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/does-microsoft-office-lock-in-cost-the-uk-government-500-million/index.htm">http://blogs.computerworlduk.com/open-enterprise/2012/04/does-microsoft-office-lock-in-cost-the-uk-government-500-million/index.htm</a>
2167 comment:</p>
2168
2169 <p><blockquote>"They're all in Danish, not unreasonably, but even
2170 with the help of Google Translate I can't find any figures about the
2171 savings of "moving to a flexible two standard" as claimed by the
2172 Microsoft email. But I assume it is backed up somewhere, so let's take
2173 it, and the £500 million figure for the UK, on trust."
2174 </blockquote></p>
2175
2176 <p>I can tell you that the Danish reports are inflated.  I believe it is
2177 the same reports that were used in the Norwegian debate around 2007,
2178 and Gisle Hannemyr (a well known IT commentator in Norway) had a look
2179 at the content.  In short, the reason it is claimed that using ODF
2180 will be so costly, is based on the assumption that this mean every
2181 existing document need to be converted from one of the MS Office
2182 formats to ODF, transferred to the receiver, and converted back from
2183 ODF to one of the MS Office formats, and that the conversion will cost
2184 10 minutes of work time for both the sender and the receiver.  In
2185 reality the sender would have a tool capable of saving to ODF, and the
2186 receiver would have a tool capable of reading it, and the time spent
2187 would at most be a few seconds for saving and loading, not 20 minutes
2188 of wasted effort.</p>
2189
2190 <p>Microsoft claimed all these costs were saved by allowing people to
2191 transfer the original files from MS Office instead of spending 10
2192 minutes converting to ODF. :)</p>
2193
2194 <p>See
2195 <a href="http://hannemyr.com/no/ms12_vl02.php">http://hannemyr.com/no/ms12_vl02.php</a>
2196 and
2197 <a href="http://hannemyr.com/no/ms12.php">http://hannemyr.com/no/ms12.php</a>
2198 for background information.  Norwegian only, sorry. :)</p>
2199 </blockquote></p>
2200
2201       </div>
2202       <div class="tags">
2203
2204
2205         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
2206
2207
2208       </div>
2209     </div>
2210     <div class="padding"></div>
2211
2212     <div class="entry">
2213       <div class="title">
2214         <a href="http://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>
2215       </div>
2216       <div class="date">
2217         21st June 2012
2218       </div>
2219       <div class="body">
2220         <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
2221 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
2222 <a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
2223 fri og åpen standard</a> i henhold til
2224 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
2225 til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
2226 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
2227 gjelder Norge.  Det ser uansett ut til å være en juridisk interessant
2228 problemstilling.  Men jeg tenkte her om dagen som så, at hvis det er
2229 nødvendig, så har store aktører som
2230 <a href="http://www.nrk.no/">NRK</a> og
2231 <a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
2232 slik avtale.  Jeg har derfor sendt forespørsel til begge (for
2233 regjeringen sin del er det Departementenes Servicesenter som gjør
2234 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
2235 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
2236 av MPEG-LA.  Her er kopi av eposten jeg har sendt til
2237 <a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
2238 Forespørselen til NRK er veldig lik.</p>
2239
2240 <p><blockquote>
2241
2242 <p>Date: Tue, 19 Jun 2012 15:18:33 +0200
2243 <br>From: Petter Reinholdtsen
2244 <br>To: postmottak@dss.dep.no
2245 <br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
2246
2247 <p>Hei.  Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
2248 til avtaler rundt bruk av videoformatene MPEG og H.264.  Jeg er
2249 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
2250 eller noen som representerer MPEG-LA i Norge.</p>
2251
2252 <p>MPEG og H.264 er videoformater som brukes både til kringkasting
2253 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
2254 via Adobe Flash.  MPEG-LA, &lt;URL:
2255 <a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> &gt;, er
2256 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
2257 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
2258 bruksrett for MPEG og H.264.</p>
2259
2260 <p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
2261 videoformater, og dette ser ut til å være organisert av DSS.  Jeg
2262 antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
2263
2264 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge &lt;URL:
2265 <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
2266 &gt;:</p>
2267
2268 <p><blockquote>
2269
2270   <p>6.17. AVC DISTRIBUTION. The following notice applies to software
2271   containing AVC import and export functionality: THIS PRODUCT IS
2272   LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
2273   NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
2274   WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
2275   WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
2276   ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
2277   LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
2278   IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
2279   FROM MPEG LA L.L.C. SEE
2280   <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
2281
2282 </blockquote></p>
2283
2284 <p>Her er det kun "non-commercial" og "personal and non-commercial"
2285 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
2286
2287 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
2288 følgende klausul i følge &lt;URL:
2289 <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
2290 &gt;:</p>
2291
2292 <p><blockquote>
2293
2294   <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
2295   funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
2296   kommersiell bruk ekstra lisensiering og følgende gjelder:
2297   AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
2298   FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
2299   KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
2300   OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
2301   PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
2302   FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
2303   AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
2304   FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
2305 </blockquote></p>
2306
2307 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
2308 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
2309 til å bruke programmet/utstyret hvis en skal lage noe annet enn
2310 private filmer og i ikke-kommersiell virksomhet.</p>
2311
2312 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
2313 ikke er begrenset av de generelle bruksvilkårene som gjelder for
2314 utstyr som bruker MPEG og/eller H.264.</p>
2315 </blockquote></p>
2316
2317 <p>Nå venter jeg spent på svaret.  Jeg planlegger å blogge om svaret
2318 her.</p>
2319
2320       </div>
2321       <div class="tags">
2322
2323
2324         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2325
2326
2327       </div>
2328     </div>
2329     <div class="padding"></div>
2330
2331     <div class="entry">
2332       <div class="title">
2333         <a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">NRK nekter å finne og utlevere eventuell avtale med MPEG-LA</a>
2334       </div>
2335       <div class="date">
2336         25th June 2012
2337       </div>
2338       <div class="body">
2339         <p>Jeg fikk nettopp svar fra NRK på
2340 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">min
2341 forespørsel om kopi av avtale</a> med MPEG-LA eller andre om bruk av
2342 MPEG og/eller H.264.  Svaret har fått saksreferanse 2011/371 (mon tro
2343 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:</p>
2344
2345 <p><blockquote>
2346
2347 <p><strong>Svar på innsynsbegjæring i MPEG / H.264-relaterte
2348 avtaler</strong></p>
2349
2350 <p>Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
2351 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
2352 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
2353 H.264».</p>
2354
2355 <p>I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
2356 en bestemt sak eller i rimelig utstrekning saker av en bestemt
2357 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
2358 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
2359 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
2360 står følgende:</p>
2361
2362 <p>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
2363 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
2364 at den enkelte saka blir identifisert.  Ein kan med andre ord i
2365 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
2366 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
2367 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
2368 til dato, partar eller liknande.»</p>
2369
2370 <p>Vedrørende denne begrensningen har Justisdepartementet uttalt
2371 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):</p>
2372
2373 <p><em>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
2374 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
2375 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
2376 vanskelege å handsame for forvaltninga.»</em></p>
2377
2378 <p>I samme sak uttaler Lovavdelingen følgende:</p>
2379
2380 <p><em>«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
2381 rimeleg utstrekning' kan krevjast innsyn i `saker av ein bestemt
2382 art'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning' kan
2383 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
2384 arbeidskrevjande det vil vere å finne fram til dei aktuelle
2385 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
2386 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
2387 mange dokument) at arbeidsmengda som ville gått med til å handsame
2388 det, er større enn det ein `i rimeleg utstrekning' kan krevje (sjølv
2389 om det nok skal mykje til).»</em></p>
2390
2391 <p>NRK har ikke noen egen sammenstilling over avtaler innenfor
2392 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
2393 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
2394 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
2395 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
2396 gjennomgang av avtaler måtte gjøres manuelt av en person med
2397 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
2398 ressurser for å finne frem relevante avtaler og for deretter å vurdere
2399 om de dekkes av det innsynsbegjæringen omfattes.</p>
2400
2401 <p>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
2402 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
2403 vil være langt større enn det som i rimelig utstrekning kan kreves i
2404 henhold til offentleglova § 28 annet ledd.</p>
2405
2406 <p>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
2407 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
2408 frem til mottakeren, i henhold til reglene i offentleglova § 32,
2409 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
2410 kirkedepartementet, og sendes til NRK.</p>
2411
2412 <p>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
2413 slik at en eventuell søknad om innsyn kan tydeligere identifisere
2414 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
2415 for inneværende og forrige måned ligger ute på
2416 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
2417 på forespørsel til innsyn (at) nrk.no.</p>
2418
2419 <p>Med hilsen
2420 <br>Dokumentarkivet i NRK
2421 <br>v/ Elin Brandsrud
2422 <br>Tel. direkte: 23 04 29 29
2423 <br>Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
2424 <br>innsyn (at) nrk.no</p>
2425
2426 </blockquote></p>
2427
2428 <p>Svaret kom
2429 <a href="http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf">i
2430 PDF-form som vedlegg på epost</a>.  Jeg er litt usikker på hvordan jeg
2431 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
2432 på å vurdere om jeg skal klage.  Enten må nok forespørselen
2433 reformuleres eller så må jeg vel klage.  Synes jo det er merkelig at
2434 NRK ikke har bedre kontroll med hvilke avtaler de har inngått.  Det
2435 burde jo være noen i ledelsen som vet om de har signert en avtale med
2436 MPEG-LA eller ikke...</p>
2437
2438 <p>Oppdatering 2012-06-25 20:20: Et google-søk på "2011/371 nrk"
2439 sendte meg til postjournalen for
2440 <a href="http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf">2012-06-19</a>
2441 og
2442 <a href="http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf">2012-06-20</a>
2443 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
2444 er "Graphic Systems Regions MA 2378/10E".  Videre søk etter "Graphic
2445 Systems Regions" viser at dette er saken til et anbud om
2446 "<a href="http://no.mercell.com/m/mts/Tender/27179412.aspx">a graphics
2447 system for 12 or 13 sites broadcasting regional news</a>" hos Mercell
2448 Sourcing Service, også omtalt på
2449 <a href="http://www.publictenders.net/tender/595705">Public
2450 Tenders</a> og
2451 <a href="http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521">Doffin</a>.
2452 Jeg er dog usikker på hvordan dette er relatert til min
2453 forespørsel.</p>
2454
2455 <p>Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
2456 miljøet rundt
2457 <a href="http://code.google.com/p/open-broadcast-encoder/">Open
2458 Broadcast Encoder</a>, at listen over de som har lisensavtale med
2459 MPEG-LA er
2460 <a href="http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx">tilgjengelig
2461 på web</a>.  Veldig fint å oppdage hvor den finnes, da jeg må ha lett
2462 etter feil ting da jeg forsøke å finne den.  Der står ikke NRK, men
2463 flere andre "Broadcasting Company"-oppføringer.  Lurer på om det betyr
2464 at NRK ikke trenger avtale, eller noe helt annet?</p>
2465
2466       </div>
2467       <div class="tags">
2468
2469
2470         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2471
2472
2473       </div>
2474     </div>
2475     <div class="padding"></div>
2476
2477     <div class="entry">
2478       <div class="title">
2479         <a href="http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html">MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H.264-video</a>
2480       </div>
2481       <div class="date">
2482         28th June 2012
2483       </div>
2484       <div class="body">
2485         <p>Etter at NRK
2486 <a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">nektet
2487 å spore opp eventuell avtale med MPEG-LA</a> eller andre om bruk av
2488 MPEG/H.264-video etter at jeg <a
2489 href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">ba
2490 om innsyn i slike avtaler</a>, tenkte jeg at i stedet for å forsøke å
2491 få NRK til å finne en slik avtale, så burde det være like enkelt å
2492 spørre MPEG-LA om de hadde avtale med NRK.  Spørsmålet ble sendt før
2493 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
2494 "in Good Standing" befant seg.  MPEG-LA svarte meg i dag, og kan
2495 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
2496 slått fast.  Ikke overraskende mener MPEG-LA at det trengs en avtale
2497 med MPEG-LA for å streame H.264, men deres rammer er jo
2498 rettstilstanden i USA og ikke Norge.  Jeg tar dermed den delen av
2499 svaret med en klype salt.  Jeg er dermed fortsatt ikke klok på om det
2500 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
2501 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
2502 gjør at de ikke trenger avtale direkte med MPEG-LA.  Jeg håper NRKs
2503 jurister har vurdert dette, og at det er mulig å få tilgang til
2504 vurderingen uansett om de trenger en avtale eller ikke.</p>
2505
2506 <p>Her er epostutvekslingen med MPEG-LA så langt.  Håper ikke
2507 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
2508 MPEG-LA.</p>
2509
2510 <p><blockquote>
2511 <p>Date: Mon, 25 Jun 2012 15:29:37 +0200
2512 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2513 <br>To: licensing-web (at) mpegla.com
2514 <br>Subject: Do NRK have a license agreement with MPEG-LA?</p>
2515
2516 <p>Hi.  I have a small question for you, that I hope it is OK that I
2517 ask.</p>
2518
2519 <p>Is there any license agreements between MPEG-LA and NRK, &lt;URL:
2520 <a href="http://www.nrk.no/">http://www.nrk.no/</a> &gt;, the
2521 Norwegian national broadcasting cooperation?  I am not sure if they
2522 need one, and am just curious if such agreeement exist.</p>
2523
2524 <p>The postal address is</p>
2525
2526 <p><blockquote>
2527   NRK
2528   <br>Postbox 8500, Majorstuen
2529   <br>0340 Oslo
2530   <br>Norway
2531 </blockquote></p>
2532
2533 <p>if it make it easier for you to locate such agreement.</p>
2534
2535 <p>Can you tell me how many entities in Norway have an agreement with
2536 MPEG-LA, and the name of these entities?</p>
2537
2538 <p>--
2539 <br>Happy hacking
2540 <br>Petter Reinholdtsen
2541 </blockquote></p>
2542
2543 <p>I dag, to dager senere, fikk jeg følgende svar:</p>
2544
2545 <p><blockquote>
2546 <p>Date: Thu, 28 Jun 2012 14:11:17 +0000
2547 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com>
2548 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com>
2549 <br>CC: MD Administration &lt;MDAdministration (at) mpegla.com>
2550 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
2551
2552 <p>Dear Mr. Reinholdtsen,</p>
2553
2554 <p>Thank you for your message and for your interest in MPEG LA. We
2555 appreciate hearing from you and I will be happy to assist you.</p>
2556
2557 <p>To begin, I will assume that you are referring to AVC/H.264
2558 technology in your message below, as this technology is commonly used
2559 in the transmission of video content.  In that case, please allow me
2560 to briefly summarize the coverage provided by our AVC Patent Portfolio
2561 License.</p>
2562
2563 <P>Our AVC License provides coverage for end products and video
2564 services that make use of AVC/H.264 technology.  Accordingly, the
2565 party offering such end products and video to End Users concludes the
2566 AVC License and is responsible for paying the applicable royalties
2567 associated with the end products/video they offer.</p>
2568
2569 <p>While the Norwegian Broadcast Corporation (NRK) is not currently a
2570 Licensee to MPEG LA's AVC License (or any other Portfolio License
2571 offered by MPEG LA), if NRK offers AVC Video to End Users for
2572 remuneration (for example, Title-by-Title, Subscription, Free
2573 Television, or Internet Broadcast AVC Video), then NRK will need to
2574 conclude the AVC License and may be responsible for paying applicable
2575 royalties associated with the AVC Video it distributes.</p>
2576
2577 <p>Today I will send you a FedEx package containing a copy of our AVC
2578 License for your review.  You should receive the License document
2579 within the next few days.</p>
2580
2581 <p>Meanwhile, MPEG LA currently has several Norwegian Licensees that
2582 can be found under the "Licensees" header within the respective
2583 portion of our website.  For example, you may find our list of
2584 Licensees in Good Standing to our AVC License in the AVC portion of
2585 our website,
2586 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</a></p>
2587
2588 <p>I hope the above information is helpful.  If you have additional
2589 questions or need further assistance with the AVC License, please feel
2590 free to contact me directly.  I look forward to hearing from you again
2591 soon.</p>
2592
2593 <p>Best regards,</p>
2594
2595 <p>Ryan</p>
2596
2597 <p>Ryan M. Rodriguez
2598 <br>Licensing Associate
2599 <br>MPEG LA
2600 <br>5425 Wisconsin Avenue
2601 <br>Suite 801
2602 <br>Chevy Chase, MD 20815
2603 <br>U.S.A.
2604 <br>Phone:  +1 (301) 986-6660 x211
2605 <br>Fax:    +1 (301) 986-8575
2606 <br>Email: rrodriguez (at) mpegla.com</p>
2607
2608 </blockquote></p>
2609
2610 <p>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
2611 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
2612 da han jo ikke hadde fått noen postadresse som nådde meg.</p>
2613
2614 <p><blockquote>
2615
2616 <p>Date: Thu, 28 Jun 2012 16:36:15 +0200
2617 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2618 <br>To: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2619 <br>Cc: MD Administration &lt;MDAdministration (at) mpegla.com&gt;
2620 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
2621
2622 <p>[Ryan Rodriguez]
2623 <br>&gt; Dear Mr. Reinholdtsen,</p>
2624
2625 <p>Thank you for your quick reply.</p>
2626
2627 <p>&gt; Today I will send you a FedEx package containing a copy of our AVC
2628 <br>&gt; License for your review.  You should receive the License document
2629 <br>&gt; within the next few days.</p>
2630
2631 <p>The part about sending a FedEx package confused me, though.  I did not
2632 <br>give you my address, nor am I associated with NRK in any way, so I hope
2633 <br>you did not try to send me a package using the address of NRK.  If you
2634 <br>would send me the Internet address of to the document, it would be more
2635 <br>useful to me to be able to download it as an electronic document.</p>
2636
2637 <p>&gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
2638 <br>&gt; be found under the "Licensees" header within the respective portion
2639 <br>&gt; of our website.  For example, you may find our list of Licensees in
2640 <br>&gt; Good Standing to our AVC License in the AVC portion of our website,
2641 <br>&gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</p>
2642
2643 <p>How can I recognize the Norwegian licensees?</p>
2644
2645 <p>--
2646 <br>Happy hacking
2647 <br>Petter Reinholdtsen</p>
2648 </blockquote></p>
2649
2650 <p>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
2651 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
2652 siste epost.  Får håpe noen likevel følger opp "FedEx-pakken".  For å
2653 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
2654 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
2655 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
2656 min epost tidsnok.</p>
2657
2658 <p><blockquote>
2659
2660 <p>Date: Thu, 28 Jun 2012 14:36:20 +0000
2661 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2662 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2663 <br>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?</p>
2664
2665 <p>Thank you for your message.</p>
2666
2667 <p>I will be out of the office until Thursday, July 5 and will respond
2668 to all messages upon my return.  If this is a matter that requires
2669 immediate attention, please contact Sidney Wolf (swolf (at)
2670 mpegla.com)</p>
2671
2672 <p>Best regards,</p>
2673
2674 <p>Ryan</p>
2675
2676 <p>Ryan M. Rodriguez
2677 <br>Licensing Associate
2678 <br>MPEG LA</p>
2679
2680 </blockquote></p>
2681
2682 <p>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
2683 som er om en trenger avtale med MPEG-LA for å publisere eller
2684 kringkaste H.264-video i Norge.</p>
2685
2686       </div>
2687       <div class="tags">
2688
2689
2690         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2691
2692
2693       </div>
2694     </div>
2695     <div class="padding"></div>
2696
2697     <div class="entry">
2698       <div class="title">
2699         <a href="http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html">Departementenes servicesenter har ingen avtale om bruk av H.264 med MPEG-LA</a>
2700       </div>
2701       <div class="date">
2702         29th June 2012
2703       </div>
2704       <div class="body">
2705         <p>Da fikk jeg nettopp svar fra
2706 <a href="http://www.dss.dep.no/">Departementenes servicesenter</a>
2707 (DSS) på
2708 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">mitt
2709 spørsmål om avtale rundt bruk av H.264</a>.  De har ingen avtale med
2710 MPEG LA eller dets representanter.  Her er svaret.
2711
2712 <p><blockquote>
2713
2714 <p>Date: Fri, 29 Jun 2012 07:04:42 +0000
2715 <br>From: Nielsen Mette Haga &lt;Mette-Haga.Nielsen (at) dss.dep.no&gt;
2716 <br>To: Petter Reinholdtsen &lt;petter.reinholdtsen (at) ...&gt;
2717 <br>CC: Postmottak &lt;Postmottak (at) dss.dep.no&gt;
2718 <br>Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler</p>
2719
2720 <p>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
2721 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
2722 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
2723 vår avtale med Smartcom.</p>
2724
2725 <p>Vennlig hilsen</p>
2726
2727 <p>Mette Haga Nielsen
2728 <br>Fung. seksjonssjef</p>
2729
2730 <p>Departementenes servicesenter</p>
2731
2732 <p>Informasjonsforvaltning
2733
2734 <p>Mobil 93 09 83 51
2735 <br>E-post mette-haga.nielsen (at) dss.dep.no</p>
2736 </blockquote></p>
2737
2738 <p>Hvis den norske regjeringen representert ved DSS ikke har slik
2739 avtale, så kan en kanskje konkludere med at det ikke trengs?  Jeg er
2740 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
2741 minste interessant å vite at hverken NRK eller DSS har funnet det
2742 nødvendig å ha avtale om bruk av H.264.</p>
2743
2744 <p>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
2745 til bruk av opphavsrettsbeskyttet materiale de bruker til
2746 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
2747 privatpersoner i Norge.  Har de lov til å bryte vilkårene, eller har
2748 de brutt dem og så langt sluppet unna med det?  Jeg aner ikke.</p>
2749
2750       </div>
2751       <div class="tags">
2752
2753
2754         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
2755
2756
2757       </div>
2758     </div>
2759     <div class="padding"></div>
2760
2761     <div class="entry">
2762       <div class="title">
2763         <a href="http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html">DIFI foreslår å kaste ut ODF og ta inn OOXML fra statens standardkatalog</a>
2764       </div>
2765       <div class="date">
2766         29th June 2012
2767       </div>
2768       <div class="body">
2769         <p>DIFI har nettopp annonsert høring om revisjon av
2770 <a href="http://www.standard.difi.no/forvaltningsstandarder">standardkatalogen</a>,
2771 og endelig har Microsoft fått viljen sin.  Se
2772 <a href="http://www.standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">høringssiden</a>
2773 for hele teksten.</p>
2774
2775 <p>Her er forslaget i sin helhet:</p>
2776
2777 <p><blockquote>
2778 <p>3.2 Revisjon av krav til redigerbare dokumenter</p>
2779
2780 <p>I første versjon av referansekatalogen i 2007 ble det satt krav om
2781 Open Document Format (ODF), versjon 1.1 (OASIS, 1.2.2007) for
2782 redigerbare dokumenter. Kravet var obligatorisk for stat og sterkt
2783 anbefalt for kommunal sektor. I 2009 ble kravet gjort obligatorisk for
2784 hele offentlig sektor i
2785 <a href="http://www.lovdata.no/for/sf/fa/xa-20090925-1222.html">forskrift
2786 om IT-standarder i forvaltningen</a>. Anvendelsesområdet for kravet
2787 har vært begrenset til publisering av dokumenter som skal bearbeides
2788 videre (§ 4 nr. 1 andre ledd). I 2011 ble anvendelsesområdet utvidet
2789 til å omfatte utveksling av dokumenter beregnet for redigering som
2790 vedlegg til e-post (§4 nr.  2).</p>
2791
2792 <p>Office Open XML ISO/IEC 29500:2011 (OOXML) er et dokumentformat
2793 opprinnelig utviklet av Microsoft med tilsvarende anvendelsesområde
2794 som ODF. Formatet er blant annet tatt i bruk i nyere versjoner av
2795 kontorstøtteprogamvaren MS Office.  Difi har foretatt en
2796 <a href="http://www.standard.difi.no/filearchive/revisjonsvurdering-standarder-for-redigerbare-dokumenter-v1-0.pdf">revisjonsvurdering</a>
2797 av krav som stilles til redigerbare dokumenter i Forskrift om
2798 IT-standarder i forvaltningen, og anbefaler at kravet til ODF
2799 fjernes. Dette innebærer at det ikke stilles krav til dokumentformater
2800 for redigerbare dokumenter ved publisering på offentlige virksomheters
2801 nettsider og for redigerbare vedlegg til e-post som sendes fra
2802 offentlige virksomheter til innbyggere og næringsliv. Offentlige
2803 virksomheter vil dermed stå fritt til å publisere eller sende
2804 redigerbare dokumenter i det format som ivaretar brukernes behov
2805 best.</p>
2806
2807 <p>Forslaget innebærer at krav til ODF utgår § 4 nr. 1 tredje ledd og
2808 § 4 nr. 2 første ledd</p>
2809
2810 <P>Imidlertid bør det stilles strengere krav til hvilke formater
2811 offentlige virksomheter plikter å motta redigerbare dokumenter. Vi
2812 mener at det ikke bør skilles mellom mottak av redigerbare dokumenter
2813 som sendes i ODF eller OOXML3, som begge er åpne standarder. Dette
2814 medfører at innbyggere og næringsliv skal kunne basere sitt valg av
2815 programvare på egne behov og ikke på de valg offentlige virksomheter
2816 tar. Kravet vil omfatte hele offentlig sektor, herunder
2817 utdanningssektoren, hvor det kanskje er størst bruk av ODF. Kravet er
2818 foreslått som ny § 4 nr.2 andre ledd</p>
2819 </blockquote></p>
2820
2821 <P>De satser vel på at det hele blir glemt over sommeren, og at de
2822 fleste har glemt Standard Norge og ISOs fallitt fra da OOXML ble
2823 jukset igjennom som ISO-standard.  Jeg håper mine lesere sender inn
2824 høringsuttalelser til høringen.</p>
2825
2826 <p>Anbefaler alle å friske opp sine argumenter ved å lese
2827 <a href="http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html">svaret
2828 fra senator Edgar Villanueva til Microsoft i Peru</a>.  Det er en
2829 klassisk tekst som er like gyldig i dag som da det ble skrevet.</p>
2830
2831
2832       </div>
2833       <div class="tags">
2834
2835
2836         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
2837
2838
2839       </div>
2840     </div>
2841     <div class="padding"></div>
2842
2843     <p style="text-align: right;"><a href="standard.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
2844     <div id="sidebar">
2845
2846
2847
2848 <h2>Archive</h2>
2849 <ul>
2850
2851 <li>2012
2852 <ul>
2853
2854 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
2855
2856 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
2857
2858 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
2859
2860 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
2861
2862 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
2863
2864 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
2865
2866 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (1)</a></li>
2867
2868 </ul></li>
2869
2870 <li>2011
2871 <ul>
2872
2873 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
2874
2875 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
2876
2877 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
2878
2879 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
2880
2881 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
2882
2883 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
2884
2885 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
2886
2887 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
2888
2889 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
2890
2891 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
2892
2893 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
2894
2895 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
2896
2897 </ul></li>
2898
2899 <li>2010
2900 <ul>
2901
2902 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
2903
2904 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
2905
2906 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
2907
2908 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
2909
2910 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
2911
2912 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
2913
2914 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
2915
2916 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
2917
2918 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
2919
2920 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
2921
2922 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
2923
2924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
2925
2926 </ul></li>
2927
2928 <li>2009
2929 <ul>
2930
2931 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
2932
2933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
2934
2935 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
2936
2937 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
2938
2939 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
2940
2941 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
2942
2943 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
2944
2945 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
2946
2947 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
2948
2949 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
2950
2951 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
2952
2953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
2954
2955 </ul></li>
2956
2957 <li>2008
2958 <ul>
2959
2960 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
2961
2962 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
2963
2964 </ul></li>
2965
2966 </ul>
2967
2968
2969
2970 <h2>Tags</h2>
2971 <ul>
2972
2973  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
2974
2975  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
2976
2977  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
2978
2979  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
2980
2981  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
2982
2983  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
2984
2985  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (55)</a></li>
2986
2987  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (106)</a></li>
2988
2989  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (9)</a></li>
2990
2991  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (3)</a></li>
2992
2993  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (137)</a></li>
2994
2995  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (16)</a></li>
2996
2997  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
2998
2999  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (5)</a></li>
3000
3001  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (29)</a></li>
3002
3003  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
3004
3005  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
3006
3007  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
3008
3009  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
3010
3011  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (21)</a></li>
3012
3013  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (181)</a></li>
3014
3015  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (134)</a></li>
3016
3017  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (3)</a></li>
3018
3019  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
3020
3021  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (30)</a></li>
3022
3023  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (48)</a></li>
3024
3025  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
3026
3027  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
3028
3029  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
3030
3031  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
3032
3033  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
3034
3035  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
3036
3037  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (1)</a></li>
3038
3039  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
3040
3041  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
3042
3043  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (34)</a></li>
3044
3045  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
3046
3047  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
3048
3049  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
3050
3051  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
3052
3053  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (30)</a></li>
3054
3055  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
3056
3057  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (24)</a></li>
3058
3059 </ul>
3060
3061
3062     </div>
3063     <p style="text-align: right">
3064  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
3065 </p>
3066
3067   </body>
3068 </html>