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/Why_is_your_site_not_using_Content_Security_Policy___CSP_.html">Why is your site not using Content Security Policy / CSP?</a>
  26       </div>
  27       <div class="date">
  28          9th December 2018
  29       </div>
  30       <div class="body">
  31         <p>Yesterday, I had the pleasure of watching on Frikanalen the OWASP
  32 talk by Scott Helme titled
  33 "<a href="https://frikanalen.no/video/626080/">What We’ve Learned From
  34 Billions of Security Reports</a>".  I had not heard of the
  35 <a href="https://en.wikipedia.org/wiki/Content_Security_Policy">Content
  36 Security Policy standard</a> nor its ability to "call home" when a
  37 browser detect a policy breach (I do not follow web page design
  38 development much these days), and found the talk very illuminating.</p>
  39
  40 <p>The mechanism allow a web site owner to use HTTP headers to tell
  41 visitors web browser which sources (internal and external) are allowed to
  42 be used on the web site.  Thus it become possible to enforce a "only
  43 local content" policy despite web designers urge to fetch programs
  44 from random sites on the Internet, like the one
  45 <a href="https://securityaffairs.co/wordpress/68966/hacking/browsealoud-plugin-hack.html">enabling
  46 the attack</a> reported by Scott Helme earlier this year.</p>
  47
  48 <p>Using CSP seem like an obvious thing for a site admin to implement
  49 to take some control over the information leak that occur when
  50 external sources are used to render web pages, it is a mystery more
  51 sites are not using CSP?  It is being
  52 <a href="https://www.w3.org/TR/CSP/">standardized under W3C</a> these
  53 days, and is supposed by most web browsers</p>
  54
  55 <p>I managed to find <a href="https://github.com/mozilla/django-csp">a
  56 Django middleware for implementing CSP</a> and was happy to discover
  57 it was already in Debian.  I plan to use it to add CSP support to the
  58 Frikanalen web site soon.</p>
  59
  60 <p>As usual, if you use Bitcoin and want to show your support of my
  61 activities, please send Bitcoin donations to my address
  62 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  63
  64       </div>
  65       <div class="tags">
  66
  67
  68         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/web">web</a>.
  69
  70
  71       </div>
  72     </div>
  73     <div class="padding"></div>
  74
  75     <div class="entry">
  76       <div class="title">
  77         <a href="http://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html">Time for an official MIME type for patches?</a>
  78       </div>
  79       <div class="date">
  80          1st November 2018
  81       </div>
  82       <div class="body">
  83         <p>As part of my involvement in
  84 <a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core">the Nikita
  85 archive API project</a>, I've been importing a fairly large lump of
  86 emails into a test instance of the archive to see how well this would
  87 go.  I picked a subset of <a href="https://notmuchmail.org/">my
  88 notmuch email database</a>, all public emails sent to me via
  89 @lists.debian.org, giving me a set of around 216 000 emails to import.
  90 In the process, I had a look at the various attachments included in
  91 these emails, to figure out what to do with attachments, and noticed
  92 that one of the most common attachment formats do not have
  93 <a href="https://www.iana.org/assignments/media-types/media-types.xhtml">an
  94 official MIME type</a> registered with IANA/IETF.  The output from
  95 diff, ie the input for patch, is on the top 10 list of formats
  96 included in these emails.  At the moment people seem to use either
  97 text/x-patch or text/x-diff, but neither is officially registered.  It
  98 would be better if one official MIME type were registered and used
  99 everywhere.</p>
 100
 101 <p>To try to get one official MIME type for these files, I've brought
 102 up the topic on
 103 <a href="https://www.ietf.org/mailman/listinfo/media-types">the
 104 media-types mailing list</a>.  If you are interested in discussion
 105 which MIME type to use as the official for patch files, or involved in
 106 making software using a MIME type for patches, perhaps you would like
 107 to join the discussion?</p>
 108
 109 <p>As usual, if you use Bitcoin and want to show your support of my
 110 activities, please send Bitcoin donations to my address
 111 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 112
 113       </div>
 114       <div class="tags">
 115
 116
 117         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/standard">standard</a>.
 118
 119
 120       </div>
 121     </div>
 122     <div class="padding"></div>
 123
 124     <div class="entry">
 125       <div class="title">
 126         <a href="http://people.skolelinux.org/pere/blog/Release_0_2_of_free_software_archive_system_Nikita_announced.html">Release 0.2 of free software archive system Nikita announced</a>
 127       </div>
 128       <div class="date">
 129         18th October 2018
 130       </div>
 131       <div class="body">
 132         <p>This morning, the new release of the
 133 <a href="https://gitlab.com/OsloMet-ABI/nikita-noark5-core/">Nikita
 134 Noark 5 core project</a> was
 135 <a href="https://lists.nuug.no/pipermail/nikita-noark/2018-October/000406.html">announced
 136 on the project mailing list</a>.  The free software solution is an
 137 implementation of the Norwegian archive standard Noark 5 used by
 138 government offices in Norway.  These were the changes in version 0.2
 139 since version 0.1.1 (from NEWS.md):
 140
 141 <ul>
 142   <li>Fix typos in REL names</li>
 143   <li>Tidy up error message reporting</li>
 144   <li>Fix issue where we used Integer.valueOf(), not Integer.getInteger()</li>
 145   <li>Change some String handling to StringBuffer</li>
 146   <li>Fix error reporting</li>
 147   <li>Code tidy-up</li>
 148   <li>Fix issue using static non-synchronized SimpleDateFormat to avoid
 149       race conditions</li>
 150   <li>Fix problem where deserialisers were treating integers as strings</li>
 151   <li>Update methods to make them null-safe</li>
 152   <li>Fix many issues reported by coverity</li>
 153   <li>Improve equals(), compareTo() and hash() in domain model</li>
 154   <li>Improvements to the domain model for metadata classes</li>
 155   <li>Fix CORS issues when downloading document</li>
 156   <li>Implementation of case-handling with registryEntry and document upload</li>
 157   <li>Better support in Javascript for OPTIONS</li>
 158   <li>Adding concept description of mail integration</li>
 159   <li>Improve setting of default values for GET on ny-journalpost</li>
 160   <li>Better handling of required values during deserialisation </li>
 161   <li>Changed tilknyttetDato (M620) from date to dateTime</li>
 162   <li>Corrected some opprettetDato (M600) (de)serialisation errors.</li>
 163   <li>Improve parse error reporting.</li>
 164   <li>Started on OData search and filtering.</li>
 165   <li>Added Contributor Covenant Code of Conduct to project.</li>
 166   <li>Moved repository and project from Github to Gitlab.</li>
 167   <li>Restructured repository, moved code into src/ and web/.</li>
 168   <li>Updated code to use Spring Boot version 2.</li>
 169   <li>Added support for OAuth2 authentication.</li>
 170   <li>Fixed several bugs discovered by Coverity.</li>
 171   <li>Corrected handling of date/datetime fields.</li>
 172   <li>Improved error reporting when rejecting during deserializatoin.</li>
 173   <li>Adjusted default values provided for ny-arkivdel, ny-mappe,
 174    ny-saksmappe, ny-journalpost and ny-dokumentbeskrivelse.</li>
 175   <li>Several fixes for korrespondansepart*.</li>
 176   <li>Updated web GUI:
 177      <ul>
 178        <li>Now handle both file upload and download.</li>
 179        <li>Uses new OAuth2 authentication for login.</li>
 180        <li>Forms now fetches default values from API using GET.</li>
 181        <li>Added RFC 822 (email), TIFF and JPEG to list of possible file formats.</li>
 182      </ul></li>
 183 </ul>
 184
 185 <p>The changes and improvements are extensive.  Running diffstat on
 186 the changes between git tab 0.1.1 and 0.2 show 1098 files changed,
 187 108666 insertions(+), 54066 deletions(-).</p>
 188
 189 <p>If free and open standardized archiving API sound interesting to
 190 you, please contact us on IRC
 191 (<a href="irc://irc.freenode.net/%23nikita">#nikita on
 192 irc.freenode.net</a>) or email
 193 (<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
 194 mailing list</a>).</p>
 195
 196 <p>As usual, if you use Bitcoin and want to show your support of my
 197 activities, please send Bitcoin donations to my address
 198 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 199
 200       </div>
 201       <div class="tags">
 202
 203
 204         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/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 205
 206
 207       </div>
 208     </div>
 209     <div class="padding"></div>
 210
 211     <div class="entry">
 212       <div class="title">
 213         <a href="http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html">Release 0.1.1 of free software archive system Nikita announced</a>
 214       </div>
 215       <div class="date">
 216         10th June 2017
 217       </div>
 218       <div class="body">
 219         <p>I am very happy to report that the
 220 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita Noark 5
 221 core project</a> tagged its second release today.  The free software
 222 solution is an implementation of the Norwegian archive standard Noark
 223 5 used by government offices in Norway.  These were the changes in
 224 version 0.1.1 since version 0.1.0 (from NEWS.md):
 225
 226 <ul>
 227
 228  <li>Continued work on the angularjs GUI, including document upload.</li>
 229  <li>Implemented correspondencepartPerson, correspondencepartUnit and
 230    correspondencepartInternal</li>
 231  <li>Applied for coverity coverage and started submitting code on
 232    regualr basis.</li>
 233  <li>Started fixing bugs reported by coverity</li>
 234  <li>Corrected and completed HATEOAS links to make sure entire API is
 235    available via URLs in _links.</li>
 236  <li>Corrected all relation URLs to use trailing slash.</li>
 237  <li>Add initial support for storing data in ElasticSearch.</li>
 238  <li>Now able to receive and store uploaded files in the archive.</li>
 239  <li>Changed JSON output for object lists to have relations in _links.</li>
 240  <li>Improve JSON output for empty object lists.</li>
 241  <li>Now uses correct MIME type application/vnd.noark5-v4+json.</li>
 242  <li>Added support for docker container images.</li>
 243  <li>Added simple API browser implemented in JavaScript/Angular.</li>
 244  <li>Started on archive client implemented in JavaScript/Angular.</li>
 245  <li>Started on prototype to show the public mail journal.</li>
 246  <li>Improved performance by disabling Sprint FileWatcher.</li>
 247  <li>Added support for 'arkivskaper', 'saksmappe' and 'journalpost'.</li>
 248  <li>Added support for some metadata codelists.</li>
 249  <li>Added support for Cross-origin resource sharing (CORS).</li>
 250  <li>Changed login method from Basic Auth to JSON Web Token (RFC 7519)
 251    style.</li>
 252  <li>Added support for GET-ing ny-* URLs.</li>
 253  <li>Added support for modifying entities using PUT and eTag.</li>
 254  <li>Added support for returning XML output on request.</li>
 255  <li>Removed support for English field and class names, limiting ourself
 256    to the official names.</li>
 257  <li>...</li>
 258
 259 </ul>
 260
 261 <p>If this sound interesting to you, please contact us on IRC (#nikita
 262 on irc.freenode.net) or email
 263 (<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
 264 mailing list).</p>
 265
 266       </div>
 267       <div class="tags">
 268
 269
 270         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/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 271
 272
 273       </div>
 274     </div>
 275     <div class="padding"></div>
 276
 277     <div class="entry">
 278       <div class="title">
 279         <a href="http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html">Idea for storing trusted timestamps in a Noark 5 archive</a>
 280       </div>
 281       <div class="date">
 282          7th June 2017
 283       </div>
 284       <div class="body">
 285         <p><em>This is a copy of
 286 <a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an
 287 email I posted to the nikita-noark mailing list</a>.  Please follow up
 288 there if you would like to discuss this topic.  The background is that
 289 we are making a free software archive system based on the Norwegian
 290 <a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark
 291 5 standard</a> for government archives.</em></p>
 292
 293 <p>I've been wondering a bit lately how trusted timestamps could be
 294 stored in Noark 5.
 295 <a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted
 296 timestamps</a> can be used to verify that some information
 297 (document/file/checksum/metadata) have not been changed since a
 298 specific time in the past.  This is useful to verify the integrity of
 299 the documents in the archive.</p>
 300
 301 <p>Then it occured to me, perhaps the trusted timestamps could be
 302 stored as dokument variants (ie dokumentobjekt referered to from
 303 dokumentbeskrivelse) with the filename set to the hash it is
 304 stamping?</p>
 305
 306 <p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt",
 307 a new dokumentobjekt is associated with "dokumentbeskrivelse" with the
 308 same attributes as the stamped dokumentobjekt except these
 309 attributes:</p>
 310
 311 <ul>
 312
 313 <li>format -> "RFC3161"
 314 <li>mimeType -> "application/timestamp-reply"
 315 <li>formatDetaljer -> "&lt;source URL for timestamp service&gt;"
 316 <li>filenavn -> "&lt;sjekksum&gt;.tsr"
 317
 318 </ul>
 319
 320 <p>This assume a service following
 321 <a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> is
 322 used, which specifiy the given MIME type for replies and the .tsr file
 323 ending for the content of such trusted timestamp.  As far as I can
 324 tell from the Noark 5 specifications, it is OK to have several
 325 variants/renderings of a dokument attached to a given
 326 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 327 some of these variants represent crypto-signatures useful for
 328 verifying the document integrity instead of representing the dokument
 329 itself.</p>
 330
 331 <p>Using the source of the service in formatDetaljer allow several
 332 timestamping services to be used.  This is useful to spread the risk
 333 of key compromise over several organisations.  It would only be a
 334 problem to trust the timestamps if all of the organisations are
 335 compromised.</p>
 336
 337 <p>The following oneliner on Linux can be used to generate the tsr
 338 file.  $input is the path to the file to checksum, and $sha256 is the
 339 SHA-256 checksum of the file (ie the "<sjekksum>.tsr" value mentioned
 340 above).</p>
 341
 342 <p><blockquote><pre>
 343 openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \
 344   | curl -s -H "Content-Type: application/timestamp-query" \
 345       --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr
 346 </pre></blockquote></p>
 347
 348 <p>To verify the timestamp, you first need to download the public key
 349 of the trusted timestamp service, for example using this command:</p>
 350
 351 <p><blockquote><pre>
 352 wget -O ca-cert.txt \
 353   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 354 </pre></blockquote></p>
 355
 356 <p>Note, the public key should be stored alongside the timestamps in
 357 the archive to make sure it is also available 100 years from now.  It
 358 is probably a good idea to standardise how and were to store such
 359 public keys, to make it easier to find for those trying to verify
 360 documents 100 or 1000 years from now. :)</p>
 361
 362 <p>The verification itself is a simple openssl command:</p>
 363
 364 <p><blockquote><pre>
 365 openssl ts -verify -data $inputfile -in $sha256.tsr \
 366   -CAfile ca-cert.txt -text
 367 </pre></blockquote></p>
 368
 369 <p>Is there any reason this approach would not work?  Is it somehow against
 370 the Noark 5 specification?</p>
 371
 372       </div>
 373       <div class="tags">
 374
 375
 376         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 377
 378
 379       </div>
 380     </div>
 381     <div class="padding"></div>
 382
 383     <div class="entry">
 384       <div class="title">
 385         <a href="http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html">Epost inn som arkivformat i Riksarkivarens forskrift?</a>
 386       </div>
 387       <div class="date">
 388         27th April 2017
 389       </div>
 390       <div class="body">
 391         <p>I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
 392 sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
 393 som går ut på søndag.  Denne forskriften er det som lister opp hvilke
 394 formater det er greit å arkivere i
 395 <a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark
 396 5-løsninger</a> i Norge.</p>
 397
 398 <p>Jeg fant høringsdokumentene hos
 399 <a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk
 400 Arkivråd</a> etter å ha blitt tipset på epostlisten til
 401 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri
 402 programvareprosjektet Nikita Noark5-Core</a>, som lager et Noark 5
 403 Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
 404 være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
 405 god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
 406 at standard epost ikke er på listen over godkjente formater som kan
 407 arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
 408 forsøke å gjøre noe med det.  Jeg holder på med
 409 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen
 410 høringsuttalelse</a>, og lurer på om andre er interessert i å støtte
 411 forslaget om å tillate arkivering av epost som epost i arkivet.</p>
 412
 413 <p>Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
 414 kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
 415 ikke det trengs så mye.  Her et kort forslag til tekst:</p>
 416
 417 <p><blockquote>
 418
 419   <p>Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
 420   2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
 421   revisjon av Forskrift om utfyllende tekniske og arkivfaglige
 422   bestemmelser om behandling av offentlige arkiver (Riksarkivarens
 423   forskrift).</p>
 424
 425   <p>Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
 426   foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
 427   RFC 5322,
 428   <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. bør
 429   inn som godkjent dokumentformat.  Vi foreslår at forskriftens
 430   oversikt over godkjente dokumentformater ved innlevering i § 5-16
 431   endres til å ta med Internett-e-post.</p>
 432
 433 </blockquote></p>
 434
 435 <p>Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
 436 epost kan lagres i en Noark 5-struktur, og holder på å skrive et
 437 forslag om hvordan dette kan gjøres som vil bli sendt over til
 438 arkivverket så snart det er ferdig.  De som er interesserte kan
 439 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge
 440 fremdriften på web</a>.</p>
 441
 442 <p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
 443   <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt
 444   inn av foreningen NUUG</a>.</p>
 445
 446       </div>
 447       <div class="tags">
 448
 449
 450         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 451
 452
 453       </div>
 454     </div>
 455     <div class="padding"></div>
 456
 457     <div class="entry">
 458       <div class="title">
 459         <a href="http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html">Free software archive system Nikita now able to store documents</a>
 460       </div>
 461       <div class="date">
 462         19th March 2017
 463       </div>
 464       <div class="body">
 465         <p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
 466 Noark 5 core project</a> is implementing the Norwegian standard for
 467 keeping an electronic archive of government documents.
 468 <a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
 469 Noark 5 standard</a> document the requirement for data systems used by
 470 the archives in the Norwegian government, and the Noark 5 web interface
 471 specification document a REST web service for storing, searching and
 472 retrieving documents and metadata in such archive.  I've been involved
 473 in the project since a few weeks before Christmas, when the Norwegian
 474 Unix User Group
 475 <a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
 476 it supported the project</a>.  I believe this is an important project,
 477 and hope it can make it possible for the government archives in the
 478 future to use free software to keep the archives we citizens depend
 479 on.  But as I do not hold such archive myself, personally my first use
 480 case is to store and analyse public mail journal metadata published
 481 from the government.  I find it useful to have a clear use case in
 482 mind when developing, to make sure the system scratches one of my
 483 itches.</p>
 484
 485 <p>If you would like to help make sure there is a free software
 486 alternatives for the archives, please join our IRC channel
 487 (<a href="irc://irc.freenode.net/%23nikita">#nikita on
 488 irc.freenode.net</a>) and
 489 <a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
 490 project mailing list</a>.</p>
 491
 492 <p>When I got involved, the web service could store metadata about
 493 documents.  But a few weeks ago, a new milestone was reached when it
 494 became possible to store full text documents too.  Yesterday, I
 495 completed an implementation of a command line tool
 496 <tt>archive-pdf</tt> to upload a PDF file to the archive using this
 497 API.  The tool is very simple at the moment, and find existing
 498 <a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, series and
 499 files while asking the user to select which one to use if more than
 500 one exist.  Once a file is identified, the PDF is associated with the
 501 file and uploaded, using the title extracted from the PDF itself.  The
 502 process is fairly similar to visiting the archive, opening a cabinet,
 503 locating a file and storing a piece of paper in the archive.  Here is
 504 a test run directly after populating the database with test data using
 505 our API tester:</p>
 506
 507 <p><blockquote><pre>
 508 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
 509 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
 510 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
 511
 512  0 - Title of the test case file created 2017-03-18T23:49:32.103446
 513  1 - Title of the test file created 2017-03-18T23:49:32.103446
 514 Select which mappe you want (or search term): 0
 515 Uploading mangelmelding/mangler.pdf
 516   PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
 517   File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
 518 ~/src//noark5-tester$
 519 </pre></blockquote></p>
 520
 521 <p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
 522 one option, while the user need to choose which file (mappe) to use
 523 among the two created by the API tester.  The <tt>archive-pdf</tt>
 524 tool can be found in the git repository for the API tester.</p>
 525
 526 <p>In the project, I have been mostly working on
 527 <a href="https://github.com/petterreinholdtsen/noark5-tester">the API
 528 tester</a> so far, while getting to know the code base.  The API
 529 tester currently use
 530 <a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
 531 to traverse the entire exposed service API and verify that the exposed
 532 operations and objects match the specification, as well as trying to
 533 create objects holding metadata and uploading a simple XML file to
 534 store.  The tester has proved very useful for finding flaws in our
 535 implementation, as well as flaws in the reference site and the
 536 specification.</p>
 537
 538 <p>The test document I uploaded is a summary of all the specification
 539 defects we have collected so far while implementing the web service.
 540 There are several unclear and conflicting parts of the specification,
 541 and we have
 542 <a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
 543 writing down</a> the questions we get from implementing it.  We use a
 544 format inspired by how <a href="http://www.opengroup.org/austin/">The
 545 Austin Group</a> collect defect reports for the POSIX standard with
 546 <a href="http://www.opengroup.org/austin/mantis.html">their
 547 instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md">request for a procedure for submitting defect reports</a> :).
 548
 549 <p>The Nikita project is implemented using Java and Spring, and is
 550 fairly easy to get up and running using Docker containers for those
 551 that want to test the current code base.  The API tester is
 552 implemented in Python.</p>
 553
 554       </div>
 555       <div class="tags">
 556
 557
 558         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/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 559
 560
 561       </div>
 562     </div>
 563     <div class="padding"></div>
 564
 565     <div class="entry">
 566       <div class="title">
 567         <a href="http://people.skolelinux.org/pere/blog/Detect_OOXML_files_with_undefined_behaviour_.html">Detect OOXML files with undefined behaviour?</a>
 568       </div>
 569       <div class="date">
 570         21st February 2017
 571       </div>
 572       <div class="body">
 573         <p>I just noticed
 574 <a href="http://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">the
 575 new Norwegian proposal for archiving rules in the goverment</a> list
 576 <a href="http://www.ecma-international.org/publications/standards/Ecma-376.htm">ECMA-376</a>
 577 / ISO/IEC 29500 (aka OOXML) as valid formats to put in long term
 578 storage.  Luckily such files will only be accepted based on
 579 pre-approval from the National Archive.  Allowing OOXML files to be
 580 used for long term storage might seem like a good idea as long as we
 581 forget that there are plenty of ways for a "valid" OOXML document to
 582 have content with no defined interpretation in the standard, which
 583 lead to a question and an idea.</p>
 584
 585 <p>Is there any tool to detect if a OOXML document depend on such
 586 undefined behaviour?  It would be useful for the National Archive (and
 587 anyone else interested in verifying that a document is well defined)
 588 to have such tool available when considering to approve the use of
 589 OOXML.  I'm aware of the
 590 <a href="https://github.com/arlm/officeotron/">officeotron OOXML
 591 validator</a>, but do not know how complete it is nor if it will
 592 report use of undefined behaviour.  Are there other similar tools
 593 available?  Please send me an email if you know of any such tool.</p>
 594
 595       </div>
 596       <div class="tags">
 597
 598
 599         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>.
 600
 601
 602       </div>
 603     </div>
 604     <div class="padding"></div>
 605
 606     <div class="entry">
 607       <div class="title">
 608         <a href="http://people.skolelinux.org/pere/blog/Introducing_ical_archiver_to_split_out_old_iCalendar_entries.html">Introducing ical-archiver to split out old iCalendar entries</a>
 609       </div>
 610       <div class="date">
 611          4th January 2017
 612       </div>
 613       <div class="body">
 614         <p>Do you have a large <a href="https://icalendar.org/">iCalendar</a>
 615 file with lots of old entries, and would like to archive them to save
 616 space and resources?  At least those of us using KOrganizer know that
 617 turning on and off an event set become slower and slower the more
 618 entries are in the set.  While working on migrating our calendars to a
 619 <a href="http://radicale.org/">Radicale CalDAV server</a> on our
 620 <a href="https://freedomboxfoundation.org/">Freedombox server</a/>, my
 621 loved one wondered if I could find a way to split up the calendar file
 622 she had in KOrganizer, and I set out to write a tool.  I spent a few
 623 days writing and polishing the system, and it is now ready for general
 624 consumption.  The
 625 <a href="https://github.com/petterreinholdtsen/ical-archiver">code for
 626 ical-archiver</a> is publicly available from a git repository on
 627 github.  The system is written in Python and depend on
 628 <a href="http://eventable.github.io/vobject/">the vobject Python
 629 module</a>.</p>
 630
 631 <p>To use it, locate the iCalendar file you want to operate on and
 632 give it as an argument to the ical-archiver script.  This will
 633 generate a set of new files, one file per component type per year for
 634 all components expiring more than two years in the past.  The vevent,
 635 vtodo and vjournal entries are handled by the script.  The remaining
 636 entries are stored in a 'remaining' file.</p>
 637
 638 <p>This is what a test run can look like:
 639
 640 <p><pre>
 641 % ical-archiver t/2004-2016.ics
 642 Found 3612 vevents
 643 Found 6 vtodos
 644 Found 2 vjournals
 645 Writing t/2004-2016.ics-subset-vevent-2004.ics
 646 Writing t/2004-2016.ics-subset-vevent-2005.ics
 647 Writing t/2004-2016.ics-subset-vevent-2006.ics
 648 Writing t/2004-2016.ics-subset-vevent-2007.ics
 649 Writing t/2004-2016.ics-subset-vevent-2008.ics
 650 Writing t/2004-2016.ics-subset-vevent-2009.ics
 651 Writing t/2004-2016.ics-subset-vevent-2010.ics
 652 Writing t/2004-2016.ics-subset-vevent-2011.ics
 653 Writing t/2004-2016.ics-subset-vevent-2012.ics
 654 Writing t/2004-2016.ics-subset-vevent-2013.ics
 655 Writing t/2004-2016.ics-subset-vevent-2014.ics
 656 Writing t/2004-2016.ics-subset-vjournal-2007.ics
 657 Writing t/2004-2016.ics-subset-vjournal-2011.ics
 658 Writing t/2004-2016.ics-subset-vtodo-2012.ics
 659 Writing t/2004-2016.ics-remaining.ics
 660 %
 661 </pre></p>
 662
 663 <p>As you can see, the original file is untouched and new files are
 664 written with names derived from the original file.  If you are happy
 665 with their content, the *-remaining.ics file can replace the original
 666 the the others can be archived or imported as historical calendar
 667 collections.</p>
 668
 669 <p>The script should probably be improved a bit.  The error handling
 670 when discovering broken entries is not good, and I am not sure yet if
 671 it make sense to split different entry types into separate files or
 672 not.  The program is thus likely to change.  If you find it
 673 interesting, please get in touch. :)</p>
 674
 675 <p>As usual, if you use Bitcoin and want to show your support of my
 676 activities, please send Bitcoin donations to my address
 677 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 678
 679       </div>
 680       <div class="tags">
 681
 682
 683         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>.
 684
 685
 686       </div>
 687     </div>
 688     <div class="padding"></div>
 689
 690     <div class="entry">
 691       <div class="title">
 692         <a href="http://people.skolelinux.org/pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html">UsingQR - "Electronic" paper invoices using JSON and QR codes</a>
 693       </div>
 694       <div class="date">
 695         19th March 2016
 696       </div>
 697       <div class="body">
 698         <p>Back in 2013 I proposed
 699 <a href="http://people.skolelinux.org/pere/blog/_Electronic__paper_invoices___using_vCard_in_a_QR_code.html">a
 700 way to make paper and PDF invoices easier to process electronically by
 701 adding a QR code with the key information about the invoice</a>.  I
 702 suggested using vCard field definition, to get some standard format
 703 for name and address, but any format would work.  I did not do
 704 anything about the proposal, but hoped someone one day would make
 705 something like it.  It would make it possible to efficiently send
 706 machine readable invoices directly between seller and buyer.</p>
 707
 708 <p>This was the background when I came across a proposal and
 709 specification from the web based accounting and invoicing supplier
 710 <a href="http://www.visma.com/">Visma</a> in Sweden called
 711 <a href="http://usingqr.com/">UsingQR</a>.  Their PDF invoices contain
 712 a QR code with the key information of the invoice in JSON format.
 713 This is the typical content of a QR code following the UsingQR
 714 specification (based on a real world example, some numbers replaced to
 715 get a more bogus entry).  I've reformatted the JSON to make it easier
 716 to read.  Normally this is all on one long line:</p>
 717
 718 <p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
 719 {
 720  "vh":500.00,
 721  "vm":0,
 722  "vl":0,
 723  "uqr":1,
 724  "tp":1,
 725  "nme":"Din Leverandør",
 726  "cc":"NO",
 727  "cid":"997912345 MVA",
 728  "iref":"12300001",
 729  "idt":"20151022",
 730  "ddt":"20151105",
 731  "due":2500.0000,
 732  "cur":"NOK",
 733  "pt":"BBAN",
 734  "acc":"17202612345",
 735  "bc":"BIENNOK1",
 736  "adr":"0313 OSLO"
 737 }
 738 </pre></p>
 739
 740 </p>The interpretation of the fields can be found in the
 741 <a href="http://usingqr.com/wp-content/uploads/2014/06/UsingQR_specification1.pdf">format
 742 specification</a> (revision 2 from june 2014).  The format seem to
 743 have most of the information needed to handle accounting and payment
 744 of invoices, at least the fields I have needed so far here in
 745 Norway.</p>
 746
 747 <p>Unfortunately, the site and document do not mention anything about
 748 the patent, trademark and copyright status of the format and the
 749 specification.  Because of this, I asked the people behind it back in
 750 November to clarify.  Ann-Christine Savlid (ann-christine.savlid (at)
 751 visma.com) replied that Visma had not applied for patent or trademark
 752 protection for this format, and that there were no copyright based
 753 usage limitations for the format.  I urged her to make sure this was
 754 explicitly written on the web pages and in the specification, but
 755 unfortunately this has not happened yet.  So I guess if there is
 756 submarine patents, hidden trademarks or a will to sue for copyright
 757 infringements, those starting to use the UsingQR format might be at
 758 risk, but if this happen there is some legal defense in the fact that
 759 the people behind the format claimed it was safe to do so.  At least
 760 with patents, there is always
 761 <a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
 762 chance of getting sued...</a></p>
 763
 764 <p>I also asked if they planned to maintain the format in an
 765 independent standard organization to give others more confidence that
 766 they would participate in the standardization process on equal terms
 767 with Visma, but they had no immediate plans for this.  Their plan was
 768 to work with banks to try to get more users of the format, and
 769 evaluate the way forward if the format proved to be popular.  I hope
 770 they conclude that using an open standard organisation like
 771 <a href="http://www.ietf.org/">IETF</a> is the correct place to
 772 maintain such specification.</p>
 773
 774 <p><strong>Update 2016-03-20</strong>: Via Twitter I became aware of
 775 <a href="https://news.ycombinator.com/item?id=11319492">some comments
 776 about this blog post</a> that had several useful links and references to
 777 similar systems.  In the Czech republic, the Czech Banking Association
 778 standard #26, with short name SPAYD, uses QR codes with payment
 779 information.  More information is available from the Wikipedia page on
 780 <a href="https://en.wikipedia.org/wiki/Short_Payment_Descriptor">Short
 781 Payment Descriptor</a>.  And in Germany, there is a system named
 782 <a href="http://www.bezahlcode.de/">BezahlCode</a>,
 783 (<a href="http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf">specification
 784 v1.8 2013-12-05 available as PDF</a>), which uses QR codes with
 785 URL-like formatting using "bank:" as the URI schema/protocol to
 786 provide the payment information.  There is also the
 787 <a href="http://www.ferd-net.de/front_content.php?idcat=231">ZUGFeRD</a>
 788 file format that perhaps could be transfered using QR codes, but I am
 789 not sure if it is done already.  Last, in Bolivia there are reports
 790 that tax information since november 2014 need to be printed in QR
 791 format on invoices.  I have not been able to track down a
 792 specification for this format, because of my limited language skill
 793 sets.</p>
 794
 795       </div>
 796       <div class="tags">
 797
 798
 799         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>.
 800
 801
 802       </div>
 803     </div>
 804     <div class="padding"></div>
 805
 806     <div class="entry">
 807       <div class="title">
 808         <a href="http://people.skolelinux.org/pere/blog/MPEG_LA_on__Internet_Broadcast_AVC_Video__licensing_and_non_private_use.html">MPEG LA on "Internet Broadcast AVC Video" licensing and non-private use</a>
 809       </div>
 810       <div class="date">
 811          7th July 2015
 812       </div>
 813       <div class="body">
 814         <p>After asking the Norwegian Broadcasting Company (NRK)
 815 <a href="http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html">why
 816 they can broadcast and stream H.264 video without an agreement with
 817 the MPEG LA</a>, I was wiser, but still confused.  So I asked MPEG LA
 818 if their understanding matched that of NRK.  As far as I can tell, it
 819 does not.</p>
 820
 821 <p>I started by asking for more information about the various
 822 licensing classes and what exactly is covered by the "Internet
 823 Broadcast AVC Video" class that NRK pointed me at to explain why NRK
 824 did not need a license for streaming H.264 video:
 825
 826 <p><blockquote>
 827
 828 <p>According to
 829 <a href="http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf">a
 830 MPEG LA press release dated 2010-02-02</a>, there is no charge when
 831 using MPEG AVC/H.264 according to the terms of "Internet Broadcast AVC
 832 Video".  I am trying to understand exactly what the terms of "Internet
 833 Broadcast AVC Video" is, and wondered if you could help me.  What
 834 exactly is covered by these terms, and what is not?</p>
 835
 836 <p>The only source of more information I have been able to find is a
 837 PDF named
 838 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">AVC
 839 Patent Portfolio License Briefing</a>, which states this about the
 840 fees:</p>
 841
 842 <ul>
 843  <li>Where End User pays for AVC Video
 844   <ul>
 845    <li>Subscription (not limited by title) – 100,000 or fewer
 846      subscribers/yr = no royalty; &gt; 100,000 to 250,000 subscribers/yr =
 847      $25,000; &gt;250,000 to 500,000 subscribers/yr = $50,000; &gt;500,000 to
 848      1M subscribers/yr = $75,000; &gt;1M subscribers/yr = $100,000</li>
 849
 850    <li>Title-by-Title - 12 minutes or less = no royalty; &gt;12 minutes in
 851      length = lower of (a) 2% or (b) $0.02 per title</li>
 852   </ul></li>
 853
 854  <li>Where remuneration is from other sources
 855   <ul>
 856    <li>Free Television - (a) one-time $2,500 per transmission encoder or
 857      (b) annual fee starting at $2,500 for &gt; 100,000 HH rising to
 858      maximum $10,000 for &gt;1,000,000 HH</li>
 859
 860    <li>Internet Broadcast AVC Video (not title-by-title, not subscription)
 861      – no royalty for life of the AVC Patent Portfolio License</li>
 862   </ul></li>
 863 </ul>
 864
 865 <p>Am I correct in assuming that the four categories listed is the
 866 categories used when selecting licensing terms, and that "Internet
 867 Broadcast AVC Video" is the category for things that do not fall into
 868 one of the other three categories?  Can you point me to a good source
 869 explaining what is ment by "title-by-title" and "Free Television" in
 870 the license terms for AVC/H.264?</p>
 871
 872 <p>Will a web service providing H.264 encoded video content in a
 873 "video on demand" fashing similar to Youtube and Vimeo, where no
 874 subscription is required and no payment is required from end users to
 875 get access to the videos, fall under the terms of the "Internet
 876 Broadcast AVC Video", ie no royalty for life of the AVC Patent
 877 Portfolio license?  Does it matter if some users are subscribed to get
 878 access to personalized services?</p>
 879
 880 <p>Note, this request and all answers will be published on the
 881 Internet.</p>
 882 </blockquote></p>
 883
 884 <p>The answer came quickly from Benjamin J. Myers, Licensing Associate
 885 with the MPEG LA:</p>
 886
 887 <p><blockquote>
 888 <p>Thank you for your message and for your interest in MPEG LA.  We
 889 appreciate hearing from you and I will be happy to assist you.</p>
 890
 891 <p>As you are aware, MPEG LA offers our AVC Patent Portfolio License
 892 which provides coverage under patents that are essential for use of
 893 the AVC/H.264 Standard (MPEG-4 Part 10).  Specifically, coverage is
 894 provided for end products and video content that make use of AVC/H.264
 895 technology.  Accordingly, the party offering such end products and
 896 video to End Users concludes the AVC License and is responsible for
 897 paying the applicable royalties.</p>
 898
 899 <p>Regarding Internet Broadcast AVC Video, the AVC License generally
 900 defines such content to be video that is distributed to End Users over
 901 the Internet free-of-charge.  Therefore, if a party offers a service
 902 which allows users to upload AVC/H.264 video to its website, and such
 903 AVC Video is delivered to End Users for free, then such video would
 904 receive coverage under the sublicense for Internet Broadcast AVC
 905 Video, which is not subject to any royalties for the life of the AVC
 906 License.  This would also apply in the scenario where a user creates a
 907 free online account in order to receive a customized offering of free
 908 AVC Video content.  In other words, as long as the End User is given
 909 access to or views AVC Video content at no cost to the End User, then
 910 no royalties would be payable under our AVC License.</p>
 911
 912 <p>On the other hand, if End Users pay for access to AVC Video for a
 913 specific period of time (e.g., one month, one year, etc.), then such
 914 video would constitute Subscription AVC Video.  In cases where AVC
 915 Video is delivered to End Users on a pay-per-view basis, then such
 916 content would constitute Title-by-Title AVC Video.  If a party offers
 917 Subscription or Title-by-Title AVC Video to End Users, then they would
 918 be responsible for paying the applicable royalties you noted below.</p>
 919
 920 <p>Finally, in the case where AVC Video is distributed for free
 921 through an "over-the-air, satellite and/or cable transmission", then
 922 such content would constitute Free Television AVC Video and would be
 923 subject to the applicable royalties.</p>
 924
 925 <p>For your reference, I have attached
 926 <a href="http://people.skolelinux.org/pere/blog/images/2015-07-07-mpegla.pdf">a
 927 .pdf copy of the AVC License</a>. You will find the relevant
 928 sublicense information regarding AVC Video in Sections 2.2 through
 929 2.5, and the corresponding royalties in Section 3.1.2 through 3.1.4.
 930 You will also find the definitions of Title-by-Title AVC Video,
 931 Subscription AVC Video, Free Television AVC Video, and Internet
 932 Broadcast AVC Video in Section 1 of the License.  Please note that the
 933 electronic copy is provided for informational purposes only and cannot
 934 be used for execution.</p>
 935
 936 <p>I hope the above information is helpful.  If you have additional
 937 questions or need further assistance with the AVC License, please feel
 938 free to contact me directly.</p>
 939 </blockquote></p>
 940
 941 <p>Having a fresh copy of the license text was useful, and knowing
 942 that the definition of Title-by-Title required payment per title made
 943 me aware that my earlier understanding of that phrase had been wrong.
 944 But I still had a few questions:</p>
 945
 946 <p><blockquote>
 947 <p>I have a small followup question.  Would it be possible for me to get
 948 a license with MPEG LA even if there are no royalties to be paid?  The
 949 reason I ask, is that some video related products have a copyright
 950 clause limiting their use without a license with MPEG LA.  The clauses
 951 typically look similar to this:
 952
 953 <p><blockquote>
 954   This product is licensed under the AVC patent portfolio license for
 955   the personal and non-commercial use of a consumer to (a) encode
 956   video in compliance with the AVC standard ("AVC video") and/or (b)
 957   decode AVC video that was encoded by a consumer engaged in a
 958   personal and non-commercial activity and/or AVC video that was
 959   obtained from a video provider licensed to provide AVC video. No
 960   license is granted or shall be implied for any other use. additional
 961   information may be obtained from MPEG LA L.L.C.
 962 </blockquote></p>
 963
 964 <p>It is unclear to me if this clause mean that I need to enter into
 965 an agreement with MPEG LA to use the product in question, even if
 966 there are no royalties to be paid to MPEG LA.  I suspect it will
 967 differ depending on the jurisdiction, and mine is Norway.  What is
 968 MPEG LAs view on this?</p>
 969 </blockquote></p>
 970
 971 <p>According to the answer, MPEG LA believe those using such tools for
 972 non-personal or commercial use need a license with them:</p>
 973
 974 <p><blockquote>
 975
 976 <p>With regard to the Notice to Customers, I would like to begin by
 977 clarifying that the Notice from Section 7.1 of the AVC License
 978 reads:</p>
 979
 980 <p>THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR
 981 THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT
 982 RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC
 983 STANDARD ("AVC VIDEO") AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED
 984 BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM
 985 A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED
 986 OR SHALL BE IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE
 987 OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM</p>
 988
 989 <p>The Notice to Customers is intended to inform End Users of the
 990 personal usage rights (for example, to watch video content) included
 991 with the product they purchased, and to encourage any party using the
 992 product for commercial purposes to contact MPEG LA in order to become
 993 licensed for such use (for example, when they use an AVC Product to
 994 deliver Title-by-Title, Subscription, Free Television or Internet
 995 Broadcast AVC Video to End Users, or to re-Sell a third party's AVC
 996 Product as their own branded AVC Product).</p>
 997
 998 <p>Therefore, if a party is to be licensed for its use of an AVC
 999 Product to Sell AVC Video on a Title-by-Title, Subscription, Free
1000 Television or Internet Broadcast basis, that party would need to
1001 conclude the AVC License, even in the case where no royalties were
1002 payable under the License.  On the other hand, if that party (either a
1003 Consumer or business customer) simply uses an AVC Product for their
1004 own internal purposes and not for the commercial purposes referenced
1005 above, then such use would be included in the royalty paid for the AVC
1006 Products by the licensed supplier.</p>
1007
1008 <p>Finally, I note that our AVC License provides worldwide coverage in
1009 countries that have AVC Patent Portfolio Patents, including
1010 Norway.</p>
1011
1012 <p>I hope this clarification is helpful.  If I may be of any further
1013 assistance, just let me know.</p>
1014 </blockquote></p>
1015
1016 <p>The mentioning of Norwegian patents made me a bit confused, so I
1017 asked for more information:</p>
1018
1019 <p><blockquote>
1020
1021 <p>But one minor question at the end.  If I understand you correctly,
1022 you state in the quote above that there are patents in the AVC Patent
1023 Portfolio that are valid in Norway.  This make me believe I read the
1024 list available from &lt;URL:
1025 <a href="http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx">http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx</a>
1026 &gt; incorrectly, as I believed the "NO" prefix in front of patents
1027 were Norwegian patents, and the only one I could find under Mitsubishi
1028 Electric Corporation expired in 2012.  Which patents are you referring
1029 to that are relevant for Norway?</p>
1030
1031 </blockquote></p>
1032
1033 <p>Again, the quick answer explained how to read the list of patents
1034 in that list:</p>
1035
1036 <p><blockquote>
1037
1038 <p>Your understanding is correct that the last AVC Patent Portfolio
1039 Patent in Norway expired on 21 October 2012.  Therefore, where AVC
1040 Video is both made and Sold in Norway after that date, then no
1041 royalties would be payable for such AVC Video under the AVC License.
1042 With that said, our AVC License provides historic coverage for AVC
1043 Products and AVC Video that may have been manufactured or Sold before
1044 the last Norwegian AVC patent expired.  I would also like to clarify
1045 that coverage is provided for the country of manufacture and the
1046 country of Sale that has active AVC Patent Portfolio Patents.</p>
1047
1048 <p>Therefore, if a party offers AVC Products or AVC Video for Sale in
1049 a country with active AVC Patent Portfolio Patents (for example,
1050 Sweden, Denmark, Finland, etc.), then that party would still need
1051 coverage under the AVC License even if such products or video are
1052 initially made in a country without active AVC Patent Portfolio
1053 Patents (for example, Norway).  Similarly, a party would need to
1054 conclude the AVC License if they make AVC Products or AVC Video in a
1055 country with active AVC Patent Portfolio Patents, but eventually Sell
1056 such AVC Products or AVC Video in a country without active AVC Patent
1057 Portfolio Patents.</p>
1058 </blockquote></p>
1059
1060 <p>As far as I understand it, MPEG LA believe anyone using Adobe
1061 Premiere and other video related software with a H.264 distribution
1062 license need a license agreement with MPEG LA to use such tools for
1063 anything non-private or commercial, while it is OK to set up a
1064 Youtube-like service as long as no-one pays to get access to the
1065 content.  I still have no clear idea how this applies to Norway, where
1066 none of the patents MPEG LA is licensing are valid.  Will the
1067 copyright terms take precedence or can those terms be ignored because
1068 the patents are not valid in Norway?</p>
1069
1070       </div>
1071       <div class="tags">
1072
1073
1074         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</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>.
1075
1076
1077       </div>
1078     </div>
1079     <div class="padding"></div>
1080
1081     <div class="entry">
1082       <div class="title">
1083         <a href="http://people.skolelinux.org/pere/blog/Hva_gj_r_at_NRK_kan_distribuere_H_264_video_uten_patentavtale_med_MPEG_LA_.html">Hva gjør at NRK kan distribuere H.264-video uten patentavtale med MPEG LA?</a>
1084       </div>
1085       <div class="date">
1086         10th June 2015
1087       </div>
1088       <div class="body">
1089         <p>Helt siden jeg i 2012 fikk beskjed fra MPEG LA om at
1090 <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">NRK
1091 trengte patentavtale med dem</a> hvis de distribuerte H.264-video til
1092 sluttbrukere, har jeg lurt på hva som gjør at NRK ikke har slik
1093 avtale.  For noen dager siden fikk jeg endelig gjort noe med min
1094 undring, og sendte 2015-05-28 følgende epost til info (at) nrk.no med
1095 tittel "Hva gjør at NRK kan distribuere H.264-video uten patentavtale
1096 med MPEG LA?":</p>
1097
1098 <p><blockquote>
1099 <p>Jeg lurer på en ting rundt NRKs bruk av H.264-video på sine
1100 websider samt distribusjon via RiksTV og kabel-TV.  Har NRK vurdert om
1101 det er behov for en patentavtale med
1102 <a href="http://www.mpegla.com/">MPEG LA</a> slik det står i
1103 programvarelisensene til blant annet Apple Final Cut Studio, Adobe
1104 Premiere Pro, Avid og Apples Final Cut Pro X?</p>
1105
1106 <p>Hvis dere har vurdert dette, hva var utfallet av en slik vurdering?</p>
1107
1108 <p>Hvis dere ikke har vurdert dette, har NRK planer om å vurdere behovet
1109 for patentavtale?</p>
1110
1111 <p>I følge en artikkel på
1112 <a href="https://nrkbeta.no/2012/02/01/siste-kutt-for-final-cut/">NRK
1113 Beta i 2012</a> har NRK brukt eller testet både Apple Final Cut
1114 Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X til bruk
1115 for å redigere video før sending. Alle disse har bruksvilkår
1116 understøttet av opphavsretten som sier at de kun kan brukes til å lage
1117 filmer til personlig og ikke-kommersiell bruk - med mindre en har en
1118 lisensavtale med MPEG LA om bruk av patenter utstedt i USA for H.264.
1119 Se f.eks. <a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">bruksvilkårene for Avid</a>, <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">Adobe Premiere</a> og <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">Apple Final
1120 Cut Studio</a> og søk etter "MPEG LA".</p>
1121
1122 <p>Dette får meg til å lure på om det er brudd på opphavsretten å bruke
1123 disse verktøyene i strid med bruksvilkårene uten patentavtale med MPEG
1124 LA.  Men NRK bruker jo tilsynelatende disse verktøyene uten patentavtale
1125 med MPEG LA.</p>
1126
1127 <p>I følge forfatteren av Open Broadcast Encoder finnes det to typer
1128 H.264-relaterte avtaler en kan få med MPEG LA. Det er én for å lage
1129 programvare og utstyr som produserer H.264-video, og en annen for å
1130 kringkaste video som bruker H.264. Dette forteller meg at selv om
1131 produsentene av utstyr og programvare som NRK bruker har en slik avtale
1132 med MPEG LA, så trenges det en egen avtale for å kringkaste video på det
1133 formatet.</p>
1134
1135 <p>I følge Ryan Rodriguez hos MPEG LA, da jeg spurte ham på epost i
1136 juni 2012, har NRK ikke en slik avtale med MPEG LA. Han sa videre at
1137 NRK trenger en slik avtale hvis NRK tilbyr H.264-kodet video til
1138 sluttbrukere.  Jeg sjekket listen med
1139 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">organisasjoner
1140 med avtale med MPEG LA</a> og NRK står fortsatt ikke der.</p>
1141
1142 <p>Jeg lurer dermed på hva som gjør at NRK kan bruke de overnevnte
1143 videoredigeringsverktøyene, som tilsynelatende har krav om avtale med
1144 MPEG LA for å kunne brukes slik NRK bruker dem, til å lage videofiler
1145 for distribusjon uten å ha en avtale med MPEG LA om distribusjon av
1146 H.264-video?  Dette er spesielt interessant å vite for oss andre som
1147 også vurderer å spre H.264-video etter å ha redigert dem med disse mye
1148 brukte videoredigeringsverktøyene.</p>
1149 </blockquote></p>
1150
1151 <p>Samme dag fikk jeg automatisk svar om at min henvendelse hadde fått
1152 saksid 1294699.  Jeg fikk deretter følgende respons fra NRK
1153 2015-06-09:</p>
1154
1155 <p><blockquote>
1156 <p>Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som kunne
1157 svare på dette.</p>
1158
1159 <p>For selskaper som leverer h.264 til sluttbrukere på nett (f.eks
1160 NRKs nett- tv utgaver som bruker h.264) - og som leverer slike
1161 tjenester uten betaling fra forbrukere – er det heller ikke påkrevd
1162 noen patentavtale.</p>
1163
1164 <p><a href="http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y">http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</a></p>
1165
1166 <p>Med vennlig hilsen
1167 <br>Gunn Helen Berg
1168 <br>Informasjonskonsulent, Publikumsservice</p>
1169
1170 <p>NRK
1171 <br>Strategidivisjonen
1172 <Br>Sentralbord: +47 23 04 70 00
1173 <br>Post: NRK Publikumsservice, 8608 Mo i Rana
1174 <br>nrk.no / info (at) nrk.no</p>
1175 </blockquote></p>
1176
1177 Da dette ikke helt var svar på det jeg lurte på, sendte jeg samme dag
1178 oppfølgerepost tilbake:
1179
1180 <p><blockquote>
1181 <p>[Gunn Helen Berg]
1182 <br>> Hei, beklager lang svartid, men det tok litt tid å finne ut hvem som
1183 <br>> kunne svare på dette.</p>
1184
1185 <p>Takk for svar.  Men det besvarte ikke helt det jeg spurte om.</p>
1186
1187 <p>> For selskaper som leverer h.264 til sluttbrukere på nett (f.eks NRKs
1188 <br>> nett- tv utgaver som bruker h.264) - og som leverer slike tjenester
1189 <br>> uten betaling fra forbrukere – er det heller ikke påkrevd noen
1190 <br>> patentavtale.
1191 <br>>
1192 <br>> http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</p>
1193
1194 <p>Spørsmålet er ikke kun om MPEG LA krever patentavtale eller ikke
1195 (hvilket ikke helt besvares av pressemeldingen omtalt over, gitt at
1196 pressemeldingen kom i 2010, to år før MPEG LA ansvarlige for
1197 internasjonal lisensiering egen Ryan Rodriguez fortalte meg på epost
1198 at NRK trenger en lisens.</p>
1199
1200 <p>Det er uklart fra pressemeldingen hva "Internet Broadcast AVC
1201 Video" konkret betyr, men i følge en
1202 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">presentasjon
1203 fra MPEG LA med tema "AVC PAtent Portfoli License Briefing" datert
1204 2015-05-15</a> gjelder "Internet Broadcast AVC Video" kun kringkasting
1205 på Internet som ikke tilbyr valg av enkeltinnslag ("not
1206 title-by-title"), hvilket jo NRK gjør på sine nettsider.  I tillegg
1207 kringkaster jo NRK H.264-video også utenom Internet (RiksTV, kabel,
1208 satelitt), hvilket helt klart ikke er dekket av vilkårene omtalt i
1209 pressemeldingen.</p>
1210
1211 <p>Spørsmålet mitt er hvordan NRK kan bruke verktøy med bruksvilkår
1212 som krever avtale med MPEG LA for det NRK bruker dem til, når NRK ikke
1213 har avtale med MPEG LA.  Hvis jeg forsto spørsmålet riktig, så mener
1214 NRK at dere ikke trenger avtale med MPEG LA, men uten slik avtale kan
1215 dere vel ikke bruke hverken Apple Final Cut Studio, Adobe Premiere
1216 Pro, Avid eller Apples Final Cut Pro X for å redigere video før
1217 sending?</p>
1218
1219 <p>Mine konkrete spørsmål var altså:</p>
1220
1221 <ul>
1222
1223 <li>Hvis NRK har vurdert om det er behov for en patentavtale med MPEG LA
1224    slik det er krav om i programvarelisensene til blant annet Apple
1225    Final Cut Studio, Adobe Premiere Pro, Avid og Apples Final Cut Pro X,
1226    hva var utfallet av en slik vurdering? Kan jeg få kopi av vurderingen
1227    hvis den er gjort skriftlig?</li>
1228
1229 <li>Hvis NRK ikke har vurdert dette, har NRK planer om å vurdere behovet
1230    for patentavtale?</li>
1231
1232 <li>Hva slags saksnummer fikk min henvendelse i NRKs offentlige
1233    postjournal?  Jeg ser at postjournalen ikke er publisert for den
1234    aktuelle perioden ennå, så jeg fikk ikke sjekket selv.</li>
1235
1236 </ul>
1237 </blockquote></p>
1238
1239 <p>Det hjelper å ha funnet rette vedkommende i NRK, for denne gangen
1240 fikk jeg svar tilbake dagen etter (2015-06-10), fra Geir Børdalen i
1241 NRK:</p>
1242
1243 <p><blockquote>
1244 <p>Hei Petter Reinholdtsen</p>
1245
1246 <p>Jeg har sjekket saken med distribusjonssjef for tv, Arild Hellgren
1247 (som var teknologidirektør da bakkenettet ble satt opp). NRK v/
1248 Hellgren hadde møte med MPEG LA sammen med den europeiske
1249 kringkastingsunionen EBU før bakkenettet for TV ble satt opp
1250 (igangsatt høsten 2007). I dette møtet ble det avklart at NRK/EBU ikke
1251 trengte noen patentavtale for h.264 i forbindelse med oppsett av
1252 bakkenettet eller bruk av MPEG4 h.264 som kompresjonsalgoritme fordi
1253 tjenesten «in full»(nor: helt) var betalt av utsendelseselskapene og
1254 ikke av forbrukerne.</p>
1255
1256 <p><a href="http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555">http://www.nrk.no/oppdrag/digitalt-bakkenett-1.3214555</a></p>
1257
1258 <p>Det er også klart slått fast at selskaper som leverer video basert
1259 på MPEG4 h.264 til sluttbrukere på nett, heller ikke påkrevd noen
1260 patentavtale – så lenge de leverer slike tjenester uten betaling fra
1261 sluttbrukere.</p>
1262
1263 <a href="http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y">http://www.businesswire.com/news/home/20100825006629/en/MPEG-LA%E2%80%99s-AVC-License-Charge-Royalties-Internet#.VWb2ws_774Y</a>
1264
1265 <p>“MPEG LA announced today that its AVC Patent Portfolio License will
1266 continue not to charge royalties for Internet Video that is free to
1267 end users (known as “Internet Broadcast AVC Video”) during the entire
1268 life of this License. MPEG LA previously announced it would not charge
1269 royalties for such video through December 31, 2015 (see
1270 <a href="http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf">http://www.mpegla.com/Lists/MPEG%20LA%20News%20List/Attachments/226/n-10-02-02.pdf</a>),
1271 and today’s announcement makes clear that royalties will continue not
1272 to be charged for such video beyond that time. Products and services
1273 other than Internet Broadcast AVC Video continue to be
1274 royalty-bearing.”</p>
1275
1276 <p>Vi har derfor ikke noe behov for å vurdere noen patentavtale med
1277 MPEG LA.</p>
1278
1279 <p>Understreker for øvrig at NRK ikke er låst til MPEG4 – h.264 som
1280 utsendelsesformat – og at vi har brukt og bruker flere andre
1281 alternativer i våre tjenester. Ulike «devicer» har ofte behov for
1282 forskjellige løsninger – og NRK har forsøkt å levere med best mulig
1283 kvalitet /økonomi /stabilitet avhengig av
1284 plattform. Produksjonsformater i NRK spenner for øvrig over en rekke
1285 forskjellige formater – hvor MPEG4 bare er en av disse. Når NRK kjøper
1286 teknisk utstyr er betaling for kodekstøtte ofte en del av
1287 anskaffelsesprisen for denne maskinvaren (enten dette er spesialiserte
1288 enkodere eller forskjellige typer produksjonsutstyr).</p>
1289
1290 <p>Vennlig hilsen
1291 <br>Geir Børdalen</p>
1292
1293 <p>________________________________________
1294 <br>Geir Børdalen
1295 <br>Investeringsansvarlig NRK / Hovedprosjektleder - Origo
1296 <br>Avdeling for utvikling, innovasjon, investering og eiendom
1297 <br>NRK medietjenester
1298 <br>Sentralbord: +47 23 04 70 00
1299 <br>Post: NRK, AUTV (RBM5), Pb. 8500 Majorstuen, 0340 Oslo
1300 <br>nrk.no
1301 </blockquote></p>
1302
1303 <p>Et godt og grundig svar, som var informativt om hvordan NRK tenker
1304 rundt patentavtale med MPEG LA, men heller ikke helt besvarte det jeg
1305 lurte på, så jeg sendte epostoppfølging samme dag.</p>
1306
1307 <p><blockquote>
1308 <p>[Geir Børdalen]
1309 <br>> Hei Petter Reinholdtsen</p>
1310
1311 <p>Hei, og takk for raskt svar.  Er min henvendelse journalført slik
1312 at den dukker opp i NRKs postjournal?</p>
1313
1314 <p>Svaret ditt var meget nyttig, og jeg forstår ut fra det du skriver
1315 at avklaringen med MPEG LA rundt H.264-distribusjon via bakkenettet
1316 gjelder alle TV-kanaler i Norge.  Hvilke saksnummer fikk dokumenter
1317 som ble opprettet i forbindelse med det omtalte møtet NRK v/Hellgren
1318 og EBU hadde med MPEG LA (dvs. referater, avtaler, etc),
1319 f.eks. dokumentet der formuleringen "in full" som du omtaler
1320 finnes?<p>
1321
1322 <p>Men det er et par ting jeg fortsatt ikke forstår.  Det ene er
1323 hvorfor NRKs forståelse av hva "Internet Broadcast AVC Video" dekker
1324 ser ut til å avvike fra det som presenteres i
1325 <a href="http://www.mpegla.com/main/programs/avc/Documents/avcweb.pdf">lysark
1326 fra MPEG LA</a> i mai, der MPEG LA på lysark med overskriften
1327 "AVC/H.264 License Terms Participation Fees" og undertittel "Where
1328 remuneration is from other sources" skriver "Internet Broadcast AVC
1329 Video (not title-by-title, not subscription) – no royalty for life of
1330 the AVC Patent Portfolio License".</p>
1331
1332 <p>Her leser jeg MPEG LA dithen at det kun er kringkasting uten
1333 abonnement via Internet som er dekket at vilkårne omtalt i
1334 pressemeldingen, mens jeg forstår deg dithen at NRK mener NRKs
1335 nettsider som også har enkeltfilmer og innslag (som jeg forstår dekket
1336 av formuleringen "title-by-title") dekkes av "Internet Broadcast AVC
1337 Video" fra MPEG LA.  Hva baserer dere denne tolkningen på?  Jeg har
1338 ikke sett noe skriftlig fra MPEG LA som støtter NRKs tolkning, og
1339 lurer på om dere har andre kilder enn den pressemeldingen fra 5 år
1340 tilbake, der NRKS forståelse av hva "Internet Broadcast AVC Video"
1341 dekker er beskrevet?</p>
1342
1343 <p>Det andre er at eposten din ikke nevnte spørsmålet mitt om
1344 bruksvilkårene til videoredigeringsverktøyene som NRK bruker.  Disse
1345 har som tidligere nevnt krav om at de kun skal brukes til private og
1346 ikke-kommersielle formål med mindre en har avtale med MPEG LA, og uten
1347 avtale med MPEG LA kan det jo virke som om NRK bruker verktøyene i
1348 strid med bruksvilkårene.  Hva gjør at disse bruksvilkårene ikke
1349 gjelder for NRK?</p>
1350 </blockquote></p>
1351
1352 <p>Noen minutter senere får jeg foreløpig siste svar i
1353 føljetongen:</p>
1354
1355 <p><blockquote>
1356 <p>Hei igjen</p>
1357
1358 <p>Vårt dokumentarkiv har fått en kopi (journalføringsnr kan jeg
1359 dessverre ikke gi deg).<p>
1360
1361 <p>> Svaret ditt var meget nyttig, og jeg forstår ut fra det du
1362 <br>> skriver at avklaringen med MPEG LA rundt H.264-distribusjon via
1363 <br>> bakkenettet gjelder alle TV-kanaler i Norge.</p>
1364
1365 <p>Svar: Kan ikke svare for andre enn for NRK/EBU - og for bakkenettet
1366 i Norge er det kun NRK som er et lisensbasert selskap. Kan ikke gi noe
1367 svar på saksnr på dokumenter eller ytterligere informasjon da jeg selv
1368 ikke var del i dette.</p>
1369
1370 <p>> Men det er et par ting jeg fortsatt ikke forstår.  ...</p>
1371
1372 <p>Svar: Kan ikke gå ytterligere inn i dette fra min side og mitt
1373 fagfelt som er produksjon/publisering og systemstrukturene bak
1374 disse. For øvrig ligger det etter vår formening ingen begrensninger
1375 for NRK i mulighetene til publisering mht til kodek i
1376 produksjonssystemer. Som tidligere skrevet mener vi at NRK ikke
1377 trenger noen avtale med MPEG LA og støtter oss til det vi allerede har
1378 kommunisert i forrige epost.</p>
1379
1380 <p>Mvh
1381 <br>Geir Børdalen</p>
1382 </blockquote></p>
1383
1384 <p>Det syntes vanskelig å komme videre når NRK ikke ønsker å gå inn i
1385 problemstillingen rundt bruksvilkårene til videoredigeringsverktøyene
1386 NRK bruker, så jeg sendte takk for svarene og avsluttet utvekslingen
1387 så langt:</p>
1388
1389 <p><blockquote>
1390 <p>Tusen takk for rask respons, og oppklarende forklaring om hvordan
1391 NRK tenker rundt MPEG LA.</p>
1392
1393 <p>Jeg vil høre med NRK-arkivet for å se om de kan spore opp de
1394 omtalte dokumentene.  Jeg setter pris på om du kan dele titler, dato
1395 eller annen informasjon som kan gjøre det enklere for arkivet å finne
1396 dem.</p>
1397
1398 <p>Når det gjelder hvordan bruksvilkårene til
1399 videoredigeringsverktøyene skal tolkes, så skal jeg høre med MPEG LA
1400 og produsentene av verktøyene for å forsøke å få klarhet i hva de
1401 mener er rikgig rettstilstand.</p>
1402 </blockquote></p>
1403
1404 <p>Jeg ble litt klokere, men fortsatt er det uklart for meg hva som er
1405 grunnlaget til NRK for å se bort fra bruksvilkår i
1406 videoredigeringsprogramvare som krever MPEG LA-avtale til alt annet
1407 enn privat og ikke-kommersiell bruk.</p>
1408
1409       </div>
1410       <div class="tags">
1411
1412
1413         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
1414
1415
1416       </div>
1417     </div>
1418     <div class="padding"></div>
1419
1420     <div class="entry">
1421       <div class="title">
1422         <a href="http://people.skolelinux.org/pere/blog/Hvordan_vurderer_regjeringen_H_264_patentutfordringen_.html">Hvordan vurderer regjeringen H.264-patentutfordringen?</a>
1423       </div>
1424       <div class="date">
1425         16th November 2014
1426       </div>
1427       <div class="body">
1428         <p>For en stund tilbake spurte jeg Fornyingsdepartementet om hvilke
1429 juridiske vurderinger rundt patentproblemstillingen som var gjort da
1430 H.264 ble tatt inn i <a href="http://standard.difi.no/">statens
1431 referansekatalog over standarder</a>.  Stig Hornnes i FAD tipset meg
1432 om følgende som står i oppsumeringen til høringen om
1433 referansekatalogen versjon 2.0, som jeg siden ved hjelp av en
1434 innsynsforespørsel fikk tak i
1435 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">PDF-utgaven av</a>
1436 datert 2009-06-03 (saksnummer 200803291, saksbehandler Henrik
1437 Linnestad).</p>
1438
1439 <p>Der står det følgende om problemstillingen:</p>
1440
1441 <p><blockquote>
1442 <strong>4.4 Patentproblematikk</strong>
1443
1444 <p>NUUG og Opera ser det som særlig viktig at forslagene knyttet til
1445 lyd og video baserer seg på de royalty-frie standardene Vorbis, Theora
1446 og FLAC.</p>
1447
1448 <p>Kommentarene relaterer seg til at enkelte standarder er åpne, men
1449 inneholder tekniske prosedyrer som det i USA (og noen andre land som
1450 Japan) er gitt patentrettigheter til. I vårt tilfelle berører dette
1451 spesielt standardene Mp3 og H.264, selv om Politidirektoratet peker på
1452 at det muligens kan være tilsvarende problematikk også for Theora og
1453 Vorbis.  Dette medfører at det i USA kan kreves royalties for bruk av
1454 tekniske løsninger knyttet til standardene, et krav som også
1455 håndheves. Patenter kan imidlertid bare hevdes i de landene hvor
1456 patentet er gitt, så amerikanske patenter gjelder ikke andre steder
1457 enn USA.</p>
1458
1459 <p>Spesielt for utvikling av fri programvare er patenter
1460 problematisk. GPL, en "grunnleggende" lisens for distribusjon av fri
1461 programvare, avviser at programvare kan distribueres under denne
1462 lisensen hvis det inneholder referanser til patenterte rutiner som
1463 utløser krav om royalties. Det er imidlertid uproblematisk å
1464 distribuere fri programvareløsninger under GPL som benytter de
1465 aktuelle standardene innen eller mellom land som ikke anerkjenner
1466 patentene. Derfor finner vi også flere implementeringer av Mp3 og
1467 H.264 som er fri programvare, lisensiert under GPL.</p>
1468
1469 <p>I Norge og EU er patentlovgivningen langt mer restriktiv enn i USA,
1470 men det er også her mulig å få patentert metoder for løsning av et
1471 problem som relaterer seg til databehandling. Det er AIF bekjent ikke
1472 relevante patenter i EU eller Norge hva gjelder H.264 og Mp3, men
1473 muligheten for at det finnes patenter uten at det er gjort krav om
1474 royalties eller at det senere vil gis slike patenter kan ikke helt
1475 avvises.</p>
1476
1477 <p>AIF mener det er et behov for å gi offentlige virksomheter mulighet
1478 til å benytte antatt royaltyfrie åpne standarder som et likeverdig
1479 alternativ eller i tillegg til de markedsledende åpne standardene.</p>
1480
1481 </blockquote></p>
1482
1483 <p>Det ser dermed ikke ut til at de har vurdert patentspørsmålet i
1484 sammenheng med opphavsrettsvilkår slik de er formulert for f.eks.
1485 Apple Final Cut Pro, Adobe Premiere Pro, Avid og Sorenson-verktøyene,
1486 der det kreves brukstillatelse for patenter som ikke er gyldige i
1487 Norge for å bruke disse verktøyene til annet en personlig og ikke
1488 kommersiell aktivitet når det gjelder H.264-video.  Jeg må nok lete
1489 videre etter svar på det spørsmålet.</p>
1490
1491       </div>
1492       <div class="tags">
1493
1494
1495         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
1496
1497
1498       </div>
1499     </div>
1500     <div class="padding"></div>
1501
1502     <div class="entry">
1503       <div class="title">
1504         <a href="http://people.skolelinux.org/pere/blog/Do_you_need_an_agreement_with_MPEG_LA_to_publish_and_broadcast_H_264_video_in_Norway_.html">Do you need an agreement with MPEG-LA to publish and broadcast H.264 video in Norway?</a>
1505       </div>
1506       <div class="date">
1507         25th August 2014
1508       </div>
1509       <div class="body">
1510         <p>Two years later, I am still not sure if it is legal here in Norway
1511 to use or publish a video in H.264 or MPEG4 format edited by the
1512 commercially licensed video editors, without limiting the use to
1513 create "personal" or "non-commercial" videos or get a license
1514 agreement with <a href="http://www.mpegla.com">MPEG LA</a>.  If one
1515 want to publish and broadcast video in a non-personal or commercial
1516 setting, it might be that those tools can not be used, or that video
1517 format can not be used, without breaking their copyright license.  I
1518 am not sure.
1519 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">Back
1520 then</a>, I found that the copyright license terms for Adobe Premiere
1521 and Apple Final Cut Pro both specified that one could not use the
1522 program to produce anything else without a patent license from MPEG
1523 LA.  The issue is not limited to those two products, though.  Other
1524 much used products like those from Avid and Sorenson Media have terms
1525 of use are similar to those from Adobe and Apple.  The complicating
1526 factor making me unsure if those terms have effect in Norway or not is
1527 that the patents in question are not valid in Norway, but copyright
1528 licenses are.</p>
1529
1530 <p>These are the terms for Avid Artist Suite, according to their
1531 <a href="http://www.avid.com/US/about-avid/legal-notices/legal-enduserlicense2">published
1532 end user</a>
1533 <a href="http://www.avid.com/static/resources/common/documents/corporate/LICENSE.pdf">license
1534 text</a> (converted to lower case text for easier reading):</p>
1535
1536 <p><blockquote>
1537 <p>18.2. MPEG-4. MPEG-4 technology may be included with the
1538 software. MPEG LA, L.L.C. requires this notice: </p>
1539
1540 <p>This product is licensed under the MPEG-4 visual patent portfolio
1541 license for the personal and non-commercial use of a consumer for (i)
1542 encoding video in compliance with the MPEG-4 visual standard (“MPEG-4
1543 video”) and/or (ii) decoding MPEG-4 video that was encoded by a
1544 consumer engaged in a personal and non-commercial activity and/or was
1545 obtained from a video provider licensed by MPEG LA to provide MPEG-4
1546 video.  No license is granted or shall be implied for any other
1547 use. Additional information including that relating to promotional,
1548 internal and commercial uses and licensing may be obtained from MPEG
1549 LA, LLC.  See http://www.mpegla.com. This product is licensed under
1550 the MPEG-4 systems patent portfolio license for encoding in compliance
1551 with the MPEG-4 systems standard, except that an additional license
1552 and payment of royalties are necessary for encoding in connection with
1553 (i) data stored or replicated in physical media which is paid for on a
1554 title by title basis and/or (ii) data which is paid for on a title by
1555 title basis and is transmitted to an end user for permanent storage
1556 and/or use, such additional license may be obtained from MPEG LA,
1557 LLC. See http://www.mpegla.com for additional details.</p>
1558
1559 <p>18.3. H.264/AVC. H.264/AVC technology may be included with the
1560 software.  MPEG LA, L.L.C. requires this notice:</p>
1561
1562 <p>This product is licensed under the AVC patent portfolio license for
1563 the personal use of a consumer or other uses in which it does not
1564 receive remuneration to (i) encode video in compliance with the AVC
1565 standard (“AVC video”) and/or (ii) decode AVC video that was encoded
1566 by a consumer engaged in a personal activity and/or was obtained from
1567 a video provider licensed to provide AVC video. No license is granted
1568 or shall be implied for any other use. Additional information may be
1569 obtained from MPEG LA, L.L.C. See http://www.mpegla.com.</p>
1570 </blockquote></p>
1571
1572 <p>Note the requirement that the videos created can only be used for
1573 personal or non-commercial purposes.</p>
1574
1575 <p>The Sorenson Media software have
1576 <a href="http://www.sorensonmedia.com/terms/">similar terms</a>:</p>
1577
1578 <p><blockquote>
1579
1580 <p>With respect to a license from Sorenson pertaining to MPEG-4 Video
1581 Decoders and/or Encoders: Any such product is licensed under the
1582 MPEG-4 visual patent portfolio license for the personal and
1583 non-commercial use of a consumer for (i) encoding video in compliance
1584 with the MPEG-4 visual standard (“MPEG-4 video”) and/or (ii) decoding
1585 MPEG-4 video that was encoded by a consumer engaged in a personal and
1586 non-commercial activity and/or was obtained from a video provider
1587 licensed by MPEG LA to provide MPEG-4 video. No license is granted or
1588 shall be implied for any other use. Additional information including
1589 that relating to promotional, internal and commercial uses and
1590 licensing may be obtained from MPEG LA, LLC. See
1591 http://www.mpegla.com.</p>
1592
1593 <p>With respect to a license from Sorenson pertaining to MPEG-4
1594 Consumer Recorded Data Encoder, MPEG-4 Systems Internet Data Encoder,
1595 MPEG-4 Mobile Data Encoder, and/or MPEG-4 Unique Use Encoder: Any such
1596 product is licensed under the MPEG-4 systems patent portfolio license
1597 for encoding in compliance with the MPEG-4 systems standard, except
1598 that an additional license and payment of royalties are necessary for
1599 encoding in connection with (i) data stored or replicated in physical
1600 media which is paid for on a title by title basis and/or (ii) data
1601 which is paid for on a title by title basis and is transmitted to an
1602 end user for permanent storage and/or use. Such additional license may
1603 be obtained from MPEG LA, LLC. See http://www.mpegla.com for
1604 additional details.</p>
1605
1606 </blockquote></p>
1607
1608 <p>Some free software like
1609 <a href="https://handbrake.fr/">Handbrake</A> and
1610 <a href="http://ffmpeg.org/">FFMPEG</a> uses GPL/LGPL licenses and do
1611 not have any such terms included, so for those, there is no
1612 requirement to limit the use to personal and non-commercial.</p>
1613
1614       </div>
1615       <div class="tags">
1616
1617
1618         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</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>.
1619
1620
1621       </div>
1622     </div>
1623     <div class="padding"></div>
1624
1625     <div class="entry">
1626       <div class="title">
1627         <a href="http://people.skolelinux.org/pere/blog/Hvor_godt_fungerer_Linux_klienter_mot_MS_Exchange_.html">Hvor godt fungerer Linux-klienter mot MS Exchange?</a>
1628       </div>
1629       <div class="date">
1630         26th November 2013
1631       </div>
1632       <div class="body">
1633         <p>Jeg
1634 <a href="http://people.skolelinux.org/pere/blog/_pent_m_te_p__onsdag_om_bruken_av_Microsoft_Exchange_ved_Universitetet_i_Oslo.html">skrev
1635 i juni om protestene</a> på planene til min arbeidsplass,
1636 <a href="http://www.uio.no/">Universitetet i Oslo</a>, om å gå bort fra
1637 fri programvare- og åpne standardløsninger for å håndtere epost,
1638 vekk fra IETF-standarden SIEVE for filtrering av epost og over til
1639 godseide spesifikasjoner og epostsystemet Microsoft Exchange.
1640 Protestene har fått litt ny omtale i media de siste dagene, i tillegg
1641 til de oppslagene som kom i mai.</p>
1642
1643 <ul>
1644
1645 <li>2013-11-26 <a href="http://www.version2.dk/artikel/gigantisk-outlook-konvertering-moeder-protester-paa-universitet-55147">Gigantisk Outlook-konvertering møder protester på universitet</a> - versjon2.dk</li>
1646
1647 <li>2013-11-25
1648   <a href="http://www.idg.no/computerworld/article279407.ece">Microsoft-protest
1649   på Universitetet</a> - Computerworld</li>
1650
1651 <li>2013-11-25
1652   <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-bor-bruke-apen-programvare.html">Kjemper
1653   mot innføring av Microsoft Exchange på UiO</a> - Uniforum</li>
1654
1655 <li>2013-11-25
1656   <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-utsetter-innforing-av-nytt-e-postsystem.html">Utsetter
1657   innføring av nytt e-postsystem</a> - Uniforum</li>
1658
1659 <li>2013-05-29
1660   <a href="http://universitas.no/nyhet/58462/forsvarer-nytt-it-system">Forsvarer
1661   nytt IT-system</a> - Universitas</li>
1662
1663 <li>2013-05-23
1664   <a href="http://www.uniforum.uio.no/nyheter/2013/05/uio-innforer-nytt-epost-og-kalendersystem.html">UiO
1665   innfører nytt epost- og kalenderverktøy</a> - Uniforum</li>
1666
1667 <li>2013-05-22
1668   <a href="http://universitas.no/nyhet/58424/protestgruppe-vil-stanse-it-system">Protestgruppe
1669   vil stanse IT-system</a> - Universitas</li>
1670
1671 <li>2013-05-15
1672   <a href="http://www.uniforum.uio.no/leserbrev/2013/uio-ma-ha-kontroll-over-sitt-eget-epostsystem.html">UiO
1673   må ha kontroll over sitt eget epostsystem</a> - Uniforum</li>
1674
1675 </ul>
1676
1677 <p>Prosjektledelsen har fortalt at dette skal fungere like godt for
1678 Linux-brukere som for brukere av Microsoft Windows og Apple MacOSX,
1679 men jeg lurer på hva slags erfaringer Linux-brukere i eksisterende
1680 miljøer som bruker MS Exchange har gjort.  Hvis du har slik erfaring
1681 hadet det vært veldig fint om du kan send et leserbrev til
1682 <a href="http://www.uniforum.uio.no/">Uniforum</a> og fortelle om hvor
1683 greit det er å bruke Exchange i kryss-platform-miljøer?  De jeg har
1684 snakket med sier en greit får lest e-posten sin hvis Exchange har
1685 slått på IMAP-funksjonalitet, men at kalender og møtebooking ikke
1686 fungerer godt for Linux-klienter. Jeg har ingen personlig erfaring å
1687 komme med, så jeg er nysgjerrig på hva andre kan dele av erfaringer
1688 med universitetet.</p>
1689
1690 <p>Mitt ankerpunkt mot å bytte ut fri programvare som fungerer godt
1691 med godseid programvare er at en mister kontroll over egen
1692 infrastruktur, låser seg inn i en løsning det vil bli dyrt å komme ut
1693 av, uten at en får funksjonalitet en ikke kunne skaffet seg med fri
1694 programvare, eventuelt videreutviklet med de pengene som brukes på
1695 overgangen til MS Exchange.  Personlig planlegger jeg å fortsette å
1696 laste ned all eposten min til lokal maskin for indeksering og lesing
1697 med <a href=="http://notmuchmail.org">notmuch</a>, så jeg håper jeg
1698 ikke blir veldig skadelidende av overgangen.</p>
1699
1700 <p><a href="http://dinis.linguateca.pt/Diana/ImotMSUiO.html">Underskriftslista
1701 for oss som er mot endringen</a>, som omtales i artiklene, er fortsatt
1702 åpen for de som vil signere på oppropet.  Akkurat nå er det 298
1703 personer som har signert.</p>
1704
1705       </div>
1706       <div class="tags">
1707
1708
1709         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1710
1711
1712       </div>
1713     </div>
1714     <div class="padding"></div>
1715
1716     <div class="entry">
1717       <div class="title">
1718         <a href="http://people.skolelinux.org/pere/blog/_pent_m_te_p__onsdag_om_bruken_av_Microsoft_Exchange_ved_Universitetet_i_Oslo.html">Åpent møte på onsdag om bruken av Microsoft Exchange ved Universitetet i Oslo</a>
1719       </div>
1720       <div class="date">
1721          3rd June 2013
1722       </div>
1723       <div class="body">
1724         <p>Jeg jobber til daglig ved <a href="http://www.uio.no/">Universitetet
1725 i Oslo</a>, en institusjon som lenge har vektlagt verdien av åpne
1726 standarder og fri programvare.  Men noe har endret seg, og for en
1727 liten stund tilbake annonserte USIT at dagens fungerende e-postsystemet
1728 basert på fri programvare skulle byttes ut med Microsoft Exchange og
1729 at Microsoft Outlook skulle bli den best fungerende men antagelig ikke
1730 eneste støttede e-postklienten.  Annonseringen har ført til flere
1731 protester og <a href="http://folk.uio.no/dssantos/nooutlookatuio/">en
1732 underskriftskampanje</a>, initiert av Diana Santos, der så langt 253
1733 personer har signert.  Prosjektet
1734 <a href="http://www.usit.uio.no/prosjekter/nike/">NIKE (Ny integrert
1735 kalender/e-post)</a> ble initiert for å se på mulige løsninger med
1736 utgangspunkt i at en kombinert epost/kalenderløsning var påkrevd, og
1737 prosjektet
1738 <a href="http://www.usit.uio.no/prosjekter/nike-implementasjon/">NIKE-implementasjon</a>
1739 er igang med å rulle ut MS Exchange ved Universitetet i Oslo.</p>
1740
1741 <p>For kun kort tid siden ble det annonsert at det blir et åpent møte
1742 med ledelsen hos universitetet i Oslo med disse planene som tema:</p>
1743
1744 <p>Tid: <strong>Onsdag 2013-06-05 kl. 10:00</strong>
1745 <br>Sted: <strong>9. etasje i Lucy Smiths hus (admin-bygget)</strong></p>
1746
1747 <p> Det kan være en god plass å stille opp hvis en som meg ikke tror
1748 valget av Microsoft Exchange som sentral epostinfrastruktur er et
1749 heldig valg for Norges ledende forskningsuniversitet, men at en er mer
1750 tjent med å selv
1751 <a href="http://nuug.no/dokumenter/kronikk-friprog-itsikkerhet.shtml">beholde
1752 kontrollen over egen infrastruktur</a>.</p>
1753
1754 <p>Saken har ført til endel presseoppslag så langt.  Her er de jeg har
1755 fått med meg:</p>
1756
1757 <ul>
1758
1759 <li>2013-05-29
1760   <a href="http://universitas.no/nyhet/58462/forsvarer-nytt-it-system">Forsvarer
1761   nytt IT-system</a> - Universitas</li>
1762
1763 <li>2013-05-23
1764   <a href="http://www.uniforum.uio.no/nyheter/2013/05/uio-innforer-nytt-epost-og-kalendersystem.html">UiO
1765   innfører nytt epost- og kalenderverktøy</a> - Uniforum</li>
1766
1767
1768 <li>2013-05-22
1769   <a href="http://universitas.no/nyhet/58424/protestgruppe-vil-stanse-it-system">Protestgruppe
1770   vil stanse IT-system</a> - Universitas</li>
1771
1772
1773 <li>2013-05-15
1774   <a href="http://www.uniforum.uio.no/leserbrev/2013/uio-ma-ha-kontroll-over-sitt-eget-epostsystem.html">UiO
1775   må ha kontroll over sitt eget epostsystem</a> - Uniforum</li>
1776
1777 </ul>
1778
1779
1780
1781       </div>
1782       <div class="tags">
1783
1784
1785         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1786
1787
1788       </div>
1789     </div>
1790     <div class="padding"></div>
1791
1792     <div class="entry">
1793       <div class="title">
1794         <a href="http://people.skolelinux.org/pere/blog/Mer_innsyn_i_bakgrunnen_for_fjerning_av_ODF_fra_statens_standardkatalog.html">Mer innsyn i bakgrunnen for fjerning av ODF fra statens standardkatalog</a>
1795       </div>
1796       <div class="date">
1797          9th April 2013
1798       </div>
1799       <div class="body">
1800         <p>For cirka en måned siden
1801 <ahref="http://people.skolelinux.org/pere/blog/Regjeringen__Fornyingsdepartementet_og_DIFI_g_r_inn_for___fjerne_ODF_som_obligatorisk_standard_i_det_offentlige.html">ba
1802 jeg om begrunnelse på nektet innsyn i dokumenter</a> om
1803 standardkatalogen fra Fornyingsdepartementet.  I dag fikk jeg svar fra
1804 Fornyingsdepartementet, og tilgang til dokumentene.  Jeg fikk både
1805 innsyn i vedlegg sendt fra DIFI, og også innsyn i et notat brukt
1806 internt i Fornyingsdepartementet:</p>
1807
1808 <ul>
1809
1810 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-Fornyingsdepartementet/sak-2012-2168/Oppsummering%20av%20h%f8ringen%20om%20endringer%20i%20forskrift%20om%20IT-standarder.pdf">Epost fra DIFI til Fornyingsdepartementet, datert 2012-11-23</a></li>
1811
1812 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-Fornyingsdepartementet/sak-2012-2168/Oppsummering%20og%20anbefaling%20etter%20h%f8ring.pdf">vedlegg 1, Oppsummering og anbefalinger etter høring av endringer i forskrift om IT-standarer i offentlig forvaltning, datert 2012-11-23</a></li>
1813
1814 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-Fornyingsdepartementet/sak-2012-2168/Vedlegg%20Om%20h%f8ringe.docx%20(L)(898066).pdf">Notat fra avdeling for IKT og fornying til statsråd i Fornyingsdepartementet om høringen, datert 2013-01-03</a></li>
1815
1816 </ul>
1817
1818 <p>Det bør nevnes at da jeg ble nektet innsyn hos mottaker
1819 Fornyingsdepartementet på høringsoppsummeringen som DIFI hadde sendt
1820 ut, spurte jeg DIFI om innsyn i stedet.  Det fikk jeg i løpet av et
1821 par dager.  Moralen er at hvis ikke mottaker ikke vil gi innsyn, spør
1822 avsender i stedet.  Kanskje de har forskjellig forståelse av hva som
1823 bør holdes skjult for folket.  Her er de tilsvarende dokumentene jeg
1824 fikk innsyn i fra DIFI:</p>
1825
1826 <ul>
1827
1828 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-DIFI/Epostforsendelse.pdf">Epost fra DIFI til Fornyingsdepartementet, datert 2012-11-23</a></li>
1829
1830 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-DIFI/Vedlegg%201,%20Oppsummering%20av%20h%f8ring%20om%20endringer%20i%20forskrift%20om%20IT-standarder.pdf">vedlegg 1, Oppsummering og anbefalinger etter høring av endringer i forskrift om IT-standarer i offentlig forvaltning, datert 2012-11-23</a></li>
1831
1832 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-DIFI/Vedlegg%202,%20Forslag%20til%20endringsforskrift.pdf">Vedlegg 2, Forslag til endringsforskrift, udatert</a></li>
1833
1834 <li><a href="http://www.nuug.no/pub/offentliginnsyn/from-DIFI/Vedlegg%203%20Forskrift%20om%20IT-standarder%20i%20offentlig%20forvaltning.pdf">Vedlegg 3, Forskrift om IT-standarder i offentlig forvaltning, udatert</a></li>
1835
1836 </ul>
1837
1838 <p>Det jeg synes er mest interessant er endel av aktørene som
1839 protesterte på fjerningen (Kartverket, Drammen kommune), og hvordan
1840 høringsoppsummeringen ikke tar stilling til effekten av å fjerne ODF
1841 fra katalogen.</p>
1842
1843       </div>
1844       <div class="tags">
1845
1846
1847         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
1848
1849
1850       </div>
1851     </div>
1852     <div class="padding"></div>
1853
1854     <div class="entry">
1855       <div class="title">
1856         <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>
1857       </div>
1858       <div class="date">
1859         18th March 2013
1860       </div>
1861       <div class="body">
1862         <p>I
1863 <a href="http://standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">siste
1864 høring</a> om
1865 <a href="http://standard.difi.no/forvaltningsstandarder">referansekatalogen
1866 for IT-standarder i offentlig sektor</a>, med høringsfrist 2012-09-30
1867 (DIFI-sak 2012/498), ble det foreslått å fjerne ODF som obligatorisk
1868 standard når en publiserte dokumenter som skulle kunne redigeres
1869 videre av mottaker.  NUUG og andre protesterte på forslaget, som er et
1870 langt steg tilbake når det gjelder å sikre like rettigheter for alle
1871 når en kommuniserer med det offentlige.  For noen dager siden ble jeg
1872 oppmerksom på at Direktoratet for forvaltning og IKT (DIFI) og
1873 Fornyings-,administrasjons- og kirkedepartementet (FAD) har
1874 konkludert, og oversendt forslag til regjeringen i saken. FADs
1875 dokument
1876 <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,
1877 «Utkast til endring av standardiseringsforskriften» datert 2013-02-06
1878 har følgende triste oppsummering fra høringen i saken:</p>
1879
1880 <p><blockquote>
1881 Det kom noen innvendinger på forslaget om å fjerne ODF som
1882 obligatorisk standard for redigerbare dokumenter. Innvendingene har
1883 ikke blitt ilagt avgjørende vekt.
1884 </blockquote></p>
1885
1886 <p>Ved å fjerne ODF som obligatorisk format ved publisering av
1887 redigerbare dokumenter setter en Norge tiår tilbake.  Det som vil skje
1888 er at offentlige etater går tilbake til kun å publisere dokumenter på
1889 et av de mange formatene til Microsoft Office, og alle som ikke
1890 aksepterer bruksvilkårene til Microsoft eller ikke har råd til å bruke
1891 penger på å få tilgang til Microsoft Office må igjen basere seg på
1892 verktøy fra utviklerne som er avhengig av å reversutvikle disse
1893 formatene.  I og med at ISO-spesifikasjonen for OOXML ikke komplett og
1894 korrekt spesifiserer formatene til MS Office (men er nyttige å titte i
1895 når en reversutvikler), er en tilbake til en situasjon der en ikke har
1896 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">en
1897 fri og åpen standard</a> å forholde seg til, men i stedet må springe
1898 etter Microsoft.  Alle andre leverandører enn Microsoft vil dermed ha
1899 en seriøs ulempe.  Det er som å fjerne krav om bruk av meter som
1900 måleenhet, og heretter aksepterer alle måleenheter som like gyldige,
1901 når en vet at den mest brukte enheten vil være armlengden til Steve
1902 Ballmer slik Microsoft måler den.</p>
1903
1904 <p>Jeg er ikke sikker på om forslaget er vedtatt av regjeringen ennå.
1905 Kristian Bergem hos DIFI nevnte på et møte forrige tirsdag at han
1906 trodde det var vedtatt i statsråd 8. mars, men jeg har ikke klart å
1907 finne en skriftlig kilde på regjeringen.no som bekrefter dette.
1908 Kanskje det ennå ikke er for sent...</p>
1909
1910 <p>Jeg ba i forrige uke om innsyn i dokument 6, 7 og 8 i FAD-saken, og
1911 har i dag fått innsyn i dokument 7 og 8.  Ble nektet innsyn i
1912 dokumentet med tittelen «Oppsummering av høring om endringer i
1913 forskrift om IT-standarder i offentlig forvaltning» med hjemmel i
1914 off. lovens §15.1, så det er vanskelig å vite hvordan argumentene fra
1915 høringen ble mottatt og forstått av saksbehandleren hos DIFI.  Lurer
1916 på hvordan jeg kan klage på at jeg ikke fikk se oppsummeringen.  Fikk
1917 tre PDFer tilsendt fra FAD,
1918 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/20130115%20Notat%20FAD%20-%20EHF.pdf%20(L)(889185).pdf">Endring av underversjon i EHF</a>,
1919 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/Bakgrunnsnotat%20knyttet%20til%20versjon%20av%20EHF%20standarden%20i%20Forskrift%20om%20IT-standarder%20i%20offentlig%20sektor.pdf">Bakgrunnsnotat knyttet til versjon av EHF standarden i Forskrift om IT-standarder i offentlig sektor</a> og
1920 <a href="http://www.nuug.no/pub/offentliginnsyn/from-FAD/sak-2012-2168/Utkast%20Kongelig%20resolusjon.docx%20(L)(898064).pdf">Utkast til endring av standardiseringsforskriften</a>, hvis du vil ta en titt.</p>
1921
1922       </div>
1923       <div class="tags">
1924
1925
1926         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>.
1927
1928
1929       </div>
1930     </div>
1931     <div class="padding"></div>
1932
1933     <div class="entry">
1934       <div class="title">
1935         <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>
1936       </div>
1937       <div class="date">
1938         12th February 2013
1939       </div>
1940       <div class="body">
1941         <p>Here in Norway, electronic invoices are spreading, and the
1942 <a href="http://www.anskaffelser.no/e-handel/faktura">solution promoted
1943 by the Norwegian government</a> require that invoices are sent through
1944 one of the approved facilitators, and it is not possible to send
1945 electronic invoices without an agreement with one of these
1946 facilitators.  This seem like a needless limitation to be able to
1947 transfer invoice information between buyers and sellers.  My preferred
1948 solution would be to just transfer the invoice information directly
1949 between seller and buyer, for example using SMTP, or some HTTP based
1950 protocol like REST or SOAP.  But this might also be overkill, as the
1951 "electronic" information can be transferred using paper invoices too,
1952 using a simple bar code.  My bar code encoding of choice would be QR
1953 codes, as this encoding can be read by any smart phone out there.  The
1954 content of the code could be anything, but I would go with
1955 <a href="http://en.wikipedia.org/wiki/VCard">the vCard format</a>, as
1956 it too is supported by a lot of computer equipment these days.</p>
1957
1958 <p>The vCard format support extentions, and the invoice specific
1959 information can be included using such extentions.  For example an
1960 invoice from SLX Debian Labs (picked because we
1961 <a href="http://www.linuxiskolen.no/slxdebianlabs/donations.html">ask
1962 for donations to the Debian Edu project</a> and thus have bank account
1963 information publicly available) for NOK 1000.00 could have these extra
1964 fields:</p>
1965
1966 <p><pre>
1967 X-INVOICE-NUMBER:1
1968 X-INVOICE-AMOUNT:NOK1000.00
1969 X-INVOICE-KID:123412341234
1970 X-INVOICE-MSG:Donation to Debian Edu
1971 X-BANK-ACCOUNT-NUMBER:16040884339
1972 X-BANK-IBAN-NUMBER:NO8516040884339
1973 X-BANK-SWIFT-NUMBER:DNBANOKKXXX
1974 </pre></p>
1975
1976 <p>The X-BANK-ACCOUNT-NUMBER field was proposed in a stackoverflow
1977 answer regarding
1978 <a href="http://stackoverflow.com/questions/10045664/storing-bank-account-in-vcard-file">how
1979 to put bank account information into a vCard</a>.  For payments in
1980 Norway, either X-INVOICE-KID (payment ID) or X-INVOICE-MSG could be
1981 used to pass on information to the seller when paying the invoice.</p>
1982
1983 <p>The complete vCard could look like this:</p>
1984
1985 <p><pre>
1986 BEGIN:VCARD
1987 VERSION:2.1
1988 ORG:SLX Debian Labs Foundation
1989 ADR;WORK:;;Gunnar Schjelderups vei 29D;OSLO;;0485;Norway
1990 URL;WORK:http://www.linuxiskolen.no/slxdebianlabs/
1991 EMAIL;PREF;INTERNET:sdl-styret@rt.nuug.no
1992 REV:20130212T095000Z
1993 X-INVOICE-NUMBER:1
1994 X-INVOICE-AMOUNT:NOK1000.00
1995 X-INVOICE-MSG:Donation to Debian Edu
1996 X-BANK-ACCOUNT-NUMBER:16040884339
1997 X-BANK-IBAN-NUMBER:NO8516040884339
1998 X-BANK-SWIFT-NUMBER:DNBANOKKXXX
1999 END:VCARD
2000 </pre></p>
2001
2002 <p>The resulting QR code created using
2003 <a href="http://fukuchi.org/works/qrencode/">qrencode</a> would look
2004 like this, and should be readable (and thus checkable) by any smart
2005 phone, or for example the <a href="http://zbar.sourceforge.net/">zbar
2006 bar code reader</a> and feed right into the approval and accounting
2007 system.</p>
2008
2009 <p><img src="http://people.skolelinux.org/pere/blog/images/2013-02-12-qr-invoice.png"></p>
2010
2011 <p>The extension fields will most likely not show up in any normal
2012 vCard reader, so those parts would have to go directly into a system
2013 handling invoices.  I am a bit unsure how vCards without name parts
2014 are handled, but a simple test indicate that this work just fine.</p>
2015
2016 <p><strong>Update 2013-02-12 11:30</strong>: Added KID to the proposal
2017 based on feedback from Sturle Sunde.</p>
2018
2019       </div>
2020       <div class="tags">
2021
2022
2023         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>.
2024
2025
2026       </div>
2027     </div>
2028     <div class="padding"></div>
2029
2030     <div class="entry">
2031       <div class="title">
2032         <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>
2033       </div>
2034       <div class="date">
2035         26th October 2012
2036       </div>
2037       <div class="body">
2038         <p>I work at the <a href="http://www.uio.no/">University of Oslo</a>
2039 looking after the computers, mostly on the unix side, but in general
2040 all over the place.  I am also a member (and currently leader) of
2041 <a href="http://www.nuug.no/">the NUUG association</a>, which in turn
2042 make me a member of <a href="http://www.usenix.org/">USENIX</a>.  NUUG
2043 is an member organisation for us in Norway interested in free
2044 software, open standards and unix like operating systems, and USENIX
2045 is a US based member organisation with similar targets.  And thanks to
2046 these memberships, I get all issues of the great USENIX magazine
2047 <a href="https://www.usenix.org/publications/login">;login:</a> in the
2048 mail several times a year.  The magazine is great, and I read most of
2049 it every time.</p>
2050
2051 <p>In the last issue of the USENIX magazine ;login:, there is an
2052 article by <a href="http://www.skendric.com/">Stuart Kendrick</a> from
2053 Fred Hutchinson Cancer Research Center titled
2054 "<a href="https://www.usenix.org/publications/login/october-2012-volume-37-number-5/what-takes-us-down">What
2055 Takes Us Down</a>" (longer version also
2056 <a href="http://www.skendric.com/problem/incident-analysis/2012-06-30/What-Takes-Us-Down.pdf">available
2057 from his own site</a>), where he report what he found when he
2058 processed the outage reports (both planned and unplanned) from the
2059 last twelve years and classified them according to cause, time of day,
2060 etc etc.  The article is a good read to get some empirical data on
2061 what kind of problems affect a data centre, but what really inspired
2062 me was the kind of reporting they had put in place since 2000.<p>
2063
2064 <p>The centre set up a mailing list, and started to send fairly
2065 standardised messages to this list when a outage was planned or when
2066 it already occurred, to announce the plan and get feedback on the
2067 assumtions on scope and user impact.  Here is the two example from the
2068 article: First the unplanned outage:
2069
2070 <blockquote><pre>
2071 Subject:     Exchange 2003 Cluster Issues
2072 Severity:    Critical (Unplanned)
2073 Start:       Monday, May 7, 2012, 11:58
2074 End:         Monday, May 7, 2012, 12:38
2075 Duration:    40 minutes
2076 Scope:       Exchange 2003
2077 Description: The HTTPS service on the Exchange cluster crashed, triggering
2078              a cluster failover.
2079
2080 User Impact: During this period, all Exchange users were unable to
2081              access e-mail. Zimbra users were unaffected.
2082 Technician:  [xxx]
2083 </pre></blockquote>
2084
2085 Next the planned outage:
2086
2087 <blockquote><pre>
2088 Subject:     H Building Switch Upgrades
2089 Severity:    Major (Planned)
2090 Start:       Saturday, June 16, 2012, 06:00
2091 End:         Saturday, June 16, 2012, 16:00
2092 Duration:    10 hours
2093 Scope:       H2 Transport
2094 Description: Currently, Catalyst 4006s provide 10/100 Ethernet to end-
2095              stations. We will replace these with newer Catalyst
2096              4510s.
2097 User Impact: All users on H2 will be isolated from the network during
2098              this work. Afterward, they will have gigabit
2099              connectivity.
2100 Technician:  [xxx]
2101 </pre></blockquote>
2102
2103 <p>He notes in his article that the date formats and other fields have
2104 been a bit too free form to make it easy to automatically process them
2105 into a database for further analysis, and I would have used ISO 8601
2106 dates myself to make it easier to process (in other words I would ask
2107 people to write '2012-06-16 06:00 +0000' instead of the start time
2108 format listed above).  There are also other issues with the format
2109 that could be improved, read the article for the details.</p>
2110
2111 <p>I find the idea of standardising outage messages seem to be such a
2112 good idea that I would like to get it implemented here at the
2113 university too.  We do register
2114 <a href="http://www.uio.no/tjenester/it/aktuelt/planlagte-tjenesteavbrudd/">planned
2115 changes and outages in a calendar</a>, and report the to a mailing
2116 list, but we do not do so in a structured format and there is not a
2117 report to the same location for unplanned outages.  Perhaps something
2118 for other sites to consider too?</p>
2119
2120       </div>
2121       <div class="tags">
2122
2123
2124         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/usenix">usenix</a>.
2125
2126
2127       </div>
2128     </div>
2129     <div class="padding"></div>
2130
2131     <div class="entry">
2132       <div class="title">
2133         <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>
2134       </div>
2135       <div class="date">
2136          1st October 2012
2137       </div>
2138       <div class="body">
2139         <p>Som jeg
2140 <a href="http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html">skrev
2141 i juni</a> har DIFI foreslått å fjerne krav om å bruke ODF til
2142 utveksling av redigerbare dokumenter med det offentlige, og
2143 derigjennom tvinge innbyggerne til å forholde seg til formatene til MS
2144 Office når en kommuniserer med det offentlige.</p>
2145
2146 <p>I går kveld fikk vi i <a href="http://www.nuug.no/">NUUG</a>
2147 fullført vår høringsuttalelse og sendt den inn til DIFI.  Du finner
2148 <a href="http://wiki.nuug.no/uttalelser/201209-forskrift-standardkatalog">uttalelsen
2149 på wikien</a>.  Ta en titt.  Fristen for å sende inn uttalelse var i
2150 går søndag, men en får kanskje sitt innspill med hvis en sender i
2151 dag.</p>
2152
2153       </div>
2154       <div class="tags">
2155
2156
2157         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>.
2158
2159
2160       </div>
2161     </div>
2162     <div class="padding"></div>
2163
2164     <div class="entry">
2165       <div class="title">
2166         <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>
2167       </div>
2168       <div class="date">
2169         23rd August 2012
2170       </div>
2171       <div class="body">
2172         <p>I came across a great comment from Simon Phipps today, about how
2173 <a href="http://www.infoworld.com/d/open-source-software/how-microsoft-was-forced-open-office-200233">Microsoft
2174 have been forced to open Office</a>, and it made me remember and
2175 revisit the great site
2176 <a href="http://www.officeshots.org/">officeshots</a> which allow you
2177 to check out how different programs present the ODF file format.  I
2178 recommend both to those of my readers interested in ODF. :)</p>
2179
2180       </div>
2181       <div class="tags">
2182
2183
2184         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>.
2185
2186
2187       </div>
2188     </div>
2189     <div class="padding"></div>
2190
2191     <div class="entry">
2192       <div class="title">
2193         <a href="http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html">OOXML og standardisering</a>
2194       </div>
2195       <div class="date">
2196         25th July 2012
2197       </div>
2198       <div class="body">
2199         <p>DIFI har
2200 <a href="http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html">en
2201 høring gående</a> om ny versjon av statens standardkatalog, med frist
2202 2012-09-30, der det foreslås å fjerne ODF fra katalogen og ta inn ISO
2203 OOXML.  I den anledning minnes jeg
2204 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">notatet
2205 FAD skrev</a> da versjon 2 av standardkatalogen var under
2206 utarbeidelse, da FAD og DIFI fortsatt forsto poenget med og verdien av
2207 frie og åpne standarder.</p>
2208
2209 <p>Det er mange som tror at OOXML er ett spesifikt format, men det
2210 brukes ofte som fellesbetegnelse for både formatet spesifisert av
2211 ECMA, ISO, og formatet produsert av Microsoft Office (aka docx), som
2212 dessverre ikke er det samme formatet.  Fra en av de som implementerte
2213 støtte for docx-formatet i KDE fikk jeg høre at ISO-spesifikasjonen
2214 var en nyttig referanse, men at det var mange avvik som gjorde at en
2215 ikke kunne gå ut ifra at Microsoft Office produserte dokumenter i
2216 henhold til ISO-spesifikasjonen.</p>
2217
2218 <p>ISOs OOXML-spesifikasjon har (eller hadde, usikker på om
2219 kommentaren er oppdatert) i følge
2220 <a href="http://surguy.net/articles/ooxml-validation-and-technical-review.xml">Inigo
2221 Surguy</a> feil i mer enn 10% av eksemplene, noe som i tillegg gjør
2222 det vanskelig å bruke spesifikasjonen til å implementere støtte for
2223 ISO OOXML.  Jeg har ingen erfaring med å validere OOXML-dokumenter
2224 selv, men ser at
2225 <a href="http://www.microsoft.com/en-us/download/details.aspx?id=5124">Microsoft
2226 har laget en validator</a> som jeg ikke kan teste da den kun er
2227 tilgjengelig på MS Windows.  Finner også en annen kalt
2228 <a href="http://code.google.com/p/officeotron/">Office-O-Tron</A> som
2229 er oppdatert i fjor.  Lurer på om de validerer at dokumenter er i
2230 formatet til Microsoft office, eller om de validerer at de er i
2231 henhold til formatene spesifisert av ECMA og ISO. Det hadde også vært
2232 interessant å se om docx-dokumentene publisert av det offentlige er
2233 gyldige ISO OOXML-dokumenter.</p>
2234
2235       </div>
2236       <div class="tags">
2237
2238
2239         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>.
2240
2241
2242       </div>
2243     </div>
2244     <div class="padding"></div>
2245
2246     <div class="entry">
2247       <div class="title">
2248         <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>
2249       </div>
2250       <div class="date">
2251          5th July 2012
2252       </div>
2253       <div class="body">
2254         <p>I føljetongen om H.264
2255 <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
2256 jeg leserne i undring</a> om hvor pakken fra MPEG-LA tok veien, og om
2257 hvilke selskaper i Norge som har avtale med MPEG-LA.  Da Ryan hos
2258 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
2259 og dagen etter fikk jeg følgende svar derfra:</p>
2260
2261 <p><blockquote>
2262 <p>Date: Fri, 29 Jun 2012 18:32:34 +0000
2263 <br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
2264 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2265 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2266 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
2267
2268 <p>Dear Mr. Reinholdtsen,</p>
2269
2270 <p>Thank you for your message. As you know, Ryan is currently our of the
2271 office, so it will be my pleasure to assist you.</p>
2272
2273 <p>Per your request, attached please find an electronic copy of the
2274 AVC Patent Portfolio License. Please note that the electronic copy of
2275 the License is provided as a convenience and for informational
2276 purposes only. When concluding the Licenses, only the hard copies
2277 provided by MPEG LA may be used.</p>
2278
2279 <p>To your question, MPEG LA lists our Licensees on our website
2280 according to each program.  The lists are in alphabetical order, so it
2281 is very easy to search.</p>
2282
2283 <p>I hope that this was helpful. If we can be of additional
2284 assistance, please let me know.</p>
2285
2286 <p>Kind regards,</p>
2287
2288 <p>Sidney A. Wolf
2289 <br>Manager, Global Licensing
2290 <br>MPEG LA</p>
2291 </blockquote></p>
2292
2293 <p>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
2294 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
2295 som må deles på individuell basis.  Opphavsretten krever godkjenning
2296 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
2297 opp med et spørsmål om dette var greit.</p>
2298
2299 <p><blockquote>
2300 <p>Date: Wed, 4 Jul 2012 20:25:06 +0200
2301 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2302 <br>To: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
2303 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2304 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
2305
2306 <p>Thank you for your reply.</p>
2307
2308 <p>[Sidney Wolf]
2309 <br>&gt; Per your request, attached please find an electronic copy of the AVC
2310 <br>&gt; Patent Portfolio License. Please note that the electronic copy of
2311 <br>&gt; the License is provided as a convenience and for informational
2312 <br>&gt; purposes only. When concluding the Licenses, only the hard copies
2313 <br>&gt; provided by MPEG LA may be used.</p>
2314
2315 <p>This is useful for me to learn, but the reason I asked for the
2316 Internet address of the licensing document was to ensure I could
2317 publish a link to it when I discuss the topic of H.264 licensing here
2318 in Norway, and allow others to verify my observations.  I can not do
2319 the same with an email attachment.  Thus I would like to ask you if it
2320 is OK with MPEG LA that I publish this document on the Internet for
2321 others to read?</p>
2322
2323 <p>&gt; To your question, MPEG LA lists our Licensees on our website
2324 <br>&gt; according to each program. The lists are in alphabetical order, so
2325 <br>&gt; it is very easy to search.</p>
2326
2327 <p>I am afraid this do not help me locate Norwegian companies in the
2328 list of Licensees.  I do not know the name of all companies and
2329 organisations in Norway, and thus do not know how to locate the
2330 Norwegian ones on that list.</p>
2331
2332 <p>&gt; I hope that this was helpful. If we can be of additional assistance,
2333 <br>&gt; please let me know.</p>
2334
2335 <p>Absoutely helpful to learn more about how MPEG LA handle licensing.</p>
2336
2337 <p>--
2338 <br>Happy hacking
2339 <br>Petter Reinholdtsen</p>
2340 </blockquote></p>
2341
2342 <p>Jeg håpet også at det skulle være mulig å få vite hvilke av de
2343 mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
2344 i Norge.  Begge mine håp falt i grus med svaret fra MPEG-LA.
2345
2346 <p><blockquote>
2347 <p>Date: Thu, 5 Jul 2012 17:42:39 +0000
2348 <br>From: Sidney Wolf &lt;SWolf (at) mpegla.com&gt;
2349 <br>To: 'Petter Reinholdtsen' &lt;pere (at) hungry.com&gt;
2350 <br>Cc: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2351 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
2352
2353 <p>Dear Mr. Reinholdtsen,</p>
2354
2355 <p>Thank you for your reply.</p>
2356
2357 <p>We appreciate the additional explanation you have provided and for
2358 asking our permission to publish the electronic copy of the License in
2359 advance of doing so.  Typically, MPEG LA prefers to distribute the
2360 electronic copies of our Licenses to interested parties. Therefore,
2361 please feel free to send interested parties to the AVC portion of our
2362 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
2363 their further reference.</p>
2364
2365 <p>As previously mentioned, MPEG LA maintains a list of Licensees in good
2366 standing on our website according to each program. Due to the large
2367 volume of Licensees, it would be administratively impractical to
2368 provide this level of detail to interested parties.  Therefore, I am
2369 afraid we are not in a position to assist you with your request.</p>
2370
2371 <p>Kind regards,</p>
2372
2373 <p>Sidney A. Wolf
2374 <br>Manager, Global Licensing
2375 <br>MPEG LA</p>
2376 </blockquote></p>
2377
2378 <p>Men takket være epostvedlegget kunne jeg søke på Google etter
2379 setningen "WHEREAS, a video standard commonly referred to as AVC has
2380 been defined and is referred to in this Agreement as the “AVC
2381 Standard” (as more fully defined herein below)" som finnes i avtalen,
2382 og lokalisere en kopi fra 2007 av
2383 <a href="http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm">lisensavtalen
2384 mellom MPEG-LA og DivX, Inc.</a>, slik at mine lesere kan se hvordan
2385 avtalen så ut da.  Jeg har ikke sammenlignet tekstene for å se om noe
2386 har endret seg siden den tid, men satser på at teksten er representativ.</p>
2387
2388 <p>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
2389 MPEG-LA.</p>
2390
2391 <p>Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
2392 klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
2393 interessant bloggpost fra 2010 hos LibreVideo med tittelen
2394 "<a href="http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/">MPEG-LA
2395 answers some questions about AVC/H.264 licensing</a>.  Anbefales!</p>
2396
2397       </div>
2398       <div class="tags">
2399
2400
2401         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
2402
2403
2404       </div>
2405     </div>
2406     <div class="padding"></div>
2407
2408     <div class="entry">
2409       <div class="title">
2410         <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>
2411       </div>
2412       <div class="date">
2413         29th June 2012
2414       </div>
2415       <div class="body">
2416         <p>DIFI har nettopp annonsert høring om revisjon av
2417 <a href="http://www.standard.difi.no/forvaltningsstandarder">standardkatalogen</a>,
2418 og endelig har Microsoft fått viljen sin.  Se
2419 <a href="http://www.standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">høringssiden</a>
2420 for hele teksten.</p>
2421
2422 <p>Her er forslaget i sin helhet:</p>
2423
2424 <p><blockquote>
2425 <p>3.2 Revisjon av krav til redigerbare dokumenter</p>
2426
2427 <p>I første versjon av referansekatalogen i 2007 ble det satt krav om
2428 Open Document Format (ODF), versjon 1.1 (OASIS, 1.2.2007) for
2429 redigerbare dokumenter. Kravet var obligatorisk for stat og sterkt
2430 anbefalt for kommunal sektor. I 2009 ble kravet gjort obligatorisk for
2431 hele offentlig sektor i
2432 <a href="http://www.lovdata.no/for/sf/fa/xa-20090925-1222.html">forskrift
2433 om IT-standarder i forvaltningen</a>. Anvendelsesområdet for kravet
2434 har vært begrenset til publisering av dokumenter som skal bearbeides
2435 videre (§ 4 nr. 1 andre ledd). I 2011 ble anvendelsesområdet utvidet
2436 til å omfatte utveksling av dokumenter beregnet for redigering som
2437 vedlegg til e-post (§4 nr.  2).</p>
2438
2439 <p>Office Open XML ISO/IEC 29500:2011 (OOXML) er et dokumentformat
2440 opprinnelig utviklet av Microsoft med tilsvarende anvendelsesområde
2441 som ODF. Formatet er blant annet tatt i bruk i nyere versjoner av
2442 kontorstøtteprogamvaren MS Office.  Difi har foretatt en
2443 <a href="http://www.standard.difi.no/filearchive/revisjonsvurdering-standarder-for-redigerbare-dokumenter-v1-0.pdf">revisjonsvurdering</a>
2444 av krav som stilles til redigerbare dokumenter i Forskrift om
2445 IT-standarder i forvaltningen, og anbefaler at kravet til ODF
2446 fjernes. Dette innebærer at det ikke stilles krav til dokumentformater
2447 for redigerbare dokumenter ved publisering på offentlige virksomheters
2448 nettsider og for redigerbare vedlegg til e-post som sendes fra
2449 offentlige virksomheter til innbyggere og næringsliv. Offentlige
2450 virksomheter vil dermed stå fritt til å publisere eller sende
2451 redigerbare dokumenter i det format som ivaretar brukernes behov
2452 best.</p>
2453
2454 <p>Forslaget innebærer at krav til ODF utgår § 4 nr. 1 tredje ledd og
2455 § 4 nr. 2 første ledd</p>
2456
2457 <P>Imidlertid bør det stilles strengere krav til hvilke formater
2458 offentlige virksomheter plikter å motta redigerbare dokumenter. Vi
2459 mener at det ikke bør skilles mellom mottak av redigerbare dokumenter
2460 som sendes i ODF eller OOXML3, som begge er åpne standarder. Dette
2461 medfører at innbyggere og næringsliv skal kunne basere sitt valg av
2462 programvare på egne behov og ikke på de valg offentlige virksomheter
2463 tar. Kravet vil omfatte hele offentlig sektor, herunder
2464 utdanningssektoren, hvor det kanskje er størst bruk av ODF. Kravet er
2465 foreslått som ny § 4 nr.2 andre ledd</p>
2466 </blockquote></p>
2467
2468 <P>De satser vel på at det hele blir glemt over sommeren, og at de
2469 fleste har glemt Standard Norge og ISOs fallitt fra da OOXML ble
2470 jukset igjennom som ISO-standard.  Jeg håper mine lesere sender inn
2471 høringsuttalelser til høringen.</p>
2472
2473 <p>Anbefaler alle å friske opp sine argumenter ved å lese
2474 <a href="http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html">svaret
2475 fra senator Edgar Villanueva til Microsoft i Peru</a>.  Det er en
2476 klassisk tekst som er like gyldig i dag som da det ble skrevet.</p>
2477
2478
2479       </div>
2480       <div class="tags">
2481
2482
2483         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>.
2484
2485
2486       </div>
2487     </div>
2488     <div class="padding"></div>
2489
2490     <div class="entry">
2491       <div class="title">
2492         <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>
2493       </div>
2494       <div class="date">
2495         29th June 2012
2496       </div>
2497       <div class="body">
2498         <p>Da fikk jeg nettopp svar fra
2499 <a href="http://www.dss.dep.no/">Departementenes servicesenter</a>
2500 (DSS) på
2501 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">mitt
2502 spørsmål om avtale rundt bruk av H.264</a>.  De har ingen avtale med
2503 MPEG LA eller dets representanter.  Her er svaret.
2504
2505 <p><blockquote>
2506
2507 <p>Date: Fri, 29 Jun 2012 07:04:42 +0000
2508 <br>From: Nielsen Mette Haga &lt;Mette-Haga.Nielsen (at) dss.dep.no&gt;
2509 <br>To: Petter Reinholdtsen &lt;petter.reinholdtsen (at) ...&gt;
2510 <br>CC: Postmottak &lt;Postmottak (at) dss.dep.no&gt;
2511 <br>Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler</p>
2512
2513 <p>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
2514 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
2515 levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
2516 vår avtale med Smartcom.</p>
2517
2518 <p>Vennlig hilsen</p>
2519
2520 <p>Mette Haga Nielsen
2521 <br>Fung. seksjonssjef</p>
2522
2523 <p>Departementenes servicesenter</p>
2524
2525 <p>Informasjonsforvaltning
2526
2527 <p>Mobil 93 09 83 51
2528 <br>E-post mette-haga.nielsen (at) dss.dep.no</p>
2529 </blockquote></p>
2530
2531 <p>Hvis den norske regjeringen representert ved DSS ikke har slik
2532 avtale, så kan en kanskje konkludere med at det ikke trengs?  Jeg er
2533 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
2534 minste interessant å vite at hverken NRK eller DSS har funnet det
2535 nødvendig å ha avtale om bruk av H.264.</p>
2536
2537 <p>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
2538 til bruk av opphavsrettsbeskyttet materiale de bruker til
2539 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
2540 privatpersoner i Norge.  Har de lov til å bryte vilkårene, eller har
2541 de brutt dem og så langt sluppet unna med det?  Jeg aner ikke.</p>
2542
2543       </div>
2544       <div class="tags">
2545
2546
2547         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
2548
2549
2550       </div>
2551     </div>
2552     <div class="padding"></div>
2553
2554     <div class="entry">
2555       <div class="title">
2556         <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>
2557       </div>
2558       <div class="date">
2559         28th June 2012
2560       </div>
2561       <div class="body">
2562         <p>Etter at NRK
2563 <a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">nektet
2564 å spore opp eventuell avtale med MPEG-LA</a> eller andre om bruk av
2565 MPEG/H.264-video etter at jeg <a
2566 href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">ba
2567 om innsyn i slike avtaler</a>, tenkte jeg at i stedet for å forsøke å
2568 få NRK til å finne en slik avtale, så burde det være like enkelt å
2569 spørre MPEG-LA om de hadde avtale med NRK.  Spørsmålet ble sendt før
2570 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
2571 "in Good Standing" befant seg.  MPEG-LA svarte meg i dag, og kan
2572 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
2573 slått fast.  Ikke overraskende mener MPEG-LA at det trengs en avtale
2574 med MPEG-LA for å streame H.264, men deres rammer er jo
2575 rettstilstanden i USA og ikke Norge.  Jeg tar dermed den delen av
2576 svaret med en klype salt.  Jeg er dermed fortsatt ikke klok på om det
2577 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
2578 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
2579 gjør at de ikke trenger avtale direkte med MPEG-LA.  Jeg håper NRKs
2580 jurister har vurdert dette, og at det er mulig å få tilgang til
2581 vurderingen uansett om de trenger en avtale eller ikke.</p>
2582
2583 <p>Her er epostutvekslingen med MPEG-LA så langt.  Håper ikke
2584 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
2585 MPEG-LA.</p>
2586
2587 <p><blockquote>
2588 <p>Date: Mon, 25 Jun 2012 15:29:37 +0200
2589 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2590 <br>To: licensing-web (at) mpegla.com
2591 <br>Subject: Do NRK have a license agreement with MPEG-LA?</p>
2592
2593 <p>Hi.  I have a small question for you, that I hope it is OK that I
2594 ask.</p>
2595
2596 <p>Is there any license agreements between MPEG-LA and NRK, &lt;URL:
2597 <a href="http://www.nrk.no/">http://www.nrk.no/</a> &gt;, the
2598 Norwegian national broadcasting cooperation?  I am not sure if they
2599 need one, and am just curious if such agreeement exist.</p>
2600
2601 <p>The postal address is</p>
2602
2603 <p><blockquote>
2604   NRK
2605   <br>Postbox 8500, Majorstuen
2606   <br>0340 Oslo
2607   <br>Norway
2608 </blockquote></p>
2609
2610 <p>if it make it easier for you to locate such agreement.</p>
2611
2612 <p>Can you tell me how many entities in Norway have an agreement with
2613 MPEG-LA, and the name of these entities?</p>
2614
2615 <p>--
2616 <br>Happy hacking
2617 <br>Petter Reinholdtsen
2618 </blockquote></p>
2619
2620 <p>I dag, to dager senere, fikk jeg følgende svar:</p>
2621
2622 <p><blockquote>
2623 <p>Date: Thu, 28 Jun 2012 14:11:17 +0000
2624 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com>
2625 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com>
2626 <br>CC: MD Administration &lt;MDAdministration (at) mpegla.com>
2627 <br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
2628
2629 <p>Dear Mr. Reinholdtsen,</p>
2630
2631 <p>Thank you for your message and for your interest in MPEG LA. We
2632 appreciate hearing from you and I will be happy to assist you.</p>
2633
2634 <p>To begin, I will assume that you are referring to AVC/H.264
2635 technology in your message below, as this technology is commonly used
2636 in the transmission of video content.  In that case, please allow me
2637 to briefly summarize the coverage provided by our AVC Patent Portfolio
2638 License.</p>
2639
2640 <P>Our AVC License provides coverage for end products and video
2641 services that make use of AVC/H.264 technology.  Accordingly, the
2642 party offering such end products and video to End Users concludes the
2643 AVC License and is responsible for paying the applicable royalties
2644 associated with the end products/video they offer.</p>
2645
2646 <p>While the Norwegian Broadcast Corporation (NRK) is not currently a
2647 Licensee to MPEG LA's AVC License (or any other Portfolio License
2648 offered by MPEG LA), if NRK offers AVC Video to End Users for
2649 remuneration (for example, Title-by-Title, Subscription, Free
2650 Television, or Internet Broadcast AVC Video), then NRK will need to
2651 conclude the AVC License and may be responsible for paying applicable
2652 royalties associated with the AVC Video it distributes.</p>
2653
2654 <p>Today I will send you a FedEx package containing a copy of our AVC
2655 License for your review.  You should receive the License document
2656 within the next few days.</p>
2657
2658 <p>Meanwhile, MPEG LA currently has several Norwegian Licensees that
2659 can be found under the "Licensees" header within the respective
2660 portion of our website.  For example, you may find our list of
2661 Licensees in Good Standing to our AVC License in the AVC portion of
2662 our website,
2663 <a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</a></p>
2664
2665 <p>I hope the above information is helpful.  If you have additional
2666 questions or need further assistance with the AVC License, please feel
2667 free to contact me directly.  I look forward to hearing from you again
2668 soon.</p>
2669
2670 <p>Best regards,</p>
2671
2672 <p>Ryan</p>
2673
2674 <p>Ryan M. Rodriguez
2675 <br>Licensing Associate
2676 <br>MPEG LA
2677 <br>5425 Wisconsin Avenue
2678 <br>Suite 801
2679 <br>Chevy Chase, MD 20815
2680 <br>U.S.A.
2681 <br>Phone:  +1 (301) 986-6660 x211
2682 <br>Fax:    +1 (301) 986-8575
2683 <br>Email: rrodriguez (at) mpegla.com</p>
2684
2685 </blockquote></p>
2686
2687 <p>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
2688 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
2689 da han jo ikke hadde fått noen postadresse som nådde meg.</p>
2690
2691 <p><blockquote>
2692
2693 <p>Date: Thu, 28 Jun 2012 16:36:15 +0200
2694 <br>From: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2695 <br>To: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2696 <br>Cc: MD Administration &lt;MDAdministration (at) mpegla.com&gt;
2697 <br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
2698
2699 <p>[Ryan Rodriguez]
2700 <br>&gt; Dear Mr. Reinholdtsen,</p>
2701
2702 <p>Thank you for your quick reply.</p>
2703
2704 <p>&gt; Today I will send you a FedEx package containing a copy of our AVC
2705 <br>&gt; License for your review.  You should receive the License document
2706 <br>&gt; within the next few days.</p>
2707
2708 <p>The part about sending a FedEx package confused me, though.  I did not
2709 <br>give you my address, nor am I associated with NRK in any way, so I hope
2710 <br>you did not try to send me a package using the address of NRK.  If you
2711 <br>would send me the Internet address of to the document, it would be more
2712 <br>useful to me to be able to download it as an electronic document.</p>
2713
2714 <p>&gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
2715 <br>&gt; be found under the "Licensees" header within the respective portion
2716 <br>&gt; of our website.  For example, you may find our list of Licensees in
2717 <br>&gt; Good Standing to our AVC License in the AVC portion of our website,
2718 <br>&gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</p>
2719
2720 <p>How can I recognize the Norwegian licensees?</p>
2721
2722 <p>--
2723 <br>Happy hacking
2724 <br>Petter Reinholdtsen</p>
2725 </blockquote></p>
2726
2727 <p>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
2728 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
2729 siste epost.  Får håpe noen likevel følger opp "FedEx-pakken".  For å
2730 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
2731 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
2732 Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
2733 min epost tidsnok.</p>
2734
2735 <p><blockquote>
2736
2737 <p>Date: Thu, 28 Jun 2012 14:36:20 +0000
2738 <br>From: Ryan Rodriguez &lt;RRodriguez (at) mpegla.com&gt;
2739 <br>To: Petter Reinholdtsen &lt;pere (at) hungry.com&gt;
2740 <br>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?</p>
2741
2742 <p>Thank you for your message.</p>
2743
2744 <p>I will be out of the office until Thursday, July 5 and will respond
2745 to all messages upon my return.  If this is a matter that requires
2746 immediate attention, please contact Sidney Wolf (swolf (at)
2747 mpegla.com)</p>
2748
2749 <p>Best regards,</p>
2750
2751 <p>Ryan</p>
2752
2753 <p>Ryan M. Rodriguez
2754 <br>Licensing Associate
2755 <br>MPEG LA</p>
2756
2757 </blockquote></p>
2758
2759 <p>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
2760 som er om en trenger avtale med MPEG-LA for å publisere eller
2761 kringkaste H.264-video i Norge.</p>
2762
2763       </div>
2764       <div class="tags">
2765
2766
2767         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
2768
2769
2770       </div>
2771     </div>
2772     <div class="padding"></div>
2773
2774     <div class="entry">
2775       <div class="title">
2776         <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>
2777       </div>
2778       <div class="date">
2779         25th June 2012
2780       </div>
2781       <div class="body">
2782         <p>Jeg fikk nettopp svar fra NRK på
2783 <a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">min
2784 forespørsel om kopi av avtale</a> med MPEG-LA eller andre om bruk av
2785 MPEG og/eller H.264.  Svaret har fått saksreferanse 2011/371 (mon tro
2786 hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:</p>
2787
2788 <p><blockquote>
2789
2790 <p><strong>Svar på innsynsbegjæring i MPEG / H.264-relaterte
2791 avtaler</strong></p>
2792
2793 <p>Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
2794 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
2795 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
2796 H.264».</p>
2797
2798 <p>I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
2799 en bestemt sak eller i rimelig utstrekning saker av en bestemt
2800 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
2801 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
2802 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
2803 står følgende:</p>
2804
2805 <p>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
2806 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
2807 at den enkelte saka blir identifisert.  Ein kan med andre ord i
2808 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
2809 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
2810 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
2811 til dato, partar eller liknande.»</p>
2812
2813 <p>Vedrørende denne begrensningen har Justisdepartementet uttalt
2814 følgende (Lovavdelingens uttalelser JDLOV-2010-3295):</p>
2815
2816 <p><em>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
2817 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
2818 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
2819 vanskelege å handsame for forvaltninga.»</em></p>
2820
2821 <p>I samme sak uttaler Lovavdelingen følgende:</p>
2822
2823 <p><em>«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
2824 rimeleg utstrekning' kan krevjast innsyn i `saker av ein bestemt
2825 art'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning' kan
2826 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
2827 arbeidskrevjande det vil vere å finne fram til dei aktuelle
2828 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
2829 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
2830 mange dokument) at arbeidsmengda som ville gått med til å handsame
2831 det, er større enn det ein `i rimeleg utstrekning' kan krevje (sjølv
2832 om det nok skal mykje til).»</em></p>
2833
2834 <p>NRK har ikke noen egen sammenstilling over avtaler innenfor
2835 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
2836 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
2837 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
2838 gjelder for utstyr som bruker MPEG og/eller H.264». En slik
2839 gjennomgang av avtaler måtte gjøres manuelt av en person med
2840 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
2841 ressurser for å finne frem relevante avtaler og for deretter å vurdere
2842 om de dekkes av det innsynsbegjæringen omfattes.</p>
2843
2844 <p>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
2845 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
2846 vil være langt større enn det som i rimelig utstrekning kan kreves i
2847 henhold til offentleglova § 28 annet ledd.</p>
2848
2849 <p>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
2850 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
2851 frem til mottakeren, i henhold til reglene i offentleglova § 32,
2852 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
2853 kirkedepartementet, og sendes til NRK.</p>
2854
2855 <p>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
2856 slik at en eventuell søknad om innsyn kan tydeligere identifisere
2857 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
2858 for inneværende og forrige måned ligger ute på
2859 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
2860 på forespørsel til innsyn (at) nrk.no.</p>
2861
2862 <p>Med hilsen
2863 <br>Dokumentarkivet i NRK
2864 <br>v/ Elin Brandsrud
2865 <br>Tel. direkte: 23 04 29 29
2866 <br>Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
2867 <br>innsyn (at) nrk.no</p>
2868
2869 </blockquote></p>
2870
2871 <p>Svaret kom
2872 <a href="http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf">i
2873 PDF-form som vedlegg på epost</a>.  Jeg er litt usikker på hvordan jeg
2874 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
2875 på å vurdere om jeg skal klage.  Enten må nok forespørselen
2876 reformuleres eller så må jeg vel klage.  Synes jo det er merkelig at
2877 NRK ikke har bedre kontroll med hvilke avtaler de har inngått.  Det
2878 burde jo være noen i ledelsen som vet om de har signert en avtale med
2879 MPEG-LA eller ikke...</p>
2880
2881 <p>Oppdatering 2012-06-25 20:20: Et google-søk på "2011/371 nrk"
2882 sendte meg til postjournalen for
2883 <a href="http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf">2012-06-19</a>
2884 og
2885 <a href="http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf">2012-06-20</a>
2886 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
2887 er "Graphic Systems Regions MA 2378/10E".  Videre søk etter "Graphic
2888 Systems Regions" viser at dette er saken til et anbud om
2889 "<a href="http://no.mercell.com/m/mts/Tender/27179412.aspx">a graphics
2890 system for 12 or 13 sites broadcasting regional news</a>" hos Mercell
2891 Sourcing Service, også omtalt på
2892 <a href="http://www.publictenders.net/tender/595705">Public
2893 Tenders</a> og
2894 <a href="http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521">Doffin</a>.
2895 Jeg er dog usikker på hvordan dette er relatert til min
2896 forespørsel.</p>
2897
2898 <p>Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
2899 miljøet rundt
2900 <a href="http://code.google.com/p/open-broadcast-encoder/">Open
2901 Broadcast Encoder</a>, at listen over de som har lisensavtale med
2902 MPEG-LA er
2903 <a href="http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx">tilgjengelig
2904 på web</a>.  Veldig fint å oppdage hvor den finnes, da jeg må ha lett
2905 etter feil ting da jeg forsøke å finne den.  Der står ikke NRK, men
2906 flere andre "Broadcasting Company"-oppføringer.  Lurer på om det betyr
2907 at NRK ikke trenger avtale, eller noe helt annet?</p>
2908
2909       </div>
2910       <div class="tags">
2911
2912
2913         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
2914
2915
2916       </div>
2917     </div>
2918     <div class="padding"></div>
2919
2920     <div class="entry">
2921       <div class="title">
2922         <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>
2923       </div>
2924       <div class="date">
2925         21st June 2012
2926       </div>
2927       <div class="body">
2928         <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
2929 distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
2930 <a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
2931 fri og åpen standard</a> i henhold til
2932 <a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
2933 til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
2934 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
2935 gjelder Norge.  Det ser uansett ut til å være en juridisk interessant
2936 problemstilling.  Men jeg tenkte her om dagen som så, at hvis det er
2937 nødvendig, så har store aktører som
2938 <a href="http://www.nrk.no/">NRK</a> og
2939 <a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
2940 slik avtale.  Jeg har derfor sendt forespørsel til begge (for
2941 regjeringen sin del er det Departementenes Servicesenter som gjør
2942 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
2943 og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
2944 av MPEG-LA.  Her er kopi av eposten jeg har sendt til
2945 <a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
2946 Forespørselen til NRK er veldig lik.</p>
2947
2948 <p><blockquote>
2949
2950 <p>Date: Tue, 19 Jun 2012 15:18:33 +0200
2951 <br>From: Petter Reinholdtsen
2952 <br>To: postmottak@dss.dep.no
2953 <br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
2954
2955 <p>Hei.  Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
2956 til avtaler rundt bruk av videoformatene MPEG og H.264.  Jeg er
2957 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
2958 eller noen som representerer MPEG-LA i Norge.</p>
2959
2960 <p>MPEG og H.264 er videoformater som brukes både til kringkasting
2961 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
2962 via Adobe Flash.  MPEG-LA, &lt;URL:
2963 <a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> &gt;, er
2964 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
2965 av immaterielle rettigheter knyttet til MPEG og H.264, å selge
2966 bruksrett for MPEG og H.264.</p>
2967
2968 <p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
2969 videoformater, og dette ser ut til å være organisert av DSS.  Jeg
2970 antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
2971
2972 <p>F.eks. har Adobe Premiere Pro har følgende klausul i følge &lt;URL:
2973 <a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
2974 &gt;:</p>
2975
2976 <p><blockquote>
2977
2978   <p>6.17. AVC DISTRIBUTION. The following notice applies to software
2979   containing AVC import and export functionality: THIS PRODUCT IS
2980   LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
2981   NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
2982   WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
2983   WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
2984   ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
2985   LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
2986   IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
2987   FROM MPEG LA L.L.C. SEE
2988   <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
2989
2990 </blockquote></p>
2991
2992 <p>Her er det kun "non-commercial" og "personal and non-commercial"
2993 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
2994
2995 <p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
2996 følgende klausul i følge &lt;URL:
2997 <a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
2998 &gt;:</p>
2999
3000 <p><blockquote>
3001
3002   <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
3003   funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
3004   kommersiell bruk ekstra lisensiering og følgende gjelder:
3005   AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
3006   FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
3007   KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
3008   OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
3009   PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
3010   FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
3011   AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
3012   FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
3013 </blockquote></p>
3014
3015 <p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
3016 bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
3017 til å bruke programmet/utstyret hvis en skal lage noe annet enn
3018 private filmer og i ikke-kommersiell virksomhet.</p>
3019
3020 <p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
3021 ikke er begrenset av de generelle bruksvilkårene som gjelder for
3022 utstyr som bruker MPEG og/eller H.264.</p>
3023 </blockquote></p>
3024
3025 <p>Nå venter jeg spent på svaret.  Jeg planlegger å blogge om svaret
3026 her.</p>
3027
3028       </div>
3029       <div class="tags">
3030
3031
3032         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
3033
3034
3035       </div>
3036     </div>
3037     <div class="padding"></div>
3038
3039     <div class="entry">
3040       <div class="title">
3041         <a href="http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html">The cost of ODF and OOXML</a>
3042       </div>
3043       <div class="date">
3044         26th May 2012
3045       </div>
3046       <div class="body">
3047         <p>I just come across a blog post from Glyn Moody reporting the
3048 claimed cost from Microsoft on requiring ODF to be used by the UK
3049 government.  I just sent him an email to let him know that his
3050 assumption are most likely wrong.  Sharing it here in case some of my
3051 blog readers have seem the same numbers float around in the UK.</p>
3052
3053 <p><blockquote> <p>Hi.  I just noted your
3054 <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>
3055 comment:</p>
3056
3057 <p><blockquote>"They're all in Danish, not unreasonably, but even
3058 with the help of Google Translate I can't find any figures about the
3059 savings of "moving to a flexible two standard" as claimed by the
3060 Microsoft email. But I assume it is backed up somewhere, so let's take
3061 it, and the £500 million figure for the UK, on trust."
3062 </blockquote></p>
3063
3064 <p>I can tell you that the Danish reports are inflated.  I believe it is
3065 the same reports that were used in the Norwegian debate around 2007,
3066 and Gisle Hannemyr (a well known IT commentator in Norway) had a look
3067 at the content.  In short, the reason it is claimed that using ODF
3068 will be so costly, is based on the assumption that this mean every
3069 existing document need to be converted from one of the MS Office
3070 formats to ODF, transferred to the receiver, and converted back from
3071 ODF to one of the MS Office formats, and that the conversion will cost
3072 10 minutes of work time for both the sender and the receiver.  In
3073 reality the sender would have a tool capable of saving to ODF, and the
3074 receiver would have a tool capable of reading it, and the time spent
3075 would at most be a few seconds for saving and loading, not 20 minutes
3076 of wasted effort.</p>
3077
3078 <p>Microsoft claimed all these costs were saved by allowing people to
3079 transfer the original files from MS Office instead of spending 10
3080 minutes converting to ODF. :)</p>
3081
3082 <p>See
3083 <a href="http://hannemyr.com/no/ms12_vl02.php">http://hannemyr.com/no/ms12_vl02.php</a>
3084 and
3085 <a href="http://hannemyr.com/no/ms12.php">http://hannemyr.com/no/ms12.php</a>
3086 for background information.  Norwegian only, sorry. :)</p>
3087 </blockquote></p>
3088
3089       </div>
3090       <div class="tags">
3091
3092
3093         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>.
3094
3095
3096       </div>
3097     </div>
3098     <div class="padding"></div>
3099
3100     <div class="entry">
3101       <div class="title">
3102         <a href="http://people.skolelinux.org/pere/blog/OpenOffice_org_fungerer_da_fint_for_blinde_.html">OpenOffice.org fungerer da fint for blinde?</a>
3103       </div>
3104       <div class="date">
3105         21st May 2012
3106       </div>
3107       <div class="body">
3108         <p>De siste dagene har høringsuttalelsene om DIFIs forslag til
3109 standardkatalog v3.1 blitt
3110 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder?tab=comments">publisert
3111 på DIFIs nettside</a>, og jeg kunne der glede meg over at
3112 <a href="http://wiki.nuug.no/uttalelser/201204-standardkatalog-v3.1">NUUGs</a>
3113 uttalelse er kommet med.  En uttalelse som overrasker og forvirrer meg
3114 er
3115 <a href="http://www.standard.difi.no/filearchive/norges-blindeforbund.pdf">den
3116 fra Norges Blindeforbund</a>, som 5 år etter at Klaus Knopper sammen
3117 med sin blinde kone blant annet
3118 <a href="http://www.nuug.no/aktiviteter/20071211-accessibility/">demonstrerte
3119 høyttalende OpenOffice.org på nynorsk for blinde</a> på et NUUG-møte.</p>
3120
3121 <p><a href="https://www.blindeforbundet.no/">Norges Blindeforbund</a>
3122 skriver følgende, som for meg virker å være formulert på sviktende
3123 grunnlag:</p>
3124
3125 <p><blockquote>
3126 <p>Bruk av fri programvare
3127
3128 <p>I FRIPROGSENTERET, RAPPORT 2009-02: Universell utforming
3129 <a href="http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf">http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf</a>
3130 sies det "Det finnes i dag ikke mange fri programvare-rammeverk eller
3131 generelle løsninger som støtter tilgjengelighet eller som er
3132 universelt utformet."</p>
3133
3134 <p>Til tross for at det gjennom prinsippene i fri programvare åpnes
3135 for større frihet til selv å påvirke programvareløsninger i retning av
3136 universell utforming viser praksis at virkeligheten er en annen.
3137 Mange av de mest alminnelige frie programvarepakkene mangler delvis
3138 eller fullstendig tilgjengelighet for mennesker med nedsatt
3139 syn. Eksempler på dette er OpenOffice og LibreOffice m.fl.</p>
3140
3141 <p>En annen utfordring ved bruk av fri programvare kan være manglende
3142 kundestøtte og muligheter til opplæring i bruk av løsningen. Svaksynte
3143 og blinde har et høyere behov for denne typen støtte enn andre brukere
3144 ettersom mange av dem har behov for tilleggsprogramvare som skal
3145 fungere sammen med den opprinnelige programvaren, og ettersom man ikke
3146 har de samme muligheter for overblikk over grensesnittet som en seende
3147 bruker. I tillegg til dette kommer de mer tilgjengelighetstekniske
3148 utfordringene som ofte må løses i samarbeid med
3149 programvareleverandør/produsent.</p>
3150
3151 <p>Fri programvare er ikke på samme måte underlagt lovgivning gjennom
3152 for eksempel diskriminerings og tilgjengelighetsloven ettersom det
3153 ikke alltid finnes en produsent/tilbyder av tjenesten eller produktet.</p>
3154
3155 <p>Norges Blindeforbund krever at universell utforming og
3156 brukskvalitet tas med som viktige hensyn i utredninger som ligger til
3157 grunn for valg av standarder som primært leder brukeren mot fri
3158 programvare. Et eksempel på dette er bruk av dokumentformatet ODF som
3159 leder brukeren i retning av OpenOffice, som er helt eller delvis
3160 utilgjengelig for svaksynte og blinde – noe avhengig av plattform og
3161 hjelpemiddelprogramvare.</p>
3162
3163 </blockquote></p>
3164
3165 <p>Jeg håper noen involvert i OpenOffice.org og/eller LibreOffice tar
3166 kontakt med Norges Blindeforbund og oppklarer det som for meg virker å
3167 være en misforståelse, i og med at OpenOffice.org så vidt jeg vet
3168 fungerer fint også for blinde.</p>
3169
3170 <p>Jeg ble minnet på problemstillingen da jeg leste Slashdot-saken om
3171 "<a href="http://linux.slashdot.org/story/12/05/21/1417221/the-state-of-linux-accessibility">The
3172 State of Linux Accessibility</a>", som også hevder at Linux fungerer
3173 utmerket for blinde.</p>
3174
3175       </div>
3176       <div class="tags">
3177
3178
3179         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>.
3180
3181
3182       </div>
3183     </div>
3184     <div class="padding"></div>
3185
3186     <div class="entry">
3187       <div class="title">
3188         <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>
3189       </div>
3190       <div class="date">
3191         27th April 2012
3192       </div>
3193       <div class="body">
3194         <p>NUUG-styremedlem Hans-Petter Fjeld
3195 <a href="https://plus.google.com/u/0/110394259537201279374/posts/AGzRmAuFdW1">meldte
3196 nettopp</a> at han har sendt inn <a href="http://www.nuug.no/">NUUG</a>s
3197 høringsuttalelse angående Difi sin standardkatalog v3.1.  Jeg er veldig
3198 glad for at så mange bidro og sikret at vår stemme blir hørt i denne
3199 høringen.  Anbefaler alle å lese våre
3200 <a href="http://wiki.nuug.no/uttalelser/201204-standardkatalog-v3.1">to
3201 sider med innspill</a>.</p>
3202
3203       </div>
3204       <div class="tags">
3205
3206
3207         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
3208
3209
3210       </div>
3211     </div>
3212     <div class="padding"></div>
3213
3214     <div class="entry">
3215       <div class="title">
3216         <a href="http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html">HTC One X - Your video?  What do you mean?</a>
3217       </div>
3218       <div class="date">
3219         26th April 2012
3220       </div>
3221       <div class="body">
3222         <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
3223 article today</a> published by Computerworld Norway, the photographer
3224 <a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
3225 that the video editor application included with
3226 <a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
3227 X</a> have some quite surprising terms of use.  The article is mostly
3228 based on the twitter message from mister Urke, stating:
3229
3230 <p><blockquote>
3231 "<a href="http://twitter.com/urke/status/194062269724897280">Drøy
3232 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
3233 kan jeg KUN bruke dem privat.</a>"
3234 </blockquote></p>
3235
3236 <p>I quickly translated it to this English message:</p>
3237
3238 <p><blockquote>
3239 "Arrogant user agreement: HTC can use MY edited videos
3240 commercially.  Although I can ONLY use them privately."
3241 </blockquote></p>
3242
3243 <p>I've been unable to find the text of the license term myself, but
3244 suspect it is a variation of the MPEG-LA terms I
3245 <a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
3246 with my Canon IXUS 130</a>.  The HTC One X specification specifies that
3247 the recording format of the phone is .amr for audio and .mp3 for
3248 video.  AMR is
3249 <a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
3250 Multi-Rate audio codec</a> with patents which according to the
3251 Wikipedia article require an license agreement with
3252 <a href="http://www.voiceage.com/">VoiceAge</a>.  MP4 is
3253 <a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
3254 H.264</a>, which according to Wikipedia require a licence agreement
3255 with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
3256
3257 <p>I know why I prefer
3258 <a href="http://www.digistan.org/open-standard:definition">free and open
3259 standards</a> also for video.</p>
3260
3261       </div>
3262       <div class="tags">
3263
3264
3265         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/h264">h264</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>.
3266
3267
3268       </div>
3269     </div>
3270     <div class="padding"></div>
3271
3272     <div class="entry">
3273       <div class="title">
3274         <a href="http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html">RAND terms - non-reasonable and discriminatory</a>
3275       </div>
3276       <div class="date">
3277         19th April 2012
3278       </div>
3279       <div class="body">
3280         <p>Here in Norway, the
3281 <a href="http://www.regjeringen.no/nb/dep/fad.html?id=339"> Ministry of
3282 Government Administration, Reform and Church Affairs</a> is behind
3283 a <a href="http://standard.difi.no/forvaltningsstandarder">directory of
3284 standards</a> that are recommended or mandatory for use by the
3285 government.  When the directory was created, the people behind it made
3286 an effort to ensure that everyone would be able to implement the
3287 standards and compete on equal terms to supply software and solutions
3288 to the government.  Free software and non-free software could compete
3289 on the same level.</p>
3290
3291 <p>But recently, some standards with RAND
3292 (<a href="http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing">Reasonable
3293 And Non-Discriminatory</a>) terms have made their way into the
3294 directory.  And while this might not sound too bad, the fact is that
3295 standard specifications with RAND terms often block free software from
3296 implementing them.  The reasonable part of RAND mean that the cost per
3297 user/unit is low,and the non-discriminatory part mean that everyone
3298 willing to pay will get a license.  Both sound great in theory.  In
3299 practice, to get such license one need to be able to count users, and
3300 be able to pay a small amount of money per unit or user.  By
3301 definition, users of free software do not need to register their use.
3302 So counting users or units is not possible for free software projects.
3303 And given that people will use the software without handing any money
3304 to the author, it is not really economically possible for a free
3305 software author to pay a small amount of money to license the rights
3306 to implement a standard when the income available is zero.  The result
3307 in these situations is that free software are locked out from
3308 implementing standards with RAND terms.</p>
3309
3310 <p>Because of this, when I see someone claiming the terms of a
3311 standard is reasonable and non-discriminatory, all I can think of is
3312 how this really is non-reasonable and discriminatory.  Because free
3313 software developers are working in a global market, it does not really
3314 help to know that software patents are not supposed to be enforceable
3315 in Norway.  The patent regimes in other countries affect us even here.
3316 I really hope the people behind the standard directory will pay more
3317 attention to these issues in the future.</p>
3318
3319 <p>You can find more on the issues with RAND, FRAND and RAND-Z terms
3320 from Simon Phipps
3321 (<a href="http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/">RAND:
3322 Not So Reasonable?</a>).</p>
3323
3324 <p>Update 2012-04-21: Just came across a
3325 <a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm">blog
3326 post from Glyn Moody</a> over at Computer World UK warning about the
3327 same issue, and urging people to speak out to the UK government.  I
3328 can only urge Norwegian users to do the same for
3329 <a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder">the
3330 hearing taking place at the moment</a> (respond before 2012-04-27).
3331 It proposes to require video conferencing standards including
3332 specifications with RAND terms.</p>
3333
3334       </div>
3335       <div class="tags">
3336
3337
3338         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>.
3339
3340
3341       </div>
3342     </div>
3343     <div class="padding"></div>
3344
3345     <div class="entry">
3346       <div class="title">
3347         <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>
3348       </div>
3349       <div class="date">
3350         16th January 2011
3351       </div>
3352       <div class="body">
3353         <p>The video format struggle on the web continues, and the three
3354 contenders seem to be Ogg Theora, H.264 and WebM.  Most video sites
3355 seem to use H.264, while others use Ogg Theora.  Interestingly enough,
3356 the comments I see give me the feeling that a lot of people believe
3357 H.264 is the most supported video format in browsers, but according to
3358 the Wikipedia article on
3359 <a href="http://en.wikipedia.org/wiki/HTML5_video">HTML5 video</a>,
3360 this is not true.  Check out the nice table of supprted formats in
3361 different browsers there.  The format supported by most browsers is
3362 Ogg Theora, supported by released versions of Mozilla Firefox, Google
3363 Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
3364 BOLT browser, while not supported by Internet Explorer nor Safari.
3365 The runner up is WebM supported by released versions of Google Chrome
3366 Chromium Opera and Origyn Web Browser, and test versions of Mozilla
3367 Firefox.  H.264 is supported by released versions of Safari, Origyn
3368 Web Browser and BOLT browser, and the test version of Internet
3369 Explorer.  Those wanting Ogg Theora support in Internet Explorer and
3370 Safari can install plugins to get it.</p>
3371
3372 <p>To me, the simple conclusion from this is that to reach most users
3373 without any extra software installed, one uses Ogg Theora with the
3374 HTML5 video tag.   Of course to reach all those without a browser
3375 handling HTML5, one need fallback mechanisms.  In
3376 <a href="http://www.nuug.no/">NUUG</a>, we provide first fallback to a
3377 plugin capable of playing MPEG1 video, and those without such support
3378 we have a second fallback to the Cortado java applet playing Ogg
3379 Theora.  This seem to work quite well, as can be seen in an <a
3380 href="http://www.nuug.no/aktiviteter/20110111-semantic-web/">example
3381 from last week</a>.</p>
3382
3383 <p>The reason Ogg Theora is the most supported format, and H.264 is
3384 the least supported is simple.  Implementing and using H.264
3385 require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
3386 are incompatible with free software licensing.  If you believed H.264
3387 was without royalties and license terms, check out
3388 "<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
3389 Free That Matters</a>" by Simon Phipps.</p>
3390
3391 <p>A incomplete list of sites providing video in Ogg Theora is
3392 available from
3393 <a href="http://wiki.xiph.org/index.php/List_of_Theora_videos">the
3394 Xiph.org wiki</a>, if you want to have a look.  I'm not aware of a
3395 similar list for WebM nor H.264.</p>
3396
3397 <p>Update 2011-01-16 09:40: A question from Tollef on IRC made me
3398 realise that I failed to make it clear enough this text is about the
3399 &lt;video&gt; tag support in browsers and not the video support
3400 provided by external plugins like the Flash plugins.</p>
3401
3402       </div>
3403       <div class="tags">
3404
3405
3406         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
3407
3408
3409       </div>
3410     </div>
3411     <div class="padding"></div>
3412
3413     <div class="entry">
3414       <div class="title">
3415         <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>
3416       </div>
3417       <div class="date">
3418         12th January 2011
3419       </div>
3420       <div class="body">
3421         <p>Today I discovered
3422 <a href="http://www.digi.no/860070/google-dropper-h264-stotten-i-chrome">via
3423 digi.no</a> that the Chrome developers, in a surprising announcement,
3424 <a href="http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html">yesterday
3425 announced</a> plans to drop H.264 support for HTML5 &lt;video&gt; in
3426 the browser.  The argument used is that H.264 is not a "completely
3427 open" codec technology.  If you believe H.264 was free for everyone
3428 to use, I recommend having a look at the essay
3429 "<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
3430 Free That Matters</a>".  It is not free of cost for creators of video
3431 tools, nor those of us that want to publish on the Internet, and the
3432 terms provided by MPEG-LA excludes free software projects from
3433 licensing the patents needed for H.264.  Some background information
3434 on the Google announcement is available from
3435 <a href="http://www.osnews.com/story/24243/Google_To_Drop_H264_Support_from_Chrome">OSnews</a>.
3436 A good read. :)</p>
3437
3438 <p>Personally, I believe it is great that Google is taking a stand to
3439 promote equal terms for everyone when it comes to video publishing on
3440 the Internet.  This can only be done by publishing using free and open
3441 standards, which is only possible if the web browsers provide support
3442 for these free and open standards.  At the moment there seem to be two
3443 camps in the web browser world when it come to video support.  Some
3444 browsers support H.264, and others support
3445 <a href="http://www.theora.org/">Ogg Theora</a> and
3446 <a href="http://www.webmproject.org/">WebM</a>
3447 (<a href="http://www.diracvideo.org/">Dirac</a> is not really an option
3448 yet), forcing those of us that want to publish video on the Internet
3449 and which can not accept the terms of use presented by MPEG-LA for
3450 H.264 to not reach all potential viewers.
3451 Wikipedia keep <a href="http://en.wikipedia.org/wiki/HTML5_video">an
3452 updated summary</a> of the current browser support.</p>
3453
3454 <p>Not surprising, several people would prefer Google to keep
3455 promoting H.264, and John Gruber
3456 <a href="http://daringfireball.net/2011/01/simple_questions">presents
3457 the mind set</a> of these people quite well.  His rhetorical questions
3458 provoked a reply from Thom Holwerda with another set of questions
3459 <a href="http://www.osnews.com/story/24245/10_Questions_for_John_Gruber_Regarding_H_264_WebM">presenting
3460 the issues with H.264</a>. Both are worth a read.</p>
3461
3462 <p>Some argue that if Google is dropping H.264 because it isn't free,
3463 they should also drop support for the Adobe Flash plugin.  This
3464 argument was covered by Simon Phipps in
3465 <a href="http://blogs.computerworlduk.com/simon-says/2011/01/google-and-h264---far-from-hypocritical/index.htm">todays
3466 blog post</a>, which I find to put the issue in context.  To me it
3467 make perfect sense to drop native H.264 support for HTML5 in the
3468 browser while still allowing plugins.</p>
3469
3470 <p>I suspect the reason this announcement make so many people protest,
3471 is that all the users and promoters of H.264 suddenly get an uneasy
3472 feeling that they might be backing the wrong horse.  A lot of TV
3473 broadcasters have been moving to H.264 the last few years, and a lot
3474 of money has been invested in hardware based on the belief that they
3475 could use the same video format for both broadcasting and web
3476 publishing.  Suddenly this belief is shaken.</p>
3477
3478 <p>An interesting question is why Google is doing this.  While the
3479 presented argument might be true enough, I believe Google would only
3480 present the argument if the change make sense from a business
3481 perspective.  One reason might be that they are currently negotiating
3482 with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
3483 feeling that dropping H.264 completely from Chroome, Youtube and
3484 Google Video would improve the negotiation position of Google.
3485 Another reason might be that Google want to save money by not having
3486 to pay the video tax to MPEG-LA at all, and thus want to move to a
3487 video format not requiring royalties at all.  A third reason might be
3488 that the Chrome development team simply want to avoid the
3489 Chrome/Chromium split to get more help with the development of Chrome.
3490 I guess time will tell.</p>
3491
3492 <p>Update 2011-01-15: The Google Chrome team provided
3493 <a href="http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html">more
3494 background and information on the move</a> it a blog post yesterday.</p>
3495
3496       </div>
3497       <div class="tags">
3498
3499
3500         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
3501
3502
3503       </div>
3504     </div>
3505     <div class="padding"></div>
3506
3507     <div class="entry">
3508       <div class="title">
3509         <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>
3510       </div>
3511       <div class="date">
3512         30th December 2010
3513       </div>
3514       <div class="body">
3515         <p>After trying to
3516 <a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
3517 Ogg Theora</a> to
3518 <a href="http://www.digistan.org/open-standard:definition">the Digistan
3519 definition</a> of a free and open standard, I concluded that this need
3520 to be done for more standards and started on a framework for doing
3521 this.  As a start, I want to get the status for all the standards in
3522 the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
3523 JPEG, PNG, SVG and others.  But to be able to complete this in a
3524 reasonable time frame, I will need help.</p>
3525
3526 <p>If you want to help out with this work, please visit
3527 <a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
3528 wiki pages I have set up for this</a>, and let me know that you want
3529 to help out.  The IRC channel #nuug on irc.freenode.net is a good
3530 place to coordinate this for now, as it is the IRC channel for the
3531 NUUG association where I have created the framework (I am the leader
3532 of the Norwegian Unix User Group).</p>
3533
3534 <p>The framework is still forming, and a lot is left to do.  Do not be
3535 scared by the sketchy form of the current pages. :)</p>
3536
3537       </div>
3538       <div class="tags">
3539
3540
3541         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>.
3542
3543
3544       </div>
3545     </div>
3546     <div class="padding"></div>
3547
3548     <div class="entry">
3549       <div class="title">
3550         <a href="http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
3551       </div>
3552       <div class="date">
3553         27th December 2010
3554       </div>
3555       <div class="body">
3556         <p>One of the reasons I like the Digistan definition of
3557 "<a href="http://www.digistan.org/open-standard:definition">Free and
3558 Open Standard</a>" is that this is a new term, and thus the meaning of
3559 the term has been decided by Digistan.  The term "Open Standard" has
3560 become so misunderstood that it is no longer very useful when talking
3561 about standards.  One end up discussing which definition is the best
3562 one and with such frame the only one gaining are the proponents of
3563 de-facto standards and proprietary solutions.</p>
3564
3565 <p>But to give us an idea about the diversity of definitions of open
3566 standards, here are a few that I know about.  This list is not
3567 complete, but can be a starting point for those that want to do a
3568 complete survey.  More definitions are available on the
3569 <a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
3570 page</a>.</p>
3571
3572 <p>First off is my favourite, the definition from the European
3573 Interoperability Framework version 1.0.  Really sad to notice that BSA
3574 and others has succeeded in getting it removed from version 2.0 of the
3575 framework by stacking the committee drafting the new version with
3576 their own people.  Anyway, the definition is still available and it
3577 include the key properties needed to make sure everyone can use a
3578 specification on equal terms.</p>
3579
3580 <blockquote>
3581
3582 <p>The following are the minimal characteristics that a specification
3583 and its attendant documents must have in order to be considered an
3584 open standard:</p>
3585
3586 <ul>
3587
3588 <li>The standard is adopted and will be maintained by a not-for-profit
3589 organisation, and its ongoing development occurs on the basis of an
3590 open decision-making procedure available to all interested parties
3591 (consensus or majority decision etc.).</li>
3592
3593 <li>The standard has been published and the standard specification
3594 document is available either freely or at a nominal charge. It must be
3595 permissible to all to copy, distribute and use it for no fee or at a
3596 nominal fee.</li>
3597
3598 <li>The intellectual property - i.e. patents possibly present - of
3599 (parts of) the standard is made irrevocably available on a royalty-
3600 free basis.</li>
3601
3602 <li>There are no constraints on the re-use of the standard.</li>
3603
3604 </ul>
3605 </blockquote>
3606
3607 <p>Another one originates from my friends over at
3608 <a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
3609 support for <a href="http://www.aaben-standard.dk/">this
3610 definition</a> in 2004.  It even made it into the Danish parlament as
3611 <a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
3612 definition of a open standard</a>.  Another from a different part of
3613 the Danish government is available from the wikipedia page.</p>
3614
3615 <blockquote>
3616
3617 <p>En åben standard opfylder følgende krav:</p>
3618
3619 <ol>
3620
3621 <li>Veldokumenteret med den fuldstændige specifikation offentligt
3622 tilgængelig.</li>
3623
3624 <li>Frit implementerbar uden økonomiske, politiske eller juridiske
3625 begrænsninger på implementation og anvendelse.</li>
3626
3627 <li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
3628 "standardiseringsorganisation") via en åben proces.</li>
3629
3630 </ol>
3631
3632 </blockquote>
3633
3634 <p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
3635 definition</a> from Free Software Foundation Europe.</p>
3636
3637 <blockquote>
3638
3639 <p>An Open Standard refers to a format or protocol that is</p>
3640
3641 <ol>
3642
3643 <li>subject to full public assessment and use without constraints in a
3644 manner equally available to all parties;</li>
3645
3646 <li>without any components or extensions that have dependencies on
3647 formats or protocols that do not meet the definition of an Open
3648 Standard themselves;</li>
3649
3650 <li>free from legal or technical clauses that limit its utilisation by
3651 any party or in any business model;</li>
3652
3653 <li>managed and further developed independently of any single vendor
3654 in a process open to the equal participation of competitors and third
3655 parties;</li>
3656
3657 <li>available in multiple complete implementations by competing
3658 vendors, or as a complete implementation equally available to all
3659 parties.</li>
3660
3661 </ol>
3662
3663 </blockquote>
3664
3665 <p>A long time ago, SUN Microsystems, now bought by Oracle, created
3666 its
3667 <a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
3668 Standards Checklist</a> with a fairly detailed description.</p>
3669
3670 <blockquote>
3671 <p>Creation and Management of an Open Standard
3672
3673 <ul>
3674
3675 <li>Its development and management process must be collaborative and
3676   democratic:
3677
3678          <ul>
3679
3680          <li>Participation must be accessible to all those who wish to
3681             participate and can meet fair and reasonable criteria
3682             imposed by the organization under which it is developed
3683             and managed.</li>
3684
3685          <li>The processes must be documented and, through a known
3686             method, can be changed through input from all
3687             participants.</li>
3688
3689          <li>The process must be based on formal and binding commitments for
3690             the disclosure and licensing of intellectual property rights.</li>
3691
3692          <li>Development and management should strive for consensus,
3693             and an appeals process must be clearly outlined.</li>
3694
3695          <li>The standard specification must be open to extensive
3696             public review at least once in its life-cycle, with
3697             comments duly discussed and acted upon, if required.</li>
3698
3699          </ul>
3700
3701 </li>
3702
3703 </ul>
3704
3705 <p>Use and Licensing of an Open Standard</p>
3706 <ul>
3707
3708 <li>The standard must describe an interface, not an implementation,
3709   and the industry must be capable of creating multiple, competing
3710   implementations to the interface described in the standard without
3711   undue or restrictive constraints.  Interfaces include APIs,
3712   protocols, schemas, data formats and their encoding.</li>
3713
3714 <li> The standard must not contain any proprietary "hooks" that create
3715   a technical or economic barriers</li>
3716
3717 <li>Faithful implementations of the standard must
3718   interoperate. Interoperability means the ability of a computer
3719   program to communicate and exchange information with other computer
3720   programs and mutually to use the information which has been
3721   exchanged. This includes the ability to use, convert, or exchange
3722   file formats, protocols, schemas, interface information or
3723   conventions, so as to permit the computer program to work with other
3724   computer programs and users in all the ways in which they are
3725   intended to function.</li>
3726
3727 <li>It must be permissible for anyone to copy, distribute and read the
3728   standard for a nominal fee, or even no fee. If there is a fee, it
3729   must be low enough to not preclude widespread use.</li>
3730
3731 <li>It must be possible for anyone to obtain free (no royalties or
3732   fees; also known as "royalty free"), worldwide, non-exclusive and
3733   perpetual licenses to all essential patent claims to make, use and
3734   sell products based on the standard.  The only exceptions are
3735   terminations per the reciprocity and defensive suspension terms
3736   outlined below. Essential patent claims include pending, unpublished
3737   patents, published patents, and patent applications. The license is
3738   only for the exact scope of the standard in question.
3739
3740       <ul>
3741
3742       <li> May be conditioned only on reciprocal licenses to any of
3743         licensees' patent claims essential to practice that standard
3744         (also known as a reciprocity clause)</li>
3745
3746       <li> May be terminated as to any licensee who sues the licensor
3747         or any other licensee for infringement of patent claims
3748         essential to practice that standard (also known as a
3749         "defensive suspension" clause)</li>
3750
3751       <li> The same licensing terms are available to every potential
3752         licensor</li>
3753
3754       </ul>
3755 </li>
3756
3757 <li>The licensing terms of an open standards must not preclude
3758   implementations of that standard under open source licensing terms
3759   or restricted licensing terms</li>
3760
3761 </ul>
3762
3763 </blockquote>
3764
3765 <p>It is said that one of the nice things about standards is that
3766 there are so many of them.  As you can see, the same holds true for
3767 open standard definitions.  Most of the definitions have a lot in
3768 common, and it is not really controversial what properties a open
3769 standard should have, but the diversity of definitions have made it
3770 possible for those that want to avoid a level marked field and real
3771 competition to downplay the significance of open standards.  I hope we
3772 can turn this tide by focusing on the advantages of Free and Open
3773 Standards.</p>
3774
3775       </div>
3776       <div class="tags">
3777
3778
3779         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>.
3780
3781
3782       </div>
3783     </div>
3784     <div class="padding"></div>
3785
3786     <div class="entry">
3787       <div class="title">
3788         <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>
3789       </div>
3790       <div class="date">
3791         25th December 2010
3792       </div>
3793       <div class="body">
3794         <p><a href="http://www.digistan.org/open-standard:definition">The
3795 Digistan definition</a> of a free and open standard reads like this:</p>
3796
3797 <blockquote>
3798
3799 <p>The Digital Standards Organization defines free and open standard
3800 as follows:</p>
3801
3802 <ol>
3803
3804 <li>A free and open standard is immune to vendor capture at all stages
3805 in its life-cycle. Immunity from vendor capture makes it possible to
3806 freely use, improve upon, trust, and extend a standard over time.</li>
3807
3808 <li>The standard is adopted and will be maintained by a not-for-profit
3809 organisation, and its ongoing development occurs on the basis of an
3810 open decision-making procedure available to all interested
3811 parties.</li>
3812
3813 <li>The standard has been published and the standard specification
3814 document is available freely. It must be permissible to all to copy,
3815 distribute, and use it freely.</li>
3816
3817 <li>The patents possibly present on (parts of) the standard are made
3818 irrevocably available on a royalty-free basis.</li>
3819
3820 <li>There are no constraints on the re-use of the standard.</li>
3821
3822 </ol>
3823
3824 <p>The economic outcome of a free and open standard, which can be
3825 measured, is that it enables perfect competition between suppliers of
3826 products based on the standard.</p>
3827 </blockquote>
3828
3829 <p>For a while now I have tried to figure out of Ogg Theora is a free
3830 and open standard according to this definition.  Here is a short
3831 writeup of what I have been able to gather so far.  I brought up the
3832 topic on the Xiph advocacy mailing list
3833 <a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
3834 July 2009</a>, for those that want to see some background information.
3835 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
3836 the Ogg Theora specification fulfils the Digistan definition.</p>
3837
3838 <p><strong>Free from vendor capture?</strong></p>
3839
3840 <p>As far as I can see, there is no single vendor that can control the
3841 Ogg Theora specification.  It can be argued that the
3842 <a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
3843 given that it is a non-profit foundation with the expressed goal
3844 making free and open protocols and standards available, it is not
3845 obvious that this is a real risk.  One issue with the Xiph
3846 foundation is that its inner working (as in board member list, or who
3847 control the foundation) are not easily available on the web.  I've
3848 been unable to find out who is in the foundation board, and have not
3849 seen any accounting information documenting how money is handled nor
3850 where is is spent in the foundation.  It is thus not obvious for an
3851 external observer who control The Xiph foundation, and for all I know
3852 it is possible for a single vendor to take control over the
3853 specification.  But it seem unlikely.</p>
3854
3855 <p><strong>Maintained by open not-for-profit organisation?</strong></p>
3856
3857 <p>Assuming that the Xiph foundation is the organisation its web pages
3858 claim it to be, this point is fulfilled.  If Xiph foundation is
3859 controlled by a single vendor, it isn't, but I have not found any
3860 documentation indicating this.</p>
3861
3862 <p>According to
3863 <a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
3864 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
3865 government, the Xiph foundation is a non-commercial organisation and
3866 the development process is open, transparent and non-Discrimatory.
3867 Until proven otherwise, I believe it make most sense to believe the
3868 report is correct.</p>
3869
3870 <p><strong>Specification freely available?</strong></p>
3871
3872 <p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
3873 container format</a> and both the
3874 <a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
3875 <a href="http://theora.org/doc/">Theora</a> codeces are available on
3876 the web.  This are the terms in the Vorbis and Theora specification:
3877
3878 <blockquote>
3879
3880 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
3881 specifications, whether in private, public, or corporate
3882 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
3883 the right to set the Ogg [Vorbis/Theora] specification and certify
3884 specification compliance.
3885
3886 </blockquote>
3887
3888 <p>The Ogg container format is specified in IETF
3889 <a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
3890 this is the term:<p>
3891
3892 <blockquote>
3893
3894 <p>This document and translations of it may be copied and furnished to
3895 others, and derivative works that comment on or otherwise explain it
3896 or assist in its implementation may be prepared, copied, published and
3897 distributed, in whole or in part, without restriction of any kind,
3898 provided that the above copyright notice and this paragraph are
3899 included on all such copies and derivative works.  However, this
3900 document itself may not be modified in any way, such as by removing
3901 the copyright notice or references to the Internet Society or other
3902 Internet organizations, except as needed for the purpose of developing
3903 Internet standards in which case the procedures for copyrights defined
3904 in the Internet Standards process must be followed, or as required to
3905 translate it into languages other than English.</p>
3906
3907 <p>The limited permissions granted above are perpetual and will not be
3908 revoked by the Internet Society or its successors or assigns.</p>
3909 </blockquote>
3910
3911 <p>All these terms seem to allow unlimited distribution and use, an
3912 this term seem to be fulfilled.  There might be a problem with the
3913 missing permission to distribute modified versions of the text, and
3914 thus reuse it in other specifications.  Not quite sure if that is a
3915 requirement for the Digistan definition.</p>
3916
3917 <p><strong>Royalty-free?</strong></p>
3918
3919 <p>There are no known patent claims requiring royalties for the Ogg
3920 Theora format.
3921 <a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
3922 and
3923 <a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
3924 Jobs</a> in Apple claim to know about some patent claims (submarine
3925 patents) against the Theora format, but no-one else seem to believe
3926 them.  Both Opera Software and the Mozilla Foundation have looked into
3927 this and decided to implement Ogg Theora support in their browsers
3928 without paying any royalties.  For now the claims from MPEG-LA and
3929 Steve Jobs seem more like FUD to scare people to use the H.264 codec
3930 than any real problem with Ogg Theora.</p>
3931
3932 <p><strong>No constraints on re-use?</strong></p>
3933
3934 <p>I am not aware of any constraints on re-use.</p>
3935
3936 <p><strong>Conclusion</strong></p>
3937
3938 <p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
3939 depend on the governing structure of the Xiph foundation.  Given the
3940 background report used by the Norwegian government, I believe it is
3941 safe to assume the last two requirements are fulfilled too, but it
3942 would be nice if the Xiph foundation web site made it easier to verify
3943 this.</p>
3944
3945 <p>It would be nice to see other analysis of other specifications to
3946 see if they are free and open standards.</p>
3947
3948       </div>
3949       <div class="tags">
3950
3951
3952         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/h264">h264</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>.
3953
3954
3955       </div>
3956     </div>
3957     <div class="padding"></div>
3958
3959     <div class="entry">
3960       <div class="title">
3961         <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>
3962       </div>
3963       <div class="date">
3964         25th December 2010
3965       </div>
3966       <div class="body">
3967         <p>A few days ago
3968 <a href="http://www.idg.no/computerworld/article189879.ece">an
3969 article</a> in the Norwegian Computerworld magazine about how version
3970 2.0 of
3971 <a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
3972 Interoperability Framework</a> has been successfully lobbied by the
3973 proprietary software industry to remove the focus on free software.
3974 Nothing very surprising there, given
3975 <a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
3976 reports</a> on how Microsoft and others have stacked the committees in
3977 this work.  But I find this very sad.   The definition of
3978 <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
3979 open standard from version 1</a> was very good, and something I
3980 believe should be used also in the future, alongside
3981 <a href="http://www.digistan.org/open-standard:definition">the
3982 definition from Digistan</A>.  Version 2 have removed the open
3983 standard definition from its content.</p>
3984
3985 <p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
3986 Villanueva, congressman in Peru at the time, to Microsoft as a reply
3987 to Microsofts attack on his proposal regarding the use of free software
3988 in the public sector in Peru.  As the text was not available from a
3989 few of the URLs where it used to be available, I copy it here from
3990 <a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
3991 source</a> to ensure it is available also in the future.  Some
3992 background information about that story is available in
3993 <a href="http://www.linuxjournal.com/article/6099">an article</a> from
3994 Linux Journal in 2002.</p>
3995
3996 <blockquote>
3997 <p>Lima, 8th of April, 2002<br>
3998 To: Señor JUAN ALBERTO GONZÁLEZ<br>
3999 General Manager of Microsoft Perú</p>
4000
4001 <p>Dear Sir:</p>
4002
4003 <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>
4004
4005 <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>
4006
4007 <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>
4008
4009 <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>
4010
4011 <p>
4012 <ul>
4013 <li>Free access to public information by the citizen. </li>
4014 <li>Permanence of public data. </li>
4015 <li>Security of the State and citizens.</li>
4016 </ul>
4017 </p>
4018
4019 <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>
4020
4021 <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>
4022
4023 <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>
4024
4025 <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>
4026
4027 <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>
4028
4029
4030 <p>From reading the Bill it will be clear that once passed:<br>
4031 <li>the law does not forbid the production of proprietary software</li>
4032 <li>the law does not forbid the sale of proprietary software</li>
4033 <li>the law does not specify which concrete software to use</li>
4034 <li>the law does not dictate the supplier from whom software will be bought</li>
4035 <li>the law does not limit the terms under which a software product can be licensed.</li>
4036
4037 </p>
4038
4039 <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>
4040
4041 <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>
4042
4043 <p>As for the observations you have made, we will now go on to analyze them in detail:</p>
4044
4045 <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>
4046
4047 <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>
4048
4049 <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>
4050
4051 <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>
4052
4053 <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>
4054
4055 <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>
4056
4057 <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>
4058
4059 <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>
4060
4061 <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>
4062
4063 <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>
4064
4065 <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>
4066
4067 <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>
4068
4069 <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>
4070
4071 <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>
4072
4073 <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>
4074
4075 <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>
4076
4077 <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>
4078
4079 <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>
4080
4081 <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>
4082
4083 <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>
4084
4085 <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>
4086
4087 <p>On security:</p>
4088
4089 <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>
4090
4091 <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>
4092
4093 <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>
4094
4095 <p>In respect of the guarantee:</p>
4096
4097 <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>
4098
4099 <p>On Intellectual Property:</p>
4100
4101 <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>
4102
4103 <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>
4104
4105 <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>
4106
4107 <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>
4108
4109 <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>
4110
4111 <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>
4112
4113 <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>
4114
4115 <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>
4116
4117 <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>
4118
4119 <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>
4120
4121 <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>
4122
4123 <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>
4124
4125 <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>
4126
4127 <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>
4128
4129 <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>
4130
4131 <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>
4132
4133 <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>
4134
4135 <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>
4136
4137 <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>
4138
4139 <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>
4140
4141 <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>
4142
4143 <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>
4144
4145 <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>
4146
4147 <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>
4148
4149 <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>
4150
4151 <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>
4152
4153 <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>
4154
4155 <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>
4156
4157 <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>
4158
4159 <p>Cordially,<br>
4160 DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
4161 Congressman of the Republic of Perú.</p>
4162 </blockquote>
4163
4164       </div>
4165       <div class="tags">
4166
4167
4168         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>.
4169
4170
4171       </div>
4172     </div>
4173     <div class="padding"></div>
4174
4175     <div class="entry">
4176       <div class="title">
4177         <a href="http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html">Officeshots still going strong</a>
4178       </div>
4179       <div class="date">
4180         25th December 2010
4181       </div>
4182       <div class="body">
4183         <p>Half a year ago I
4184 <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">wrote
4185 a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
4186 a web service to allow anyone to test how ODF documents are handled by
4187 the different programs reading and writing the ODF format.</p>
4188
4189 <p>I just had a look at the service, and it seem to be going strong.
4190 Very interesting to see the results reported in the gallery, how
4191 different Office implementations handle different ODF features.  Sad
4192 to see that KOffice was not doing it very well, and happy to see that
4193 LibreOffice has been tested already (but sadly not listed as a option
4194 for OfficeShots users yet).  I am glad to see that the ODF community
4195 got such a great test tool available.</p>
4196
4197       </div>
4198       <div class="tags">
4199
4200
4201         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>.
4202
4203
4204       </div>
4205     </div>
4206     <div class="padding"></div>
4207
4208     <div class="entry">
4209       <div class="title">
4210         <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>
4211       </div>
4212       <div class="date">
4213         30th October 2010
4214       </div>
4215       <div class="body">
4216         <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
4217 <a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
4218 hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
4219 filmene NRK la ut ikke var tilgjengelig i et
4220 <a href="http://www.digistan.org/open-standard:definition">fritt og
4221 åpent format</a>.  Dette var det jeg skrev publiserte der 07:39.</p>
4222
4223 <p><blockquote>
4224 <p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
4225 nedlasting.  Mange av oss som kan mer enn gjennomsnittet om systemer
4226 som dette, vet at det stort sett er mulig å lure ut ting med den
4227 nødvendige forkunnskapen."</p>
4228
4229 <p>Haha.  Å streame innhold er det samme som å laste ned innhold, så å
4230 beskytte en stream mot nedlasting er ikke mulig.  Å skrive noe slikt
4231 er å forlede leseren.</p>
4232
4233 <p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
4234 vil tillate streaming men ikke nedlasting meningsløs.</p>
4235
4236 <p>Anbefaler forresten å lese
4237 <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>
4238 om hva som ville være konsekvensen hvis digitale avspillingssperrer
4239 (DRM) fungerte.  Det gjør de naturligvis ikke teknisk - det er jo
4240 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
4241 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
4242 opp under.</p>
4243 </blockquote></p>
4244
4245 <p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
4246 NRKBeta:</p>
4247
4248 <p><blockquote>
4249 <p>From: Anders Hofseth &lt;XXX@gmail.com>
4250 <br>To: "pere@hungry.com" &lt;pere@hungry.com>
4251 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>, Jon Ståle Carlsen &lt;XXX@gmail.com>, Henrik Lied &lt;XXX@gmail.com>
4252 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
4253 <br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
4254
4255 <p>Hei Petter.
4256 <br>Det du forsøker dra igang er egentlig en interessant diskusjon,
4257 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
4258 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
4259 særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
4260
4261 <p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
4262 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
4263 konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
4264
4265 <p>Med hilsen,
4266 <br>-anders</p>
4267
4268 <p>Ring meg om noe er uklart: 95XXXXXXX</p>
4269 </blockquote></p>
4270
4271 <p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
4272 over følgende svar.  I og med at debatten er fjernet fra NRK Betas
4273 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
4274 Har fjernet epostadresser og telefonnummer til de involverte, for å
4275 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
4276
4277 <p><blockquote>
4278 <p>From: Petter Reinholdtsen &lt;pere@hungry.com>
4279 <br>To: Anders Hofseth &lt;XXX@gmail.com>
4280 <br>Cc: Eirik Solheim &lt;XXX@gmail.com>,
4281 <br>        Jon Ståle Carlsen &lt;XXX@gmail.com>,
4282 <br>        Henrik Lied &lt;XXX@gmail.com>
4283 <br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
4284 <br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
4285
4286 <p>[Anders Hofseth]
4287 <br>> Hei Petter.</p>
4288
4289 <p>Hei.</p>
4290
4291 <p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
4292 <br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
4293 <br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
4294 <br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
4295
4296 <p>Godt å se at du er enig i at dette er en interessant diskusjon.  Den
4297 vil nok fortsette en stund til.  :)</p>
4298
4299 <p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
4300 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
4301 fortsette å legge ut arkivmateriale.</p>
4302
4303 <p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
4304 faktum, som er at streaming er det samme som nedlasting, og at innhold
4305 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
4306 det.</p>
4307
4308 <p>Det du sier er jo at klarering av arkivmateriale for publisering på
4309 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
4310 Det er ikke et argument som holder vann. :)</p>
4311
4312 <p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
4313 <br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
4314 <br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
4315
4316 <p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
4317 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
4318 mot de som vil låse kulturen inne.  Jeg synes det er en skam at NRK
4319 godtar å forlede publikum.  Ville heller at NRK krever at innhold som
4320 skal sendes skal være uten bruksbegresninger og kan publiseres i
4321 formater som heller ikke har bruksbegresninger (bruksbegresningene til
4322 H.264 burde få varselbjellene i NRK til å ringe).</p>
4323
4324 <p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
4325 påstander om at "streaming beskytter mot nedlasting" som bare er egnet
4326 til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
4327
4328 <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
4329 titt på
4330 &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> >.
4331 for å se hva slags bruksbegresninger H.264 innebærer.</p>
4332
4333 <p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
4334 kan brukes før rettighetshaverene også innser at de er med på å skade
4335 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
4336 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
4337 langt på overtid.</p>
4338
4339 <p>> Ring meg om noe er uklart: XXX</p>
4340
4341 <p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
4342 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
4343 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
4344 for videre diskusjon hadde dere i mine øyne kommet fra det med
4345 ryggraden på plass.</p>
4346
4347 <p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
4348
4349 <p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
4350 &lt;URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
4351 &lt;URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
4352 NRK1. :)</p>
4353
4354 <p>Vennlig hilsen,
4355 <br>--
4356 <br>Petter Reinholdtsen</p>
4357
4358       </div>
4359       <div class="tags">
4360
4361
4362         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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>.
4363
4364
4365       </div>
4366     </div>
4367     <div class="padding"></div>
4368
4369     <div class="entry">
4370       <div class="title">
4371         <a href="http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html">Standardkrav inn i anbudstekster?</a>
4372       </div>
4373       <div class="date">
4374         17th October 2010
4375       </div>
4376       <div class="body">
4377         <p>Hvis det å følge standarder skal ha noen effekt overfor
4378 leverandører, så må slike krav og ønsker komme inn i anbudstekster når
4379 systemer kjøpes inn.  Har ikke sett noen slike formuleringer i anbud
4380 så langt, men har tenkt litt på hva som bør inn.  Her er noen ideer og
4381 forslag.  Min drøm er at en kan sette krav til slik støtte i
4382 anbudstekster, men så langt er det nok mer sannsynlig at en må nøye
4383 seg med å skrive at det er en fordel om slik støtte er tilstede i
4384 leveranser.</p>
4385
4386 <p>Som systemadministrator på Universitetet er det typisk to områder
4387 som er problematiske for meg.  Det ene er admin-grensesnittene på
4388 tjenermaskiner, som vi ønsker å bruke via ssh.  Det andre er nettsider
4389 som vi ønsker å bruke via en nettleser.  For begge deler er det viktig
4390 at protokollene og formatene som brukes følger standarder våre verktøy
4391 støtter.</p>
4392
4393 <p>De fleste har nå støtte for SSH som overføringsprotkoll for
4394 admin-grensesnittet, men det er ikke tilstrekkelig for å kunne stille
4395 inn f.eks BIOS og RAID-kontroller via ssh-forbindelsen.  Det er flere
4396 aktuelle protokoller for fremvisning av BIOS-oppsett og
4397 oppstartmeldinger, og min anbefaling ville være å kreve
4398 VT100-kompatibel protokoll, for å sikre at flest mulig
4399 terminalemulatorer kan forstå hva som kommer fra admin-grensesnittet
4400 via ssh.  Andre aktuelle alternativer er ANSI-terminalemulering og
4401 VT220.  Kanskje en formulering ala dette i anbudsutlysninger vil
4402 fungere:</p>
4403
4404 <p><blockquote>
4405 BIOS og oppstartmeldinger i administrasjonsgrensesnittet til maskinen
4406 bør/skal være tilgjengelig via SSH-protokollen som definert av IETF
4407 (RFC 4251 mfl.) og følge terminalfremvisningprotokollen VT100 (ref?)
4408 når en kobler seg til oppstart via ssh.
4409 </blockquote></p>
4410
4411 <p>Har ikke lykkes med å finne en god referanse for
4412 VT100-spesifikasjonen.</p>
4413
4414 <p>Når det gjelder nettsider, så er det det HTML, CSS og
4415 JavaScript-spesifikasjonen til W3C som gjelder.</p>
4416
4417 <p><blockquote>
4418 Alle systemets nettsider bør/skal være i henhold til statens
4419 standardkatalogs krav om nettsider og følge HTML-standarden som
4420 definert av W3C, og validere uten feil hos W3Cs HTML-validator
4421 (http://validator.w3.org).  Hvis det brukes CSS så bør/skal denne
4422 validere uten feil hos W3Cs CSS-validator
4423 (http://jigsaw.w3.org/css-validator/).  Eventuelle JavaScript skal
4424 være i henhold til EcmaScript-standarden.  I tillegg til å følge de
4425 overnevnte standardene skal websidene fungere i nettleserne (fyll inn
4426 relevant liste for organisasjonen) Firefox 3.5, Internet Explorer 8,
4427 Opera 9, etc.
4428 </blockquote></p>
4429
4430 <p>Vil et slikt avsnitt være konkret nok til å få leverandørene til å
4431 lage nettsider som følger standardene og fungerer i flere
4432 nettlesere?</p>
4433
4434 <p>Tar svært gjerne imot innspill på dette temaet til aktive (at)
4435 nuug.no, og er spesielt interessert i hva andre skriver i sine anbud
4436 for å oppmuntre leverandører til å følge standardene.  Kanskje NUUG
4437 burde lage et dokument med forslag til standardformuleringer å ta med
4438 i anbudsutlysninger?</p>
4439
4440 <p>Oppdatering 2010-12-03: I følge Wikipedias oppføring om
4441 <a href="http://en.wikipedia.org/wiki/ANSI_escape_code">ANSI escape
4442 code</a>, så bruker VT100-terminaler ECMA-48-spesifikasjonen som
4443 basis for sin oppførsel.  Det kan dermed være et alternativ når en
4444 skal spesifisere hvordan seriell-konsoll skal fungere.</p>
4445
4446       </div>
4447       <div class="tags">
4448
4449
4450         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>.
4451
4452
4453       </div>
4454     </div>
4455     <div class="padding"></div>
4456
4457     <div class="entry">
4458       <div class="title">
4459         <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>
4460       </div>
4461       <div class="date">
4462          9th September 2010
4463       </div>
4464       <div class="body">
4465         <p>A few days ago I had the mixed pleasure of bying a new digital
4466 camera, a Canon IXUS 130.  It was instructive and very disturbing to
4467 be able to verify that also this camera producer have the nerve to
4468 specify how I can or can not use the videos produced with the camera.
4469 Even thought I was aware of the issue, the options with new cameras
4470 are limited and I ended up bying the camera anyway.  What is the
4471 problem, you might ask?  It is software patents, MPEG-4, H.264 and the
4472 MPEG-LA that is the problem, and our right to record our experiences
4473 without asking for permissions that is at risk.
4474
4475 <p>On page 27 of the Danish instruction manual, this section is
4476 written:</p>
4477
4478 <blockquote>
4479 <p>This product is licensed under AT&T patents for the MPEG-4 standard
4480 and may be used for encoding MPEG-4 compliant video and/or decoding
4481 MPEG-4 compliant video that was encoded only (1) for a personal and
4482 non-commercial purpose or (2) by a video provider licensed under the
4483 AT&T patents to provide MPEG-4 compliant video.</p>
4484
4485 <p>No license is granted or implied for any other use for MPEG-4
4486 standard.</p>
4487 </blockquote>
4488
4489 <p>In short, the camera producer have chosen to use technology
4490 (MPEG-4/H.264) that is only provided if I used it for personal and
4491 non-commercial purposes, or ask for permission from the organisations
4492 holding the knowledge monopoly (patent) for technology used.</p>
4493
4494 <p>This issue has been brewing for a while, and I recommend you to
4495 read
4496 "<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
4497 Our Civilization's Video Art and Culture is Threatened by the
4498 MPEG-LA</a>" by Eugenia Loli-Queru and
4499 "<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
4500 The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
4501 the issue.  The solution is to support the
4502 <a href="http://www.digistan.org/open-standard:definition">free and
4503 open standards</a> for video, like <a href="http://www.theora.org/">Ogg
4504 Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
4505
4506       </div>
4507       <div class="tags">
4508
4509
4510         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/h264">h264</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>.
4511
4512
4513       </div>
4514     </div>
4515     <div class="padding"></div>
4516
4517     <div class="entry">
4518       <div class="title">
4519         <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">Officeshots taking shape</a>
4520       </div>
4521       <div class="date">
4522         13th June 2010
4523       </div>
4524       <div class="body">
4525         <p>For those of us caring about document exchange and
4526 interoperability, <a href="http://www.officeshots.org/">OfficeShots</a>
4527 is a great service.  It is to ODF documents what
4528 <a href="http://browsershots.org/">BrowserShots</a> is for web
4529 pages.</p>
4530
4531 <p>A while back, I was contacted by Knut Yrvin at the part of Nokia
4532 that used to be Trolltech, who wanted to help the OfficeShots project
4533 and wondered if the University of Oslo where I work would be
4534 interested in supporting the project.  I helped him to navigate his
4535 request to the right people at work, and his request was answered with
4536 a spot in the machine room with power and network connected, and Knut
4537 arranged funding for a machine to fill the spot.  The machine is
4538 administrated by the OfficeShots people, so I do not have daily
4539 contact with its progress, and thus from time to time check back to
4540 see how the project is doing.</p>
4541
4542 <p>Today I had a look, and was happy to see that the Dell box in our
4543 machine room now is the host for several virtual machines running as
4544 OfficeShots factories, and the project is able to render ODF documents
4545 in 17 different document processing implementation on Linux and
4546 Windows.  This is great.</p>
4547
4548       </div>
4549       <div class="tags">
4550
4551
4552         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>.
4553
4554
4555       </div>
4556     </div>
4557     <div class="padding"></div>
4558
4559     <div class="entry">
4560       <div class="title">
4561         <a href="http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html">A manual for standards wars...</a>
4562       </div>
4563       <div class="date">
4564          6th June 2010
4565       </div>
4566       <div class="body">
4567         <p>Via the
4568 <a href="http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html">blog
4569 of Rob Weir</a> I came across the very interesting essay named
4570 <a href="http://faculty.haas.berkeley.edu/shapiro/wars.pdf">The Art of
4571 Standards Wars</a> (PDF 25 pages).  I recommend it for everyone
4572 following the standards wars of today.</p>
4573
4574       </div>
4575       <div class="tags">
4576
4577
4578         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>.
4579
4580
4581       </div>
4582     </div>
4583     <div class="padding"></div>
4584
4585     <div class="entry">
4586       <div class="title">
4587         <a href="http://people.skolelinux.org/pere/blog/Danmark_g_r_for_ODF_.html">Danmark går for ODF?</a>
4588       </div>
4589       <div class="date">
4590         29th January 2010
4591       </div>
4592       <div class="body">
4593         <p>Ble nettopp gjort oppmerksom på en
4594 <a href="http://www.version2.dk/artikel/13690-breaking-odf-vinder-dokumentformat-krigen ">nyhet fra Version2</a>
4595 fra Danmark, der det hevdes at Folketinget har vedtatt at ODF skal
4596 brukes som dokumentutvekslingsformat i Staten.</p>
4597
4598 <p>Hyggelig lesning, spesielt hvis det viser seg at de av vedtatt
4599 kravlisten for hva som skal aksepteres som referert i kommentarfeltet
4600 til artikkelen og
4601 <a href="http://www.version2.dk/artikel/13693-er-ooxml-doemt-ude-her-er-kravene-til-en-offentlig-dokumentstandard">en
4602 annen artikkel</a> i samme nett-avis.  Liker spesielt godt denne:</p>
4603
4604 <p><blockquote> Det skal demonstreres, at standarden i sin helhed kan
4605 implementeres af alle direkte i sin helhed på flere
4606 platforme.</blockquote></p>
4607
4608 <p>Noe slikt burde være et krav også i Norge.</p>
4609
4610       </div>
4611       <div class="tags">
4612
4613
4614         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>.
4615
4616
4617       </div>
4618     </div>
4619     <div class="padding"></div>
4620
4621     <div class="entry">
4622       <div class="title">
4623         <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>
4624       </div>
4625       <div class="date">
4626         12th August 2009
4627       </div>
4628       <div class="body">
4629         <p>Just for fun, I did a search right now on Google for a few file ODF
4630 and MS Office based formats (not to be mistaken for ISO or ECMA
4631 OOXML), to get an idea of their relative usage.  I searched using
4632 'filetype:odt' and equvalent terms, and got these results:</P>
4633
4634 <table>
4635 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
4636 <tr><td>Tekst</td> <td>odt:282000</td> <td>docx:308000</td></tr>
4637 <tr><td>Presentasjon</td> <td>odp:75600</td> <td>pptx:183000</td></tr>
4638 <tr><td>Regneark</td> <td>ods:26500     </td> <td>xlsx:145000</td></tr>
4639 </table>
4640
4641 <p>Next, I added a 'site:no' limit to get the numbers for Norway, and
4642 got these numbers:</p>
4643
4644 <table>
4645 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
4646 <tr><td>Tekst</td> <td>odt:2480 </td> <td>docx:4460</td></tr>
4647 <tr><td>Presentasjon</td> <td>odp:299   </td> <td>pptx:741</td></tr>
4648 <tr><td>Regneark</td> <td>ods:187       </td> <td>xlsx:372</td></tr>
4649 </table>
4650
4651 <p>I wonder how these numbers change over time.</p>
4652
4653 <p>I am aware of Google returning different results and numbers based
4654 on where the search is done, so I guess these numbers will differ if
4655 they are conduced in another country.  Because of this, I did the same
4656 search from a machine in California, USA, a few minutes after the
4657 search done from a machine here in Norway.</p>
4658
4659
4660 <table>
4661 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
4662 <tr><td>Tekst</td> <td>odt:129000</td> <td>docx:308000</td></tr>
4663 <tr><td>Presentasjon</td> <td>odp:44200</td> <td>pptx:93900</td></tr>
4664 <tr><td>Regneark</td> <td>ods:26500     </td> <td>xlsx:82400</td></tr>
4665 </table>
4666
4667 <p>And with 'site:no':
4668
4669 <table>
4670 <tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
4671 <tr><td>Tekst</td> <td>odt:2480</td> <td>docx:3410</td></tr>
4672 <tr><td>Presentasjon</td> <td>odp:175</td> <td>pptx:604</td></tr>
4673 <tr><td>Regneark</td> <td>ods:186       </td> <td>xlsx:296</td></tr>
4674 </table>
4675
4676 <p>Interesting difference, not sure what to conclude from these
4677 numbers.</p>
4678
4679       </div>
4680       <div class="tags">
4681
4682
4683         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>.
4684
4685
4686       </div>
4687     </div>
4688     <div class="padding"></div>
4689
4690     <div class="entry">
4691       <div class="title">
4692         <a href="http://people.skolelinux.org/pere/blog/ISO_still_hope_to_fix_OOXML.html">ISO still hope to fix OOXML</a>
4693       </div>
4694       <div class="date">
4695          8th August 2009
4696       </div>
4697       <div class="body">
4698         <p>According to <a
4699 href="http://twerner.blogspot.com/2009/08/defects-of-office-open-xml.html">a
4700 blog post from Torsten Werner</a>, the current defect report for ISO
4701 29500 (ISO OOXML) is 809 pages.  His interesting point is that the
4702 defect report is 71 pages more than the full ODF 1.1 specification.
4703 Personally I find it more interesting that ISO still believe ISO OOXML
4704 can be fixed in ISO.  Personally, I believe it is broken beyon repair,
4705 and I completely lack any trust in ISO for being able to get anywhere
4706 close to solving the problems.  I was part of the Norwegian committee
4707 involved in the OOXML fast track process, and was not impressed with
4708 Standard Norway and ISO in how they handled it.</p>
4709
4710 <p>These days I focus on ODF instead, which seem like a specification
4711 with the future ahead of it.  We are working in NUUG to organise a ODF
4712 seminar this autumn.</p>
4713
4714       </div>
4715       <div class="tags">
4716
4717
4718         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>.
4719
4720
4721       </div>
4722     </div>
4723     <div class="padding"></div>
4724
4725     <div class="entry">
4726       <div class="title">
4727         <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>
4728       </div>
4729       <div class="date">
4730          9th July 2009
4731       </div>
4732       <div class="body">
4733         <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
4734 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
4735 for regjeringen da de tok sin avgjørelse.  De er nå lagt ut på NUUGs
4736 wiki, direkte tilgjengelig via "<a
4737 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
4738 v2.0 - Oppsummering av høring</a>" og "<a
4739 href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
4740 for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
4741 UTKAST</a>".</p>
4742
4743 <p>Det er tre ting jeg merker meg i oppsummeringen fra
4744 høringsuttalelsen da jeg skummet igjennom den.  Det første er at
4745 forståelsen av hvordan programvarepatenter påvirker fri
4746 programvareutvikling også i Norge når en argumenterer med at
4747 royalty-betaling ikke er et relevant problem i Norge.  Det andre er at
4748 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
4749 standard innenfor hvert område.  Det siste er at påstander i
4750 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
4751 Microsoft om hvordan Ogg blir standardisert og påstanden fra
4752 politidirektoratet om patentproblemer i Theora).</p>
4753
4754       </div>
4755       <div class="tags">
4756
4757
4758         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>.
4759
4760
4761       </div>
4762     </div>
4763     <div class="padding"></div>
4764
4765     <div class="entry">
4766       <div class="title">
4767         <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>
4768       </div>
4769       <div class="date">
4770          6th July 2009
4771       </div>
4772       <div class="body">
4773         <p>Jeg ble glad da regjeringen
4774 <a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
4775 versjon 2 av
4776 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
4777 referansekatalog over standarder</a>, men trist da jeg leste hva som
4778 faktisk var vedtatt etter
4779 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
4780 De fleste av de valgte åpne standardene er gode og vil bidra til at
4781 alle kan delta på like vilkår i å lage løsninger for staten, men
4782 noen av dem blokkerer for de som ikke har anledning til å benytte
4783 spesifikasjoner som krever betaling for bruk (såkalt
4784 royalty-betaling).  Det gjelder spesifikt for H.264 for video og MP3
4785 for lyd.  Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
4786 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
4787 fra statens websider gjøre dette uten å måtte bruke programmer der
4788 betaling for bruk var nødvendig.  Når det nå er gjort valgfritt for
4789 de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
4790 Vorbis), så vil en bli tvunget til å forholde seg til
4791 royalty-belastede standarder for å få tilgang til videoen og
4792 lyden.</p>
4793
4794 <p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
4795 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
4796 være uten royalty-betaling.  Jeg håper det ikke betyr at en har mistet
4797 all forståelse for hvilke prinsipper som må følges for å oppnå
4798 likeverdig konkurranse mellom aktørene i IT-bransjen.  NUUG advarte
4799 mot dette i
4800 <a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
4801 høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
4802
4803 <p>Oppdatering 2012-06-29: Kom over <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">en
4804 rapport til FAD</a> fra da versjon 1 av katalogen ble vedtatt, og der
4805 er det tydelig at problemstillingen var kjent og forstått.</p>
4806
4807       </div>
4808       <div class="tags">
4809
4810
4811         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/h264">h264</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/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>.
4812
4813
4814       </div>
4815     </div>
4816     <div class="padding"></div>
4817
4818     <div class="entry">
4819       <div class="title">
4820         <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
4821       </div>
4822       <div class="date">
4823         26th June 2009
4824       </div>
4825       <div class="body">
4826         <p>I
4827 <a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
4828 sin høringsuttalelse</a> til
4829 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
4830 til versjon 2 av statens referansekatalog over standarder</a>, lirer
4831 de av seg følgende FUD-perle:</p>
4832
4833 <p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
4834   spesifikasjoner overordnet styrt av xiph.org, som er en
4835   ikke-kommersiell organisasjon.  Etablerte og anerkjente
4836   standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
4837   innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
4838   Det er derimot helt opp til hver enkelt organisasjon å bestemme
4839   hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
4840   spesifikasjonene bør derfor ikke defineres som åpne
4841   standarder."</blockquote></p>
4842
4843 <p>De vokter seg vel for å nevne den anerkjente
4844 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
4845 IP og det meste av protokoller på Internet, og RFC-standardene som
4846 IETF står bak.  Ogg er spesifisert i
4847 <a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
4848 tvil å anse som en åpen standard.  Vorbis er
4849 <a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>.  Theora er
4850
4851 under standardisering via IETF, med
4852 <a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
4853 utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
4854 skrevet i stein ennå, men det blir neppe endringer som ikke er
4855 bakoverkompatibel).  De kan være inne på noe når det gjelder FLAC da
4856 jeg ikke finner tegn til at <a
4857 href="http://flac.sourceforge.net/format.html">spesifikasjonen
4858 tilgjengelig på web</a> er på tur via noen
4859 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
4860 og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
4861 bort fra at også den organiseres via IETF.  Jeg kjenner personlig lite
4862 til FLAC.</p>
4863
4864 <p>Uredelig argumentasjon bør en holde seg for god til å komme med,
4865 spesielt når det er så enkelt i dagens Internet-hverdag å gå
4866 misvisende påstander etter i sømmene.</p>
4867
4868       </div>
4869       <div class="tags">
4870
4871
4872         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>.
4873
4874
4875       </div>
4876     </div>
4877     <div class="padding"></div>
4878
4879     <div class="entry">
4880       <div class="title">
4881         <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>
4882       </div>
4883       <div class="date">
4884         19th May 2009
4885       </div>
4886       <div class="body">
4887         <p>En standard er noe man samler seg rundt, ut fra ideen om at en får
4888 fordeler når mange står sammen.  Jo flere som står sammen, jo
4889 bedre.  Når en vet dette, blir det litt merkelig å lese noen av
4890 uttalelsene som er kommet inn til
4891 <a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2/horingsuttalelser.html?id=549423">høringen
4892 om versjon 2 av statens referansekatalog over standarder</a>.  Blant
4893 annet Abelia, NHO og Microsoft tror det er lurt med flere standarder
4894 innenfor samme område.  Det blir som å si at det er fint om Norge
4895 standardiserte både på A4- og Letter-størrelser på arkene, ulik
4896 sporvidde på jernbaneskinnene, meter og fot som lengemål, eller
4897 høyre- og venstrekjøring - slik at en kan konkurrere på hvilken
4898 standard som er best.  De fleste forstår heldigvis at dette ikke
4899 bidrar positivt.</p>
4900
4901       </div>
4902       <div class="tags">
4903
4904
4905         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>.
4906
4907
4908       </div>
4909     </div>
4910     <div class="padding"></div>
4911
4912     <div class="entry">
4913       <div class="title">
4914         <a href="http://people.skolelinux.org/pere/blog/Hvorfor_jeg_ikke_bruker_eFaktura.html">Hvorfor jeg ikke bruker eFaktura</a>
4915       </div>
4916       <div class="date">
4917         23rd April 2009
4918       </div>
4919       <div class="body">
4920         <p>Telenors annonsering om å kreve 35 kroner i gebyr fra alle som
4921 ønsker papirfaktura har satt sinnene i kok, og pressedekningen så
4922 langt snakker om at eldre og folk som ikke behersker data vil få en
4923 urimelig ekstrakostnad.  Jeg tror ikke jeg passer inn i noen av de
4924 kategoriene, men velger å holde meg unna eFaktura - som er det
4925 Telenor ønsker å få folk over på - pga. systemets egenskaper.</p>
4926
4927 <p>Slik jeg har sett eFaktura til forbrukere så langt, så sender
4928 selger en elektronisk beskjed til kundens bank, som legger ut
4929 informasjon om fakturaen i nettbanken for godkjenning.  Personlig
4930 ville jeg sett det som mer naturlig at det gikk en elektronisk beskjed
4931 fra selger til kunde, dvs meg, og at jeg så kunne bruke den videre
4932 mot banken eller andre hvis jeg ønsket dette.  Mine innkjøp og
4933 regninger er jo en sak mellom meg og mine leverandører, ikke en sak
4934 mellom min bank og mine leverandører.  Kun hvis jeg ønsker å betale
4935 fakturaen skal banken involveres.  En faktura bør jo inn i
4936 regnskapet, og jeg ønsker mulighet til å legge det inn der.  Når
4937 fakturaen sendes til banken i stedet for meg, blir det vanskeligere.
4938 Hele eFaktura-modellen virker på meg som en umyndiggjøring av meg
4939 som kunde.</p>
4940
4941 <p>I tillegg har jeg ikke vært i stand til å finne
4942 eFaktura-formatets spesifikasjon, og det ser ut til at utsending av
4943 slike krever dyre avtaler med bankene for å få lov til å sende ut
4944 eFaktura til kunder.  Jeg ser vel helst at fakturering på
4945 elektroniske formater kan gjøres f.eks. via epost eller HTTP uten å
4946 måtte betale mellommenn for retten til å lever ut en faktura, og
4947 liker rett og slett ikke dagens faktureringsmodeller.</p>
4948
4949       </div>
4950       <div class="tags">
4951
4952
4953         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>.
4954
4955
4956       </div>
4957     </div>
4958     <div class="padding"></div>
4959
4960     <div class="entry">
4961       <div class="title">
4962         <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>
4963       </div>
4964       <div class="date">
4965         30th March 2009
4966       </div>
4967       <div class="body">
4968         <p>Where I work at the University of Oslo, one decision stand out as a
4969 very good one to form a long lived computer infrastructure.  It is the
4970 simple one, lost by many in todays computer industry: Standardize on
4971 open network protocols and open exchange/storage formats, not applications.
4972 Applications come and go, while protocols and files tend to stay, and
4973 thus one want to make it easy to change application and vendor, while
4974 avoiding conversion costs and locking users to a specific platform or
4975 application.</p>
4976
4977 <p>This approach make it possible to replace the client applications
4978 independently of the server applications.  One can even allow users to
4979 use several different applications as long as they handle the selected
4980 protocol and format.  In the normal case, only one client application
4981 is recommended and users only get help if they choose to use this
4982 application, but those that want to deviate from the easy path are not
4983 blocked from doing so.</p>
4984
4985 <p>It also allow us to replace the server side without forcing the
4986 users to replace their applications, and thus allow us to select the
4987 best server implementation at any moment, when scale and resouce
4988 requirements change.</p>
4989
4990 <p>I strongly recommend standardizing - on open network protocols and
4991 open formats, but I would never recommend standardizing on a single
4992 application that do not use open network protocol or open formats.</p>
4993
4994       </div>
4995       <div class="tags">
4996
4997
4998         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>.
4999
5000
5001       </div>
5002     </div>
5003     <div class="padding"></div>
5004
5005     <div class="entry">
5006       <div class="title">
5007         <a href="http://people.skolelinux.org/pere/blog/Hva_er_egentlig_en__pen_standard_.html">Hva er egentlig en åpen standard?</a>
5008       </div>
5009       <div class="date">
5010         28th March 2009
5011       </div>
5012       <div class="body">
5013         <p>Jeg møter alle slags interessante mennesker på min vei, og et møte
5014 jeg lærte mye av var å treffe på en svært kompetent IT-fyr som
5015 benektet ting jeg anser som åpenbart og selvfølgelig når det gjelder
5016 standarder.  Det var interessant, da det fikk meg til å tenke litt
5017 nøyere på hvilke mekanismer som ligger til grunn for at noe oppfattes
5018 som en standard.  Det hele startet med arbeid rundt integrering av NSS
5019 LDAP mot Active Directory, og problemer som oppstår pga. at Active
5020 Directory ikke følger LDAP-spesifikasjonen som dokumentert i RFCer fra
5021 IETF (konkret, AD returnerer kun et subset av attributter hvis det er
5022 mer enn 1500 atributter av en gitt type i et LDAP-objekt, og en må be
5023 om resten i bolker av 1500).  Jeg hevdet måten dette ble gjort på brøt
5024 med LDAP-spesifikasjonen, og henviste til hvor i LDAP-spesifikasjonen
5025 fra IETF det sto at oppførselen til AD ikke fulgte
5026 LDAP-spesifikasjonen.  AD-spesialisten overrasket meg da ved å
5027 fortelle at IETF var ikke de som definerte LDAP-spesifikasjonen, og at
5028 Active Directory ikke brøt den virkelige LDAP-spesifikasjonen som han
5029 mente lå til grunn.  Jeg ble spesielt overrasket over denne
5030 tilnærmingen til problemstillingen, da til og med Microsoft så vidt
5031 jeg kan se anerkjenner IETF som organisasjonen som definerer
5032 LDAP-spesifikasjonen.  Jeg fikk aldri spurt hvem han mente sto bak den
5033 egentlige LDAP-spesifikasjonen, da det var irrelevant for problemet vi
5034 måtte løse (få Linux og AD til å fungere sammen).  Dette møtet
5035 fortalte meg uansett at det ikke er gitt at alle aktører er enige om
5036 hva en standard er, og hva som er kilden til en gitt standard.  Det er
5037 vanskelig å enes om felles standarder før en først enes om hvem som
5038 bestemmer hva en gitt standard innebærer.</p>
5039
5040 <p>Hva er så en standard?  I sin abstrakte form er det noe å samles
5041 om.  På engelsk er en av betydningene fane brukt i krig, du vet, den
5042 type fane en samlet seg rundt på kamplassen i riddertiden.  En
5043 standard definerer altså et felleskap, noen som har noe felles.  Det
5044 er naturligvis mange måter å utgjøre et felleskap på.  En kan
5045 f.eks. enes om å gjøre alt slik som Ole gjør det, og dermed si at Oles
5046 oppførsel er standard.  Hver gang Ole endrer oppførsel endrer også
5047 standarden seg uten noe mer organisering og prosedyre.  En variant av
5048 dette er å gjøre slik som Ole har gjort det i stedet for slik Ole til
5049 enhver til gjør noe.  Dette er ofte litt enklere å forholde seg til,
5050 da en slipper å sjekke med Ole hver gang for å vite hvordan ting skal
5051 gjøres nå, men hvis det Ole gjorde noe dumt den gang en bestemte seg
5052 for å følge Ole, så er det vanskeligere å få endret oppførsel for å
5053 unngå dette dumme.</p>
5054
5055 <p>En kan også ta det et skritt videre, og istedet for å basere seg på
5056 enkeltpersoners oppførsel sette seg ned og bli enige om hvordan en
5057 skal gjøre ting, dvs. lage et felleskap basert på konsensus.  Dette
5058 tar naturligvis litt mer tid (en må diskutere ting i forkant før en
5059 kan sette igang), men det kan bidra til at den oppførselen en
5060 planlegger å benytte seg av er mer gjennomtenkt.  Det ender også
5061 typisk opp med en beskrivelse av ønsket oppførsel som flere kan forstå
5062 - da flere har vært involvert i å utarbeide beskrivelsen.</p>
5063
5064 <p>Dette er dessverre ikke alt som trengs for å forstå hva en åpen
5065 standard er for noe.  Der alle kan se på hvordan folk oppfører seg, og
5066 dermed har valget om de vil oppføre seg likt eller ikke, så er det
5067 endel juridiske faktorer som gjør det hele mer komplisert -
5068 opphavsretten og patentlovgivningen for å være helt konkret.  For å gi
5069 et eksempel. Hvis noen blir enige om å alltid plystre en bestemt
5070 melodi når de møtes, for å identifisere hverandre, så kan
5071 opphavsretten brukes til å styre hvem som får lov til å gjøre dette.
5072 De har standardisert hvordan de kjenner igjen alle som følger denne
5073 standarden, men ikke alle har nødvendigvis lov til å følge den.
5074 Musikk er opphavsrettsbeskyttet, og fremføring av musikk i
5075 offentligheten er opphavsmannens enerett (dvs. et monopol).  Det vil i
5076 sin ytterste konsekvens si at alle som skal plystre en
5077 opphavsrettsbeskyttet melodi i det offentlige rom må ha godkjenning
5078 fra opphavsmannen.  Har en ikke dette, så bryter en loven og kan
5079 straffes.  Det er dermed mulig for opphavsmannen å kontrollere hvem
5080 som får lov til å benytte seg av denne standarden.  En annen variant
5081 er hvis en standard er dokumentert, så er dokumentet som definerer
5082 standarden (spesifikasjonen) beskyttet av opphavsretten, og det er
5083 dermed mulig for rettighetsinnehaver å begrense tilgang til
5084 spesifikasjonen, og slik styre hvem som kan ta i bruk standarden på
5085 den måten.</p>
5086
5087 <p>Der opphavsretten innvilger et monopol på kunstneriske uttrykk med
5088 verkshøyde, innvilger patentlovgivningen monopol på ideer.  Hvis en
5089 slik patentert idé (fortrinnsvis uttrykt i en teknisk innretning, men
5090 det er kompliserende faktorer som gjør at det ikke er et krav) trengs
5091 for å ta i bruk en standard, så vil den som innehar patent kunne styre
5092 hvem som får ta i bruk standarden.  Det er dermed ikke gitt at alle
5093 kan delta i et standard-felleskap, og hvis de kan delta, så er det
5094 ikke sikkert at det er på like vilkår.  F.eks. kan rettighetsinnehaver
5095 sette vilkår som gjør at noen faller utenfor, det være seg av
5096 finansielle, avtalemessige eller prinsipielle årsaker.  Vanlige slike
5097 vilkår er "må betale litt for hver kunde/bruker" som utelukker de som
5098 gir bort en løsning gratis og "må gi fra seg retten til å håndheve
5099 sine egne patentrettigheter ovenfor rettighetshaver" som utelukker
5100 alle som ønsker å beholde den muligheten.</p>
5101
5102 <p>En åpen standard innebærer for meg at alle kan få innsikt i en
5103 komplett beskrivelse av oppførsel som standarden skal dekke, og at
5104 ingen kan nektes å benytte seg av standarden.  Noen mener at det
5105 holder at alle med tilstrekkelig finansiering kan få tilgang til
5106 spesifikasjonen og at en kun har finansielle krav til bruk.
5107 Pga. denne konflikten har et nytt begrep spredt seg de siste årene,
5108 nemlig fri og åpen standard, der en har gjort det klart at alle må ha
5109 komplett og lik tilgang til spesifikasjoner og retten til å gjøre bruk
5110 av en standard for at en standard skal kunne kalles fri og åpen.</p>
5111
5112       </div>
5113       <div class="tags">
5114
5115
5116         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>.
5117
5118
5119       </div>
5120     </div>
5121     <div class="padding"></div>
5122
5123     <div class="entry">
5124       <div class="title">
5125         <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>
5126       </div>
5127       <div class="date">
5128         31st January 2009
5129       </div>
5130       <div class="body">
5131         <p>Det er mange ulike definisjoner om hva en åpen standard er for noe,
5132 og NUUG hadde <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">en
5133 pressemelding om dette sommeren 2005</a>.  Der ble definisjonen til
5134 <a href="http://www.aaben-standard.dk/">DKUUG</a>,
5135 <a href="http://europa.eu.int/idabc/servlets/Doc?id=19529">EU-kommissionens
5136 European Interoperability Framework ( side 9)</a> og
5137 <a href="http://www.teknologiradet.no/files/7polert_copy.htm">teknologirådet</a> omtalt.</p>
5138
5139 <p>Siden den gang har regjeringens standardiseringsråd dukket opp, og de
5140 ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
5141 <a href="http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=476407">sin
5142 arbeidsmetodikk</a>.  Personlig synes jeg det er en god ide, da
5143 kravene som stilles der gjør at alle markedsaktører får like vilkår,
5144 noe som kommer kundene til gode ved hjelp av økt konkurranse.</p>
5145
5146 <p>I sommer kom det en ny definisjon på banen.
5147 <a href="http://www.digistan.org/">Digistan</a> lanserte
5148 <a href="http://www.digistan.org/open-standard:definition">en
5149 definisjon på en fri og åpen standard</a>.  Jeg liker måten de bryter
5150 ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
5151 ved å legge på et ord og poengtere at en standard som er både åpen og
5152 fri har noen spesielle krav.  Her er den definisjonen etter rask
5153 oversettelse fra engelsk til norsk av meg:</p>
5154
5155 <blockquote>
5156 <p><strong>Definisjonen av en fri og åpen standard</strong></p>
5157
5158 <p>Den digitale standardorganisasjonen definierer fri og åpen standard
5159 som følger:</p>
5160 <ul>
5161 <li>En fri og åpen standard er immun for leverandørinnlåsing i alle
5162 stadier av dens livssyklus.  Immuniteten fra leverandørinnlåsing gjør
5163 det mulig å fritt bruke, forbedre, stole på og utvide en standard over
5164 tid.</li>
5165 <li>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
5166 organisasjon, og dens pågående utvikling gjøres med en åpen
5167 beslutningsprosedyre som er tilgjengelig for alle som er interessert i
5168 å delta.</li>
5169 <li>Standarden er publisert og spesifikasjonsdokumentet er fritt
5170 tilgjengelig.  Det må være tillatt for alle å kopiere, distribuere og
5171 bruke den uten begresninger.</li>
5172 <li>Patentene som muligens gjelder (deler av) standarden er gjort
5173 ugjenkallelig tilgjengelig uten krav om betaling.</li>
5174 <li>Det er ingen begresninger i gjenbruk av standarden.</li>
5175 </ul>
5176 <p>Det økonomiske resultatet av en fri og åpen standard, som kan
5177 måles, er at det muliggjør perfekt konkurranse mellom leverandører av
5178 produkter basert på standarden.</p>
5179 </blockquote>
5180
5181 <p>(Tar gjerne imot forbedringer av oversettelsen.)</p>
5182
5183       </div>
5184       <div class="tags">
5185
5186
5187         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>.
5188
5189
5190       </div>
5191     </div>
5192     <div class="padding"></div>
5193
5194     <div class="entry">
5195       <div class="title">
5196         <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>
5197       </div>
5198       <div class="date">
5199         22nd January 2009
5200       </div>
5201       <div class="body">
5202         <p>I går publiserte
5203 <a href="http://universitas.no/nyhet/52776/">Universitas</a>,
5204 <a href="http://www.dagensit.no/trender/article1588462.ece">Dagens-IT</a>
5205 og <a href="http://www.idg.no/computerworld/article118622.ece">Computerworld
5206 Norge</a> en sak om at de ansatte ved Universitetet i Oslo ikke følger
5207 regjeringens pålegg om å publisere i HTML, PDF eller ODF.  Det er bra
5208 at det kommer litt fokus på dette, og jeg håper noen journalister tar
5209 en titt på de andre statlige instansene også.</p>
5210
5211 <p>Skulle ønske det var en enkel måte å sjekke om ODF-dokumenter er i
5212 henholdt til ODF-spesifikasjonen, og en måte å teste om programmer som
5213 hevder å støtte ODF forstår alle delene av ODF-spesifikasjonen.
5214 Kjenner kun til ufullstendige løsninger for slikt.</p>
5215
5216       </div>
5217       <div class="tags">
5218
5219
5220         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>.
5221
5222
5223       </div>
5224     </div>
5225     <div class="padding"></div>
5226
5227     <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>
5228     <div id="sidebar">
5229
5230
5231
5232 <h2>Archive</h2>
5233 <ul>
5234
5235 <li>2019
5236 <ul>
5237
5238 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/01/">January (4)</a></li>
5239
5240 <li><a href="http://people.skolelinux.org/pere/blog/archive/2019/02/">February (3)</a></li>
5241
5242 </ul></li>
5243
5244 <li>2018
5245 <ul>
5246
5247 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/01/">January (1)</a></li>
5248
5249 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/02/">February (5)</a></li>
5250
5251 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/03/">March (5)</a></li>
5252
5253 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/04/">April (3)</a></li>
5254
5255 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/06/">June (2)</a></li>
5256
5257 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/07/">July (5)</a></li>
5258
5259 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/08/">August (3)</a></li>
5260
5261 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/09/">September (3)</a></li>
5262
5263 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/10/">October (5)</a></li>
5264
5265 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/11/">November (2)</a></li>
5266
5267 <li><a href="http://people.skolelinux.org/pere/blog/archive/2018/12/">December (4)</a></li>
5268
5269 </ul></li>
5270
5271 <li>2017
5272 <ul>
5273
5274 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
5275
5276 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
5277
5278 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
5279
5280 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
5281
5282 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
5283
5284 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
5285
5286 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/08/">August (1)</a></li>
5287
5288 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/09/">September (3)</a></li>
5289
5290 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/10/">October (5)</a></li>
5291
5292 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/11/">November (3)</a></li>
5293
5294 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/12/">December (4)</a></li>
5295
5296 </ul></li>
5297
5298 <li>2016
5299 <ul>
5300
5301 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
5302
5303 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
5304
5305 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
5306
5307 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
5308
5309 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
5310
5311 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
5312
5313 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
5314
5315 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
5316
5317 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
5318
5319 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
5320
5321 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
5322
5323 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
5324
5325 </ul></li>
5326
5327 <li>2015
5328 <ul>
5329
5330 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
5331
5332 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
5333
5334 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
5335
5336 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
5337
5338 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
5339
5340 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
5341
5342 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
5343
5344 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
5345
5346 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
5347
5348 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
5349
5350 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
5351
5352 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
5353
5354 </ul></li>
5355
5356 <li>2014
5357 <ul>
5358
5359 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
5360
5361 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
5362
5363 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
5364
5365 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
5366
5367 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
5368
5369 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
5370
5371 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
5372
5373 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
5374
5375 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
5376
5377 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
5378
5379 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
5380
5381 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
5382
5383 </ul></li>
5384
5385 <li>2013
5386 <ul>
5387
5388 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
5389
5390 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
5391
5392 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
5393
5394 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
5395
5396 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
5397
5398 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
5399
5400 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
5401
5402 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
5403
5404 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
5405
5406 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
5407
5408 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
5409
5410 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
5411
5412 </ul></li>
5413
5414 <li>2012
5415 <ul>
5416
5417 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
5418
5419 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
5420
5421 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
5422
5423 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
5424
5425 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
5426
5427 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
5428
5429 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
5430
5431 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
5432
5433 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
5434
5435 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
5436
5437 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
5438
5439 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
5440
5441 </ul></li>
5442
5443 <li>2011
5444 <ul>
5445
5446 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
5447
5448 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
5449
5450 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
5451
5452 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
5453
5454 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
5455
5456 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
5457
5458 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
5459
5460 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
5461
5462 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
5463
5464 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
5465
5466 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
5467
5468 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
5469
5470 </ul></li>
5471
5472 <li>2010
5473 <ul>
5474
5475 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
5476
5477 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
5478
5479 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
5480
5481 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
5482
5483 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
5484
5485 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
5486
5487 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
5488
5489 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
5490
5491 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
5492
5493 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
5494
5495 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
5496
5497 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
5498
5499 </ul></li>
5500
5501 <li>2009
5502 <ul>
5503
5504 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
5505
5506 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
5507
5508 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
5509
5510 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
5511
5512 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
5513
5514 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
5515
5516 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
5517
5518 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
5519
5520 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
5521
5522 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
5523
5524 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
5525
5526 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
5527
5528 </ul></li>
5529
5530 <li>2008
5531 <ul>
5532
5533 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
5534
5535 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
5536
5537 </ul></li>
5538
5539 </ul>
5540
5541
5542
5543 <h2>Tags</h2>
5544 <ul>
5545
5546  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (16)</a></li>
5547
5548  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
5549
5550  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
5551
5552  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
5553
5554  <li><a href="http://people.skolelinux.org/pere/blog/tags/betalkontant">betalkontant (8)</a></li>
5555
5556  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (11)</a></li>
5557
5558  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (17)</a></li>
5559
5560  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
5561
5562  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
5563
5564  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (167)</a></li>
5565
5566  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
5567
5568  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (4)</a></li>
5569
5570  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
5571
5572  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (17)</a></li>
5573
5574  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (25)</a></li>
5575
5576  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
5577
5578  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (398)</a></li>
5579
5580  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
5581
5582  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (14)</a></li>
5583
5584  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (33)</a></li>
5585
5586  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
5587
5588  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (20)</a></li>
5589
5590  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
5591
5592  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
5593
5594  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (16)</a></li>
5595
5596  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
5597
5598  <li><a href="http://people.skolelinux.org/pere/blog/tags/kodi">kodi (4)</a></li>
5599
5600  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
5601
5602  <li><a href="http://people.skolelinux.org/pere/blog/tags/lego">lego (4)</a></li>
5603
5604  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
5605
5606  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
5607
5608  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
5609
5610  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
5611
5612  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (42)</a></li>
5613
5614  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (11)</a></li>
5615
5616  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (304)</a></li>
5617
5618  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (192)</a></li>
5619
5620  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (35)</a></li>
5621
5622  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
5623
5624  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (73)</a></li>
5625
5626  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (108)</a></li>
5627
5628  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (2)</a></li>
5629
5630  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
5631
5632  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
5633
5634  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
5635
5636  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (11)</a></li>
5637
5638  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
5639
5640  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (7)</a></li>
5641
5642  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
5643
5644  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (55)</a></li>
5645
5646  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
5647
5648  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
5649
5650  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (58)</a></li>
5651
5652  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (6)</a></li>
5653
5654  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (12)</a></li>
5655
5656  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (55)</a></li>
5657
5658  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (4)</a></li>
5659
5660  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
5661
5662  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (9)</a></li>
5663
5664  <li><a href="http://people.skolelinux.org/pere/blog/tags/verkidetfri">verkidetfri (15)</a></li>
5665
5666  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (73)</a></li>
5667
5668  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
5669
5670  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (42)</a></li>
5671
5672 </ul>
5673
5674
5675     </div>
5676     <p style="text-align: right">
5677  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
5678 </p>
5679
5680   </body>
5681 </html>