blog/tags/standard/index.html

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