<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
- "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html>
- <head>
- <title>Petter Reinholdtsen: Entries Tagged standard</title>
- <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css">
- <link rel="alternate" title="RSS Feed" href="standard.rss" type="application/rss+xml">
- </head>
- <body>
-
- <div class="title">
- <h1>
- <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
-
- </h1>
-
- </div>
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
+ <title>Petter Reinholdtsen: Entries Tagged standard</title>
+ <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
+ <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
+ <link rel="alternate" title="RSS Feed" href="standard.rss" type="application/rss+xml" />
+ </head>
+ <body>
+ <div class="title">
+ <h1>
+ <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
+
+ </h1>
+
+</div>
- <p>Entries tagged "standard".</p>
+ <h3>Entries tagged "standard".</h3>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/OOXML_og_standardisering.html">OOXML og standardisering</a>
+ </div>
+ <div class="date">
+ 25th July 2012
+ </div>
+ <div class="body">
+ <p>DIFI har
+<a href="http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html">en
+høring gående</a> om ny versjon av statens standardkatalog, med frist
+2012-09-30, der det foreslås å fjerne ODF fra katalogen og ta inn ISO
+OOXML. I den anledning minnes jeg
+<a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">notatet
+FAD skrev</a> da versjon 2 av standardkatalogen var under
+utarbeidelse, da FAD og DIFI fortsatt forsto poenget med og verdien av
+frie og åpne standarder.</p>
+
+<p>Det er mange som tror at OOXML er ett spesifikt format, men det
+brukes ofte som fellesbetegnelse for både formatet spesifisert av
+ECMA, ISO, og formatet produsert av Microsoft Office (aka docx), som
+dessverre ikke er det samme formatet. Fra en av de som implementerte
+støtte for docx-formatet i KDE fikk jeg høre at ISO-spesifikasjonen
+var en nyttig referanse, men at det var mange avvik som gjorde at en
+ikke kunne gå ut ifra at Microsoft Office produserte dokumenter i
+henhold til ISO-spesifikasjonen.</p>
+
+<p>ISOs OOXML-spesifikasjon har (eller hadde, usikker på om
+kommentaren er oppdatert) i følge
+<a href="http://surguy.net/articles/ooxml-validation-and-technical-review.xml">Inigo
+Surguy</a> feil i mer enn 10% av eksemplene, noe som i tillegg gjør
+det vanskelig å bruke spesifikasjonen til å implementere støtte for
+ISO OOXML. Jeg har ingen erfaring med å validere OOXML-dokumenter
+selv, men ser at
+<a href="http://www.microsoft.com/en-us/download/details.aspx?id=5124">Microsoft
+har laget en validator</a> som jeg ikke kan teste da den kun er
+tilgjengelig på MS Windows. Finner også en annen kalt
+<a href="http://code.google.com/p/officeotron/">Office-O-Tron</A> som
+er oppdatert i fjor. Lurer på om de validerer at dokumenter er i
+formatet til Microsoft office, eller om de validerer at de er i
+henhold til formatene spesifisert av ECMA og ISO. Det hadde også vært
+interessant å se om docx-dokumentene publisert av det offentlige er
+gyldige ISO OOXML-dokumenter.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 5th July 2012
+ </div>
+ <div class="body">
+ <p>I føljetongen om H.264
+<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
+jeg leserne i undring</a> om hvor pakken fra MPEG-LA tok veien, og om
+hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
+MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
+og dagen etter fikk jeg følgende svar derfra:</p>
+<p><blockquote>
+<p>Date: Fri, 29 Jun 2012 18:32:34 +0000
+<br>From: Sidney Wolf <SWolf (at) mpegla.com>
+<br>To: Petter Reinholdtsen <pere (at) hungry.com>
+<br>Cc: Ryan Rodriguez <RRodriguez (at) mpegla.com>
+<br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
+<p>Dear Mr. Reinholdtsen,</p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2009-01-22 23:00
- </div>
+<p>Thank you for your message. As you know, Ryan is currently our of the
+office, so it will be my pleasure to assist you.</p>
- <div class="body">
-
-<p>I går publiserte
-<a href="http://universitas.no/nyhet/52776/">Universitas</a>,
-<a href="http://www.dagensit.no/trender/article1588462.ece">Dagens-IT</a>
-og <a href="http://www.idg.no/computerworld/article118622.ece">Computerworld
-Norge</a> en sak om at de ansatte ved Universitetet i Oslo ikke følger
-regjeringens pålegg om å publisere i HTML, PDF eller ODF. Det er bra
-at det kommer litt fokus på dette, og jeg håper noen journalister tar
-en titt på de andre statlige instansene også.</p>
+<p>Per your request, attached please find an electronic copy of the
+AVC Patent Portfolio License. Please note that the electronic copy of
+the License is provided as a convenience and for informational
+purposes only. When concluding the Licenses, only the hard copies
+provided by MPEG LA may be used.</p>
-<p>Skulle ønske det var en enkel måte å sjekke om ODF-dokumenter er i
-henholdt til ODF-spesifikasjonen, og en måte å teste om programmer som
-hevder å støtte ODF forstår alle delene av ODF-spesifikasjonen.
-Kjenner kun til ufullstendige løsninger for slikt.</p>
+<p>To your question, MPEG LA lists our Licensees on our website
+according to each program. The lists are in alphabetical order, so it
+is very easy to search.</p>
- </div>
- <div class="tags">
-
+<p>I hope that this was helpful. If we can be of additional
+assistance, please let me know.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>Kind regards,</p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Hva_er_egentlig_en___pen_standard_.html">Hva er egentlig en åpen standard?</a>
- </div>
- <div class="date">
- 2009-03-28 10:50
- </div>
+<p>Sidney A. Wolf
+<br>Manager, Global Licensing
+<br>MPEG LA</p>
+</blockquote></p>
- <div class="body">
-
-<p>Jeg møter alle slags interessante mennesker på min vei, og et møte
-jeg lærte mye av var å treffe på en svært kompetent IT-fyr som
-benektet ting jeg anser som åpenbart og selvfølgelig når det gjelder
-standarder. Det var interessant, da det fikk meg til å tenke litt
-nøyere på hvilke mekanismer som ligger til grunn for at noe oppfattes
-som en standard. Det hele startet med arbeid rundt integrering av NSS
-LDAP mot Active Directory, og problemer som oppstår pga. at Active
-Directory ikke følger LDAP-spesifikasjonen som dokumentert i RFCer fra
-IETF (konkret, AD returnerer kun et subset av attributter hvis det er
-mer enn 1500 atributter av en gitt type i et LDAP-objekt, og en må be
-om resten i bolker av 1500). Jeg hevdet måten dette ble gjort på brøt
-med LDAP-spesifikasjonen, og henviste til hvor i LDAP-spesifikasjonen
-fra IETF det sto at oppførselen til AD ikke fulgte
-LDAP-spesifikasjonen. AD-spesialisten overrasket meg da ved å
-fortelle at IETF var ikke de som definerte LDAP-spesifikasjonen, og at
-Active Directory ikke brøt den virkelige LDAP-spesifikasjonen som han
-mente lå til grunn. Jeg ble spesielt overrasket over denne
-tilnærmingen til problemstillingen, da til og med Microsoft så vidt
-jeg kan se anerkjenner IETF som organisasjonen som definerer
-LDAP-spesifikasjonen. Jeg fikk aldri spurt hvem han mente sto bak den
-egentlige LDAP-spesifikasjonen, da det var irrelevant for problemet vi
-måtte løse (få Linux og AD til å fungere sammen). Dette møtet
-fortalte meg uansett at det ikke er gitt at alle aktører er enige om
-hva en standard er, og hva som er kilden til en gitt standard. Det er
-vanskelig å enes om felles standarder før en først enes om hvem som
-bestemmer hva en gitt standard innebærer.</p>
+<p>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
+et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
+som må deles på individuell basis. Opphavsretten krever godkjenning
+fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
+opp med et spørsmål om dette var greit.</p>
-<p>Hva er så en standard? I sin abstrakte form er det noe å samles
-om. På engelsk er en av betydningene fane brukt i krig, du vet, den
-type fane en samlet seg rundt på kamplassen i riddertiden. En
-standard definerer altså et felleskap, noen som har noe felles. Det
-er naturligvis mange måter å utgjøre et felleskap på. En kan
-f.eks. enes om å gjøre alt slik som Ole gjør det, og dermed si at Oles
-oppførsel er standard. Hver gang Ole endrer oppførsel endrer også
-standarden seg uten noe mer organisering og prosedyre. En variant av
-dette er å gjøre slik som Ole har gjort det i stedet for slik Ole til
-enhver til gjør noe. Dette er ofte litt enklere å forholde seg til,
-da en slipper å sjekke med Ole hver gang for å vite hvordan ting skal
-gjøres nå, men hvis det Ole gjorde noe dumt den gang en bestemte seg
-for å følge Ole, så er det vanskeligere å få endret oppførsel for å
-unngå dette dumme.</p>
+<p><blockquote>
+<p>Date: Wed, 4 Jul 2012 20:25:06 +0200
+<br>From: Petter Reinholdtsen <pere (at) hungry.com>
+<br>To: Sidney Wolf <SWolf (at) mpegla.com>
+<br>Cc: Ryan Rodriguez <RRodriguez (at) mpegla.com>
+<br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
+
+<p>Thank you for your reply.</p>
+
+<p>[Sidney Wolf]
+<br>> Per your request, attached please find an electronic copy of the AVC
+<br>> Patent Portfolio License. Please note that the electronic copy of
+<br>> the License is provided as a convenience and for informational
+<br>> purposes only. When concluding the Licenses, only the hard copies
+<br>> provided by MPEG LA may be used.</p>
+
+<p>This is useful for me to learn, but the reason I asked for the
+Internet address of the licensing document was to ensure I could
+publish a link to it when I discuss the topic of H.264 licensing here
+in Norway, and allow others to verify my observations. I can not do
+the same with an email attachment. Thus I would like to ask you if it
+is OK with MPEG LA that I publish this document on the Internet for
+others to read?</p>
+
+<p>> To your question, MPEG LA lists our Licensees on our website
+<br>> according to each program. The lists are in alphabetical order, so
+<br>> it is very easy to search.</p>
+
+<p>I am afraid this do not help me locate Norwegian companies in the
+list of Licensees. I do not know the name of all companies and
+organisations in Norway, and thus do not know how to locate the
+Norwegian ones on that list.</p>
+
+<p>> I hope that this was helpful. If we can be of additional assistance,
+<br>> please let me know.</p>
+
+<p>Absoutely helpful to learn more about how MPEG LA handle licensing.</p>
+
+<p>--
+<br>Happy hacking
+<br>Petter Reinholdtsen</p>
+</blockquote></p>
-<p>En kan også ta det et skritt videre, og istedet for å basere seg på
-enkeltpersoners oppførsel sette seg ned og bli enige om hvordan en
-skal gjøre ting, dvs. lage et felleskap basert på konsensus. Dette
-tar naturligvis litt mer tid (en må diskutere ting i forkant før en
-kan sette igang), men det kan bidra til at den oppførselen en
-planlegger å benytte seg av er mer gjennomtenkt. Det ender også
-typisk opp med en beskrivelse av ønsket oppførsel som flere kan forstå
-- da flere har vært involvert i å utarbeide beskrivelsen.</p>
+<p>Jeg håpet også at det skulle være mulig å få vite hvilke av de
+mange hundre som har avtale med MPEG-LA om bruk av H.264 som holdt til
+i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
-<p>Dette er dessverre ikke alt som trengs for å forstå hva en åpen
-standard er for noe. Der alle kan se på hvordan folk oppfører seg, og
-dermed har valget om de vil oppføre seg likt eller ikke, så er det
-endel juridiske faktorer som gjør det hele mer komplisert -
-opphavsretten og patentlovgivningen for å være helt konkret. For å gi
-et eksempel. Hvis noen blir enige om å alltid plystre en bestemt
-melodi når de møtes, for å identifisere hverandre, så kan
-opphavsretten brukes til å styre hvem som får lov til å gjøre dette.
-De har standardisert hvordan de kjenner igjen alle som følger denne
-standarden, men ikke alle har nødvendigvis lov til å følge den.
-Musikk er opphavsrettsbeskyttet, og fremføring av musikk i
-offentligheten er opphavsmannens enerett (dvs. et monopol). Det vil i
-sin ytterste konsekvens si at alle som skal plystre en
-opphavsrettsbeskyttet melodi i det offentlige rom må ha godkjenning
-fra opphavsmannen. Har en ikke dette, så bryter en loven og kan
-straffes. Det er dermed mulig for opphavsmannen å kontrollere hvem
-som får lov til å benytte seg av denne standarden. En annen variant
-er hvis en standard er dokumentert, så er dokumentet som definerer
-standarden (spesifikasjonen) beskyttet av opphavsretten, og det er
-dermed mulig for rettighetsinnehaver å begrense tilgang til
-spesifikasjonen, og slik styre hvem som kan ta i bruk standarden på
-den måten.</p>
+<p><blockquote>
+<p>Date: Thu, 5 Jul 2012 17:42:39 +0000
+<br>From: Sidney Wolf <SWolf (at) mpegla.com>
+<br>To: 'Petter Reinholdtsen' <pere (at) hungry.com>
+<br>Cc: Ryan Rodriguez <RRodriguez (at) mpegla.com>
+<br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
+
+<p>Dear Mr. Reinholdtsen,</p>
+
+<p>Thank you for your reply.</p>
+
+<p>We appreciate the additional explanation you have provided and for
+asking our permission to publish the electronic copy of the License in
+advance of doing so. Typically, MPEG LA prefers to distribute the
+electronic copies of our Licenses to interested parties. Therefore,
+please feel free to send interested parties to the AVC portion of our
+website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
+their further reference.</p>
+
+<p>As previously mentioned, MPEG LA maintains a list of Licensees in good
+standing on our website according to each program. Due to the large
+volume of Licensees, it would be administratively impractical to
+provide this level of detail to interested parties. Therefore, I am
+afraid we are not in a position to assist you with your request.</p>
+
+<p>Kind regards,</p>
+
+<p>Sidney A. Wolf
+<br>Manager, Global Licensing
+<br>MPEG LA</p>
+</blockquote></p>
-<p>Der opphavsretten innvilger et monopol på kunstneriske uttrykk med
-verkshøyde, innvilger patentlovgivningen monopol på ideer. Hvis en
-slik patentert idé (fortrinnsvis uttrykt i en teknisk innretning, men
-det er kompliserende faktorer som gjør at det ikke er et krav) trengs
-for å ta i bruk en standard, så vil den som innehar patent kunne styre
-hvem som får ta i bruk standarden. Det er dermed ikke gitt at alle
-kan delta i et standard-felleskap, og hvis de kan delta, så er det
-ikke sikkert at det er på like vilkår. F.eks. kan rettighetsinnehaver
-sette vilkår som gjør at noen faller utenfor, det være seg av
-finansielle, avtalemessige eller prinsipielle årsaker. Vanlige slike
-vilkår er "må betale litt for hver kunde/bruker" som utelukker de som
-gir bort en løsning gratis og "må gi fra seg retten til å håndheve
-sine egne patentrettigheter ovenfor rettighetshaver" som utelukker
-alle som ønsker å beholde den muligheten.</p>
+<p>Men takket være epostvedlegget kunne jeg søke på Google etter
+setningen "WHEREAS, a video standard commonly referred to as AVC has
+been defined and is referred to in this Agreement as the “AVC
+Standard” (as more fully defined herein below)" som finnes i avtalen,
+og lokalisere en kopi fra 2007 av
+<a href="http://www.sec.gov/Archives/edgar/data/1342960/000119312509050004/dex1024.htm">lisensavtalen
+mellom MPEG-LA og DivX, Inc.</a>, slik at mine lesere kan se hvordan
+avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
+har endret seg siden den tid, men satser på at teksten er representativ.</p>
+
+<p>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
+MPEG-LA.</p>
+
+<p>Update 2012-07-06: Jeg er visst ikke den første som forsøker å få
+klarhet i problemstillinger rundt H.264, og kom nettopp over en veldig
+interessant bloggpost fra 2010 hos LibreVideo med tittelen
+"<a href="http://www.librevideo.org/blog/2010/06/14/mpeg-la-answers-some-questions-about-avch-264-licensing/">MPEG-LA
+answers some questions about AVC/H.264 licensing</a>. Anbefales!</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 29th June 2012
+ </div>
+ <div class="body">
+ <p>DIFI har nettopp annonsert høring om revisjon av
+<a href="http://www.standard.difi.no/forvaltningsstandarder">standardkatalogen</a>,
+og endelig har Microsoft fått viljen sin. Se
+<a href="http://www.standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning">høringssiden</a>
+for hele teksten.</p>
+
+<p>Her er forslaget i sin helhet:</p>
-<p>En åpen standard innebærer for meg at alle kan få innsikt i en
-komplett beskrivelse av oppførsel som standarden skal dekke, og at
-ingen kan nektes å benytte seg av standarden. Noen mener at det
-holder at alle med tilstrekkelig finansiering kan få tilgang til
-spesifikasjonen og at en kun har finansielle krav til bruk.
-Pga. denne konflikten har et nytt begrep spredt seg de siste årene,
-nemlig fri og åpen standard, der en har gjort det klart at alle må ha
-komplett og lik tilgang til spesifikasjoner og retten til å gjøre bruk
-av en standard for at en standard skal kunne kalles fri og åpen.</p>
+<p><blockquote>
+<p>3.2 Revisjon av krav til redigerbare dokumenter</p>
+
+<p>I første versjon av referansekatalogen i 2007 ble det satt krav om
+Open Document Format (ODF), versjon 1.1 (OASIS, 1.2.2007) for
+redigerbare dokumenter. Kravet var obligatorisk for stat og sterkt
+anbefalt for kommunal sektor. I 2009 ble kravet gjort obligatorisk for
+hele offentlig sektor i
+<a href="http://www.lovdata.no/for/sf/fa/xa-20090925-1222.html">forskrift
+om IT-standarder i forvaltningen</a>. Anvendelsesområdet for kravet
+har vært begrenset til publisering av dokumenter som skal bearbeides
+videre (§ 4 nr. 1 andre ledd). I 2011 ble anvendelsesområdet utvidet
+til å omfatte utveksling av dokumenter beregnet for redigering som
+vedlegg til e-post (§4 nr. 2).</p>
+
+<p>Office Open XML ISO/IEC 29500:2011 (OOXML) er et dokumentformat
+opprinnelig utviklet av Microsoft med tilsvarende anvendelsesområde
+som ODF. Formatet er blant annet tatt i bruk i nyere versjoner av
+kontorstøtteprogamvaren MS Office. Difi har foretatt en
+<a href="http://www.standard.difi.no/filearchive/revisjonsvurdering-standarder-for-redigerbare-dokumenter-v1-0.pdf">revisjonsvurdering</a>
+av krav som stilles til redigerbare dokumenter i Forskrift om
+IT-standarder i forvaltningen, og anbefaler at kravet til ODF
+fjernes. Dette innebærer at det ikke stilles krav til dokumentformater
+for redigerbare dokumenter ved publisering på offentlige virksomheters
+nettsider og for redigerbare vedlegg til e-post som sendes fra
+offentlige virksomheter til innbyggere og næringsliv. Offentlige
+virksomheter vil dermed stå fritt til å publisere eller sende
+redigerbare dokumenter i det format som ivaretar brukernes behov
+best.</p>
+
+<p>Forslaget innebærer at krav til ODF utgår § 4 nr. 1 tredje ledd og
+§ 4 nr. 2 første ledd</p>
+
+<P>Imidlertid bør det stilles strengere krav til hvilke formater
+offentlige virksomheter plikter å motta redigerbare dokumenter. Vi
+mener at det ikke bør skilles mellom mottak av redigerbare dokumenter
+som sendes i ODF eller OOXML3, som begge er åpne standarder. Dette
+medfører at innbyggere og næringsliv skal kunne basere sitt valg av
+programvare på egne behov og ikke på de valg offentlige virksomheter
+tar. Kravet vil omfatte hele offentlig sektor, herunder
+utdanningssektoren, hvor det kanskje er størst bruk av ODF. Kravet er
+foreslått som ny § 4 nr.2 andre ledd</p>
+</blockquote></p>
- </div>
- <div class="tags">
-
+<P>De satser vel på at det hele blir glemt over sommeren, og at de
+fleste har glemt Standard Norge og ISOs fallitt fra da OOXML ble
+jukset igjennom som ISO-standard. Jeg håper mine lesere sender inn
+høringsuttalelser til høringen.</p>
+
+<p>Anbefaler alle å friske opp sine argumenter ved å lese
+<a href="http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html">svaret
+fra senator Edgar Villanueva til Microsoft i Peru</a>. Det er en
+klassisk tekst som er like gyldig i dag som da det ble skrevet.</p>
+
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 29th June 2012
+ </div>
+ <div class="body">
+ <p>Da fikk jeg nettopp svar fra
+<a href="http://www.dss.dep.no/">Departementenes servicesenter</a>
+(DSS) på
+<a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">mitt
+spørsmål om avtale rundt bruk av H.264</a>. De har ingen avtale med
+MPEG LA eller dets representanter. Her er svaret.
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p><blockquote>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2009-03-30 11:50
- </div>
+<p>Date: Fri, 29 Jun 2012 07:04:42 +0000
+<br>From: Nielsen Mette Haga <Mette-Haga.Nielsen (at) dss.dep.no>
+<br>To: Petter Reinholdtsen <petter.reinholdtsen (at) ...>
+<br>CC: Postmottak <Postmottak (at) dss.dep.no>
+<br>Subject: SV: Innsynsbegjæring om MPEG/H.264-relaterte avtaler</p>
- <div class="body">
-
-<p>Where I work at the University of Oslo, one decision stand out as a
-very good one to form a long lived computer infrastructure. It is the
-simple one, lost by many in todays computer industry: Standardize on
-open network protocols and open exchange/storage formats, not applications.
-Applications come and go, while protocols and files tend to stay, and
-thus one want to make it easy to change application and vendor, while
-avoiding conversion costs and locking users to a specific platform or
-application.</p>
+<p>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
+representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
+levert av Smartcom:tv. Lisensforholdet rundt H.264 er ikke omtalt i
+vår avtale med Smartcom.</p>
-<p>This approach make it possible to replace the client applications
-independently of the server applications. One can even allow users to
-use several different applications as long as they handle the selected
-protocol and format. In the normal case, only one client application
-is recommended and users only get help if they choose to use this
-application, but those that want to deviate from the easy path are not
-blocked from doing so.</p>
+<p>Vennlig hilsen</p>
-<p>It also allow us to replace the server side without forcing the
-users to replace their applications, and thus allow us to select the
-best server implementation at any moment, when scale and resouce
-requirements change.</p>
+<p>Mette Haga Nielsen
+<br>Fung. seksjonssjef</p>
-<p>I strongly recommend standardizing - on open network protocols and
-open formats, but I would never recommend standardizing on a single
-application that do not use open network protocol or open formats.</p>
+<p>Departementenes servicesenter</p>
- </div>
- <div class="tags">
-
+<p>Informasjonsforvaltning
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>Mobil 93 09 83 51
+<br>E-post mette-haga.nielsen (at) dss.dep.no</p>
+</blockquote></p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Hvorfor_jeg_ikke_bruker_eFaktura.html">Hvorfor jeg ikke bruker eFaktura</a>
- </div>
- <div class="date">
- 2009-04-23 23:00
- </div>
+<p>Hvis den norske regjeringen representert ved DSS ikke har slik
+avtale, så kan en kanskje konkludere med at det ikke trengs? Jeg er
+ikke trygg på at det er god juridisk grunn å stå på, men det er i det
+minste interessant å vite at hverken NRK eller DSS har funnet det
+nødvendig å ha avtale om bruk av H.264.</p>
+
+<p>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
+til bruk av opphavsrettsbeskyttet materiale de bruker til
+videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
+privatpersoner i Norge. Har de lov til å bryte vilkårene, eller har
+de brutt dem og så langt sluppet unna med det? Jeg aner ikke.</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 28th June 2012
+ </div>
+ <div class="body">
+ <p>Etter at NRK
+<a href="http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html">nektet
+å spore opp eventuell avtale med MPEG-LA</a> eller andre om bruk av
+MPEG/H.264-video etter at jeg <a
+href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">ba
+om innsyn i slike avtaler</a>, tenkte jeg at i stedet for å forsøke å
+få NRK til å finne en slik avtale, så burde det være like enkelt å
+spørre MPEG-LA om de hadde avtale med NRK. Spørsmålet ble sendt før
+jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
+"in Good Standing" befant seg. MPEG-LA svarte meg i dag, og kan
+fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
+slått fast. Ikke overraskende mener MPEG-LA at det trengs en avtale
+med MPEG-LA for å streame H.264, men deres rammer er jo
+rettstilstanden i USA og ikke Norge. Jeg tar dermed den delen av
+svaret med en klype salt. Jeg er dermed fortsatt ikke klok på om det
+trengs en avtale, og hvis det trengs en avtale her i Norge, heller
+ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
+gjør at de ikke trenger avtale direkte med MPEG-LA. Jeg håper NRKs
+jurister har vurdert dette, og at det er mulig å få tilgang til
+vurderingen uansett om de trenger en avtale eller ikke.</p>
+
+<p>Her er epostutvekslingen med MPEG-LA så langt. Håper ikke
+utvekslingen fører til NRK plutselig får en litt uventet pakke fra
+MPEG-LA.</p>
- <div class="body">
-
-<p>Telenors annonsering om å kreve 35 kroner i gebyr fra alle som
-ønsker papirfaktura har satt sinnene i kok, og pressedekningen så
-langt snakker om at eldre og folk som ikke behersker data vil få en
-urimelig ekstrakostnad. Jeg tror ikke jeg passer inn i noen av de
-kategoriene, men velger å holde meg unna eFaktura - som er det
-Telenor ønsker å få folk over på - pga. systemets egenskaper.</p>
+<p><blockquote>
+<p>Date: Mon, 25 Jun 2012 15:29:37 +0200
+<br>From: Petter Reinholdtsen <pere (at) hungry.com>
+<br>To: licensing-web (at) mpegla.com
+<br>Subject: Do NRK have a license agreement with MPEG-LA?</p>
-<p>Slik jeg har sett eFaktura til forbrukere så langt, så sender
-selger en elektronisk beskjed til kundens bank, som legger ut
-informasjon om fakturaen i nettbanken for godkjenning. Personlig
-ville jeg sett det som mer naturlig at det gikk en elektronisk beskjed
-fra selger til kunde, dvs meg, og at jeg så kunne bruke den videre
-mot banken eller andre hvis jeg ønsket dette. Mine innkjøp og
-regninger er jo en sak mellom meg og mine leverandører, ikke en sak
-mellom min bank og mine leverandører. Kun hvis jeg ønsker å betale
-fakturaen skal banken involveres. En faktura bør jo inn i
-regnskapet, og jeg ønsker mulighet til å legge det inn der. Når
-fakturaen sendes til banken i stedet for meg, blir det vanskeligere.
-Hele eFaktura-modellen virker på meg som en umyndiggjøring av meg
-som kunde.</p>
+<p>Hi. I have a small question for you, that I hope it is OK that I
+ask.</p>
-<p>I tillegg har jeg ikke vært i stand til å finne
-eFaktura-formatets spesifikasjon, og det ser ut til at utsending av
-slike krever dyre avtaler med bankene for å få lov til å sende ut
-eFaktura til kunder. Jeg ser vel helst at fakturering på
-elektroniske formater kan gjøres f.eks. via epost eller HTTP uten å
-måtte betale mellommenn for retten til å lever ut en faktura, og
-liker rett og slett ikke dagens faktureringsmodeller.</p>
+<p>Is there any license agreements between MPEG-LA and NRK, <URL:
+<a href="http://www.nrk.no/">http://www.nrk.no/</a> >, the
+Norwegian national broadcasting cooperation? I am not sure if they
+need one, and am just curious if such agreeement exist.</p>
- </div>
- <div class="tags">
-
+<p>The postal address is</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p><blockquote>
+ NRK
+ <br>Postbox 8500, Majorstuen
+ <br>0340 Oslo
+ <br>Norway
+</blockquote></p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2009-05-19 11:30
- </div>
+<p>if it make it easier for you to locate such agreement.</p>
- <div class="body">
-
-<p>En standard er noe man samler seg rundt, ut fra ideen om at en får
-fordeler når mange står sammen. Jo flere som står sammen, jo
-bedre. Når en vet dette, blir det litt merkelig å lese noen av
-uttalelsene som er kommet inn til
-<a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2/horingsuttalelser.html?id=549423">høringen
-om versjon 2 av statens referansekatalog over standarder</a>. Blant
-annet Abelia, NHO og Microsoft tror det er lurt med flere standarder
-innenfor samme område. Det blir som å si at det er fint om Norge
-standardiserte både på A4- og Letter-størrelser på arkene, ulik
-sporvidde på jernbaneskinnene, meter og fot som lengemål, eller
-høyre- og venstrekjøring - slik at en kan konkurrere på hvilken
-standard som er best. De fleste forstår heldigvis at dette ikke
-bidrar positivt.</p>
+<p>Can you tell me how many entities in Norway have an agreement with
+MPEG-LA, and the name of these entities?</p>
- </div>
- <div class="tags">
-
+<p>--
+<br>Happy hacking
+<br>Petter Reinholdtsen
+</blockquote></p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>I dag, to dager senere, fikk jeg følgende svar:</p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
- </div>
- <div class="date">
- 2009-06-26-13:30
- </div>
+<p><blockquote>
+<p>Date: Thu, 28 Jun 2012 14:11:17 +0000
+<br>From: Ryan Rodriguez <RRodriguez (at) mpegla.com>
+<br>To: Petter Reinholdtsen <pere (at) hungry.com>
+<br>CC: MD Administration <MDAdministration (at) mpegla.com>
+<br>Subject: RE: Do NRK have a license agreement with MPEG-LA?</p>
+
+<p>Dear Mr. Reinholdtsen,</p>
+
+<p>Thank you for your message and for your interest in MPEG LA. We
+appreciate hearing from you and I will be happy to assist you.</p>
+
+<p>To begin, I will assume that you are referring to AVC/H.264
+technology in your message below, as this technology is commonly used
+in the transmission of video content. In that case, please allow me
+to briefly summarize the coverage provided by our AVC Patent Portfolio
+License.</p>
+
+<P>Our AVC License provides coverage for end products and video
+services that make use of AVC/H.264 technology. Accordingly, the
+party offering such end products and video to End Users concludes the
+AVC License and is responsible for paying the applicable royalties
+associated with the end products/video they offer.</p>
+
+<p>While the Norwegian Broadcast Corporation (NRK) is not currently a
+Licensee to MPEG LA's AVC License (or any other Portfolio License
+offered by MPEG LA), if NRK offers AVC Video to End Users for
+remuneration (for example, Title-by-Title, Subscription, Free
+Television, or Internet Broadcast AVC Video), then NRK will need to
+conclude the AVC License and may be responsible for paying applicable
+royalties associated with the AVC Video it distributes.</p>
+
+<p>Today I will send you a FedEx package containing a copy of our AVC
+License for your review. You should receive the License document
+within the next few days.</p>
+
+<p>Meanwhile, MPEG LA currently has several Norwegian Licensees that
+can be found under the "Licensees" header within the respective
+portion of our website. For example, you may find our list of
+Licensees in Good Standing to our AVC License in the AVC portion of
+our website,
+<a href="http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</a></p>
+
+<p>I hope the above information is helpful. If you have additional
+questions or need further assistance with the AVC License, please feel
+free to contact me directly. I look forward to hearing from you again
+soon.</p>
+
+<p>Best regards,</p>
+
+<p>Ryan</p>
+
+<p>Ryan M. Rodriguez
+<br>Licensing Associate
+<br>MPEG LA
+<br>5425 Wisconsin Avenue
+<br>Suite 801
+<br>Chevy Chase, MD 20815
+<br>U.S.A.
+<br>Phone: +1 (301) 986-6660 x211
+<br>Fax: +1 (301) 986-8575
+<br>Email: rrodriguez (at) mpegla.com</p>
- <div class="body">
-
-<p>I
-<a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
-sin høringsuttalelse</a> til
-<a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
-til versjon 2 av statens referansekatalog over standarder</a>, lirer
-de av seg følgende FUD-perle:</p>
+</blockquote></p>
-<p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
- spesifikasjoner overordnet styrt av xiph.org, som er en
- ikke-kommersiell organisasjon. Etablerte og anerkjente
- standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
- innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
- Det er derimot helt opp til hver enkelt organisasjon å bestemme
- hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
- spesifikasjonene bør derfor ikke defineres som åpne
- standarder."</blockquote></p>
+<p>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
+øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
+da han jo ikke hadde fått noen postadresse som nådde meg.</p>
-<p>De vokter seg vel for å nevne den anerkjente
-standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
-IP og det meste av protokoller på Internet, og RFC-standardene som
-IETF står bak. Ogg er spesifisert i
-<a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
-tvil å anse som en åpen standard. Vorbis er
-<a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>. Theora er
+<p><blockquote>
-under standardisering via IETF, med
-<a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
-utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
-skrevet i stein ennå, men det blir neppe endringer som ikke er
-bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
-jeg ikke finner tegn til at <a
-href="http://flac.sourceforge.net/format.html">spesifikasjonen
-tilgjengelig på web</a> er på tur via noen
-standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
-og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
-bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
-til FLAC.</p>
+<p>Date: Thu, 28 Jun 2012 16:36:15 +0200
+<br>From: Petter Reinholdtsen <pere (at) hungry.com>
+<br>To: Ryan Rodriguez <RRodriguez (at) mpegla.com>
+<br>Cc: MD Administration <MDAdministration (at) mpegla.com>
+<br>Subject: Re: Do NRK have a license agreement with MPEG-LA?</p>
-<p>Uredelig argumentasjon bør en holde seg for god til å komme med,
-spesielt når det er så enkelt i dagens Internet-hverdag å gå
-misvisende påstander etter i sømmene.</p>
+<p>[Ryan Rodriguez]
+<br>> Dear Mr. Reinholdtsen,</p>
- </div>
- <div class="tags">
-
+<p>Thank you for your quick reply.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>> Today I will send you a FedEx package containing a copy of our AVC
+<br>> License for your review. You should receive the License document
+<br>> within the next few days.</p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2009-07-06 21:00
- </div>
+<p>The part about sending a FedEx package confused me, though. I did not
+<br>give you my address, nor am I associated with NRK in any way, so I hope
+<br>you did not try to send me a package using the address of NRK. If you
+<br>would send me the Internet address of to the document, it would be more
+<br>useful to me to be able to download it as an electronic document.</p>
- <div class="body">
-
-<p>Jeg ble glad da regjeringen
-<a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
-versjon 2 av
-<a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
-referansekatalog over standarder</a>, men trist da jeg leste hva som
-faktisk var vedtatt etter
-<a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
-De fleste av de valgte åpne standardene er gode og vil bidra til at
-alle kan delta på like vilkår i å lage løsninger for staten, men
-noen av dem blokkerer for de som ikke har anledning til å benytte
-spesifikasjoner som krever betaling for bruk (såkalt
-royalty-betaling). Det gjelder spesifikt for H.264 for video og MP3
-for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
-Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
-fra statens websider gjøre dette uten å måtte bruke programmer der
-betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
-de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
-Vorbis), så vil en bli tvunget til å forholde seg til
-royalty-belastede standarder for å få tilgang til videoen og
-lyden.</p>
-
-<p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
-at alle standarder som ble valgt til å være påkrevd i katalogen skulle
-være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
-all forståelse for hvilke prinsipper som må følges for å oppnå
-likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
-mot dette i
-<a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
-høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
+<p>> Meanwhile, MPEG LA currently has several Norwegian Licensees that can
+<br>> be found under the "Licensees" header within the respective portion
+<br>> of our website. For example, you may find our list of Licensees in
+<br>> Good Standing to our AVC License in the AVC portion of our website,
+<br>> http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx</p>
- </div>
- <div class="tags">
-
+<p>How can I recognize the Norwegian licensees?</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>--
+<br>Happy hacking
+<br>Petter Reinholdtsen</p>
+</blockquote></p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2009-07-09 14:40
- </div>
+<p>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
+MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
+siste epost. Får håpe noen likevel følger opp "FedEx-pakken". For å
+øke sjansen for at noen revurderer utsending av pakke uten mottaker,
+videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
+Har ikke hørt noe mer 3 timer senere, så jeg mistenker at ingen leste
+min epost tidsnok.</p>
- <div class="body">
-
-<p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
-den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
-for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
-wiki, direkte tilgjengelig via "<a
-href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
-v2.0 - Oppsummering av høring</a>" og "<a
-href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
-for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
-UTKAST</a>".</p>
+<p><blockquote>
-<p>Det er tre ting jeg merker meg i oppsummeringen fra
-høringsuttalelsen da jeg skummet igjennom den. Det første er at
-forståelsen av hvordan programvarepatenter påvirker fri
-programvareutvikling også i Norge når en argumenterer med at
-royalty-betaling ikke er et relevant problem i Norge. Det andre er at
-FAD ikke har en prinsipiell forståelse av verdien av en enkelt
-standard innenfor hvert område. Det siste er at påstander i
-høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
-Microsoft om hvordan Ogg blir standardisert og påstanden fra
-politidirektoratet om patentproblemer i Theora).</p>
+<p>Date: Thu, 28 Jun 2012 14:36:20 +0000
+<br>From: Ryan Rodriguez <RRodriguez (at) mpegla.com>
+<br>To: Petter Reinholdtsen <pere (at) hungry.com>
+<br>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?</p>
- </div>
- <div class="tags">
-
+<p>Thank you for your message.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>I will be out of the office until Thursday, July 5 and will respond
+to all messages upon my return. If this is a matter that requires
+immediate attention, please contact Sidney Wolf (swolf (at)
+mpegla.com)</p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/ISO_still_hope_to_fix_OOXML.html">ISO still hope to fix OOXML</a>
- </div>
- <div class="date">
- 2009-08-08 14:00
- </div>
+<p>Best regards,</p>
- <div class="body">
-
-<p>According to <a
-href="http://twerner.blogspot.com/2009/08/defects-of-office-open-xml.html">a
-blog post from Torsten Werner</a>, the current defect report for ISO
-29500 (ISO OOXML) is 809 pages. His interesting point is that the
-defect report is 71 pages more than the full ODF 1.1 specification.
-Personally I find it more interesting that ISO still believe ISO OOXML
-can be fixed in ISO. Personally, I believe it is broken beyon repair,
-and I completely lack any trust in ISO for being able to get anywhere
-close to solving the problems. I was part of the Norwegian committee
-involved in the OOXML fast track process, and was not impressed with
-Standard Norway and ISO in how they handled it.</p>
+<p>Ryan</p>
-<p>These days I focus on ODF instead, which seem like a specification
-with the future ahead of it. We are working in NUUG to organise a ODF
-seminar this autumn.</p>
+<p>Ryan M. Rodriguez
+<br>Licensing Associate
+<br>MPEG LA</p>
- </div>
- <div class="tags">
-
+</blockquote></p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
+som er om en trenger avtale med MPEG-LA for å publisere eller
+kringkaste H.264-video i Norge.</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 25th June 2012
+ </div>
+ <div class="body">
+ <p>Jeg fikk nettopp svar fra NRK på
+<a href="http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html">min
+forespørsel om kopi av avtale</a> med MPEG-LA eller andre om bruk av
+MPEG og/eller H.264. Svaret har fått saksreferanse 2011/371 (mon tro
+hva slags sak fra 2011 dette er?) hos NRK og lyder som følger:</p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2009-08-12 15:50
- </div>
+<p><blockquote>
- <div class="body">
-
-<p>Just for fun, I did a search right now on Google for a few file ODF
-and MS Office based formats (not to be mistaken for ISO or ECMA
-OOXML), to get an idea of their relative usage. I searched using
-'filetype:odt' and equvalent terms, and got these results:</P>
+<p><strong>Svar på innsynsbegjæring i MPEG / H.264-relaterte
+avtaler</strong></p>
+
+<p>Viser til innsynsbegjæring av 19. juni 2012. Kravet om innsyn
+gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
+bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
+H.264».</p>
+
+<p>I henhold til offentleglova § 28 annet ledd må innsynskravet gjelde
+en bestemt sak eller i rimelig utstrekning saker av en bestemt
+sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
+bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
+tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
+står følgende:</p>
+
+<p>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
+for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
+at den enkelte saka blir identifisert. Ein kan med andre ord i
+utgangspunktet ikkje krevje innsyn i til dømes alle saker om
+utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
+med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
+til dato, partar eller liknande.»</p>
+
+<p>Vedrørende denne begrensningen har Justisdepartementet uttalt
+følgende (Lovavdelingens uttalelser JDLOV-2010-3295):</p>
+
+<p><em>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
+er fyrst og fremst at meir generelle innsynskrav, utan noka form for
+identifikasjon av kva ein eigentleg ynskjer, ville vere svært
+vanskelege å handsame for forvaltninga.»</em></p>
+
+<p>I samme sak uttaler Lovavdelingen følgende:</p>
+
+<p><em>«Det følgjer vidare av offentleglova § 28 andre ledd at det `i
+rimeleg utstrekning' kan krevjast innsyn i `saker av ein bestemt
+art'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning' kan
+gjelde saker av ein bestemt art, er i hovudsak knytt til kor
+arbeidskrevjande det vil vere å finne fram til dei aktuelle
+dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
+nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
+mange dokument) at arbeidsmengda som ville gått med til å handsame
+det, er større enn det ein `i rimeleg utstrekning' kan krevje (sjølv
+om det nok skal mykje til).»</em></p>
+
+<p>NRK har ikke noen egen sammenstilling over avtaler innenfor
+bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
+vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
+avtaler som «ikke er begrenset av de generelle bruksvilkårene som
+gjelder for utstyr som bruker MPEG og/eller H.264». En slik
+gjennomgang av avtaler måtte gjøres manuelt av en person med
+spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
+ressurser for å finne frem relevante avtaler og for deretter å vurdere
+om de dekkes av det innsynsbegjæringen omfattes.</p>
+
+<p>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
+innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
+vil være langt større enn det som i rimelig utstrekning kan kreves i
+henhold til offentleglova § 28 annet ledd.</p>
+
+<p>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
+kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
+frem til mottakeren, i henhold til reglene i offentleglova § 32,
+jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
+kirkedepartementet, og sendes til NRK.</p>
+
+<p>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
+slik at en eventuell søknad om innsyn kan tydeligere identifisere
+hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
+for inneværende og forrige måned ligger ute på
+NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
+på forespørsel til innsyn (at) nrk.no.</p>
+
+<p>Med hilsen
+<br>Dokumentarkivet i NRK
+<br>v/ Elin Brandsrud
+<br>Tel. direkte: 23 04 29 29
+<br>Post: RBM3, Postboks 8500 Majorstuen, 0340 Oslo
+<br>innsyn (at) nrk.no</p>
-<table>
-<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
-<tr><td>Tekst</td> <td>odt:282000</td> <td>docx:308000</td></tr>
-<tr><td>Presentasjon</td> <td>odp:75600</td> <td>pptx:183000</td></tr>
-<tr><td>Regneark</td> <td>ods:26500 </td> <td>xlsx:145000</td></tr>
-</table>
+</blockquote></p>
-<p>Next, I added a 'site:no' limit to get the numbers for Norway, and
-got these numbers:</p>
+<p>Svaret kom
+<a href="http://people.skolelinux.org/pere/blog/images/2012-06-25-video-mpegla-nrk.pdf">i
+PDF-form som vedlegg på epost</a>. Jeg er litt usikker på hvordan jeg
+best går videre for å bli klok, men jeg har jo i hvert fall tre uker
+på å vurdere om jeg skal klage. Enten må nok forespørselen
+reformuleres eller så må jeg vel klage. Synes jo det er merkelig at
+NRK ikke har bedre kontroll med hvilke avtaler de har inngått. Det
+burde jo være noen i ledelsen som vet om de har signert en avtale med
+MPEG-LA eller ikke...</p>
+
+<p>Oppdatering 2012-06-25 20:20: Et google-søk på "2011/371 nrk"
+sendte meg til postjournalen for
+<a href="http://nrk.no/contentfile/file/1.8212365!offentligjournal19062012.pdf">2012-06-19</a>
+og
+<a href="http://nrk.no/contentfile/file/1.8214156!offentligjournal20062012.pdf">2012-06-20</a>
+hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
+er "Graphic Systems Regions MA 2378/10E". Videre søk etter "Graphic
+Systems Regions" viser at dette er saken til et anbud om
+"<a href="http://no.mercell.com/m/mts/Tender/27179412.aspx">a graphics
+system for 12 or 13 sites broadcasting regional news</a>" hos Mercell
+Sourcing Service, også omtalt på
+<a href="http://www.publictenders.net/tender/595705">Public
+Tenders</a> og
+<a href="http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521">Doffin</a>.
+Jeg er dog usikker på hvordan dette er relatert til min
+forespørsel.</p>
+
+<p>Oppdatering 2012-06-25 22:40: Ble tipset av Kieran Kunhya, fra
+miljøet rundt
+<a href="http://code.google.com/p/open-broadcast-encoder/">Open
+Broadcast Encoder</a>, at listen over de som har lisensavtale med
+MPEG-LA er
+<a href="http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx">tilgjengelig
+på web</a>. Veldig fint å oppdage hvor den finnes, da jeg må ha lett
+etter feil ting da jeg forsøke å finne den. Der står ikke NRK, men
+flere andre "Broadcasting Company"-oppføringer. Lurer på om det betyr
+at NRK ikke trenger avtale, eller noe helt annet?</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 21st June 2012
+ </div>
+ <div class="body">
+ <p>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
+distribuere og kringkaste video i MPEG4 eller med videokodingen H.264?
+<a href="http://webmink.com/essays/h-264/">H.264 og MPEG4 er jo ikke en
+fri og åpen standard</a> i henhold til
+<a href="http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html">definisjonen
+til Digistan</a>, så i enkelte land er det ingen tvil om at du må ha
+en slik avtale, men jeg må innrømme at jeg ikke vet om det også
+gjelder Norge. Det ser uansett ut til å være en juridisk interessant
+problemstilling. Men jeg tenkte her om dagen som så, at hvis det er
+nødvendig, så har store aktører som
+<a href="http://www.nrk.no/">NRK</a> og
+<a href="http://www.regjeringen.no/">regjeringen</a> skaffet seg en
+slik avtale. Jeg har derfor sendt forespørsel til begge (for
+regjeringen sin del er det Departementenes Servicesenter som gjør
+jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
+og/eller H.264 med MPEG-LA eller andre aktører som opererer på vegne
+av MPEG-LA. Her er kopi av eposten jeg har sendt til
+<a href="http://www.dss.dep.no/">Departementenes Servicesenter</a>.
+Forespørselen til NRK er veldig lik.</p>
-<table>
-<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
-<tr><td>Tekst</td> <td>odt:2480 </td> <td>docx:4460</td></tr>
-<tr><td>Presentasjon</td> <td>odp:299 </td> <td>pptx:741</td></tr>
-<tr><td>Regneark</td> <td>ods:187 </td> <td>xlsx:372</td></tr>
-</table>
+<p><blockquote>
-<p>I wonder how these numbers change over time.</p>
+<p>Date: Tue, 19 Jun 2012 15:18:33 +0200
+<br>From: Petter Reinholdtsen
+<br>To: postmottak@dss.dep.no
+<br>Subject: Innsynsbegjæring om MPEG/H.264-relaterte avtaler
+
+<p>Hei. Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
+til avtaler rundt bruk av videoformatene MPEG og H.264. Jeg er
+spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
+eller noen som representerer MPEG-LA i Norge.</p>
-<p>I am aware of Google returning different results and numbers based
-on where the search is done, so I guess these numbers will differ if
-they are conduced in another country. Because of this, I did the same
-search from a machine in California, USA, a few minutes after the
-search done from a machine here in Norway.</p>
+<p>MPEG og H.264 er videoformater som brukes både til kringkasting
+(f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
+via Adobe Flash. MPEG-LA, <URL:
+<a href="http://www.mpeg-la.com/">http://www.mpeg-la.com/</a> >, er
+en organisasjon som har fått oppgaven, av de kjente rettighetshavere
+av immaterielle rettigheter knyttet til MPEG og H.264, å selge
+bruksrett for MPEG og H.264.</p>
+<p>Via regjeringen.no kringkastes med MPEG og H.264-baserte
+videoformater, og dette ser ut til å være organisert av DSS. Jeg
+antar dermed at DSS har avtale med en eller annen aktør om dette.</p>
-<table>
-<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
-<tr><td>Tekst</td> <td>odt:129000</td> <td>docx:308000</td></tr>
-<tr><td>Presentasjon</td> <td>odp:44200</td> <td>pptx:93900</td></tr>
-<tr><td>Regneark</td> <td>ods:26500 </td> <td>xlsx:82400</td></tr>
-</table>
+<p>F.eks. har Adobe Premiere Pro har følgende klausul i følge <URL:
+<a href="http://news.cnet.com/8301-30685_3-20000101-264.html">http://news.cnet.com/8301-30685_3-20000101-264.html</a>
+>:</p>
-<p>And with 'site:no':
+<p><blockquote>
-<table>
-<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
-<tr><td>Tekst</td> <td>odt:2480</td> <td>docx:3410</td></tr>
-<tr><td>Presentasjon</td> <td>odp:175</td> <td>pptx:604</td></tr>
-<tr><td>Regneark</td> <td>ods:186 </td> <td>xlsx:296</td></tr>
-</table>
+ <p>6.17. AVC DISTRIBUTION. The following notice applies to software
+ containing AVC import and export functionality: THIS PRODUCT IS
+ LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
+ NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
+ WITH THE AVC STANDARD ("AVC VIDEO") AND/OR (b) DECODE AVC VIDEO THAT
+ WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
+ ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
+ LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
+ IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
+ FROM MPEG LA L.L.C. SEE
+ <a href="http://www.mpegla.com">http://www.mpegla.com</a>.</p>
-<p>Interesting difference, not sure what to conclude from these
-numbers.</p>
+</blockquote></p>
- </div>
- <div class="tags">
-
+<p>Her er det kun "non-commercial" og "personal and non-commercial"
+aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
+følgende klausul i følge <URL:
+<a href="http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf</a>
+>:</p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Danmark_g__r_for_ODF_.html">Danmark går for ODF?</a>
- </div>
- <div class="date">
- 2010-01-29 12:00
- </div>
+<p><blockquote>
- <div class="body">
+ <p>15. Merknad om H.264/AVC. Hvis Apple-programvaren inneholder
+ funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
+ kommersiell bruk ekstra lisensiering og følgende gjelder:
+ AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
+ FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
+ KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN ("AVC-VIDEO")
+ OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
+ PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
+ FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
+ AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
+ FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.</p>
+</blockquote></p>
-<p>Ble nettopp gjort oppmerksom på en
-<a href="http://www.version2.dk/artikel/13690-breaking-odf-vinder-dokumentformat-krigen ">nyhet fra Version2</a>
-fra Danmark, der det hevdes at Folketinget har vedtatt at ODF skal
-brukes som dokumentutvekslingsformat i Staten.</p>
+<p>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
+bruker MPEG og H.264, at en må ha en avtale med MPEG-LA for å ha lov
+til å bruke programmet/utstyret hvis en skal lage noe annet enn
+private filmer og i ikke-kommersiell virksomhet.</p>
+
+<p>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
+ikke er begrenset av de generelle bruksvilkårene som gjelder for
+utstyr som bruker MPEG og/eller H.264.</p>
+</blockquote></p>
-<p>Hyggelig lesning, spesielt hvis det viser seg at de av vedtatt
-kravlisten for hva som skal aksepteres som referert i kommentarfeltet
-til artikkelen og
-<a href="http://www.version2.dk/artikel/13693-er-ooxml-doemt-ude-her-er-kravene-til-en-offentlig-dokumentstandard">en
-annen artikkel</a> i samme nett-avis. Liker spesielt godt denne:</p>
+<p>Nå venter jeg spent på svaret. Jeg planlegger å blogge om svaret
+her.</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html">The cost of ODF and OOXML</a>
+ </div>
+ <div class="date">
+ 26th May 2012
+ </div>
+ <div class="body">
+ <p>I just come across a blog post from Glyn Moody reporting the
+claimed cost from Microsoft on requiring ODF to be used by the UK
+government. I just sent him an email to let him know that his
+assumption are most likely wrong. Sharing it here in case some of my
+blog readers have seem the same numbers float around in the UK.</p>
+
+<p><blockquote> <p>Hi. I just noted your
+<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>
+comment:</p>
+
+<p><blockquote>"They're all in Danish, not unreasonably, but even
+with the help of Google Translate I can't find any figures about the
+savings of "moving to a flexible two standard" as claimed by the
+Microsoft email. But I assume it is backed up somewhere, so let's take
+it, and the £500 million figure for the UK, on trust."
+</blockquote></p>
-<p><blockquote> Det skal demonstreres, at standarden i sin helhed kan
-implementeres af alle direkte i sin helhed på flere
-platforme.</blockquote></p>
+<p>I can tell you that the Danish reports are inflated. I believe it is
+the same reports that were used in the Norwegian debate around 2007,
+and Gisle Hannemyr (a well known IT commentator in Norway) had a look
+at the content. In short, the reason it is claimed that using ODF
+will be so costly, is based on the assumption that this mean every
+existing document need to be converted from one of the MS Office
+formats to ODF, transferred to the receiver, and converted back from
+ODF to one of the MS Office formats, and that the conversion will cost
+10 minutes of work time for both the sender and the receiver. In
+reality the sender would have a tool capable of saving to ODF, and the
+receiver would have a tool capable of reading it, and the time spent
+would at most be a few seconds for saving and loading, not 20 minutes
+of wasted effort.</p>
+
+<p>Microsoft claimed all these costs were saved by allowing people to
+transfer the original files from MS Office instead of spending 10
+minutes converting to ODF. :)</p>
+
+<p>See
+<a href="http://hannemyr.com/no/ms12_vl02.php">http://hannemyr.com/no/ms12_vl02.php</a>
+and
+<a href="http://hannemyr.com/no/ms12.php">http://hannemyr.com/no/ms12.php</a>
+for background information. Norwegian only, sorry. :)</p>
+</blockquote></p>
-<p>Noe slikt burde være et krav også i Norge.</p>
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/OpenOffice_org_fungerer_da_fint_for_blinde_.html">OpenOffice.org fungerer da fint for blinde?</a>
+ </div>
+ <div class="date">
+ 21st May 2012
+ </div>
+ <div class="body">
+ <p>De siste dagene har høringsuttalelsene om DIFIs forslag til
+standardkatalog v3.1 blitt
+<a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder?tab=comments">publisert
+på DIFIs nettside</a>, og jeg kunne der glede meg over at
+<a href="http://wiki.nuug.no/uttalelser/201204-standardkatalog-v3.1">NUUGs</a>
+uttalelse er kommet med. En uttalelse som overrasker og forvirrer meg
+er
+<a href="http://www.standard.difi.no/filearchive/norges-blindeforbund.pdf">den
+fra Norges Blindeforbund</a>, som 5 år etter at Klaus Knopper sammen
+med sin blinde kone blant annet
+<a href="http://www.nuug.no/aktiviteter/20071211-accessibility/">demonstrerte
+høyttalende OpenOffice.org på nynorsk for blinde</a> på et NUUG-møte.</p>
+
+<p><a href="https://www.blindeforbundet.no/">Norges Blindeforbund</a>
+skriver følgende, som for meg virker å være formulert på sviktende
+grunnlag:</p>
- </div>
- <div class="tags">
-
+<p><blockquote>
+<p>Bruk av fri programvare
+
+<p>I FRIPROGSENTERET, RAPPORT 2009-02: Universell utforming
+<a href="http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf">http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf</a>
+sies det "Det finnes i dag ikke mange fri programvare-rammeverk eller
+generelle løsninger som støtter tilgjengelighet eller som er
+universelt utformet."</p>
+
+<p>Til tross for at det gjennom prinsippene i fri programvare åpnes
+for større frihet til selv å påvirke programvareløsninger i retning av
+universell utforming viser praksis at virkeligheten er en annen.
+Mange av de mest alminnelige frie programvarepakkene mangler delvis
+eller fullstendig tilgjengelighet for mennesker med nedsatt
+syn. Eksempler på dette er OpenOffice og LibreOffice m.fl.</p>
+
+<p>En annen utfordring ved bruk av fri programvare kan være manglende
+kundestøtte og muligheter til opplæring i bruk av løsningen. Svaksynte
+og blinde har et høyere behov for denne typen støtte enn andre brukere
+ettersom mange av dem har behov for tilleggsprogramvare som skal
+fungere sammen med den opprinnelige programvaren, og ettersom man ikke
+har de samme muligheter for overblikk over grensesnittet som en seende
+bruker. I tillegg til dette kommer de mer tilgjengelighetstekniske
+utfordringene som ofte må løses i samarbeid med
+programvareleverandør/produsent.</p>
+
+<p>Fri programvare er ikke på samme måte underlagt lovgivning gjennom
+for eksempel diskriminerings og tilgjengelighetsloven ettersom det
+ikke alltid finnes en produsent/tilbyder av tjenesten eller produktet.</p>
+
+<p>Norges Blindeforbund krever at universell utforming og
+brukskvalitet tas med som viktige hensyn i utredninger som ligger til
+grunn for valg av standarder som primært leder brukeren mot fri
+programvare. Et eksempel på dette er bruk av dokumentformatet ODF som
+leder brukeren i retning av OpenOffice, som er helt eller delvis
+utilgjengelig for svaksynte og blinde – noe avhengig av plattform og
+hjelpemiddelprogramvare.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+</blockquote></p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html">A manual for standards wars...</a>
- </div>
- <div class="date">
- 2010-06-06 14:15
- </div>
+<p>Jeg håper noen involvert i OpenOffice.org og/eller LibreOffice tar
+kontakt med Norges Blindeforbund og oppklarer det som for meg virker å
+være en misforståelse, i og med at OpenOffice.org så vidt jeg vet
+fungerer fint også for blinde.</p>
+
+<p>Jeg ble minnet på problemstillingen da jeg leste Slashdot-saken om
+"<a href="http://linux.slashdot.org/story/12/05/21/1417221/the-state-of-linux-accessibility">The
+State of Linux Accessibility</a>", som også hevder at Linux fungerer
+utmerket for blinde.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 27th April 2012
+ </div>
+ <div class="body">
+ <p>NUUG-styremedlem Hans-Petter Fjeld
+<a href="https://plus.google.com/u/0/110394259537201279374/posts/AGzRmAuFdW1">meldte
+nettopp</a> at han har sendt inn <a href="http://www.nuug.no/">NUUG</a>s
+høringsuttalelse angående Difi sin standardkatalog v3.1. Jeg er veldig
+glad for at så mange bidro og sikret at vår stemme blir hørt i denne
+høringen. Anbefaler alle å lese våre
+<a href="http://wiki.nuug.no/uttalelser/201204-standardkatalog-v3.1">to
+sider med innspill</a>.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 26th April 2012
+ </div>
+ <div class="body">
+ <p>In <a href="http://www.idg.no/computerworld/article243690.ece">an
+article today</a> published by Computerworld Norway, the photographer
+<a href="http://www.urke.com/eirik/">Eirik Helland Urke</a> reports
+that the video editor application included with
+<a href="http://www.htc.com/www/smartphones/htc-one-x/#specs">HTC One
+X</a> have some quite surprising terms of use. The article is mostly
+based on the twitter message from mister Urke, stating:
- <div class="body">
-
-<p>Via the
-<a href="http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html">blog
-of Rob Weir</a> I came across the very interesting essay named
-<a href="http://faculty.haas.berkeley.edu/shapiro/wars.pdf">The Art of
-Standards Wars</a> (PDF 25 pages). I recommend it for everyone
-following the standards wars of today.</p>
+<p><blockquote>
+"<a href="http://twitter.com/urke/status/194062269724897280">Drøy
+brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
+kan jeg KUN bruke dem privat.</a>"
+</blockquote></p>
- </div>
- <div class="tags">
-
+<p>I quickly translated it to this English message:</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p><blockquote>
+"Arrogant user agreement: HTC can use MY edited videos
+commercially. Although I can ONLY use them privately."
+</blockquote></p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">Officeshots taking shape</a>
- </div>
- <div class="date">
- 2010-06-13 11:40
- </div>
+<p>I've been unable to find the text of the license term myself, but
+suspect it is a variation of the MPEG-LA terms I
+<a href="http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html">discovered
+with my Canon IXUS 130</a>. The HTC One X specification specifies that
+the recording format of the phone is .amr for audio and .mp3 for
+video. AMR is
+<a href="http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues">Adaptive
+Multi-Rate audio codec</a> with patents which according to the
+Wikipedia article require an license agreement with
+<a href="http://www.voiceage.com/">VoiceAge</a>. MP4 is
+<a href="http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Patent_licensing">MPEG4 with
+H.264</a>, which according to Wikipedia require a licence agreement
+with <a href="http://www.mpegla.com/">MPEG-LA</a>.</p>
+
+<p>I know why I prefer
+<a href="http://www.digistan.org/open-standard:definition">free and open
+standards</a> also for video.</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html">RAND terms - non-reasonable and discriminatory</a>
+ </div>
+ <div class="date">
+ 19th April 2012
+ </div>
+ <div class="body">
+ <p>Here in Norway, the
+<a href="http://www.regjeringen.no/nb/dep/fad.html?id=339"> Ministry of
+Government Administration, Reform and Church Affairs</a> is behind
+a <a href="http://standard.difi.no/forvaltningsstandarder">directory of
+standards</a> that are recommended or mandatory for use by the
+government. When the directory was created, the people behind it made
+an effort to ensure that everyone would be able to implement the
+standards and compete on equal terms to supply software and solutions
+to the government. Free software and non-free software could compete
+on the same level.</p>
+
+<p>But recently, some standards with RAND
+(<a href="http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing">Reasonable
+And Non-Discriminatory</a>) terms have made their way into the
+directory. And while this might not sound too bad, the fact is that
+standard specifications with RAND terms often block free software from
+implementing them. The reasonable part of RAND mean that the cost per
+user/unit is low,and the non-discriminatory part mean that everyone
+willing to pay will get a license. Both sound great in theory. In
+practice, to get such license one need to be able to count users, and
+be able to pay a small amount of money per unit or user. By
+definition, users of free software do not need to register their use.
+So counting users or units is not possible for free software projects.
+And given that people will use the software without handing any money
+to the author, it is not really economically possible for a free
+software author to pay a small amount of money to license the rights
+to implement a standard when the income available is zero. The result
+in these situations is that free software are locked out from
+implementing standards with RAND terms.</p>
+
+<p>Because of this, when I see someone claiming the terms of a
+standard is reasonable and non-discriminatory, all I can think of is
+how this really is non-reasonable and discriminatory. Because free
+software developers are working in a global market, it does not really
+help to know that software patents are not supposed to be enforceable
+in Norway. The patent regimes in other countries affect us even here.
+I really hope the people behind the standard directory will pay more
+attention to these issues in the future.</p>
+
+<p>You can find more on the issues with RAND, FRAND and RAND-Z terms
+from Simon Phipps
+(<a href="http://blogs.computerworlduk.com/simon-says/2010/11/rand-not-so-reasonable/">RAND:
+Not So Reasonable?</a>).</p>
+
+<p>Update 2012-04-21: Just came across a
+<a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/of-microsoft-netscape-patents-and-open-standards/index.htm">blog
+post from Glyn Moody</a> over at Computer World UK warning about the
+same issue, and urging people to speak out to the UK government. I
+can only urge Norwegian users to do the same for
+<a href="http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder">the
+hearing taking place at the moment</a> (respond before 2012-04-27).
+It proposes to require video conferencing standards including
+specifications with RAND terms.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 16th January 2011
+ </div>
+ <div class="body">
+ <p>The video format struggle on the web continues, and the three
+contenders seem to be Ogg Theora, H.264 and WebM. Most video sites
+seem to use H.264, while others use Ogg Theora. Interestingly enough,
+the comments I see give me the feeling that a lot of people believe
+H.264 is the most supported video format in browsers, but according to
+the Wikipedia article on
+<a href="http://en.wikipedia.org/wiki/HTML5_video">HTML5 video</a>,
+this is not true. Check out the nice table of supprted formats in
+different browsers there. The format supported by most browsers is
+Ogg Theora, supported by released versions of Mozilla Firefox, Google
+Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
+BOLT browser, while not supported by Internet Explorer nor Safari.
+The runner up is WebM supported by released versions of Google Chrome
+Chromium Opera and Origyn Web Browser, and test versions of Mozilla
+Firefox. H.264 is supported by released versions of Safari, Origyn
+Web Browser and BOLT browser, and the test version of Internet
+Explorer. Those wanting Ogg Theora support in Internet Explorer and
+Safari can install plugins to get it.</p>
- <div class="body">
-
-<p>For those of us caring about document exchange and
-interoperability, <a href="http://www.officeshots.org/">OfficeShots</a>
-is a great service. It is to ODF documents what
-<a href="http://browsershots.org/">BrowserShots</a> is for web
-pages.</p>
+<p>To me, the simple conclusion from this is that to reach most users
+without any extra software installed, one uses Ogg Theora with the
+HTML5 video tag. Of course to reach all those without a browser
+handling HTML5, one need fallback mechanisms. In
+<a href="http://www.nuug.no/">NUUG</a>, we provide first fallback to a
+plugin capable of playing MPEG1 video, and those without such support
+we have a second fallback to the Cortado java applet playing Ogg
+Theora. This seem to work quite well, as can be seen in an <a
+href="http://www.nuug.no/aktiviteter/20110111-semantic-web/">example
+from last week</a>.</p>
-<p>A while back, I was contacted by Knut Yrvin at the part of Nokia
-that used to be Trolltech, who wanted to help the OfficeShots project
-and wondered if the University of Oslo where I work would be
-interested in supporting the project. I helped him to navigate his
-request to the right people at work, and his request was answered with
-a spot in the machine room with power and network connected, and Knut
-arranged funding for a machine to fill the spot. The machine is
-administrated by the OfficeShots people, so I do not have daily
-contact with its progress, and thus from time to time check back to
-see how the project is doing.</p>
+<p>The reason Ogg Theora is the most supported format, and H.264 is
+the least supported is simple. Implementing and using H.264
+require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
+are incompatible with free software licensing. If you believed H.264
+was without royalties and license terms, check out
+"<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
+Free That Matters</a>" by Simon Phipps.</p>
-<p>Today I had a look, and was happy to see that the Dell box in our
-machine room now is the host for several virtual machines running as
-OfficeShots factories, and the project is able to render ODF documents
-in 17 different document processing implementation on Linux and
-Windows. This is great.</p>
+<p>A incomplete list of sites providing video in Ogg Theora is
+available from
+<a href="http://wiki.xiph.org/index.php/List_of_Theora_videos">the
+Xiph.org wiki</a>, if you want to have a look. I'm not aware of a
+similar list for WebM nor H.264.</p>
- </div>
- <div class="tags">
-
+<p>Update 2011-01-16 09:40: A question from Tollef on IRC made me
+realise that I failed to make it clear enough this text is about the
+<video> tag support in browsers and not the video support
+provided by external plugins like the Flash plugins.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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 <video></a>
+ </div>
+ <div class="date">
+ 12th January 2011
+ </div>
+ <div class="body">
+ <p>Today I discovered
+<a href="http://www.digi.no/860070/google-dropper-h264-stotten-i-chrome">via
+digi.no</a> that the Chrome developers, in a surprising announcement,
+<a href="http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html">yesterday
+announced</a> plans to drop H.264 support for HTML5 <video> in
+the browser. The argument used is that H.264 is not a "completely
+open" codec technology. If you believe H.264 was free for everyone
+to use, I recommend having a look at the essay
+"<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
+Free That Matters</a>". It is not free of cost for creators of video
+tools, nor those of us that want to publish on the Internet, and the
+terms provided by MPEG-LA excludes free software projects from
+licensing the patents needed for H.264. Some background information
+on the Google announcement is available from
+<a href="http://www.osnews.com/story/24243/Google_To_Drop_H264_Support_from_Chrome">OSnews</a>.
+A good read. :)</p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2010-09-09 23:55
- </div>
+<p>Personally, I believe it is great that Google is taking a stand to
+promote equal terms for everyone when it comes to video publishing on
+the Internet. This can only be done by publishing using free and open
+standards, which is only possible if the web browsers provide support
+for these free and open standards. At the moment there seem to be two
+camps in the web browser world when it come to video support. Some
+browsers support H.264, and others support
+<a href="http://www.theora.org/">Ogg Theora</a> and
+<a href="http://www.webmproject.org/">WebM</a>
+(<a href="http://www.diracvideo.org/">Dirac</a> is not really an option
+yet), forcing those of us that want to publish video on the Internet
+and which can not accept the terms of use presented by MPEG-LA for
+H.264 to not reach all potential viewers.
+Wikipedia keep <a href="http://en.wikipedia.org/wiki/HTML5_video">an
+updated summary</a> of the current browser support.</p>
- <div class="body">
-
-<p>A few days ago I had the mixed pleasure of bying a new digital
-camera, a Canon IXUS 130. It was instructive and very disturbing to
-be able to verify that also this camera producer have the nerve to
-specify how I can or can not use the videos produced with the camera.
-Even thought I was aware of the issue, the options with new cameras
-are limited and I ended up bying the camera anyway. What is the
-problem, you might ask? It is software patents, MPEG-4, H.264 and the
-MPEG-LA that is the problem, and our right to record our experiences
-without asking for permissions that is at risk.
+<p>Not surprising, several people would prefer Google to keep
+promoting H.264, and John Gruber
+<a href="http://daringfireball.net/2011/01/simple_questions">presents
+the mind set</a> of these people quite well. His rhetorical questions
+provoked a reply from Thom Holwerda with another set of questions
+<a href="http://www.osnews.com/story/24245/10_Questions_for_John_Gruber_Regarding_H_264_WebM">presenting
+the issues with H.264</a>. Both are worth a read.</p>
-<p>On page 27 of the Danish instruction manual, this section is
-written:</p>
+<p>Some argue that if Google is dropping H.264 because it isn't free,
+they should also drop support for the Adobe Flash plugin. This
+argument was covered by Simon Phipps in
+<a href="http://blogs.computerworlduk.com/simon-says/2011/01/google-and-h264---far-from-hypocritical/index.htm">todays
+blog post</a>, which I find to put the issue in context. To me it
+make perfect sense to drop native H.264 support for HTML5 in the
+browser while still allowing plugins.</p>
-<blockquote>
-<p>This product is licensed under AT&T patents for the MPEG-4 standard
-and may be used for encoding MPEG-4 compliant video and/or decoding
-MPEG-4 compliant video that was encoded only (1) for a personal and
-non-commercial purpose or (2) by a video provider licensed under the
-AT&T patents to provide MPEG-4 compliant video.</p>
+<p>I suspect the reason this announcement make so many people protest,
+is that all the users and promoters of H.264 suddenly get an uneasy
+feeling that they might be backing the wrong horse. A lot of TV
+broadcasters have been moving to H.264 the last few years, and a lot
+of money has been invested in hardware based on the belief that they
+could use the same video format for both broadcasting and web
+publishing. Suddenly this belief is shaken.</p>
-<p>No license is granted or implied for any other use for MPEG-4
-standard.</p>
-</blockquote>
+<p>An interesting question is why Google is doing this. While the
+presented argument might be true enough, I believe Google would only
+present the argument if the change make sense from a business
+perspective. One reason might be that they are currently negotiating
+with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
+feeling that dropping H.264 completely from Chroome, Youtube and
+Google Video would improve the negotiation position of Google.
+Another reason might be that Google want to save money by not having
+to pay the video tax to MPEG-LA at all, and thus want to move to a
+video format not requiring royalties at all. A third reason might be
+that the Chrome development team simply want to avoid the
+Chrome/Chromium split to get more help with the development of Chrome.
+I guess time will tell.</p>
-<p>In short, the camera producer have chosen to use technology
-(MPEG-4/H.264) that is only provided if I used it for personal and
-non-commercial purposes, or ask for permission from the organisations
-holding the knowledge monopoly (patent) for technology used.</p>
+<p>Update 2011-01-15: The Google Chrome team provided
+<a href="http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html">more
+background and information on the move</a> it a blog post yesterday.</p>
-<p>This issue has been brewing for a while, and I recommend you to
-read
-"<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
-Our Civilization's Video Art and Culture is Threatened by the
-MPEG-LA</a>" by Eugenia Loli-Queru and
-"<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
-The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
-the issue. The solution is to support the
-<a href="http://www.digistan.org/open-standard:definition">free and
-open standards</a> for video, like <a href="http://www.theora.org/">Ogg
-Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 30th December 2010
+ </div>
+ <div class="body">
+ <p>After trying to
+<a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
+Ogg Theora</a> to
+<a href="http://www.digistan.org/open-standard:definition">the Digistan
+definition</a> of a free and open standard, I concluded that this need
+to be done for more standards and started on a framework for doing
+this. As a start, I want to get the status for all the standards in
+the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
+JPEG, PNG, SVG and others. But to be able to complete this in a
+reasonable time frame, I will need help.</p>
- </div>
- <div class="tags">
-
+<p>If you want to help out with this work, please visit
+<a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
+wiki pages I have set up for this</a>, and let me know that you want
+to help out. The IRC channel #nuug on irc.freenode.net is a good
+place to coordinate this for now, as it is the IRC channel for the
+NUUG association where I have created the framework (I am the leader
+of the Norwegian Unix User Group).</p>
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>The framework is still forming, and a lot is left to do. Do not be
+scared by the sketchy form of the current pages. :)</p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html">Standardkrav inn i anbudstekster?</a>
- </div>
- <div class="date">
- 2010-10-17 19:30
- </div>
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
+ </div>
+ <div class="date">
+ 27th December 2010
+ </div>
+ <div class="body">
+ <p>One of the reasons I like the Digistan definition of
+"<a href="http://www.digistan.org/open-standard:definition">Free and
+Open Standard</a>" is that this is a new term, and thus the meaning of
+the term has been decided by Digistan. The term "Open Standard" has
+become so misunderstood that it is no longer very useful when talking
+about standards. One end up discussing which definition is the best
+one and with such frame the only one gaining are the proponents of
+de-facto standards and proprietary solutions.</p>
- <div class="body">
-
-<p>Hvis det å følge standarder skal ha noen effekt overfor
-leverandører, så må slike krav og ønsker komme inn i anbudstekster når
-systemer kjøpes inn. Har ikke sett noen slike formuleringer i anbud
-så langt, men har tenkt litt på hva som bør inn. Her er noen ideer og
-forslag. Min drøm er at en kan sette krav til slik støtte i
-anbudstekster, men så langt er det nok mer sannsynlig at en må nøye
-seg med å skrive at det er en fordel om slik støtte er tilstede i
-leveranser.</p>
+<p>But to give us an idea about the diversity of definitions of open
+standards, here are a few that I know about. This list is not
+complete, but can be a starting point for those that want to do a
+complete survey. More definitions are available on the
+<a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
+page</a>.</p>
-<p>Som systemadministrator på Universitetet er det typisk to områder
-som er problematiske for meg. Det ene er admin-grensesnittene på
-tjenermaskiner, som vi ønsker å bruke via ssh. Det andre er nettsider
-som vi ønsker å bruke via en nettleser. For begge deler er det viktig
-at protokollene og formatene som brukes følger standarder våre verktøy
-støtter.</p>
+<p>First off is my favourite, the definition from the European
+Interoperability Framework version 1.0. Really sad to notice that BSA
+and others has succeeded in getting it removed from version 2.0 of the
+framework by stacking the committee drafting the new version with
+their own people. Anyway, the definition is still available and it
+include the key properties needed to make sure everyone can use a
+specification on equal terms.</p>
-<p>De fleste har nå støtte for SSH som overføringsprotkoll for
-admin-grensesnittet, men det er ikke tilstrekkelig for å kunne stille
-inn f.eks BIOS og RAID-kontroller via ssh-forbindelsen. Det er flere
-aktuelle protokoller for fremvisning av BIOS-oppsett og
-oppstartmeldinger, og min anbefaling ville være å kreve
-VT100-kompatibel protokoll, for å sikre at flest mulig
-terminalemulatorer kan forstå hva som kommer fra admin-grensesnittet
-via ssh. Andre aktuelle alternativer er ANSI-terminalemulering og
-VT220. Kanskje en formulering ala dette i anbudsutlysninger vil
-fungere:</p>
+<blockquote>
-<p><blockquote>
-BIOS og oppstartmeldinger i administrasjonsgrensesnittet til maskinen
-bør/skal være tilgjengelig via SSH-protokollen som definert av IETF
-(RFC 4251 mfl.) og følge terminalfremvisningprotokollen VT100 (ref?)
-når en kobler seg til oppstart via ssh.
-</blockquote></p>
+<p>The following are the minimal characteristics that a specification
+and its attendant documents must have in order to be considered an
+open standard:</p>
-<p>Har ikke lykkes med å finne en god referanse for
-VT100-spesifikasjonen.</p>
+<ul>
-<p>Når det gjelder nettsider, så er det det HTML, CSS og
-JavaScript-spesifikasjonen til W3C som gjelder.</p>
+<li>The standard is adopted and will be maintained by a not-for-profit
+organisation, and its ongoing development occurs on the basis of an
+open decision-making procedure available to all interested parties
+(consensus or majority decision etc.).</li>
-<p><blockquote>
-Alle systemets nettider bør/skal være i henhold til statens
-standardkatalogs krav om nettsider og følge HTML-standarden som
-definert av W3C, og validere uten feil hos W3Cs HTML-validator
-(http://validator.w3.org). Hvis det brukes CSS så bør/skal denne
-validere uten feil hos W3Cs CSS-validator
-(http://jigsaw.w3.org/css-validator/). Eventuelle JavaScript skal
-være i henhold til EcmaScript-standarden. I tillegg til å følge de
-overnevnte standardene skal websidene fungere i nettleserne (fyll inn
-relevant liste for organisasjonen) Firefox 3.5, Internet Explorer 8,
-Opera 9, etc.
-</blockquote></p>
+<li>The standard has been published and the standard specification
+document is available either freely or at a nominal charge. It must be
+permissible to all to copy, distribute and use it for no fee or at a
+nominal fee.</li>
-<p>Vil et slikt avsnitt være konkret nok til å få leverandørene til å
-lage nettsider som følger standardene og fungerer i flere
-nettlesere?</p>
+<li>The intellectual property - i.e. patents possibly present - of
+(parts of) the standard is made irrevocably available on a royalty-
+free basis.</li>
-<p>Tar svært gjerne imot innspill på dette temaet til aktive (at)
-nuug.no, og er spesielt interessert i hva andre skriver i sine anbud
-for å oppmuntre leverandører til å følge standardene. Kanskje NUUG
-burde lage et dokument med forslag til standardformuleringer å ta med
-i anbudsutlysninger?</p>
+<li>There are no constraints on the re-use of the standard.</li>
-<p>Oppdatering 2010-12-03: I følge Wikipedias oppføring om
-<a href="http://en.wikipedia.org/wiki/ANSI_escape_code">ANSI escape
-code</a>, så bruker VT100-terminaler ECMA-48-spesifikasjonen som
-basis for sin oppførsel. Det kan dermed være et alternativ når en
-skal spesifisere hvordan seriell-konsoll skal fungere.</p>
+</ul>
+</blockquote>
- </div>
- <div class="tags">
-
+<p>Another one originates from my friends over at
+<a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
+support for <a href="http://www.aaben-standard.dk/">this
+definition</a> in 2004. It even made it into the Danish parlament as
+<a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
+definition of a open standard</a>. Another from a different part of
+the Danish government is available from the wikipedia page.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<blockquote>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2010-10-30 11:20
- </div>
+<p>En åben standard opfylder følgende krav:</p>
- <div class="body">
-
-<p>I dag la jeg inn en kommentar på en sak hos NRKBeta
-<a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
-hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
-filmene NRK la ut ikke var tilgjengelig i et
-<a href="http://www.digistan.org/open-standard:definition">fritt og
-åpent format</a>. Dette var det jeg skrev publiserte der 07:39.</p>
+<ol>
-<p><blockquote>
-<p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
-nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
-som dette, vet at det stort sett er mulig å lure ut ting med den
-nødvendige forkunnskapen."</p>
+<li>Veldokumenteret med den fuldstændige specifikation offentligt
+tilgængelig.</li>
-<p>Haha. Å streame innhold er det samme som å laste ned innhold, så å
-beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
-er å forlede leseren.</p>
+<li>Frit implementerbar uden økonomiske, politiske eller juridiske
+begrænsninger på implementation og anvendelse.</li>
-<p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
-vil tillate streaming men ikke nedlasting meningsløs.</p>
+<li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
+"standardiseringsorganisation") via en åben proces.</li>
-<p>Anbefaler forresten å lese
-<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>
-om hva som ville være konsekvensen hvis digitale avspillingssperrer
-(DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
-derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
-men det er skremmende hva samfunnet tillater og NRK er med på å bygge
-opp under.</p>
-</blockquote></p>
+</ol>
-<p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
-NRKBeta:</p>
+</blockquote>
-<p><blockquote>
-<p>From: Anders Hofseth <XXX@gmail.com>
-<br>To: "pere@hungry.com" <pere@hungry.com>
-<br>Cc: Eirik Solheim <XXX@gmail.com>, Jon Ståle Carlsen <XXX@gmail.com>, Henrik Lied <XXX@gmail.com>
-<br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
-<br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
+<p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
+definition</a> from Free Software Foundation Europe.</p>
-<p>Hei Petter.
-<br>Det du forsøker dra igang er egentlig en interessant diskusjon,
-men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
-om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
-særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
+<blockquote>
-<p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
-fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
-konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
+<p>An Open Standard refers to a format or protocol that is</p>
-<p>Med hilsen,
-<br>-anders</p>
+<ol>
-<p>Ring meg om noe er uklart: 95XXXXXXX</p>
-</blockquote></p>
+<li>subject to full public assessment and use without constraints in a
+manner equally available to all parties;</li>
-<p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
-over følgende svar. I og med at debatten er fjernet fra NRK Betas
-kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
-Har fjernet epostadresser og telefonnummer til de involverte, for å
-unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
+<li>without any components or extensions that have dependencies on
+formats or protocols that do not meet the definition of an Open
+Standard themselves;</li>
-<p><blockquote>
-<p>From: Petter Reinholdtsen <pere@hungry.com>
-<br>To: Anders Hofseth <XXX@gmail.com>
-<br>Cc: Eirik Solheim <XXX@gmail.com>,
-<br> Jon Ståle Carlsen <XXX@gmail.com>,
-<br> Henrik Lied <XXX@gmail.com>
-<br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
-<br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
+<li>free from legal or technical clauses that limit its utilisation by
+any party or in any business model;</li>
-<p>[Anders Hofseth]
-<br>> Hei Petter.</p>
+<li>managed and further developed independently of any single vendor
+in a process open to the equal participation of competitors and third
+parties;</li>
-<p>Hei.</p>
+<li>available in multiple complete implementations by competing
+vendors, or as a complete implementation equally available to all
+parties.</li>
-<p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
-<br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
-<br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
-<br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
+</ol>
-<p>Godt å se at du er enig i at dette er en interessant diskusjon. Den
-vil nok fortsette en stund til. :)</p>
+</blockquote>
-<p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
-vitende og vilje ønsker å forlede rettighetshaverne for å kunne
-fortsette å legge ut arkivmateriale.</p>
+<p>A long time ago, SUN Microsystems, now bought by Oracle, created
+its
+<a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
+Standards Checklist</a> with a fairly detailed description.</p>
-<p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
-faktum, som er at streaming er det samme som nedlasting, og at innhold
-som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
-det.</p>
+<blockquote>
+<p>Creation and Management of an Open Standard
-<p>Det du sier er jo at klarering av arkivmateriale for publisering på
-web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
-Det er ikke et argument som holder vann. :)</p>
+<ul>
-<p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
-<br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
-<br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
+<li>Its development and management process must be collaborative and
+ democratic:
-<p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
-heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
-mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
-godtar å forlede publikum. Ville heller at NRK krever at innhold som
-skal sendes skal være uten bruksbegresninger og kan publiseres i
-formater som heller ikke har bruksbegresninger (bruksbegresningene til
-H.264 burde få varselbjellene i NRK til å ringe).</p>
+ <ul>
-<p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
-påstander om at "streaming beskytter mot nedlasting" som bare er egnet
-til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
+ <li>Participation must be accessible to all those who wish to
+ participate and can meet fair and reasonable criteria
+ imposed by the organization under which it is developed
+ and managed.</li>
-<p>Anbefaler <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
-titt på
-<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> >.
-for å se hva slags bruksbegresninger H.264 innebærer.</p>
+ <li>The processes must be documented and, through a known
+ method, can be changed through input from all
+ participants.</li>
-<p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
-kan brukes før rettighetshaverene også innser at de er med på å skade
-samfunnets kultur og kollektive hukommelse, så får en i hvert fall
-synliggjort konsekvensene og antagelig mer flammer på en debatt som er
-langt på overtid.</p>
+ <li>The process must be based on formal and binding commitments for
+ the disclosure and licensing of intellectual property rights.</li>
-<p>> Ring meg om noe er uklart: XXX</p>
+ <li>Development and management should strive for consensus,
+ and an appeals process must be clearly outlined.</li>
-<p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
-Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
-gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
-for videre diskusjon hadde dere i mine øyne kommet fra det med
-ryggraden på plass.</p>
+ <li>The standard specification must be open to extensive
+ public review at least once in its life-cycle, with
+ comments duly discussed and acted upon, if required.</li>
-<p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
+ </ul>
-<p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
-<URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
-<URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
-NRK1. :)</p>
+</li>
-<p>Vennlig hilsen,
-<br>--
-<br>Petter Reinholdtsen</p>
+</ul>
- </div>
- <div class="tags">
-
+<p>Use and Licensing of an Open Standard</p>
+<ul>
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
-
- </div>
-</div>
-<div class="padding"></div>
+<li>The standard must describe an interface, not an implementation,
+ and the industry must be capable of creating multiple, competing
+ implementations to the interface described in the standard without
+ undue or restrictive constraints. Interfaces include APIs,
+ protocols, schemas, data formats and their encoding.</li>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html">Officeshots still going strong</a>
- </div>
- <div class="date">
- 2010-12-25 09:40
- </div>
+<li> The standard must not contain any proprietary "hooks" that create
+ a technical or economic barriers</li>
- <div class="body">
-
-<p>Half a year ago I
-<a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">wrote
-a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
-a web service to allow anyone to test how ODF documents are handled by
-the different programs reading and writing the ODF format.</p>
+<li>Faithful implementations of the standard must
+ interoperate. Interoperability means the ability of a computer
+ program to communicate and exchange information with other computer
+ programs and mutually to use the information which has been
+ exchanged. This includes the ability to use, convert, or exchange
+ file formats, protocols, schemas, interface information or
+ conventions, so as to permit the computer program to work with other
+ computer programs and users in all the ways in which they are
+ intended to function.</li>
-<p>I just had a look at the service, and it seem to be going strong.
-Very interesting to see the results reported in the gallery, how
-different Office implementations handle different ODF features. Sad
-to see that KOffice was not doing it very well, and happy to see that
-LibreOffice has been tested already (but sadly not listed as a option
-for OfficeShots users yet). I am glad to see that the ODF community
-got such a great test tool available.</p>
+<li>It must be permissible for anyone to copy, distribute and read the
+ standard for a nominal fee, or even no fee. If there is a fee, it
+ must be low enough to not preclude widespread use.</li>
- </div>
- <div class="tags">
-
+<li>It must be possible for anyone to obtain free (no royalties or
+ fees; also known as "royalty free"), worldwide, non-exclusive and
+ perpetual licenses to all essential patent claims to make, use and
+ sell products based on the standard. The only exceptions are
+ terminations per the reciprocity and defensive suspension terms
+ outlined below. Essential patent claims include pending, unpublished
+ patents, published patents, and patent applications. The license is
+ only for the exact scope of the standard in question.
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+ <ul>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2010-12-25 10:50
- </div>
+ <li> May be conditioned only on reciprocal licenses to any of
+ licensees' patent claims essential to practice that standard
+ (also known as a reciprocity clause)</li>
- <div class="body">
-
-<p>A few days ago
-<a href="http://www.idg.no/computerworld/article189879.ece">an
-article</a> in the Norwegian Computerworld magazine about how version
-2.0 of
-<a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
-Interoperability Framework</a> has been successfully lobbied by the
-proprietary software industry to remove the focus on free software.
-Nothing very surprising there, given
-<a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
-reports</a> on how Microsoft and others have stacked the committees in
-this work. But I find this very sad. The definition of
-<a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
-open standard from version 1</a> was very good, and something I
-believe should be used also in the future, alongside
-<a href="http://www.digistan.org/open-standard:definition">the
-definition from Digistan</A>. Version 2 have removed the open
-standard definition from its content.</p>
+ <li> May be terminated as to any licensee who sues the licensor
+ or any other licensee for infringement of patent claims
+ essential to practice that standard (also known as a
+ "defensive suspension" clause)</li>
-<p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
-Villanueva, congressman in Peru at the time, to Microsoft as a reply
-to Microsofts attack on his proposal regarding the use of free software
-in the public sector in Peru. As the text was not available from a
-few of the URLs where it used to be available, I copy it here from
-<a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
-source</a> to ensure it is available also in the future. Some
-background information about that story is available in
-<a href="http://www.linuxjournal.com/article/6099">an article</a> from
-Linux Journal in 2002.</p>
+ <li> The same licensing terms are available to every potential
+ licensor</li>
-<blockquote>
-<p>Lima, 8th of April, 2002<br>
-To: Señor JUAN ALBERTO GONZÁLEZ<br>
-General Manager of Microsoft Perú</p>
+ </ul>
+</li>
-<p>Dear Sir:</p>
+<li>The licensing terms of an open standards must not preclude
+ implementations of that standard under open source licensing terms
+ or restricted licensing terms</li>
-<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>
+</ul>
-<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>
+</blockquote>
-<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>
+<p>It is said that one of the nice things about standards is that
+there are so many of them. As you can see, the same holds true for
+open standard definitions. Most of the definitions have a lot in
+common, and it is not really controversial what properties a open
+standard should have, but the diversity of definitions have made it
+possible for those that want to avoid a level marked field and real
+competition to downplay the significance of open standards. I hope we
+can turn this tide by focusing on the advantages of Free and Open
+Standards.</p>
-<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>
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 25th December 2010
+ </div>
+ <div class="body">
+ <p><a href="http://www.digistan.org/open-standard:definition">The
+Digistan definition</a> of a free and open standard reads like this:</p>
-<p>
-<ul>
-<li>Free access to public information by the citizen. </li>
-<li>Permanence of public data. </li>
-<li>Security of the State and citizens.</li>
-</ul>
-</p>
+<blockquote>
-<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>
+<p>The Digital Standards Organization defines free and open standard
+as follows:</p>
-<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>
+<ol>
-<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>
+<li>A free and open standard is immune to vendor capture at all stages
+in its life-cycle. Immunity from vendor capture makes it possible to
+freely use, improve upon, trust, and extend a standard over time.</li>
-<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>
+<li>The standard is adopted and will be maintained by a not-for-profit
+organisation, and its ongoing development occurs on the basis of an
+open decision-making procedure available to all interested
+parties.</li>
-<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>
+<li>The standard has been published and the standard specification
+document is available freely. It must be permissible to all to copy,
+distribute, and use it freely.</li>
-
-<p>From reading the Bill it will be clear that once passed:<br>
-<li>the law does not forbid the production of proprietary software</li>
-<li>the law does not forbid the sale of proprietary software</li>
-<li>the law does not specify which concrete software to use</li>
-<li>the law does not dictate the supplier from whom software will be bought</li>
-<li>the law does not limit the terms under which a software product can be licensed.</li>
-
-</p>
-
-<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>
-
-<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>
-
-<p>As for the observations you have made, we will now go on to analyze them in detail:</p>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<p>On security:</p>
-
-<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>
-
-<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>
-
-<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>
-
-<p>In respect of the guarantee:</p>
-
-<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>
-
-<p>On Intellectual Property:</p>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<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>
-
-<p>Cordially,<br>
-DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
-Congressman of the Republic of Perú.</p>
-</blockquote>
-
- </div>
- <div class="tags">
-
-
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
-
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2010-12-25 20:25
- </div>
-
- <div class="body">
-
-<p><a href="http://www.digistan.org/open-standard:definition">The
-Digistan definition</a> of a free and open standard reads like this:</p>
-
-<blockquote>
-
-<p>The Digital Standards Organization defines free and open standard
-as follows:</p>
-
-<ol>
-
-<li>A free and open standard is immune to vendor capture at all stages
-in its life-cycle. Immunity from vendor capture makes it possible to
-freely use, improve upon, trust, and extend a standard over time.</li>
-
-<li>The standard is adopted and will be maintained by a not-for-profit
-organisation, and its ongoing development occurs on the basis of an
-open decision-making procedure available to all interested
-parties.</li>
-
-<li>The standard has been published and the standard specification
-document is available freely. It must be permissible to all to copy,
-distribute, and use it freely.</li>
-
-<li>The patents possibly present on (parts of) the standard are made
-irrevocably available on a royalty-free basis.</li>
+<li>The patents possibly present on (parts of) the standard are made
+irrevocably available on a royalty-free basis.</li>
<li>There are no constraints on the re-use of the standard.</li>
<p>It would be nice to see other analysis of other specifications to
see if they are free and open standards.</p>
- </div>
- <div class="tags">
-
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 25th December 2010
+ </div>
+ <div class="body">
+ <p>A few days ago
+<a href="http://www.idg.no/computerworld/article189879.ece">an
+article</a> in the Norwegian Computerworld magazine about how version
+2.0 of
+<a href="http://en.wikipedia.org/wiki/European_Interoperability_Framework">European
+Interoperability Framework</a> has been successfully lobbied by the
+proprietary software industry to remove the focus on free software.
+Nothing very surprising there, given
+<a href="http://news.slashdot.org/story/10/03/29/2115235/Open-Source-Open-Standards-Under-Attack-In-Europe">earlier
+reports</a> on how Microsoft and others have stacked the committees in
+this work. But I find this very sad. The definition of
+<a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">an
+open standard from version 1</a> was very good, and something I
+believe should be used also in the future, alongside
+<a href="http://www.digistan.org/open-standard:definition">the
+definition from Digistan</A>. Version 2 have removed the open
+standard definition from its content.</p>
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>Anyway, the news reminded me of the great reply sent by Dr. Edgar
+Villanueva, congressman in Peru at the time, to Microsoft as a reply
+to Microsofts attack on his proposal regarding the use of free software
+in the public sector in Peru. As the text was not available from a
+few of the URLs where it used to be available, I copy it here from
+<a href="http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html">my
+source</a> to ensure it is available also in the future. Some
+background information about that story is available in
+<a href="http://www.linuxjournal.com/article/6099">an article</a> from
+Linux Journal in 2002.</p>
-<div class="entry">
- <div class="title">
- <a href="http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html">The many definitions of a open standard</a>
- </div>
- <div class="date">
- 2010-12-27 14:45
- </div>
+<blockquote>
+<p>Lima, 8th of April, 2002<br>
+To: Señor JUAN ALBERTO GONZÁLEZ<br>
+General Manager of Microsoft Perú</p>
- <div class="body">
-
-<p>One of the reasons I like the Digistan definition of
-"<a href="http://www.digistan.org/open-standard:definition">Free and
-Open Standard</a>" is that this is a new term, and thus the meaning of
-the term has been decided by Digistan. The term "Open Standard" has
-become so misunderstood that it is no longer very useful when talking
-about standards. One end up discussing which definition is the best
-one and with such frame the only one gaining are the proponents of
-de-facto standards and proprietary solutions.</p>
+<p>Dear Sir:</p>
-<p>But to give us an idea about the diversity of definitions of open
-standards, here are a few that I know about. This list is not
-complete, but can be a starting point for those that want to do a
-complete survey. More definitions are available on the
-<a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
-page</a>.</p>
+<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>
-<p>First off is my favourite, the definition from the European
-Interoperability Framework version 1.0. Really sad to notice that BSA
-and others has succeeded in getting it removed from version 2.0 of the
-framework by stacking the committee drafting the new version with
-their own people. Anyway, the definition is still available and it
-include the key properties needed to make sure everyone can use a
-specification on equal terms.</p>
+<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>
-<blockquote>
+<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>
-<p>The following are the minimal characteristics that a specification
-and its attendant documents must have in order to be considered an
-open standard:</p>
+<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>
+<p>
<ul>
+<li>Free access to public information by the citizen. </li>
+<li>Permanence of public data. </li>
+<li>Security of the State and citizens.</li>
+</ul>
+</p>
-<li>The standard is adopted and will be maintained by a not-for-profit
-organisation, and its ongoing development occurs on the basis of an
-open decision-making procedure available to all interested parties
-(consensus or majority decision etc.).</li>
+<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>
-<li>The standard has been published and the standard specification
-document is available either freely or at a nominal charge. It must be
-permissible to all to copy, distribute and use it for no fee or at a
-nominal fee.</li>
+<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>
-<li>The intellectual property - i.e. patents possibly present - of
-(parts of) the standard is made irrevocably available on a royalty-
-free basis.</li>
+<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>
-<li>There are no constraints on the re-use of the standard.</li>
+<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>
-</ul>
-</blockquote>
+<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>
-<p>Another one originates from my friends over at
-<a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
-support for <a href="http://www.aaben-standard.dk/">this
-definition</a> in 2004. It even made it into the Danish parlament as
-<a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
-definition of a open standard</a>. Another from a different part of
-the Danish government is available from the wikipedia page.</p>
-<blockquote>
+<p>From reading the Bill it will be clear that once passed:<br>
+<li>the law does not forbid the production of proprietary software</li>
+<li>the law does not forbid the sale of proprietary software</li>
+<li>the law does not specify which concrete software to use</li>
+<li>the law does not dictate the supplier from whom software will be bought</li>
+<li>the law does not limit the terms under which a software product can be licensed.</li>
-<p>En åben standard opfylder følgende krav:</p>
+</p>
-<ol>
+<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>
-<li>Veldokumenteret med den fuldstændige specifikation offentligt
-tilgængelig.</li>
+<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>
-<li>Frit implementerbar uden økonomiske, politiske eller juridiske
-begrænsninger på implementation og anvendelse.</li>
+<p>As for the observations you have made, we will now go on to analyze them in detail:</p>
-<li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
-"standardiseringsorganisation") via en åben proces.</li>
+<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>
-</ol>
+<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>
-</blockquote>
+<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>
-<p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
-definition</a> from Free Software Foundation Europe.</p>
+<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>
-<blockquote>
+<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>
-<p>An Open Standard refers to a format or protocol that is</p>
+<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>
-<ol>
+<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>
-<li>subject to full public assessment and use without constraints in a
-manner equally available to all parties;</li>
+<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>
-<li>without any components or extensions that have dependencies on
-formats or protocols that do not meet the definition of an Open
-Standard themselves;</li>
+<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>
-<li>free from legal or technical clauses that limit its utilisation by
-any party or in any business model;</li>
+<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>
-<li>managed and further developed independently of any single vendor
-in a process open to the equal participation of competitors and third
-parties;</li>
+<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>
-<li>available in multiple complete implementations by competing
-vendors, or as a complete implementation equally available to all
-parties.</li>
+<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>
-</ol>
+<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>
-</blockquote>
+<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>
-<p>A long time ago, SUN Microsystems, now bought by Oracle, created
-its
-<a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
-Standards Checklist</a> with a fairly detailed description.</p>
+<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>
-<blockquote>
-<p>Creation and Management of an Open Standard
+<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>
-<ul>
+<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>
-<li>Its development and management process must be collaborative and
- democratic:
+<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>
- <ul>
+<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>
- <li>Participation must be accessible to all those who wish to
- participate and can meet fair and reasonable criteria
- imposed by the organization under which it is developed
- and managed.</li>
+<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>
- <li>The processes must be documented and, through a known
- method, can be changed through input from all
- participants.</li>
+<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>
- <li>The process must be based on formal and binding commitments for
- the disclosure and licensing of intellectual property rights.</li>
+<p>On security:</p>
- <li>Development and management should strive for consensus,
- and an appeals process must be clearly outlined.</li>
+<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>
- <li>The standard specification must be open to extensive
- public review at least once in its life-cycle, with
- comments duly discussed and acted upon, if required.</li>
+<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>
- </ul>
+<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>
-</li>
+<p>In respect of the guarantee:</p>
-</ul>
+<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>
-<p>Use and Licensing of an Open Standard</p>
-<ul>
+<p>On Intellectual Property:</p>
-<li>The standard must describe an interface, not an implementation,
- and the industry must be capable of creating multiple, competing
- implementations to the interface described in the standard without
- undue or restrictive constraints. Interfaces include APIs,
- protocols, schemas, data formats and their encoding.</li>
+<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>
-<li> The standard must not contain any proprietary "hooks" that create
- a technical or economic barriers</li>
+<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>
-<li>Faithful implementations of the standard must
- interoperate. Interoperability means the ability of a computer
- program to communicate and exchange information with other computer
- programs and mutually to use the information which has been
- exchanged. This includes the ability to use, convert, or exchange
- file formats, protocols, schemas, interface information or
- conventions, so as to permit the computer program to work with other
- computer programs and users in all the ways in which they are
- intended to function.</li>
+<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>
-<li>It must be permissible for anyone to copy, distribute and read the
- standard for a nominal fee, or even no fee. If there is a fee, it
- must be low enough to not preclude widespread use.</li>
+<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>
-<li>It must be possible for anyone to obtain free (no royalties or
- fees; also known as "royalty free"), worldwide, non-exclusive and
- perpetual licenses to all essential patent claims to make, use and
- sell products based on the standard. The only exceptions are
- terminations per the reciprocity and defensive suspension terms
- outlined below. Essential patent claims include pending, unpublished
- patents, published patents, and patent applications. The license is
- only for the exact scope of the standard in question.
+<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>
- <ul>
+<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>
- <li> May be conditioned only on reciprocal licenses to any of
- licensees' patent claims essential to practice that standard
- (also known as a reciprocity clause)</li>
+<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>
- <li> May be terminated as to any licensee who sues the licensor
- or any other licensee for infringement of patent claims
- essential to practice that standard (also known as a
- "defensive suspension" clause)</li>
+<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>
- <li> The same licensing terms are available to every potential
- licensor</li>
+<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>
- </ul>
-</li>
+<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>
-<li>The licensing terms of an open standards must not preclude
- implementations of that standard under open source licensing terms
- or restricted licensing terms</li>
+<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>
-</ul>
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+
+<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>
+<p>Cordially,<br>
+DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
+Congressman of the Republic of Perú.</p>
</blockquote>
-<p>It is said that one of the nice things about standards is that
-there are so many of them. As you can see, the same holds true for
-open standard definitions. Most of the definitions have a lot in
-common, and it is not really controversial what properties a open
-standard should have, but the diversity of definitions have made it
-possible for those that want to avoid a level marked field and real
-competition to downplay the significance of open standards. I hope we
-can turn this tide by focusing on the advantages of Free and Open
-Standards.</p>
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html">Officeshots still going strong</a>
+ </div>
+ <div class="date">
+ 25th December 2010
+ </div>
+ <div class="body">
+ <p>Half a year ago I
+<a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">wrote
+a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
+a web service to allow anyone to test how ODF documents are handled by
+the different programs reading and writing the ODF format.</p>
+
+<p>I just had a look at the service, and it seem to be going strong.
+Very interesting to see the results reported in the gallery, how
+different Office implementations handle different ODF features. Sad
+to see that KOffice was not doing it very well, and happy to see that
+LibreOffice has been tested already (but sadly not listed as a option
+for OfficeShots users yet). I am glad to see that the ODF community
+got such a great test tool available.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 30th October 2010
+ </div>
+ <div class="body">
+ <p>I dag la jeg inn en kommentar på en sak hos NRKBeta
+<a href="http://nrkbeta.no/2010/10/27/bakom-blindpassasjer-del-1/">om
+hvordan TV-serien Blindpassasjer ble laget</a> i forbindelse med at
+filmene NRK la ut ikke var tilgjengelig i et
+<a href="http://www.digistan.org/open-standard:definition">fritt og
+åpent format</a>. Dette var det jeg skrev publiserte der 07:39.</p>
+
+<p><blockquote>
+<p>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
+nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
+som dette, vet at det stort sett er mulig å lure ut ting med den
+nødvendige forkunnskapen."</p>
+
+<p>Haha. Å streame innhold er det samme som å laste ned innhold, så å
+beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
+er å forlede leseren.</p>
+
+<p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
+vil tillate streaming men ikke nedlasting meningsløs.</p>
+
+<p>Anbefaler forresten å lese
+<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>
+om hva som ville være konsekvensen hvis digitale avspillingssperrer
+(DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
+derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
+men det er skremmende hva samfunnet tillater og NRK er med på å bygge
+opp under.</p>
+</blockquote></p>
+
+<p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
+NRKBeta:</p>
+
+<p><blockquote>
+<p>From: Anders Hofseth <XXX@gmail.com>
+<br>To: "pere@hungry.com" <pere@hungry.com>
+<br>Cc: Eirik Solheim <XXX@gmail.com>, Jon Ståle Carlsen <XXX@gmail.com>, Henrik Lied <XXX@gmail.com>
+<br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
+<br>Date: Sat, 30 Oct 2010 07:58:44 +0200</p>
+
+<p>Hei Petter.
+<br>Det du forsøker dra igang er egentlig en interessant diskusjon,
+men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
+om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
+særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
+
+<p>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
+fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
+konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
+
+<p>Med hilsen,
+<br>-anders</p>
+
+<p>Ring meg om noe er uklart: 95XXXXXXX</p>
+</blockquote></p>
+
+<p>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
+over følgende svar. I og med at debatten er fjernet fra NRK Betas
+kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
+Har fjernet epostadresser og telefonnummer til de involverte, for å
+unngå at de tiltrekker seg uønskede direkte kontaktforsøk.</p>
+
+<p><blockquote>
+<p>From: Petter Reinholdtsen <pere@hungry.com>
+<br>To: Anders Hofseth <XXX@gmail.com>
+<br>Cc: Eirik Solheim <XXX@gmail.com>,
+<br> Jon Ståle Carlsen <XXX@gmail.com>,
+<br> Henrik Lied <XXX@gmail.com>
+<br>Subject: Re: [NRKbeta] Kommentar: "Bakom Blindpassasjer: del 1"
+<br>Date: Sat, 30 Oct 2010 08:24:34 +0200</p>
+
+<p>[Anders Hofseth]
+<br>> Hei Petter.</p>
+
+<p>Hei.</p>
+
+<p>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
+<br>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
+<br>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
+<br>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.</p>
+
+<p>Godt å se at du er enig i at dette er en interessant diskusjon. Den
+vil nok fortsette en stund til. :)</p>
+
+<p>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
+vitende og vilje ønsker å forlede rettighetshaverne for å kunne
+fortsette å legge ut arkivmateriale.</p>
+
+<p>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
+faktum, som er at streaming er det samme som nedlasting, og at innhold
+som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
+det.</p>
+
+<p>Det du sier er jo at klarering av arkivmateriale for publisering på
+web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
+Det er ikke et argument som holder vann. :)</p>
+
+<p>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
+<br>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
+<br>> konsekvensene vi beskriver ikke er noe du ønsker heller...</p>
+
+<p>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
+heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
+mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
+godtar å forlede publikum. Ville heller at NRK krever at innhold som
+skal sendes skal være uten bruksbegresninger og kan publiseres i
+formater som heller ikke har bruksbegresninger (bruksbegresningene til
+H.264 burde få varselbjellene i NRK til å ringe).</p>
+
+<p>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
+påstander om at "streaming beskytter mot nedlasting" som bare er egnet
+til å bygge opp om en myte som er skadelig for samfunnet som helhet.</p>
+
+<p>Anbefaler <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
+titt på
+<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> >.
+for å se hva slags bruksbegresninger H.264 innebærer.</p>
+
+<p>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
+kan brukes før rettighetshaverene også innser at de er med på å skade
+samfunnets kultur og kollektive hukommelse, så får en i hvert fall
+synliggjort konsekvensene og antagelig mer flammer på en debatt som er
+langt på overtid.</p>
+
+<p>> Ring meg om noe er uklart: XXX</p>
+
+<p>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
+Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
+gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
+for videre diskusjon hadde dere i mine øyne kommet fra det med
+ryggraden på plass.</p>
+
+<p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
+
+<p>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
+<URL: <a href="http://www.archive.org/details/CopyingIsNotTheft">http://www.archive.org/details/CopyingIsNotTheft</a> > og
+<URL: <a href="http://patentabsurdity.com/">http://patentabsurdity.com/</a> > hadde vært noe å kringkaste på
+NRK1. :)</p>
+
+<p>Vennlig hilsen,
+<br>--
+<br>Petter Reinholdtsen</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html">Standardkrav inn i anbudstekster?</a>
+ </div>
+ <div class="date">
+ 17th October 2010
+ </div>
+ <div class="body">
+ <p>Hvis det å følge standarder skal ha noen effekt overfor
+leverandører, så må slike krav og ønsker komme inn i anbudstekster når
+systemer kjøpes inn. Har ikke sett noen slike formuleringer i anbud
+så langt, men har tenkt litt på hva som bør inn. Her er noen ideer og
+forslag. Min drøm er at en kan sette krav til slik støtte i
+anbudstekster, men så langt er det nok mer sannsynlig at en må nøye
+seg med å skrive at det er en fordel om slik støtte er tilstede i
+leveranser.</p>
+
+<p>Som systemadministrator på Universitetet er det typisk to områder
+som er problematiske for meg. Det ene er admin-grensesnittene på
+tjenermaskiner, som vi ønsker å bruke via ssh. Det andre er nettsider
+som vi ønsker å bruke via en nettleser. For begge deler er det viktig
+at protokollene og formatene som brukes følger standarder våre verktøy
+støtter.</p>
+
+<p>De fleste har nå støtte for SSH som overføringsprotkoll for
+admin-grensesnittet, men det er ikke tilstrekkelig for å kunne stille
+inn f.eks BIOS og RAID-kontroller via ssh-forbindelsen. Det er flere
+aktuelle protokoller for fremvisning av BIOS-oppsett og
+oppstartmeldinger, og min anbefaling ville være å kreve
+VT100-kompatibel protokoll, for å sikre at flest mulig
+terminalemulatorer kan forstå hva som kommer fra admin-grensesnittet
+via ssh. Andre aktuelle alternativer er ANSI-terminalemulering og
+VT220. Kanskje en formulering ala dette i anbudsutlysninger vil
+fungere:</p>
+
+<p><blockquote>
+BIOS og oppstartmeldinger i administrasjonsgrensesnittet til maskinen
+bør/skal være tilgjengelig via SSH-protokollen som definert av IETF
+(RFC 4251 mfl.) og følge terminalfremvisningprotokollen VT100 (ref?)
+når en kobler seg til oppstart via ssh.
+</blockquote></p>
+
+<p>Har ikke lykkes med å finne en god referanse for
+VT100-spesifikasjonen.</p>
+
+<p>Når det gjelder nettsider, så er det det HTML, CSS og
+JavaScript-spesifikasjonen til W3C som gjelder.</p>
+
+<p><blockquote>
+Alle systemets nettsider bør/skal være i henhold til statens
+standardkatalogs krav om nettsider og følge HTML-standarden som
+definert av W3C, og validere uten feil hos W3Cs HTML-validator
+(http://validator.w3.org). Hvis det brukes CSS så bør/skal denne
+validere uten feil hos W3Cs CSS-validator
+(http://jigsaw.w3.org/css-validator/). Eventuelle JavaScript skal
+være i henhold til EcmaScript-standarden. I tillegg til å følge de
+overnevnte standardene skal websidene fungere i nettleserne (fyll inn
+relevant liste for organisasjonen) Firefox 3.5, Internet Explorer 8,
+Opera 9, etc.
+</blockquote></p>
+
+<p>Vil et slikt avsnitt være konkret nok til å få leverandørene til å
+lage nettsider som følger standardene og fungerer i flere
+nettlesere?</p>
+
+<p>Tar svært gjerne imot innspill på dette temaet til aktive (at)
+nuug.no, og er spesielt interessert i hva andre skriver i sine anbud
+for å oppmuntre leverandører til å følge standardene. Kanskje NUUG
+burde lage et dokument med forslag til standardformuleringer å ta med
+i anbudsutlysninger?</p>
+
+<p>Oppdatering 2010-12-03: I følge Wikipedias oppføring om
+<a href="http://en.wikipedia.org/wiki/ANSI_escape_code">ANSI escape
+code</a>, så bruker VT100-terminaler ECMA-48-spesifikasjonen som
+basis for sin oppførsel. Det kan dermed være et alternativ når en
+skal spesifisere hvordan seriell-konsoll skal fungere.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 9th September 2010
+ </div>
+ <div class="body">
+ <p>A few days ago I had the mixed pleasure of bying a new digital
+camera, a Canon IXUS 130. It was instructive and very disturbing to
+be able to verify that also this camera producer have the nerve to
+specify how I can or can not use the videos produced with the camera.
+Even thought I was aware of the issue, the options with new cameras
+are limited and I ended up bying the camera anyway. What is the
+problem, you might ask? It is software patents, MPEG-4, H.264 and the
+MPEG-LA that is the problem, and our right to record our experiences
+without asking for permissions that is at risk.
+
+<p>On page 27 of the Danish instruction manual, this section is
+written:</p>
+
+<blockquote>
+<p>This product is licensed under AT&T patents for the MPEG-4 standard
+and may be used for encoding MPEG-4 compliant video and/or decoding
+MPEG-4 compliant video that was encoded only (1) for a personal and
+non-commercial purpose or (2) by a video provider licensed under the
+AT&T patents to provide MPEG-4 compliant video.</p>
+
+<p>No license is granted or implied for any other use for MPEG-4
+standard.</p>
+</blockquote>
+
+<p>In short, the camera producer have chosen to use technology
+(MPEG-4/H.264) that is only provided if I used it for personal and
+non-commercial purposes, or ask for permission from the organisations
+holding the knowledge monopoly (patent) for technology used.</p>
+
+<p>This issue has been brewing for a while, and I recommend you to
+read
+"<a href="http://www.osnews.com/story/23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA">Why
+Our Civilization's Video Art and Culture is Threatened by the
+MPEG-LA</a>" by Eugenia Loli-Queru and
+"<a href="http://webmink.com/2010/09/03/h-264-and-foss/">H.264 Is Not
+The Sort Of Free That Matters</a>" by Simon Phipps to learn more about
+the issue. The solution is to support the
+<a href="http://www.digistan.org/open-standard:definition">free and
+open standards</a> for video, like <a href="http://www.theora.org/">Ogg
+Theora</a>, and avoid MPEG-4 and H.264 if you can.</p>
+
+ </div>
+ <div class="tags">
+
+
+ Tags: <a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">Officeshots taking shape</a>
+ </div>
+ <div class="date">
+ 13th June 2010
+ </div>
+ <div class="body">
+ <p>For those of us caring about document exchange and
+interoperability, <a href="http://www.officeshots.org/">OfficeShots</a>
+is a great service. It is to ODF documents what
+<a href="http://browsershots.org/">BrowserShots</a> is for web
+pages.</p>
+
+<p>A while back, I was contacted by Knut Yrvin at the part of Nokia
+that used to be Trolltech, who wanted to help the OfficeShots project
+and wondered if the University of Oslo where I work would be
+interested in supporting the project. I helped him to navigate his
+request to the right people at work, and his request was answered with
+a spot in the machine room with power and network connected, and Knut
+arranged funding for a machine to fill the spot. The machine is
+administrated by the OfficeShots people, so I do not have daily
+contact with its progress, and thus from time to time check back to
+see how the project is doing.</p>
+
+<p>Today I had a look, and was happy to see that the Dell box in our
+machine room now is the host for several virtual machines running as
+OfficeShots factories, and the project is able to render ODF documents
+in 17 different document processing implementation on Linux and
+Windows. This is great.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html">A manual for standards wars...</a>
+ </div>
+ <div class="date">
+ 6th June 2010
+ </div>
+ <div class="body">
+ <p>Via the
+<a href="http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html">blog
+of Rob Weir</a> I came across the very interesting essay named
+<a href="http://faculty.haas.berkeley.edu/shapiro/wars.pdf">The Art of
+Standards Wars</a> (PDF 25 pages). I recommend it for everyone
+following the standards wars of today.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Danmark_g_r_for_ODF_.html">Danmark går for ODF?</a>
+ </div>
+ <div class="date">
+ 29th January 2010
+ </div>
+ <div class="body">
+ <p>Ble nettopp gjort oppmerksom på en
+<a href="http://www.version2.dk/artikel/13690-breaking-odf-vinder-dokumentformat-krigen ">nyhet fra Version2</a>
+fra Danmark, der det hevdes at Folketinget har vedtatt at ODF skal
+brukes som dokumentutvekslingsformat i Staten.</p>
+
+<p>Hyggelig lesning, spesielt hvis det viser seg at de av vedtatt
+kravlisten for hva som skal aksepteres som referert i kommentarfeltet
+til artikkelen og
+<a href="http://www.version2.dk/artikel/13693-er-ooxml-doemt-ude-her-er-kravene-til-en-offentlig-dokumentstandard">en
+annen artikkel</a> i samme nett-avis. Liker spesielt godt denne:</p>
+
+<p><blockquote> Det skal demonstreres, at standarden i sin helhed kan
+implementeres af alle direkte i sin helhed på flere
+platforme.</blockquote></p>
+
+<p>Noe slikt burde være et krav også i Norge.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 12th August 2009
+ </div>
+ <div class="body">
+ <p>Just for fun, I did a search right now on Google for a few file ODF
+and MS Office based formats (not to be mistaken for ISO or ECMA
+OOXML), to get an idea of their relative usage. I searched using
+'filetype:odt' and equvalent terms, and got these results:</P>
+
+<table>
+<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
+<tr><td>Tekst</td> <td>odt:282000</td> <td>docx:308000</td></tr>
+<tr><td>Presentasjon</td> <td>odp:75600</td> <td>pptx:183000</td></tr>
+<tr><td>Regneark</td> <td>ods:26500 </td> <td>xlsx:145000</td></tr>
+</table>
+
+<p>Next, I added a 'site:no' limit to get the numbers for Norway, and
+got these numbers:</p>
+
+<table>
+<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
+<tr><td>Tekst</td> <td>odt:2480 </td> <td>docx:4460</td></tr>
+<tr><td>Presentasjon</td> <td>odp:299 </td> <td>pptx:741</td></tr>
+<tr><td>Regneark</td> <td>ods:187 </td> <td>xlsx:372</td></tr>
+</table>
+
+<p>I wonder how these numbers change over time.</p>
+
+<p>I am aware of Google returning different results and numbers based
+on where the search is done, so I guess these numbers will differ if
+they are conduced in another country. Because of this, I did the same
+search from a machine in California, USA, a few minutes after the
+search done from a machine here in Norway.</p>
+
+
+<table>
+<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
+<tr><td>Tekst</td> <td>odt:129000</td> <td>docx:308000</td></tr>
+<tr><td>Presentasjon</td> <td>odp:44200</td> <td>pptx:93900</td></tr>
+<tr><td>Regneark</td> <td>ods:26500 </td> <td>xlsx:82400</td></tr>
+</table>
+
+<p>And with 'site:no':
+
+<table>
+<tr><th>Type</th><th>ODF</th><th>MS Office</th></tr>
+<tr><td>Tekst</td> <td>odt:2480</td> <td>docx:3410</td></tr>
+<tr><td>Presentasjon</td> <td>odp:175</td> <td>pptx:604</td></tr>
+<tr><td>Regneark</td> <td>ods:186 </td> <td>xlsx:296</td></tr>
+</table>
+
+<p>Interesting difference, not sure what to conclude from these
+numbers.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/ISO_still_hope_to_fix_OOXML.html">ISO still hope to fix OOXML</a>
+ </div>
+ <div class="date">
+ 8th August 2009
+ </div>
+ <div class="body">
+ <p>According to <a
+href="http://twerner.blogspot.com/2009/08/defects-of-office-open-xml.html">a
+blog post from Torsten Werner</a>, the current defect report for ISO
+29500 (ISO OOXML) is 809 pages. His interesting point is that the
+defect report is 71 pages more than the full ODF 1.1 specification.
+Personally I find it more interesting that ISO still believe ISO OOXML
+can be fixed in ISO. Personally, I believe it is broken beyon repair,
+and I completely lack any trust in ISO for being able to get anywhere
+close to solving the problems. I was part of the Norwegian committee
+involved in the OOXML fast track process, and was not impressed with
+Standard Norway and ISO in how they handled it.</p>
+
+<p>These days I focus on ODF instead, which seem like a specification
+with the future ahead of it. We are working in NUUG to organise a ODF
+seminar this autumn.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 9th July 2009
+ </div>
+ <div class="body">
+ <p>For å forstå mer om hvorfor standardkatalogens versjon 2 ble som
+den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
+for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
+wiki, direkte tilgjengelig via "<a
+href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon.pdf">Referansekatalogen
+v2.0 - Oppsummering av høring</a>" og "<a
+href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2?action=AttachFile&do=get&target=kongelig-resolusjon-katalogutkast.pdf">Referansekatalog
+for IT-standarder i offentlig sektor Versjon 2.0, dd.mm.åååå -
+UTKAST</a>".</p>
+
+<p>Det er tre ting jeg merker meg i oppsummeringen fra
+høringsuttalelsen da jeg skummet igjennom den. Det første er at
+forståelsen av hvordan programvarepatenter påvirker fri
+programvareutvikling også i Norge når en argumenterer med at
+royalty-betaling ikke er et relevant problem i Norge. Det andre er at
+FAD ikke har en prinsipiell forståelse av verdien av en enkelt
+standard innenfor hvert område. Det siste er at påstander i
+høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
+Microsoft om hvordan Ogg blir standardisert og påstanden fra
+politidirektoratet om patentproblemer i Theora).</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 6th July 2009
+ </div>
+ <div class="body">
+ <p>Jeg ble glad da regjeringen
+<a href="http://www.digi.no/817635/her-er-statens-nye-it-standarder">annonserte</a>
+versjon 2 av
+<a href="http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf">statens
+referansekatalog over standarder</a>, men trist da jeg leste hva som
+faktisk var vedtatt etter
+<a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html">høringen</a>.
+De fleste av de valgte åpne standardene er gode og vil bidra til at
+alle kan delta på like vilkår i å lage løsninger for staten, men
+noen av dem blokkerer for de som ikke har anledning til å benytte
+spesifikasjoner som krever betaling for bruk (såkalt
+royalty-betaling). Det gjelder spesifikt for H.264 for video og MP3
+for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
+Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
+fra statens websider gjøre dette uten å måtte bruke programmer der
+betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
+de statlige etatene å bruke enten H.264 eller Theora (og MP3 eler
+Vorbis), så vil en bli tvunget til å forholde seg til
+royalty-belastede standarder for å få tilgang til videoen og
+lyden.</p>
+
+<p>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
+at alle standarder som ble valgt til å være påkrevd i katalogen skulle
+være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
+all forståelse for hvilke prinsipper som må følges for å oppnå
+likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
+mot dette i
+<a href="http://wiki.nuug.no/uttalelser/200901-standardkatalog-v2">sin
+høringsuttalelse</a>, men ser ut til å ha blitt ignorert.</p>
+
+<p>Oppdatering 2012-06-29: Kom over <ahref="
+http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf">en
+rapport til FAD</a> fra da versjon 1 av katalogen ble vedtatt, og der
+er det tydelig at problemstillingen var kjent og forstått.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html">Microsofts misvisende argumentasjon rundt multimediaformater</a>
+ </div>
+ <div class="date">
+ 26th June 2009
+ </div>
+ <div class="body">
+ <p>I
+<a href="http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf">Microsoft
+sin høringsuttalelse</a> til
+<a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2.html?id=549422">forslag
+til versjon 2 av statens referansekatalog over standarder</a>, lirer
+de av seg følgende FUD-perle:</p>
+
+<p><blockquote>"Vorbis, OGG, Theora og FLAC er alle tekniske
+ spesifikasjoner overordnet styrt av xiph.org, som er en
+ ikke-kommersiell organisasjon. Etablerte og anerkjente
+ standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
+ innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
+ Det er derimot helt opp til hver enkelt organisasjon å bestemme
+ hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
+ spesifikasjonene bør derfor ikke defineres som åpne
+ standarder."</blockquote></p>
+
+<p>De vokter seg vel for å nevne den anerkjente
+standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
+IP og det meste av protokoller på Internet, og RFC-standardene som
+IETF står bak. Ogg er spesifisert i
+<a href="http://ietf.org/rfc/rfc3533.txt">RFC 3533</a>, og er uten
+tvil å anse som en åpen standard. Vorbis er
+<a href="http://ietf.org/rfc/rfc5215.txt">RFC 5215</a>. Theora er
+
+under standardisering via IETF, med
+<a href="http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-00.txt">siste
+utkast publisert 2006-07-21</a> (riktignok er dermed teksten ikke
+skrevet i stein ennå, men det blir neppe endringer som ikke er
+bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
+jeg ikke finner tegn til at <a
+href="http://flac.sourceforge.net/format.html">spesifikasjonen
+tilgjengelig på web</a> er på tur via noen
+standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
+og Vorbis også har involvert seg i Flac siden 2003, så ser jeg ikke
+bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
+til FLAC.</p>
+
+<p>Uredelig argumentasjon bør en holde seg for god til å komme med,
+spesielt når det er så enkelt i dagens Internet-hverdag å gå
+misvisende påstander etter i sømmene.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 19th May 2009
+ </div>
+ <div class="body">
+ <p>En standard er noe man samler seg rundt, ut fra ideen om at en får
+fordeler når mange står sammen. Jo flere som står sammen, jo
+bedre. Når en vet dette, blir det litt merkelig å lese noen av
+uttalelsene som er kommet inn til
+<a href="http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/2009/horing---referansekatalog-versjon-2/horingsuttalelser.html?id=549423">høringen
+om versjon 2 av statens referansekatalog over standarder</a>. Blant
+annet Abelia, NHO og Microsoft tror det er lurt med flere standarder
+innenfor samme område. Det blir som å si at det er fint om Norge
+standardiserte både på A4- og Letter-størrelser på arkene, ulik
+sporvidde på jernbaneskinnene, meter og fot som lengemål, eller
+høyre- og venstrekjøring - slik at en kan konkurrere på hvilken
+standard som er best. De fleste forstår heldigvis at dette ikke
+bidrar positivt.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Hvorfor_jeg_ikke_bruker_eFaktura.html">Hvorfor jeg ikke bruker eFaktura</a>
+ </div>
+ <div class="date">
+ 23rd April 2009
+ </div>
+ <div class="body">
+ <p>Telenors annonsering om å kreve 35 kroner i gebyr fra alle som
+ønsker papirfaktura har satt sinnene i kok, og pressedekningen så
+langt snakker om at eldre og folk som ikke behersker data vil få en
+urimelig ekstrakostnad. Jeg tror ikke jeg passer inn i noen av de
+kategoriene, men velger å holde meg unna eFaktura - som er det
+Telenor ønsker å få folk over på - pga. systemets egenskaper.</p>
+
+<p>Slik jeg har sett eFaktura til forbrukere så langt, så sender
+selger en elektronisk beskjed til kundens bank, som legger ut
+informasjon om fakturaen i nettbanken for godkjenning. Personlig
+ville jeg sett det som mer naturlig at det gikk en elektronisk beskjed
+fra selger til kunde, dvs meg, og at jeg så kunne bruke den videre
+mot banken eller andre hvis jeg ønsket dette. Mine innkjøp og
+regninger er jo en sak mellom meg og mine leverandører, ikke en sak
+mellom min bank og mine leverandører. Kun hvis jeg ønsker å betale
+fakturaen skal banken involveres. En faktura bør jo inn i
+regnskapet, og jeg ønsker mulighet til å legge det inn der. Når
+fakturaen sendes til banken i stedet for meg, blir det vanskeligere.
+Hele eFaktura-modellen virker på meg som en umyndiggjøring av meg
+som kunde.</p>
+
+<p>I tillegg har jeg ikke vært i stand til å finne
+eFaktura-formatets spesifikasjon, og det ser ut til at utsending av
+slike krever dyre avtaler med bankene for å få lov til å sende ut
+eFaktura til kunder. Jeg ser vel helst at fakturering på
+elektroniske formater kan gjøres f.eks. via epost eller HTTP uten å
+måtte betale mellommenn for retten til å lever ut en faktura, og
+liker rett og slett ikke dagens faktureringsmodeller.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 30th March 2009
+ </div>
+ <div class="body">
+ <p>Where I work at the University of Oslo, one decision stand out as a
+very good one to form a long lived computer infrastructure. It is the
+simple one, lost by many in todays computer industry: Standardize on
+open network protocols and open exchange/storage formats, not applications.
+Applications come and go, while protocols and files tend to stay, and
+thus one want to make it easy to change application and vendor, while
+avoiding conversion costs and locking users to a specific platform or
+application.</p>
+
+<p>This approach make it possible to replace the client applications
+independently of the server applications. One can even allow users to
+use several different applications as long as they handle the selected
+protocol and format. In the normal case, only one client application
+is recommended and users only get help if they choose to use this
+application, but those that want to deviate from the easy path are not
+blocked from doing so.</p>
+
+<p>It also allow us to replace the server side without forcing the
+users to replace their applications, and thus allow us to select the
+best server implementation at any moment, when scale and resouce
+requirements change.</p>
+
+<p>I strongly recommend standardizing - on open network protocols and
+open formats, but I would never recommend standardizing on a single
+application that do not use open network protocol or open formats.</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <a href="http://people.skolelinux.org/pere/blog/Hva_er_egentlig_en__pen_standard_.html">Hva er egentlig en åpen standard?</a>
+ </div>
+ <div class="date">
+ 28th March 2009
+ </div>
+ <div class="body">
+ <p>Jeg møter alle slags interessante mennesker på min vei, og et møte
+jeg lærte mye av var å treffe på en svært kompetent IT-fyr som
+benektet ting jeg anser som åpenbart og selvfølgelig når det gjelder
+standarder. Det var interessant, da det fikk meg til å tenke litt
+nøyere på hvilke mekanismer som ligger til grunn for at noe oppfattes
+som en standard. Det hele startet med arbeid rundt integrering av NSS
+LDAP mot Active Directory, og problemer som oppstår pga. at Active
+Directory ikke følger LDAP-spesifikasjonen som dokumentert i RFCer fra
+IETF (konkret, AD returnerer kun et subset av attributter hvis det er
+mer enn 1500 atributter av en gitt type i et LDAP-objekt, og en må be
+om resten i bolker av 1500). Jeg hevdet måten dette ble gjort på brøt
+med LDAP-spesifikasjonen, og henviste til hvor i LDAP-spesifikasjonen
+fra IETF det sto at oppførselen til AD ikke fulgte
+LDAP-spesifikasjonen. AD-spesialisten overrasket meg da ved å
+fortelle at IETF var ikke de som definerte LDAP-spesifikasjonen, og at
+Active Directory ikke brøt den virkelige LDAP-spesifikasjonen som han
+mente lå til grunn. Jeg ble spesielt overrasket over denne
+tilnærmingen til problemstillingen, da til og med Microsoft så vidt
+jeg kan se anerkjenner IETF som organisasjonen som definerer
+LDAP-spesifikasjonen. Jeg fikk aldri spurt hvem han mente sto bak den
+egentlige LDAP-spesifikasjonen, da det var irrelevant for problemet vi
+måtte løse (få Linux og AD til å fungere sammen). Dette møtet
+fortalte meg uansett at det ikke er gitt at alle aktører er enige om
+hva en standard er, og hva som er kilden til en gitt standard. Det er
+vanskelig å enes om felles standarder før en først enes om hvem som
+bestemmer hva en gitt standard innebærer.</p>
- </div>
- <div class="tags">
-
+<p>Hva er så en standard? I sin abstrakte form er det noe å samles
+om. På engelsk er en av betydningene fane brukt i krig, du vet, den
+type fane en samlet seg rundt på kamplassen i riddertiden. En
+standard definerer altså et felleskap, noen som har noe felles. Det
+er naturligvis mange måter å utgjøre et felleskap på. En kan
+f.eks. enes om å gjøre alt slik som Ole gjør det, og dermed si at Oles
+oppførsel er standard. Hver gang Ole endrer oppførsel endrer også
+standarden seg uten noe mer organisering og prosedyre. En variant av
+dette er å gjøre slik som Ole har gjort det i stedet for slik Ole til
+enhver til gjør noe. Dette er ofte litt enklere å forholde seg til,
+da en slipper å sjekke med Ole hver gang for å vite hvordan ting skal
+gjøres nå, men hvis det Ole gjorde noe dumt den gang en bestemte seg
+for å følge Ole, så er det vanskeligere å få endret oppførsel for å
+unngå dette dumme.</p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>En kan også ta det et skritt videre, og istedet for å basere seg på
+enkeltpersoners oppførsel sette seg ned og bli enige om hvordan en
+skal gjøre ting, dvs. lage et felleskap basert på konsensus. Dette
+tar naturligvis litt mer tid (en må diskutere ting i forkant før en
+kan sette igang), men det kan bidra til at den oppførselen en
+planlegger å benytte seg av er mer gjennomtenkt. Det ender også
+typisk opp med en beskrivelse av ønsket oppførsel som flere kan forstå
+- da flere har vært involvert i å utarbeide beskrivelsen.</p>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2010-12-30 23:15
- </div>
+<p>Dette er dessverre ikke alt som trengs for å forstå hva en åpen
+standard er for noe. Der alle kan se på hvordan folk oppfører seg, og
+dermed har valget om de vil oppføre seg likt eller ikke, så er det
+endel juridiske faktorer som gjør det hele mer komplisert -
+opphavsretten og patentlovgivningen for å være helt konkret. For å gi
+et eksempel. Hvis noen blir enige om å alltid plystre en bestemt
+melodi når de møtes, for å identifisere hverandre, så kan
+opphavsretten brukes til å styre hvem som får lov til å gjøre dette.
+De har standardisert hvordan de kjenner igjen alle som følger denne
+standarden, men ikke alle har nødvendigvis lov til å følge den.
+Musikk er opphavsrettsbeskyttet, og fremføring av musikk i
+offentligheten er opphavsmannens enerett (dvs. et monopol). Det vil i
+sin ytterste konsekvens si at alle som skal plystre en
+opphavsrettsbeskyttet melodi i det offentlige rom må ha godkjenning
+fra opphavsmannen. Har en ikke dette, så bryter en loven og kan
+straffes. Det er dermed mulig for opphavsmannen å kontrollere hvem
+som får lov til å benytte seg av denne standarden. En annen variant
+er hvis en standard er dokumentert, så er dokumentet som definerer
+standarden (spesifikasjonen) beskyttet av opphavsretten, og det er
+dermed mulig for rettighetsinnehaver å begrense tilgang til
+spesifikasjonen, og slik styre hvem som kan ta i bruk standarden på
+den måten.</p>
- <div class="body">
-
-<p>After trying to
-<a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
-Ogg Theora</a> to
-<a href="http://www.digistan.org/open-standard:definition">the Digistan
-definition</a> of a free and open standard, I concluded that this need
-to be done for more standards and started on a framework for doing
-this. As a start, I want to get the status for all the standards in
-the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
-JPEG, PNG, SVG and others. But to be able to complete this in a
-reasonable time frame, I will need help.</p>
+<p>Der opphavsretten innvilger et monopol på kunstneriske uttrykk med
+verkshøyde, innvilger patentlovgivningen monopol på ideer. Hvis en
+slik patentert idé (fortrinnsvis uttrykt i en teknisk innretning, men
+det er kompliserende faktorer som gjør at det ikke er et krav) trengs
+for å ta i bruk en standard, så vil den som innehar patent kunne styre
+hvem som får ta i bruk standarden. Det er dermed ikke gitt at alle
+kan delta i et standard-felleskap, og hvis de kan delta, så er det
+ikke sikkert at det er på like vilkår. F.eks. kan rettighetsinnehaver
+sette vilkår som gjør at noen faller utenfor, det være seg av
+finansielle, avtalemessige eller prinsipielle årsaker. Vanlige slike
+vilkår er "må betale litt for hver kunde/bruker" som utelukker de som
+gir bort en løsning gratis og "må gi fra seg retten til å håndheve
+sine egne patentrettigheter ovenfor rettighetshaver" som utelukker
+alle som ønsker å beholde den muligheten.</p>
-<p>If you want to help out with this work, please visit
-<a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
-wiki pages I have set up for this</a>, and let me know that you want
-to help out. The IRC channel #nuug on irc.freenode.net is a good
-place to coordinate this for now, as it is the IRC channel for the
-NUUG association where I have created the framework (I am the leader
-of the Norwegian Unix User Group).</p>
+<p>En åpen standard innebærer for meg at alle kan få innsikt i en
+komplett beskrivelse av oppførsel som standarden skal dekke, og at
+ingen kan nektes å benytte seg av standarden. Noen mener at det
+holder at alle med tilstrekkelig finansiering kan få tilgang til
+spesifikasjonen og at en kun har finansielle krav til bruk.
+Pga. denne konflikten har et nytt begrep spredt seg de siste årene,
+nemlig fri og åpen standard, der en har gjort det klart at alle må ha
+komplett og lik tilgang til spesifikasjoner og retten til å gjøre bruk
+av en standard for at en standard skal kunne kalles fri og åpen.</p>
-<p>The framework is still forming, and a lot is left to do. Do not be
-scared by the sketchy form of the current pages. :)</p>
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 31st January 2009
+ </div>
+ <div class="body">
+ <p>Det er mange ulike definisjoner om hva en åpen standard er for noe,
+og NUUG hadde <a href="http://www.nuug.no/dokumenter/standard-presse-def-200506.txt">en
+pressemelding om dette sommeren 2005</a>. Der ble definisjonen til
+<a href="http://www.aaben-standard.dk/">DKUUG</a>,
+<a href="http://europa.eu.int/idabc/servlets/Doc?id=19529">EU-kommissionens
+European Interoperability Framework ( side 9)</a> og
+<a href="http://www.teknologiradet.no/files/7polert_copy.htm">teknologirådet</a> omtalt.</p>
+
+<p>Siden den gang har regjeringens standardiseringsråd dukket opp, og de
+ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
+<a href="http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=476407">sin
+arbeidsmetodikk</a>. Personlig synes jeg det er en god ide, da
+kravene som stilles der gjør at alle markedsaktører får like vilkår,
+noe som kommer kundene til gode ved hjelp av økt konkurranse.</p>
+
+<p>I sommer kom det en ny definisjon på banen.
+<a href="http://www.digistan.org/">Digistan</a> lanserte
+<a href="http://www.digistan.org/open-standard:definition">en
+definisjon på en fri og åpen standard</a>. Jeg liker måten de bryter
+ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
+ved å legge på et ord og poengtere at en standard som er både åpen og
+fri har noen spesielle krav. Her er den definisjonen etter rask
+oversettelse fra engelsk til norsk av meg:</p>
- </div>
- <div class="tags">
-
+<blockquote>
+<p><strong>Definisjonen av en fri og åpen standard</strong></p>
-
- 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>.
-
- </div>
-</div>
-<div class="padding"></div>
+<p>Den digitale standardorganisasjonen definierer fri og åpen standard
+som følger:</p>
+<ul>
+<li>En fri og åpen standard er immun for leverandørinnlåsing i alle
+stadier av dens livssyklus. Immuniteten fra leverandørinnlåsing gjør
+det mulig å fritt bruke, forbedre, stole på og utvide en standard over
+tid.</li>
+<li>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
+organisasjon, og dens pågående utvikling gjøres med en åpen
+beslutningsprosedyre som er tilgjengelig for alle som er interessert i
+å delta.</li>
+<li>Standarden er publisert og spesifikasjonsdokumentet er fritt
+tilgjengelig. Det må være tillatt for alle å kopiere, distribuere og
+bruke den uten begresninger.</li>
+<li>Patentene som muligens gjelder (deler av) standarden er gjort
+ugjenkallelig tilgjengelig uten krav om betaling.</li>
+<li>Det er ingen begresninger i gjenbruk av standarden.</li>
+</ul>
+<p>Det økonomiske resultatet av en fri og åpen standard, som kan
+måles, er at det muliggjør perfekt konkurranse mellom leverandører av
+produkter basert på standarden.</p>
+</blockquote>
-<div class="entry">
- <div class="title">
- <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 <video></a>
- </div>
- <div class="date">
- 2011-01-12 22:10
- </div>
+<p>(Tar gjerne imot forbedringer av oversettelsen.)</p>
+
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <div class="entry">
+ <div class="title">
+ <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>
+ </div>
+ <div class="date">
+ 22nd January 2009
+ </div>
+ <div class="body">
+ <p>I går publiserte
+<a href="http://universitas.no/nyhet/52776/">Universitas</a>,
+<a href="http://www.dagensit.no/trender/article1588462.ece">Dagens-IT</a>
+og <a href="http://www.idg.no/computerworld/article118622.ece">Computerworld
+Norge</a> en sak om at de ansatte ved Universitetet i Oslo ikke følger
+regjeringens pålegg om å publisere i HTML, PDF eller ODF. Det er bra
+at det kommer litt fokus på dette, og jeg håper noen journalister tar
+en titt på de andre statlige instansene også.</p>
- <div class="body">
-
-<p>Today I discovered
-<a href="http://www.digi.no/860070/google-dropper-h264-stotten-i-chrome">via
-digi.no</a> that the Chrome developers, in a surprising announcement,
-<a href="http://blog.chromium.org/2011/01/html-video-codec-support-in-chrome.html">yesterday
-announced</a> plans to drop H.264 support for HTML5 <video> in
-the browser. The argument used is that H.264 is not a "completely
-open" codec technology. If you believe H.264 was free for everyone
-to use, I recommend having a look at the essay
-"<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
-Free That Matters</a>". It is not free of cost for creators of video
-tools, nor those of us that want to publish on the Internet, and the
-terms provided by MPEG-LA excludes free software projects from
-licensing the patents needed for H.264. Some background information
-on the Google announcement is available from
-<a href="http://www.osnews.com/story/24243/Google_To_Drop_H264_Support_from_Chrome">OSnews</a>.
-A good read. :)</p>
+<p>Skulle ønske det var en enkel måte å sjekke om ODF-dokumenter er i
+henholdt til ODF-spesifikasjonen, og en måte å teste om programmer som
+hevder å støtte ODF forstår alle delene av ODF-spesifikasjonen.
+Kjenner kun til ufullstendige løsninger for slikt.</p>
-<p>Personally, I believe it is great that Google is taking a stand to
-promote equal terms for everyone when it comes to video publishing on
-the Internet. This can only be done by publishing using free and open
-standards, which is only possible if the web browsers provide support
-for these free and open standards. At the moment there seem to be two
-camps in the web browser world when it come to video support. Some
-browsers support H.264, and others support
-<a href="http://www.theora.org/">Ogg Theora</a> and
-<a href="http://www.webmproject.org/">WebM</a>
-(<a href="http://www.diracvideo.org/">Dirac</a> is not really an option
-yet), forcing those of us that want to publish video on the Internet
-and which can not accept the terms of use presented by MPEG-LA for
-H.264 to not reach all potential viewers.
-Wikipedia keep <a href="http://en.wikipedia.org/wiki/HTML5_video">an
-updated summary</a> of the current browser support.</p>
+ </div>
+ <div class="tags">
+
+
+ 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>.
+
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
+ <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>
+ <div id="sidebar">
+
-<p>Not surprising, several people would prefer Google to keep
-promoting H.264, and John Gruber
-<a href="http://daringfireball.net/2011/01/simple_questions">presents
-the mind set</a> of these people quite well. His rhetorical questions
-provoked a reply from Thom Holwerda with another set of questions
-<a href="http://www.osnews.com/story/24245/10_Questions_for_John_Gruber_Regarding_H_264_WebM">presenting
-the issues with H.264</a>. Both are worth a read.</p>
-<p>Some argue that if Google is dropping H.264 because it isn't free,
-they should also drop support for the Adobe Flash plugin. This
-argument was covered by Simon Phipps in
-<a href="http://blogs.computerworlduk.com/simon-says/2011/01/google-and-h264---far-from-hypocritical/index.htm">todays
-blog post</a>, which I find to put the issue in context. To me it
-make perfect sense to drop native H.264 support for HTML5 in the
-browser while still allowing plugins.</p>
+<h2>Archive</h2>
+<ul>
-<p>I suspect the reason this announcement make so many people protest,
-is that all the users and promoters of H.264 suddenly get an uneasy
-feeling that they might be backing the wrong horse. A lot of TV
-broadcasters have been moving to H.264 the last few years, and a lot
-of money has been invested in hardware based on the belief that they
-could use the same video format for both broadcasting and web
-publishing. Suddenly this belief is shaken.</p>
+<li>2012
+<ul>
-<p>An interesting question is why Google is doing this. While the
-presented argument might be true enough, I believe Google would only
-present the argument if the change make sense from a business
-perspective. One reason might be that they are currently negotiating
-with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
-feeling that dropping H.264 completely from Chroome, Youtube and
-Google Video would improve the negotiation position of Google.
-Another reason might be that Google want to save money by not having
-to pay the video tax to MPEG-LA at all, and thus want to move to a
-video format not requiring royalties at all. A third reason might be
-that the Chrome development team simply want to avoid the
-Chrome/Chromium split to get more help with the development of Chrome.
-I guess time will tell.</p>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
-<p>Update 2011-01-15: The Google Chrome team provided
-<a href="http://blog.chromium.org/2011/01/more-about-chrome-html-video-codec.html">more
-background and information on the move</a> it a blog post yesterday.</p>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
- </div>
- <div class="tags">
-
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
-
- </div>
-</div>
-<div class="padding"></div>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
-<div class="entry">
- <div class="title">
- <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>
- </div>
- <div class="date">
- 2011-01-16 00:20
- </div>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
- <div class="body">
-
-<p>The video format struggle on the web continues, and the three
-contenders seem to be Ogg Theora, H.264 and WebM. Most video sites
-seem to use H.264, while others use Ogg Theora. Interestingly enough,
-the comments I see give me the feeling that a lot of people believe
-H.264 is the most supported video format in browsers, but according to
-the Wikipedia article on
-<a href="http://en.wikipedia.org/wiki/HTML5_video">HTML5 video</a>,
-this is not true. Check out the nice table of supprted formats in
-different browsers there. The format supported by most browsers is
-Ogg Theora, supported by released versions of Mozilla Firefox, Google
-Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
-BOLT browser, while not supported by Internet Explorer nor Safari.
-The runner up is WebM supported by released versions of Google Chrome
-Chromium Opera and Origyn Web Browser, and test versions of Mozilla
-Firefox. H.264 is supported by released versions of Safari, Origyn
-Web Browser and BOLT browser, and the test version of Internet
-Explorer. Those wanting Ogg Theora support in Internet Explorer and
-Safari can install plugins to get it.</p>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
-<p>To me, the simple conclusion from this is that to reach most users
-without any extra software installed, one uses Ogg Theora with the
-HTML5 video tag. Of course to reach all those without a browser
-handling HTML5, one need fallback mechanisms. In
-<a href="http://www.nuug.no/">NUUG</a>, we provide first fallback to a
-plugin capable of playing MPEG1 video, and those without such support
-we have a second fallback to the Cortado java applet playing Ogg
-Theora. This seem to work quite well, as can be seen in an <a
-href="http://www.nuug.no/aktiviteter/20110111-semantic-web/">example
-from last week</a>.</p>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (16)</a></li>
-<p>The reason Ogg Theora is the most supported format, and H.264 is
-the least supported is simple. Implementing and using H.264
-require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
-are incompatible with free software licensing. If you believed H.264
-was without royalties and license terms, check out
-"<a href="http://webmink.com/essays/h-264/">H.264 – Not The Kind Of
-Free That Matters</a>" by Simon Phipps.</p>
+</ul></li>
-<p>A incomplete list of sites providing video in Ogg Theora is
-available from
-<a href="http://wiki.xiph.org/index.php/List_of_Theora_videos">the
-Xiph.org wiki</a>, if you want to have a look. I'm not aware of a
-similar list for WebM nor H.264.</p>
+<li>2011
+<ul>
-<p>Update 2011-01-16 09:40: A question from Tollef on IRC made me
-realise that I failed to make it clear enough this text is about the
-<video> tag support in browsers and not the video support
-provided by external plugins like the Flash plugins.</p>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
- </div>
- <div class="tags">
-
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
-
- </div>
-</div>
-<div class="padding"></div>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
- <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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
-<div id="sidebar">
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
-<h2>Archive</h2>
-<ul>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
-<li>2011
-<ul>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
-<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (14)</a></li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
+
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
</ul></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (10)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (55)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (110)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (47)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (58)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (143)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (85)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (17)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (1)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (11)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (6)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (4)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (30)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (5)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (11)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (22)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (105)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (190)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (116)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (142)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (18)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (4)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (35)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (34)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (48)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (22)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (3)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (23)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (1)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (36)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (7)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (19)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (32)</a></li>
<li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (14)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (25)</a></li>
</ul>
-</div>
-</body>
+
+ </div>
+ <p style="text-align: right">
+ Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
+</p>
+
+ </body>
</html>
projects / homepage.git / blobdiff