<!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 digistan</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="digistan.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 digistan</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="digistan.rss" type="application/rss+xml" />
+ </head>
+ <body>
+ <div class="title">
+ <h1>
+ <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
+
+ </h1>
+
+</div>
+
+
+ <h3>Entries tagged "digistan".</h3>
+
+ <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>
+
+<p><blockquote>
- <p>Entries tagged "digistan".</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>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>
+
+<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><blockquote>
+ <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>
+</blockquote></p>
-<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">
- 2009-01-31 23:10
- </div>
+<p>Her er det kun "non-commercial" og "personal and non-commercial"
+aktivitet som er tillatt uten ekstra avtale med MPEG-LA.</p>
+
+<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>
+
+<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>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>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>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>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/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:
-<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>
+<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>
+
+<p>I quickly translated it to this English message:</p>
+
+<p><blockquote>
+"Arrogant user agreement: HTC can use MY edited videos
+commercially. Although I can ONLY use them privately."
+</blockquote></p>
+
+<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/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>
+
+<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>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/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>
+
+<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 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>
<blockquote>
-<p><strong>Definisjonen av en fri og åpen standard</strong></p>
-<p>Den digitale standardorganisasjonen definierer fri og åpen standard
-som følger:</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>
+
<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>
+
+<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>
+
+<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>
+
+<li>The intellectual property - i.e. patents possibly present - of
+(parts of) the standard is made irrevocably available on a royalty-
+free basis.</li>
+
+<li>There are no constraints on the re-use of the standard.</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>
-<p>(Tar gjerne imot forbedringer av oversettelsen.)</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>
- </div>
- <div class="tags">
-
+<blockquote>
-
- 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>
+<p>En åben standard opfylder følgende krav:</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>
+<ol>
- <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.
+<li>Veldokumenteret med den fuldstændige specifikation offentligt
+tilgængelig.</li>
-<p>On page 27 of the Danish instruction manual, this section is
-written:</p>
+<li>Frit implementerbar uden økonomiske, politiske eller juridiske
+begrænsninger på implementation og anvendelse.</li>
+
+<li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
+"standardiseringsorganisation") via en åben proces.</li>
+
+</ol>
+
+</blockquote>
+
+<p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
+definition</a> from Free Software Foundation Europe.</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>
+<p>An Open Standard refers to a format or protocol that is</p>
+
+<ol>
+
+<li>subject to full public assessment and use without constraints in a
+manner equally available to all parties;</li>
+
+<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>
+
+<li>free from legal or technical clauses that limit its utilisation by
+any party or in any business model;</li>
+
+<li>managed and further developed independently of any single vendor
+in a process open to the equal participation of competitors and third
+parties;</li>
+
+<li>available in multiple complete implementations by competing
+vendors, or as a complete implementation equally available to all
+parties.</li>
+
+</ol>
+
</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>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>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>
+<blockquote>
+<p>Creation and Management of an Open Standard
- </div>
- <div class="tags">
-
+<ul>
-
- 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>
+<li>Its development and management process must be collaborative and
+ democratic:
-<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>
+ <ul>
- <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>
+ <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><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>The processes must be documented and, through a known
+ method, can be changed through input from all
+ participants.</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>The process must be based on formal and binding commitments for
+ the disclosure and licensing of intellectual property rights.</li>
-<p>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
-vil tillate streaming men ikke nedlasting meningsløs.</p>
+ <li>Development and management should strive for consensus,
+ and an appeals process must be clearly outlined.</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>
+ <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>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
-NRKBeta:</p>
+ </ul>
-<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>
+</li>
-<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>
+</ul>
-<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>Use and Licensing of an Open Standard</p>
+<ul>
-<p>Med hilsen,
-<br>-anders</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>Ring meg om noe er uklart: 95XXXXXXX</p>
-</blockquote></p>
+<li> The standard must not contain any proprietary "hooks" that create
+ a technical or economic barriers</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>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><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>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>[Anders Hofseth]
-<br>> Hei Petter.</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.
+
+ <ul>
+
+ <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>
+
+ <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>
+
+ <li> The same licensing terms are available to every potential
+ licensor</li>
+
+ </ul>
+</li>
+
+<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>
+
+</ul>
+
+</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/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>
+
+<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>There are no constraints on the re-use of the standard.</li>
+
+</ol>
+
+<p>The economic outcome of a free and open standard, which can be
+measured, is that it enables perfect competition between suppliers of
+products based on the standard.</p>
+</blockquote>
+
+<p>For a while now I have tried to figure out of Ogg Theora is a free
+and open standard according to this definition. Here is a short
+writeup of what I have been able to gather so far. I brought up the
+topic on the Xiph advocacy mailing list
+<a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
+July 2009</a>, for those that want to see some background information.
+According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
+the Ogg Theora specification fulfils the Digistan definition.</p>
+
+<p><strong>Free from vendor capture?</strong></p>
+
+<p>As far as I can see, there is no single vendor that can control the
+Ogg Theora specification. It can be argued that the
+<a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
+given that it is a non-profit foundation with the expressed goal
+making free and open protocols and standards available, it is not
+obvious that this is a real risk. One issue with the Xiph
+foundation is that its inner working (as in board member list, or who
+control the foundation) are not easily available on the web. I've
+been unable to find out who is in the foundation board, and have not
+seen any accounting information documenting how money is handled nor
+where is is spent in the foundation. It is thus not obvious for an
+external observer who control The Xiph foundation, and for all I know
+it is possible for a single vendor to take control over the
+specification. But it seem unlikely.</p>
+
+<p><strong>Maintained by open not-for-profit organisation?</strong></p>
-<p>Hei.</p>
+<p>Assuming that the Xiph foundation is the organisation its web pages
+claim it to be, this point is fulfilled. If Xiph foundation is
+controlled by a single vendor, it isn't, but I have not found any
+documentation indicating this.</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>According to
+<a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
+prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
+government, the Xiph foundation is a non-commercial organisation and
+the development process is open, transparent and non-Discrimatory.
+Until proven otherwise, I believe it make most sense to believe the
+report is correct.</p>
-<p>Godt å se at du er enig i at dette er en interessant diskusjon. Den
-vil nok fortsette en stund til. :)</p>
+<p><strong>Specification freely available?</strong></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>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
+container format</a> and both the
+<a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
+<a href="http://theora.org/doc/">Theora</a> codeces are available on
+the web. This are the terms in the Vorbis and Theora specification:
-<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>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>
+Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
+specifications, whether in private, public, or corporate
+capacity. However, the Xiph.Org Foundation and the Ogg project reserve
+the right to set the Ogg [Vorbis/Theora] specification and certify
+specification compliance.
-<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>
+</blockquote>
-<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>The Ogg container format is specified in IETF
+<a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
+this is the term:<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>
+<blockquote>
-<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>This document and translations of it may be copied and furnished to
+others, and derivative works that comment on or otherwise explain it
+or assist in its implementation may be prepared, copied, published and
+distributed, in whole or in part, without restriction of any kind,
+provided that the above copyright notice and this paragraph are
+included on all such copies and derivative works. However, this
+document itself may not be modified in any way, such as by removing
+the copyright notice or references to the Internet Society or other
+Internet organizations, except as needed for the purpose of developing
+Internet standards in which case the procedures for copyrights defined
+in the Internet Standards process must be followed, or as required to
+translate it into languages other than English.</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>The limited permissions granted above are perpetual and will not be
+revoked by the Internet Society or its successors or assigns.</p>
+</blockquote>
-<p>> Ring meg om noe er uklart: XXX</p>
+<p>All these terms seem to allow unlimited distribution and use, an
+this term seem to be fulfilled. There might be a problem with the
+missing permission to distribute modified versions of the text, and
+thus reuse it in other specifications. Not quite sure if that is a
+requirement for the Digistan definition.</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><strong>Royalty-free?</strong></p>
-<p>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
+<p>There are no known patent claims requiring royalties for the Ogg
+Theora format.
+<a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
+and
+<a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
+Jobs</a> in Apple claim to know about some patent claims (submarine
+patents) against the Theora format, but no-one else seem to believe
+them. Both Opera Software and the Mozilla Foundation have looked into
+this and decided to implement Ogg Theora support in their browsers
+without paying any royalties. For now the claims from MPEG-LA and
+Steve Jobs seem more like FUD to scare people to use the H.264 codec
+than any real problem with Ogg Theora.</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><strong>No constraints on re-use?</strong></p>
-<p>Vennlig hilsen,
-<br>--
-<br>Petter Reinholdtsen</p>
+<p>I am not aware of any constraints on re-use.</p>
- </div>
- <div class="tags">
-
+<p><strong>Conclusion</strong></p>
-
- 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>
+<p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
+depend on the governing structure of the Xiph foundation. Given the
+background report used by the Norwegian government, I believe it is
+safe to assume the last two requirements are fulfilled too, but it
+would be nice if the Xiph foundation web site made it easier to verify
+this.</p>
-<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>
+<p>It would be nice to see other analysis of other specifications to
+see if they are free and open standards.</p>
- <div class="body">
-
-<p>A few days ago
+ </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
<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>There are no constraints on the re-use of the standard.</li>
-
-</ol>
-
-<p>The economic outcome of a free and open standard, which can be
-measured, is that it enables perfect competition between suppliers of
-products based on the standard.</p>
-</blockquote>
-
-<p>For a while now I have tried to figure out of Ogg Theora is a free
-and open standard according to this definition. Here is a short
-writeup of what I have been able to gather so far. I brought up the
-topic on the Xiph advocacy mailing list
-<a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
-July 2009</a>, for those that want to see some background information.
-According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
-the Ogg Theora specification fulfils the Digistan definition.</p>
-
-<p><strong>Free from vendor capture?</strong></p>
-
-<p>As far as I can see, there is no single vendor that can control the
-Ogg Theora specification. It can be argued that the
-<a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
-given that it is a non-profit foundation with the expressed goal
-making free and open protocols and standards available, it is not
-obvious that this is a real risk. One issue with the Xiph
-foundation is that its inner working (as in board member list, or who
-control the foundation) are not easily available on the web. I've
-been unable to find out who is in the foundation board, and have not
-seen any accounting information documenting how money is handled nor
-where is is spent in the foundation. It is thus not obvious for an
-external observer who control The Xiph foundation, and for all I know
-it is possible for a single vendor to take control over the
-specification. But it seem unlikely.</p>
-
-<p><strong>Maintained by open not-for-profit organisation?</strong></p>
-
-<p>Assuming that the Xiph foundation is the organisation its web pages
-claim it to be, this point is fulfilled. If Xiph foundation is
-controlled by a single vendor, it isn't, but I have not found any
-documentation indicating this.</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>According to
-<a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
-prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
-government, the Xiph foundation is a non-commercial organisation and
-the development process is open, transparent and non-Discrimatory.
-Until proven otherwise, I believe it make most sense to believe the
-report is correct.</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><strong>Specification freely available?</strong></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>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
-container format</a> and both the
-<a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
-<a href="http://theora.org/doc/">Theora</a> codeces are available on
-the web. This are the terms in the Vorbis and Theora specification:
+<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>
-<blockquote>
+<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>
-Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
-specifications, whether in private, public, or corporate
-capacity. However, the Xiph.Org Foundation and the Ogg project reserve
-the right to set the Ogg [Vorbis/Theora] specification and certify
-specification compliance.
+<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>
-</blockquote>
+<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>The Ogg container format is specified in IETF
-<a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
-this is the term:<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>
-<blockquote>
+<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>This document and translations of it may be copied and furnished to
-others, and derivative works that comment on or otherwise explain it
-or assist in its implementation may be prepared, copied, published and
-distributed, in whole or in part, without restriction of any kind,
-provided that the above copyright notice and this paragraph are
-included on all such copies and derivative works. However, this
-document itself may not be modified in any way, such as by removing
-the copyright notice or references to the Internet Society or other
-Internet organizations, except as needed for the purpose of developing
-Internet standards in which case the procedures for copyrights defined
-in the Internet Standards process must be followed, or as required to
-translate it into languages other than English.</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>The limited permissions granted above are perpetual and will not be
-revoked by the Internet Society or its successors or assigns.</p>
-</blockquote>
+<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>All these terms seem to allow unlimited distribution and use, an
-this term seem to be fulfilled. There might be a problem with the
-missing permission to distribute modified versions of the text, and
-thus reuse it in other specifications. Not quite sure if that is a
-requirement for the Digistan definition.</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><strong>Royalty-free?</strong></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>There are no known patent claims requiring royalties for the Ogg
-Theora format.
-<a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
-and
-<a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
-Jobs</a> in Apple claim to know about some patent claims (submarine
-patents) against the Theora format, but no-one else seem to believe
-them. Both Opera Software and the Mozilla Foundation have looked into
-this and decided to implement Ogg Theora support in their browsers
-without paying any royalties. For now the claims from MPEG-LA and
-Steve Jobs seem more like FUD to scare people to use the H.264 codec
-than any real problem with Ogg Theora.</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><strong>No constraints on re-use?</strong></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>I am not aware of any constraints on re-use.</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><strong>Conclusion</strong></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>3 of 5 requirements seem obviously fulfilled, and the remaining 2
-depend on the governing structure of the Xiph foundation. Given the
-background report used by the Norwegian government, I believe it is
-safe to assume the last two requirements are fulfilled too, but it
-would be nice if the Xiph foundation web site made it easier to verify
-this.</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>It would be nice to see other analysis of other specifications to
-see if they are free and open standards.</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>
- </div>
- <div class="tags">
-
+<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>
-
- 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>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>
-<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>
+<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>
- <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>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>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>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>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>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>
-<blockquote>
+<p>Cordially,<br>
+DR. EDGAR DAVID VILLANUEVA NUÑEZ<br>
+Congressman of the Republic of Perú.</p>
+</blockquote>
-<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>
+ </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/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>
-<ul>
+<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>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>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>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>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
+vil tillate streaming men ikke nedlasting meningsløs.</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>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>
-<li>There are no constraints on the re-use of the standard.</li>
+<p>Ca. 20 minutter senere får jeg følgende epost fra Anders Hofseth i
+NRKBeta:</p>
-</ul>
-</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>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>
+<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>En åben standard opfylder følgende krav:</p>
+<p>Med hilsen,
+<br>-anders</p>
-<ol>
+<p>Ring meg om noe er uklart: 95XXXXXXX</p>
+</blockquote></p>
-<li>Veldokumenteret med den fuldstændige specifikation offentligt
-tilgængelig.</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>Frit implementerbar uden økonomiske, politiske eller juridiske
-begrænsninger på implementation og anvendelse.</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>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
-"standardiseringsorganisation") via en åben proces.</li>
+<p>[Anders Hofseth]
+<br>> Hei Petter.</p>
-</ol>
+<p>Hei.</p>
-</blockquote>
+<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>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
-definition</a> from Free Software Foundation Europe.</p>
+<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>An Open Standard refers to a format or protocol that is</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>
-<ol>
+<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>
-<li>subject to full public assessment and use without constraints in a
-manner equally available to all parties;</li>
+<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>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>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>
-<li>free from legal or technical clauses that limit its utilisation by
-any party or in any business model;</li>
+<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>managed and further developed independently of any single vendor
-in a process open to the equal participation of competitors and third
-parties;</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>available in multiple complete implementations by competing
-vendors, or as a complete implementation equally available to all
-parties.</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>
-</ol>
+<p>> Ring meg om noe er uklart: XXX</p>
-</blockquote>
+<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>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>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.</p>
-<blockquote>
-<p>Creation and Management of an Open Standard
+<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>
-<ul>
+<p>Vennlig hilsen,
+<br>--
+<br>Petter Reinholdtsen</p>
-<li>Its development and management process must be collaborative and
- democratic:
+ </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/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.
- <ul>
+<p>On page 27 of the Danish instruction manual, this section is
+written:</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>
+<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>
- <li>The processes must be documented and, through a known
- method, can be changed through input from all
- participants.</li>
+<p>No license is granted or implied for any other use for MPEG-4
+standard.</p>
+</blockquote>
- <li>The process must be based on formal and binding commitments for
- the disclosure and licensing of intellectual property rights.</li>
+<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>
- <li>Development and management should strive for consensus,
- and an appeals process must be clearly outlined.</li>
+<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>
- <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>
+ </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/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>
- </ul>
+<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>
-</li>
+<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>
-</ul>
+<blockquote>
+<p><strong>Definisjonen av en fri og åpen standard</strong></p>
-<p>Use and Licensing of an Open Standard</p>
+<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>
-<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>
-
-<li> The standard must not contain any proprietary "hooks" that create
- a technical or economic barriers</li>
-
-<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>(Tar gjerne imot forbedringer av oversettelsen.)</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">
+
+
+ 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>
+
+ <p style="text-align: right;"><a href="digistan.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
+ <div id="sidebar">
+
-<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.
- <ul>
+<h2>Archive</h2>
+<ul>
- <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>
+<li>2012
+<ul>
- <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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
- <li> The same licensing terms are available to every potential
- licensor</li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
- </ul>
-</li>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
-<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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
-</ul>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
-</blockquote>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
-<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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
- </div>
- <div class="tags">
-
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
-
- 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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
-<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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
- <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>
+</ul></li>
-<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>
+<li>2011
+<ul>
-<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>
+<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/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>
+<li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
- <p style="text-align: right;"><a href="digistan.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 (16)</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/02/">February (5)</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 (48)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (57)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (60)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (115)</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/digistan">digistan (9)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (86)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (7)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (4)</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/fildeling">fildeling (11)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (157)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (6)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (19)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (9)</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/freeculture">freeculture (8)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (8)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (31)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (17)</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 (25)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (111)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (209)</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 (146)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (19)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (6)</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 (37)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (54)</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 (23)</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 (24)</a></li>
- <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (24)</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/stavekontroll">stavekontroll (1)</a></li>
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</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/standard">standard (39)</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/stavekontroll">stavekontroll (3)</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/stortinget">stortinget (5)</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/surveillance">surveillance (11)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (7)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (35)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
+
+ <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (26)</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