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