blog/tags/digistan/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen: Entries Tagged digistan</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="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="digistan.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 "digistan".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/Regjeringen__FAD_og_DIFI_g_r_inn_for___fjerne_ODF_som_obligatorisk_standard_i_det_offentlige.html">Regjeringen, FAD og DIFI går inn for å fjerne ODF som obligatorisk standard i det offentlige</a>
  26       </div>
  27       <div class="date">
  28         18th March 2013
  29       </div>
  30       <div class="body">
  31         <p>I
  32 <a href="http://standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">siste
  33 høring</a> om
  34 <a href="http://standard.difi.no/forvaltningsstandarder">referansekatalogen
  35 for IT-standarder i offentlig sektor</a>, med høringsfrist 2012-09-30
  36 (DIFI-sak 2012/498), ble det foreslått å fjerne ODF som obligatorisk
  37 standard når en publiserte dokumenter som skulle kunne redigeres
  38 videre av mottaker.  NUUG og andre protesterte på forslaget, som er et
  39 langt steg tilbake når det gjelder å sikre like rettigheter for alle
  40 når en kommuniserer med det offentlige.  For noen dager siden ble jeg
  41 oppmerksom på at Direktoratet for forvaltning og IKT (DIFI) og
  42 Fornyings-,administrasjons- og kirkedepartementet (FAD) har
  43 konkludert, og oversendt forslag til regjeringen i saken. FADs
  44 dokument
  45 <a href="http://www.oep.no/search/result.html?period=none&descType=both&caseNumber=2012%2F2168&senderType=both&documentType=all&list2=94&searchType=advanced&Search=S%C3%B8k+i+journaler">2012/2168</a>-8,
  46 «Utkast til endring av standardiseringsforskriften» datert 2013-02-06
  47 har følgende triste oppsummering fra høringen i saken:</p>
  48
  49 <p><blockquote>
  50 Det kom noen innvendinger på forslaget om å fjerne ODF som
  51 obligatorisk standard for redigerbare dokumenter. Innvendingene har
  52 ikke blitt ilagt avgjørende vekt.
  53 </blockquote></p>
  54
  55 <p>Ved å fjerne ODF som obligatorisk format ved publisering av
  56 redigerbare dokumenter setter en Norge tiår tilbake.  Det som vil skje
  57 er at offentlige etater går tilbake til kun å publisere dokumenter på
  58 et av de mange formatene til Microsoft Office, og alle som ikke
  59 aksepterer bruksvilkårene til Microsoft eller ikke har råd til å bruke
  60 penger på å få tilgang til Microsoft Office må igjen basere seg på
  61 verktøy fra utviklerne som er avhengig av å reversutvikle disse
  62 formatene.  I og med at ISO-spesifikasjonen for OOXML ikke komplett og
  63 korrekt spesifiserer formatene til MS Office (men er nyttige å titte i
  64 når en reversutvikler), er en tilbake til en situasjon der en ikke har
  65 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
  66 fri og åpen standard</a> å forholde seg til, men i stedet må springe
  67 etter Microsoft.  Alle andre leverandører enn Microsoft vil dermed ha
  68 en seriøs ulempe.  Det er som å fjerne krav om bruk av meter som
  69 måleenhet, og heretter aksepterer alle måleenheter som like gyldige,
  70 når en vet at den mest brukte enheten vil være armlengden til Steve
  71 Ballmer slik Microsoft måler den.</p>
  72
  73 <p>Jeg er ikke sikker på om forslaget er vedtatt av regjeringen ennå.
  74 Kristian Bergem hos DIFI nevnte på et møte forrige tirsdag at han
  75 trodde det var vedtatt i statsråd 8. mars, men jeg har ikke klart å
  76 finne en skriftlig kilde på regjeringen.no som bekrefter dette.
  77 Kanskje det ennå ikke er for sent...</p>
  78
  79 <p>Jeg ba i forrige uke om innsyn i dokument 6, 7 og 8 i FAD-saken, og
  80 har i dag fått innsyn i dokument 7 og 8.  Ble nektet innsyn i
  81 dokumentet med tittelen «Oppsummering av høring om endringer i
  82 forskrift om IT-standarder i offentlig forvaltning» med hjemmel i
  83 off. lovens §15.1, så det er vanskelig å vite hvordan argumentene fra
  84 høringen ble mottatt og forstått av saksbehandleren hos DIFI.  Lurer
  85 på hvordan jeg kan klage på at jeg ikke fikk se oppsummeringen.  Fikk
  86 tre PDFer tilsendt fra FAD,
  87 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/20130115%20Notat%20FAD%20-%20EHF.pdf%20(L)(889185).pdf">Endring av underversjon i EHF</a>,
  88 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/Bakgrunnsnotat%20knyttet%20til%20versjon%20av%20EHF%20standarden%20i%20Forskrift%20om%20IT-standarder%20i%20offentlig%20sektor.pdf">Bakgrunnsnotat knyttet til versjon av EHF standarden i Forskrift om IT-standarder i offentlig sektor</a> og
  89 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/Utkast%20Kongelig%20resolusjon.docx%20(L)(898064).pdf">Utkast til endring av standardiseringsforskriften</a>, hvis du vil ta en titt.</p>
  90
  91       </div>
  92       <div class="tags">
  93
  94
  95         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/standard">standard</a>.
  96
  97
  98       </div>
  99     </div>
 100     <div class="padding"></div>
 101
 102     <div class="entry">
 103       <div class="title">
 104         <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>
 105       </div>
 106       <div class="date">
 107         21st June 2012
 108       </div>
 109       <div class="body">
 110         <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
 111 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
 112 <a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
 113 fri og åpen standard</a> i henhold til
 114 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
 115 til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
 116 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
 117 gjelder Norge.  Det ser uansett ut til å være en juridisk interessant
 118 problemstilling.  Men jeg tenkte her om dagen som så, at hvis det er
 119 nødvendig, så har store aktører som
 120 <a href="http://www.nrk.no/">NRK</a> og
 121 <a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
 122 slik avtale.  Jeg har derfor sendt forespørsel til begge (for
 123 regjeringen sin del er det Departementenes Servicesenter som gjør
 124 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
 125 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
 126 av MPEG-LA.  Her er kopi av eposten jeg har sendt til
 127 <a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
 128 Forespørselen til NRK er veldig lik.</p>
 129
 130 <p><blockquote>
 131
 132 <p>Date: Tue, 19 Jun 2012 15:18:33 +0200
 133 <br>From: Petter Reinholdtsen
 134 <br>To: postmottak@dss.dep.no
 135 <br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
 136
 137 <p>Hei.  Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
 138 til avtaler rundt bruk av videoformatene MPEG og H.264.  Jeg er
 139 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
 140 eller noen som representerer MPEG-LA i Norge.</p>
 141
 142 <p>MPEG og H.264 er videoformater som brukes både til kringkasting
 143 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
 144 via Adobe Flash.  MPEG-LA, &lt;URL:
 145 <a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> &gt;, er
 146 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
 147 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
 148 bruksrett for MPEG og H.264.</p>
 149
 150 <p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
 151 videoformater, og dette ser ut til å være organisert av DSS.  Jeg
 152 antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
 153
 154 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge &lt;URL:
 155 <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
 156 &gt;:</p>
 157
 158 <p><blockquote>
 159
 160   <p>6.17. AVC DISTRIBUTION. The following notice applies to software
 161   containing AVC import and export functionality: THIS PRODUCT IS
 162   LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
 163   NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
 164   WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
 165   WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
 166   ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
 167   LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
 168   IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
 169   FROM MPEG LA L.L.C. SEE
 170   <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
 171
 172 </blockquote></p>
 173
 174 <p>Her er det kun "non-commercial" og "personal and non-commercial"
 175 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
 176
 177 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
 178 følgende klausul i følge &lt;URL:
 179 <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
 180 &gt;:</p>
 181
 182 <p><blockquote>
 183
 184   <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
 185   funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
 186   kommersiell bruk ekstra lisensiering og følgende gjelder:
 187   AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
 188   FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
 189   KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
 190   OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
 191   PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
 192   FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
 193   AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
 194   FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
 195 </blockquote></p>
 196
 197 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
 198 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
 199 til å bruke programmet/utstyret hvis en skal lage noe annet enn
 200 private filmer og i ikke-kommersiell virksomhet.</p>
 201
 202 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
 203 ikke er begrenset av de generelle bruksvilkårene som gjelder for
 204 utstyr som bruker MPEG og/eller H.264.</p>
 205 </blockquote></p>
 206
 207 <p>Nå venter jeg spent på svaret.  Jeg planlegger å blogge om svaret
 208 her.</p>
 209
 210       </div>
 211       <div class="tags">
 212
 213
 214         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>.
 215
 216
 217       </div>
 218     </div>
 219     <div class="padding"></div>
 220
 221     <div class="entry">
 222       <div class="title">
 223         <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>
 224       </div>
 225       <div class="date">
 226         26th April 2012
 227       </div>
 228       <div class="body">
 229         <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
 230 article today</a> published by Computerworld Norway, the photographer
 231 <a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
 232 that the video editor application included with
 233 <a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
 234 X</a> have some quite surprising terms of use.  The article is mostly
 235 based on the twitter message from mister Urke, stating:
 236
 237 <p><blockquote>
 238 "<a href="http://twitter.com/urke/status/194062269724897280">Drøy
 239 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
 240 kan jeg KUN bruke dem privat.</a>"
 241 </blockquote></p>
 242
 243 <p>I quickly translated it to this English message:</p>
 244
 245 <p><blockquote>
 246 "Arrogant user agreement: HTC can use MY edited videos
 247 commercially.  Although I can ONLY use them privately."
 248 </blockquote></p>
 249
 250 <p>I've been unable to find the text of the license term myself, but
 251 suspect it is a variation of the MPEG-LA terms I
 252 <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
 253 with my Canon IXUS 130</a>.  The HTC One X specification specifies that
 254 the recording format of the phone is .amr for audio and .mp3 for
 255 video.  AMR is
 256 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
 257 Multi-Rate audio codec</a> with patents which according to the
 258 Wikipedia article require an license agreement with
 259 <a href="http://www.voiceage.com/">VoiceAge</a>.  MP4 is
 260 <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
 261 H.264</a>, which according to Wikipedia require a licence agreement
 262 with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
 263
 264 <p>I know why I prefer
 265 <a href="http://www.digistan.org/open-standard:definition">free and open
 266 standards</a> also for video.</p>
 267
 268       </div>
 269       <div class="tags">
 270
 271
 272         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>.
 273
 274
 275       </div>
 276     </div>
 277     <div class="padding"></div>
 278
 279     <div class="entry">
 280       <div class="title">
 281         <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>
 282       </div>
 283       <div class="date">
 284         30th December 2010
 285       </div>
 286       <div class="body">
 287         <p>After trying to
 288 <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
 289 Ogg Theora</a> to
 290 <a href="http://www.digistan.org/open-standard:definition">the Digistan
 291 definition</a> of a free and open standard, I concluded that this need
 292 to be done for more standards and started on a framework for doing
 293 this.  As a start, I want to get the status for all the standards in
 294 the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
 295 JPEG, PNG, SVG and others.  But to be able to complete this in a
 296 reasonable time frame, I will need help.</p>
 297
 298 <p>If you want to help out with this work, please visit
 299 <a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
 300 wiki pages I have set up for this</a>, and let me know that you want
 301 to help out.  The IRC channel #nuug on irc.freenode.net is a good
 302 place to coordinate this for now, as it is the IRC channel for the
 303 NUUG association where I have created the framework (I am the leader
 304 of the Norwegian Unix User Group).</p>
 305
 306 <p>The framework is still forming, and a lot is left to do.  Do not be
 307 scared by the sketchy form of the current pages. :)</p>
 308
 309       </div>
 310       <div class="tags">
 311
 312
 313         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>.
 314
 315
 316       </div>
 317     </div>
 318     <div class="padding"></div>
 319
 320     <div class="entry">
 321       <div class="title">
 322         <a href="http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
 323       </div>
 324       <div class="date">
 325         27th December 2010
 326       </div>
 327       <div class="body">
 328         <p>One of the reasons I like the Digistan definition of
 329 "<a href="http://www.digistan.org/open-standard:definition">Free and
 330 Open Standard</a>" is that this is a new term, and thus the meaning of
 331 the term has been decided by Digistan.  The term "Open Standard" has
 332 become so misunderstood that it is no longer very useful when talking
 333 about standards.  One end up discussing which definition is the best
 334 one and with such frame the only one gaining are the proponents of
 335 de-facto standards and proprietary solutions.</p>
 336
 337 <p>But to give us an idea about the diversity of definitions of open
 338 standards, here are a few that I know about.  This list is not
 339 complete, but can be a starting point for those that want to do a
 340 complete survey.  More definitions are available on the
 341 <a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
 342 page</a>.</p>
 343
 344 <p>First off is my favourite, the definition from the European
 345 Interoperability Framework version 1.0.  Really sad to notice that BSA
 346 and others has succeeded in getting it removed from version 2.0 of the
 347 framework by stacking the committee drafting the new version with
 348 their own people.  Anyway, the definition is still available and it
 349 include the key properties needed to make sure everyone can use a
 350 specification on equal terms.</p>
 351
 352 <blockquote>
 353
 354 <p>The following are the minimal characteristics that a specification
 355 and its attendant documents must have in order to be considered an
 356 open standard:</p>
 357
 358 <ul>
 359
 360 <li>The standard is adopted and will be maintained by a not-for-profit
 361 organisation, and its ongoing development occurs on the basis of an
 362 open decision-making procedure available to all interested parties
 363 (consensus or majority decision etc.).</li>
 364
 365 <li>The standard has been published and the standard specification
 366 document is available either freely or at a nominal charge. It must be
 367 permissible to all to copy, distribute and use it for no fee or at a
 368 nominal fee.</li>
 369
 370 <li>The intellectual property - i.e. patents possibly present - of
 371 (parts of) the standard is made irrevocably available on a royalty-
 372 free basis.</li>
 373
 374 <li>There are no constraints on the re-use of the standard.</li>
 375
 376 </ul>
 377 </blockquote>
 378
 379 <p>Another one originates from my friends over at
 380 <a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
 381 support for <a href="http://www.aaben-standard.dk/">this
 382 definition</a> in 2004.  It even made it into the Danish parlament as
 383 <a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
 384 definition of a open standard</a>.  Another from a different part of
 385 the Danish government is available from the wikipedia page.</p>
 386
 387 <blockquote>
 388
 389 <p>En åben standard opfylder følgende krav:</p>
 390
 391 <ol>
 392
 393 <li>Veldokumenteret med den fuldstændige specifikation offentligt
 394 tilgængelig.</li>
 395
 396 <li>Frit implementerbar uden økonomiske, politiske eller juridiske
 397 begrænsninger på implementation og anvendelse.</li>
 398
 399 <li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
 400 "standardiseringsorganisation") via en åben proces.</li>
 401
 402 </ol>
 403
 404 </blockquote>
 405
 406 <p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
 407 definition</a> from Free Software Foundation Europe.</p>
 408
 409 <blockquote>
 410
 411 <p>An Open Standard refers to a format or protocol that is</p>
 412
 413 <ol>
 414
 415 <li>subject to full public assessment and use without constraints in a
 416 manner equally available to all parties;</li>
 417
 418 <li>without any components or extensions that have dependencies on
 419 formats or protocols that do not meet the definition of an Open
 420 Standard themselves;</li>
 421
 422 <li>free from legal or technical clauses that limit its utilisation by
 423 any party or in any business model;</li>
 424
 425 <li>managed and further developed independently of any single vendor
 426 in a process open to the equal participation of competitors and third
 427 parties;</li>
 428
 429 <li>available in multiple complete implementations by competing
 430 vendors, or as a complete implementation equally available to all
 431 parties.</li>
 432
 433 </ol>
 434
 435 </blockquote>
 436
 437 <p>A long time ago, SUN Microsystems, now bought by Oracle, created
 438 its
 439 <a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
 440 Standards Checklist</a> with a fairly detailed description.</p>
 441
 442 <blockquote>
 443 <p>Creation and Management of an Open Standard
 444
 445 <ul>
 446
 447 <li>Its development and management process must be collaborative and
 448   democratic:
 449
 450          <ul>
 451
 452          <li>Participation must be accessible to all those who wish to
 453             participate and can meet fair and reasonable criteria
 454             imposed by the organization under which it is developed
 455             and managed.</li>
 456
 457          <li>The processes must be documented and, through a known
 458             method, can be changed through input from all
 459             participants.</li>
 460
 461          <li>The process must be based on formal and binding commitments for
 462             the disclosure and licensing of intellectual property rights.</li>
 463
 464          <li>Development and management should strive for consensus,
 465             and an appeals process must be clearly outlined.</li>
 466
 467          <li>The standard specification must be open to extensive
 468             public review at least once in its life-cycle, with
 469             comments duly discussed and acted upon, if required.</li>
 470
 471          </ul>
 472
 473 </li>
 474
 475 </ul>
 476
 477 <p>Use and Licensing of an Open Standard</p>
 478 <ul>
 479
 480 <li>The standard must describe an interface, not an implementation,
 481   and the industry must be capable of creating multiple, competing
 482   implementations to the interface described in the standard without
 483   undue or restrictive constraints.  Interfaces include APIs,
 484   protocols, schemas, data formats and their encoding.</li>
 485
 486 <li> The standard must not contain any proprietary "hooks" that create
 487   a technical or economic barriers</li>
 488
 489 <li>Faithful implementations of the standard must
 490   interoperate. Interoperability means the ability of a computer
 491   program to communicate and exchange information with other computer
 492   programs and mutually to use the information which has been
 493   exchanged. This includes the ability to use, convert, or exchange
 494   file formats, protocols, schemas, interface information or
 495   conventions, so as to permit the computer program to work with other
 496   computer programs and users in all the ways in which they are
 497   intended to function.</li>
 498
 499 <li>It must be permissible for anyone to copy, distribute and read the
 500   standard for a nominal fee, or even no fee. If there is a fee, it
 501   must be low enough to not preclude widespread use.</li>
 502
 503 <li>It must be possible for anyone to obtain free (no royalties or
 504   fees; also known as "royalty free"), worldwide, non-exclusive and
 505   perpetual licenses to all essential patent claims to make, use and
 506   sell products based on the standard.  The only exceptions are
 507   terminations per the reciprocity and defensive suspension terms
 508   outlined below. Essential patent claims include pending, unpublished
 509   patents, published patents, and patent applications. The license is
 510   only for the exact scope of the standard in question.
 511
 512       <ul>
 513
 514       <li> May be conditioned only on reciprocal licenses to any of
 515         licensees' patent claims essential to practice that standard
 516         (also known as a reciprocity clause)</li>
 517
 518       <li> May be terminated as to any licensee who sues the licensor
 519         or any other licensee for infringement of patent claims
 520         essential to practice that standard (also known as a
 521         "defensive suspension" clause)</li>
 522
 523       <li> The same licensing terms are available to every potential
 524         licensor</li>
 525
 526       </ul>
 527 </li>
 528
 529 <li>The licensing terms of an open standards must not preclude
 530   implementations of that standard under open source licensing terms
 531   or restricted licensing terms</li>
 532
 533 </ul>
 534
 535 </blockquote>
 536
 537 <p>It is said that one of the nice things about standards is that
 538 there are so many of them.  As you can see, the same holds true for
 539 open standard definitions.  Most of the definitions have a lot in
 540 common, and it is not really controversial what properties a open
 541 standard should have, but the diversity of definitions have made it
 542 possible for those that want to avoid a level marked field and real
 543 competition to downplay the significance of open standards.  I hope we
 544 can turn this tide by focusing on the advantages of Free and Open
 545 Standards.</p>
 546
 547       </div>
 548       <div class="tags">
 549
 550
 551         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>.
 552
 553
 554       </div>
 555     </div>
 556     <div class="padding"></div>
 557
 558     <div class="entry">
 559       <div class="title">
 560         <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>
 561       </div>
 562       <div class="date">
 563         25th December 2010
 564       </div>
 565       <div class="body">
 566         <p><a href="http://www.digistan.org/open-standard:definition">The
 567 Digistan definition</a> of a free and open standard reads like this:</p>
 568
 569 <blockquote>
 570
 571 <p>The Digital Standards Organization defines free and open standard
 572 as follows:</p>
 573
 574 <ol>
 575
 576 <li>A free and open standard is immune to vendor capture at all stages
 577 in its life-cycle. Immunity from vendor capture makes it possible to
 578 freely use, improve upon, trust, and extend a standard over time.</li>
 579
 580 <li>The standard is adopted and will be maintained by a not-for-profit
 581 organisation, and its ongoing development occurs on the basis of an
 582 open decision-making procedure available to all interested
 583 parties.</li>
 584
 585 <li>The standard has been published and the standard specification
 586 document is available freely. It must be permissible to all to copy,
 587 distribute, and use it freely.</li>
 588
 589 <li>The patents possibly present on (parts of) the standard are made
 590 irrevocably available on a royalty-free basis.</li>
 591
 592 <li>There are no constraints on the re-use of the standard.</li>
 593
 594 </ol>
 595
 596 <p>The economic outcome of a free and open standard, which can be
 597 measured, is that it enables perfect competition between suppliers of
 598 products based on the standard.</p>
 599 </blockquote>
 600
 601 <p>For a while now I have tried to figure out of Ogg Theora is a free
 602 and open standard according to this definition.  Here is a short
 603 writeup of what I have been able to gather so far.  I brought up the
 604 topic on the Xiph advocacy mailing list
 605 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
 606 July 2009</a>, for those that want to see some background information.
 607 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
 608 the Ogg Theora specification fulfils the Digistan definition.</p>
 609
 610 <p><strong>Free from vendor capture?</strong></p>
 611
 612 <p>As far as I can see, there is no single vendor that can control the
 613 Ogg Theora specification.  It can be argued that the
 614 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
 615 given that it is a non-profit foundation with the expressed goal
 616 making free and open protocols and standards available, it is not
 617 obvious that this is a real risk.  One issue with the Xiph
 618 foundation is that its inner working (as in board member list, or who
 619 control the foundation) are not easily available on the web.  I've
 620 been unable to find out who is in the foundation board, and have not
 621 seen any accounting information documenting how money is handled nor
 622 where is is spent in the foundation.  It is thus not obvious for an
 623 external observer who control The Xiph foundation, and for all I know
 624 it is possible for a single vendor to take control over the
 625 specification.  But it seem unlikely.</p>
 626
 627 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
 628
 629 <p>Assuming that the Xiph foundation is the organisation its web pages
 630 claim it to be, this point is fulfilled.  If Xiph foundation is
 631 controlled by a single vendor, it isn't, but I have not found any
 632 documentation indicating this.</p>
 633
 634 <p>According to
 635 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
 636 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
 637 government, the Xiph foundation is a non-commercial organisation and
 638 the development process is open, transparent and non-Discrimatory.
 639 Until proven otherwise, I believe it make most sense to believe the
 640 report is correct.</p>
 641
 642 <p><strong>Specification freely available?</strong></p>
 643
 644 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
 645 container format</a> and both the
 646 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
 647 <a href="http://theora.org/doc/">Theora</a> codeces are available on
 648 the web.  This are the terms in the Vorbis and Theora specification:
 649
 650 <blockquote>
 651
 652 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
 653 specifications, whether in private, public, or corporate
 654 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
 655 the right to set the Ogg [Vorbis/Theora] specification and certify
 656 specification compliance.
 657
 658 </blockquote>
 659
 660 <p>The Ogg container format is specified in IETF
 661 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
 662 this is the term:<p>
 663
 664 <blockquote>
 665
 666 <p>This document and translations of it may be copied and furnished to
 667 others, and derivative works that comment on or otherwise explain it
 668 or assist in its implementation may be prepared, copied, published and
 669 distributed, in whole or in part, without restriction of any kind,
 670 provided that the above copyright notice and this paragraph are
 671 included on all such copies and derivative works.  However, this
 672 document itself may not be modified in any way, such as by removing
 673 the copyright notice or references to the Internet Society or other
 674 Internet organizations, except as needed for the purpose of developing
 675 Internet standards in which case the procedures for copyrights defined
 676 in the Internet Standards process must be followed, or as required to
 677 translate it into languages other than English.</p>
 678
 679 <p>The limited permissions granted above are perpetual and will not be
 680 revoked by the Internet Society or its successors or assigns.</p>
 681 </blockquote>
 682
 683 <p>All these terms seem to allow unlimited distribution and use, an
 684 this term seem to be fulfilled.  There might be a problem with the
 685 missing permission to distribute modified versions of the text, and
 686 thus reuse it in other specifications.  Not quite sure if that is a
 687 requirement for the Digistan definition.</p>
 688
 689 <p><strong>Royalty-free?</strong></p>
 690
 691 <p>There are no known patent claims requiring royalties for the Ogg
 692 Theora format.
 693 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
 694 and
 695 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
 696 Jobs</a> in Apple claim to know about some patent claims (submarine
 697 patents) against the Theora format, but no-one else seem to believe
 698 them.  Both Opera Software and the Mozilla Foundation have looked into
 699 this and decided to implement Ogg Theora support in their browsers
 700 without paying any royalties.  For now the claims from MPEG-LA and
 701 Steve Jobs seem more like FUD to scare people to use the H.264 codec
 702 than any real problem with Ogg Theora.</p>
 703
 704 <p><strong>No constraints on re-use?</strong></p>
 705
 706 <p>I am not aware of any constraints on re-use.</p>
 707
 708 <p><strong>Conclusion</strong></p>
 709
 710 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
 711 depend on the governing structure of the Xiph foundation.  Given the
 712 background report used by the Norwegian government, I believe it is
 713 safe to assume the last two requirements are fulfilled too, but it
 714 would be nice if the Xiph foundation web site made it easier to verify
 715 this.</p>
 716
 717 <p>It would be nice to see other analysis of other specifications to
 718 see if they are free and open standards.</p>
 719
 720       </div>
 721       <div class="tags">
 722
 723
 724         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>.
 725
 726
 727       </div>
 728     </div>
 729     <div class="padding"></div>
 730
 731     <div class="entry">
 732       <div class="title">
 733         <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>
 734       </div>
 735       <div class="date">
 736         25th December 2010
 737       </div>
 738       <div class="body">
 739         <p>A few days ago
 740 <a href="http://www.idg.no/computerworld/article189879.ece">an
 741 article</a> in the Norwegian Computerworld magazine about how version
 742 2.0 of
 743 <a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
 744 Interoperability Framework</a> has been successfully lobbied by the
 745 proprietary software industry to remove the focus on free software.
 746 Nothing very surprising there, given
 747 <a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
 748 reports</a> on how Microsoft and others have stacked the committees in
 749 this work.  But I find this very sad.   The definition of
 750 <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
 751 open standard from version 1</a> was very good, and something I
 752 believe should be used also in the future, alongside
 753 <a href="http://www.digistan.org/open-standard:definition">the
 754 definition from Digistan</A>.  Version 2 have removed the open
 755 standard definition from its content.</p>
 756
 757 <p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
 758 Villanueva, congressman in Peru at the time, to Microsoft as a reply
 759 to Microsofts attack on his proposal regarding the use of free software
 760 in the public sector in Peru.  As the text was not available from a
 761 few of the URLs where it used to be available, I copy it here from
 762 <a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
 763 source</a> to ensure it is available also in the future.  Some
 764 background information about that story is available in
 765 <a href="http://www.linuxjournal.com/article/6099">an article</a> from
 766 Linux Journal in 2002.</p>
 767
 768 <blockquote>
 769 <p>Lima, 8th of April, 2002<br>
 770 To: Señor JUAN ALBERTO GONZÁLEZ<br>
 771 General Manager of Microsoft Perú</p>
 772
 773 <p>Dear Sir:</p>
 774
 775 <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>
 776
 777 <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>
 778
 779 <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>
 780
 781 <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>
 782
 783 <p>
 784 <ul>
 785 <li>Free access to public information by the citizen. </li>
 786 <li>Permanence of public data. </li>
 787 <li>Security of the State and citizens.</li>
 788 </ul>
 789 </p>
 790
 791 <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>
 792
 793 <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>
 794
 795 <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>
 796
 797 <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>
 798
 799 <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>
 800
 801
 802 <p>From reading the Bill it will be clear that once passed:<br>
 803 <li>the law does not forbid the production of proprietary software</li>
 804 <li>the law does not forbid the sale of proprietary software</li>
 805 <li>the law does not specify which concrete software to use</li>
 806 <li>the law does not dictate the supplier from whom software will be bought</li>
 807 <li>the law does not limit the terms under which a software product can be licensed.</li>
 808
 809 </p>
 810
 811 <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>
 812
 813 <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>
 814
 815 <p>As for the observations you have made, we will now go on to analyze them in detail:</p>
 816
 817 <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>
 818
 819 <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>
 820
 821 <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>
 822
 823 <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>
 824
 825 <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>
 826
 827 <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>
 828
 829 <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>
 830
 831 <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>
 832
 833 <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>
 834
 835 <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>
 836
 837 <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>
 838
 839 <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>
 840
 841 <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>
 842
 843 <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>
 844
 845 <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>
 846
 847 <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>
 848
 849 <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>
 850
 851 <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>
 852
 853 <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>
 854
 855 <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>
 856
 857 <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>
 858
 859 <p>On security:</p>
 860
 861 <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>
 862
 863 <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>
 864
 865 <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>
 866
 867 <p>In respect of the guarantee:</p>
 868
 869 <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>
 870
 871 <p>On Intellectual Property:</p>
 872
 873 <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>
 874
 875 <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>
 876
 877 <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>
 878
 879 <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>
 880
 881 <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>
 882
 883 <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>
 884
 885 <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>
 886
 887 <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>
 888
 889 <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>
 890
 891 <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>
 892
 893 <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>
 894
 895 <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>
 896
 897 <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>
 898
 899 <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>
 900
 901 <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>
 902
 903 <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>
 904
 905 <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>
 906
 907 <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>
 908
 909 <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>
 910
 911 <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>
 912
 913 <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>
 914
 915 <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>
 916
 917 <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>
 918
 919 <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>
 920
 921 <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>
 922
 923 <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>
 924
 925 <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>
 926
 927 <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>
 928
 929 <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>
 930
 931 <p>Cordially,<br>
 932 DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
 933 Congressman of the Republic of Perú.</p>
 934 </blockquote>
 935
 936       </div>
 937       <div class="tags">
 938
 939
 940         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>.
 941
 942
 943       </div>
 944     </div>
 945     <div class="padding"></div>
 946
 947     <div class="entry">
 948       <div class="title">
 949         <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>
 950       </div>
 951       <div class="date">
 952         30th October 2010
 953       </div>
 954       <div class="body">
 955         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
 956 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
 957 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
 958 filmene NRK la ut ikke var tilgjengelig i et
 959 <a href="http://www.digistan.org/open-standard:definition">fritt og
 960 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
 961
 962 <p><blockquote>
 963 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
 964 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
 965 som dette, vet at det stort sett er mulig å lure ut ting med den
 966 nødvendige forkunnskapen."</p>
 967
 968 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
 969 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
 970 er å forlede leseren.</p>
 971
 972 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
 973 vil tillate streaming men ikke nedlasting meningsløs.</p>
 974
 975 <p>Anbefaler forresten å lese
 976 <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>
 977 om hva som ville være konsekvensen hvis digitale avspillingssperrer
 978 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
 979 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
 980 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
 981 opp under.</p>
 982 </blockquote></p>
 983
 984 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
 985 NRKBeta:</p>
 986
 987 <p><blockquote>
 988 <p>From: Anders Hofseth &lt;XXX@gmail.com>
 989 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
 990 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
 991 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
 992 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
 993
 994 <p>Hei Petter.
 995 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
 996 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
 997 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
 998 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
 999
1000 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
1001 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1002 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
1003
1004 <p>Med hilsen,
1005 <br>-anders</p>
1006
1007 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
1008 </blockquote></p>
1009
1010 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
1011 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
1012 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
1013 Har fjernet epostadresser og telefonnummer til de involverte, for å
1014 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
1015
1016 <p><blockquote>
1017 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
1018 <br>To: Anders Hofseth &lt;XXX@gmail.com>
1019 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
1020 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
1021 <br>        Henrik Lied &lt;XXX@gmail.com>
1022 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
1023 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
1024
1025 <p>[Anders Hofseth]
1026 <br>> Hei Petter.</p>
1027
1028 <p>Hei.</p>
1029
1030 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
1031 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
1032 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
1033 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
1034
1035 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
1036 vil nok fortsette en stund til.  :)</p>
1037
1038 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
1039 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
1040 fortsette å legge ut arkivmateriale.</p>
1041
1042 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
1043 faktum, som er at streaming er det samme som nedlasting, og at innhold
1044 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
1045 det.</p>
1046
1047 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
1048 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
1049 Det er ikke et argument som holder vann. :)</p>
1050
1051 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
1052 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
1053 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
1054
1055 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
1056 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
1057 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
1058 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
1059 skal sendes skal være uten bruksbegresninger og kan publiseres i
1060 formater som heller ikke har bruksbegresninger (bruksbegresningene til
1061 H.264 burde få varselbjellene i NRK til å ringe).</p>
1062
1063 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
1064 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
1065 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
1066
1067 <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
1068 titt på
1069 &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> >.
1070 for å se hva slags bruksbegresninger H.264 innebærer.</p>
1071
1072 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
1073 kan brukes før rettighetshaverene også innser at de er med på å skade
1074 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
1075 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
1076 langt på overtid.</p>
1077
1078 <p>> Ring meg om noe er uklart: XXX</p>
1079
1080 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
1081 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
1082 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
1083 for videre diskusjon hadde dere i mine øyne kommet fra det med
1084 ryggraden på plass.</p>
1085
1086 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
1087
1088 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
1089 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
1090 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
1091 NRK1. :)</p>
1092
1093 <p>Vennlig hilsen,
1094 <br>--
1095 <br>Petter Reinholdtsen</p>
1096
1097       </div>
1098       <div class="tags">
1099
1100
1101         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>.
1102
1103
1104       </div>
1105     </div>
1106     <div class="padding"></div>
1107
1108     <div class="entry">
1109       <div class="title">
1110         <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>
1111       </div>
1112       <div class="date">
1113          9th September 2010
1114       </div>
1115       <div class="body">
1116         <p>A few days ago I had the mixed pleasure of bying a new digital
1117 camera, a Canon IXUS 130.  It was instructive and very disturbing to
1118 be able to verify that also this camera producer have the nerve to
1119 specify how I can or can not use the videos produced with the camera.
1120 Even thought I was aware of the issue, the options with new cameras
1121 are limited and I ended up bying the camera anyway.  What is the
1122 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
1123 MPEG-LA that is the problem, and our right to record our experiences
1124 without asking for permissions that is at risk.
1125
1126 <p>On page 27 of the Danish instruction manual, this section is
1127 written:</p>
1128
1129 <blockquote>
1130 <p>This product is licensed under AT&T patents for the MPEG-4 standard
1131 and may be used for encoding MPEG-4 compliant video and/or decoding
1132 MPEG-4 compliant video that was encoded only (1) for a personal and
1133 non-commercial purpose or (2) by a video provider licensed under the
1134 AT&T patents to provide MPEG-4 compliant video.</p>
1135
1136 <p>No license is granted or implied for any other use for MPEG-4
1137 standard.</p>
1138 </blockquote>
1139
1140 <p>In short, the camera producer have chosen to use technology
1141 (MPEG-4/H.264) that is only provided if I used it for personal and
1142 non-commercial purposes, or ask for permission from the organisations
1143 holding the knowledge monopoly (patent) for technology used.</p>
1144
1145 <p>This issue has been brewing for a while, and I recommend you to
1146 read
1147 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
1148 Our Civilization's Video Art and Culture is Threatened by the
1149 MPEG-LA</a>" by Eugenia Loli-Queru and
1150 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
1151 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
1152 the issue.  The solution is to support the
1153 <a href="http://www.digistan.org/open-standard:definition">free and
1154 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
1155 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
1156
1157       </div>
1158       <div class="tags">
1159
1160
1161         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>.
1162
1163
1164       </div>
1165     </div>
1166     <div class="padding"></div>
1167
1168     <div class="entry">
1169       <div class="title">
1170         <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>
1171       </div>
1172       <div class="date">
1173         31st January 2009
1174       </div>
1175       <div class="body">
1176         <p>Det er mange ulike definisjoner om hva en åpen standard er for noe,
1177 og NUUG hadde <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">en
1178 pressemelding om dette sommeren 2005</a>.  Der ble definisjonen til
1179 <a href="http://www.aaben-standard.dk/">DKUUG</a>,
1180 <a href="http://europa.eu.int/idabc/servlets/Doc?id=19529">EU-kommissionens
1181 European Interoperability Framework ( side 9)</a> og
1182 <a href="http://www.teknologiradet.no/files/7polert_copy.htm">teknologirådet</a> omtalt.</p>
1183
1184 <p>Siden den gang har regjeringens standardiseringsråd dukket opp, og de
1185 ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
1186 <a href="http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=476407">sin
1187 arbeidsmetodikk</a>.  Personlig synes jeg det er en god ide, da
1188 kravene som stilles der gjør at alle markedsaktører får like vilkår,
1189 noe som kommer kundene til gode ved hjelp av økt konkurranse.</p>
1190
1191 <p>I sommer kom det en ny definisjon på banen.
1192 <a href="http://www.digistan.org/">Digistan</a> lanserte
1193 <a href="http://www.digistan.org/open-standard:definition">en
1194 definisjon på en fri og åpen standard</a>.  Jeg liker måten de bryter
1195 ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
1196 ved å legge på et ord og poengtere at en standard som er både åpen og
1197 fri har noen spesielle krav.  Her er den definisjonen etter rask
1198 oversettelse fra engelsk til norsk av meg:</p>
1199
1200 <blockquote>
1201 <p><strong>Definisjonen av en fri og åpen standard</strong></p>
1202
1203 <p>Den digitale standardorganisasjonen definierer fri og åpen standard
1204 som følger:</p>
1205 <ul>
1206 <li>En fri og åpen standard er immun for leverandørinnlåsing i alle
1207 stadier av dens livssyklus.  Immuniteten fra leverandørinnlåsing gjør
1208 det mulig å fritt bruke, forbedre, stole på og utvide en standard over
1209 tid.</li>
1210 <li>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
1211 organisasjon, og dens pågående utvikling gjøres med en åpen
1212 beslutningsprosedyre som er tilgjengelig for alle som er interessert i
1213 å delta.</li>
1214 <li>Standarden er publisert og spesifikasjonsdokumentet er fritt
1215 tilgjengelig.  Det må være tillatt for alle å kopiere, distribuere og
1216 bruke den uten begresninger.</li>
1217 <li>Patentene som muligens gjelder (deler av) standarden er gjort
1218 ugjenkallelig tilgjengelig uten krav om betaling.</li>
1219 <li>Det er ingen begresninger i gjenbruk av standarden.</li>
1220 </ul>
1221 <p>Det økonomiske resultatet av en fri og åpen standard, som kan
1222 måles, er at det muliggjør perfekt konkurranse mellom leverandører av
1223 produkter basert på standarden.</p>
1224 </blockquote>
1225
1226 <p>(Tar gjerne imot forbedringer av oversettelsen.)</p>
1227
1228       </div>
1229       <div class="tags">
1230
1231
1232         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>.
1233
1234
1235       </div>
1236     </div>
1237     <div class="padding"></div>
1238
1239     <p style="text-align: right;"><a href="digistan.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
1240     <div id="sidebar">
1241
1242
1243
1244 <h2>Archive</h2>
1245 <ul>
1246
1247 <li>2014
1248 <ul>
1249
1250 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1251
1252 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1253
1254 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1255
1256 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (3)</a></li>
1257
1258 </ul></li>
1259
1260 <li>2013
1261 <ul>
1262
1263 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1264
1265 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1266
1267 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1268
1269 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1270
1271 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1272
1273 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1274
1275 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1276
1277 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1278
1279 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1280
1281 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1282
1283 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1284
1285 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1286
1287 </ul></li>
1288
1289 <li>2012
1290 <ul>
1291
1292 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1293
1294 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1295
1296 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1297
1298 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1299
1300 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1301
1302 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1303
1304 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1305
1306 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1307
1308 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1309
1310 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1311
1312 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1313
1314 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1315
1316 </ul></li>
1317
1318 <li>2011
1319 <ul>
1320
1321 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1322
1323 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1324
1325 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1326
1327 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1328
1329 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1330
1331 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1332
1333 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1334
1335 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1336
1337 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1338
1339 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1340
1341 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1342
1343 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1344
1345 </ul></li>
1346
1347 <li>2010
1348 <ul>
1349
1350 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1351
1352 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1353
1354 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1355
1356 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1357
1358 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1359
1360 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1361
1362 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1363
1364 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1365
1366 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1367
1368 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1369
1370 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1371
1372 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1373
1374 </ul></li>
1375
1376 <li>2009
1377 <ul>
1378
1379 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1380
1381 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1382
1383 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1384
1385 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1386
1387 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1388
1389 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1390
1391 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1392
1393 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1394
1395 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1396
1397 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1398
1399 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1400
1401 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1402
1403 </ul></li>
1404
1405 <li>2008
1406 <ul>
1407
1408 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1409
1410 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1411
1412 </ul></li>
1413
1414 </ul>
1415
1416
1417
1418 <h2>Tags</h2>
1419 <ul>
1420
1421  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1422
1423  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1424
1425  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1426
1427  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1428
1429  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1430
1431  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
1432
1433  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1434
1435  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1436
1437  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (96)</a></li>
1438
1439  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (146)</a></li>
1440
1441  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1442
1443  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
1444
1445  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1446
1447  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1448
1449  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (243)</a></li>
1450
1451  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1452
1453  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1454
1455  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1456
1457  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (7)</a></li>
1458
1459  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1460
1461  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (40)</a></li>
1462
1463  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1464
1465  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1466
1467  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1468
1469  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
1470
1471  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1472
1473  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1474
1475  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (26)</a></li>
1476
1477  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (244)</a></li>
1478
1479  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (162)</a></li>
1480
1481  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
1482
1483  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1484
1485  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (46)</a></li>
1486
1487  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (72)</a></li>
1488
1489  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1490
1491  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1492
1493  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1494
1495  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1496
1497  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1498
1499  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1500
1501  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1502
1503  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1504
1505  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (39)</a></li>
1506
1507  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1508
1509  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1510
1511  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1512
1513  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1514
1515  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1516
1517  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (24)</a></li>
1518
1519  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1520
1521  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1522
1523  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (40)</a></li>
1524
1525  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1526
1527  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (29)</a></li>
1528
1529 </ul>
1530
1531
1532     </div>
1533     <p style="text-align: right">
1534  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1535 </p>
1536
1537   </body>
1538 </html>