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