1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged digistan
</title>
5 <description>Entries tagged digistan
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Fri og åpen standard, slik Digistan ser det
</title>
11 <link>http://people.skolelinux.org/pere/blog/Fri_og___pen_standard__slik_Digistan_ser_det.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fri_og___pen_standard__slik_Digistan_ser_det.html
</guid>
13 <pubDate>Sat,
31 Jan
2009 23:
10:
00 +
0100</pubDate>
15 <p
>Det er mange ulike definisjoner om hva en åpen standard er for noe,
16 og NUUG hadde
<a href=
"http://www.nuug.no/dokumenter/standard-presse-def-
200506.txt
">en
17 pressemelding om dette sommeren
2005</a
>. Der ble definisjonen til
18 <a href=
"http://www.aaben-standard.dk/
">DKUUG
</a
>,
19 <a href=
"http://europa.eu.int/idabc/servlets/Doc?id=
19529">EU-kommissionens
20 European Interoperability Framework ( side
9)
</a
> og
21 <a href=
"http://www.teknologiradet.no/files/
7polert_copy.htm
">teknologirådet
</a
> omtalt.
23 Siden den gang har regjeringens standardiseringsråd dukket opp, og de
24 ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
25 <a href=
"http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=
476407">sin
26 arbeidsmetodikk
</a
>. Personlig synes jeg det er en god ide, da
27 kravene som stilles der gjør at alle markedsaktører får like vilkår,
28 noe som kommer kundene til gode ved hjelp av økt konkurranse.
</p
>
30 <p
>I sommer kom det en ny definisjon på banen.
31 <a href=
"http://www.digistan.org/
">Digistan
</a
> lanserte
32 <a href=
"http://www.digistan.org/open-standard:definition
">en
33 definisjon på en fri og åpen standard
</a
>. Jeg liker måten de bryter
34 ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
35 ved å legge på et ord og poengtere at en standard som er både åpen og
36 fri har noen spesielle krav. Her er den definisjonen etter rask
37 oversettelse fra engelsk til norsk av meg:
</p
>
40 <p
><strong
>Definisjonen av en fri og åpen standard
</strong
></p
>
42 <p
>Den digitale standardorganisasjonen definierer fri og åpen standard
45 <li
>En fri og åpen standard er immun for leverandørinnlåsing i alle
46 stadier av dens livssyklus. Immuniteten fra leverandørinnlåsing gjør
47 det mulig å fritt bruke, forbedre, stole på og utvide en standard over
49 <li
>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
50 organisasjon, og dens pågående utvikling gjøres med en åpen
51 beslutningsprosedyre som er tilgjengelig for alle som er interessert i
53 <li
>Standarden er publisert og spesifikasjonsdokumentet er fritt
54 tilgjengelig. Det må være tillatt for alle å kopiere, distribuere og
55 bruke den uten begresninger.
</li
>
56 <li
>Patentene som muligens gjelder (deler av) standarden er gjort
57 ugjenkallelig tilgjengelig uten krav om betaling.
</li
>
58 <li
>Det er ingen begresninger i gjenbruk av standarden.
</li
>
60 <p
>Det økonomiske resultatet av en fri og åpen standard, som kan
61 måles, er at det muliggjør perfekt konkurranse mellom leverandører av
62 produkter basert på standarden.
</p
>
65 <p
>(Tar gjerne imot forbedringer av oversettelsen.)
</p
>
70 <title>Terms of use for video produced by a Canon IXUS
130 digital camera
</title>
71 <link>http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</link>
72 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</guid>
73 <pubDate>Thu,
9 Sep
2010 23:
55:
00 +
0200</pubDate>
75 <p
>A few days ago I had the mixed pleasure of bying a new digital
76 camera, a Canon IXUS
130. It was instructive and very disturbing to
77 be able to verify that also this camera producer have the nerve to
78 specify how I can or can not use the videos produced with the camera.
79 Even thought I was aware of the issue, the options with new cameras
80 are limited and I ended up bying the camera anyway. What is the
81 problem, you might ask? It is software patents, MPEG-
4, H
.264 and the
82 MPEG-LA that is the problem, and our right to record our experiences
83 without asking for permissions that is at risk.
85 <p
>On page
27 of the Danish instruction manual, this section is
89 <p
>This product is licensed under AT
&T patents for the MPEG-
4 standard
90 and may be used for encoding MPEG-
4 compliant video and/or decoding
91 MPEG-
4 compliant video that was encoded only (
1) for a personal and
92 non-commercial purpose or (
2) by a video provider licensed under the
93 AT
&T patents to provide MPEG-
4 compliant video.
</p
>
95 <p
>No license is granted or implied for any other use for MPEG-
4
99 <p
>In short, the camera producer have chosen to use technology
100 (MPEG-
4/H
.264) that is only provided if I used it for personal and
101 non-commercial purposes, or ask for permission from the organisations
102 holding the knowledge monopoly (patent) for technology used.
</p
>
104 <p
>This issue has been brewing for a while, and I recommend you to
106 "<a href=
"http://www.osnews.com/story/
23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA
">Why
107 Our Civilization
's Video Art and Culture is Threatened by the
108 MPEG-LA
</a
>" by Eugenia Loli-Queru and
109 "<a href=
"http://webmink.com/
2010/
09/
03/h-
264-and-foss/
">H
.264 Is Not
110 The Sort Of Free That Matters
</a
>" by Simon Phipps to learn more about
111 the issue. The solution is to support the
112 <a href=
"http://www.digistan.org/open-standard:definition
">free and
113 open standards
</a
> for video, like
<a href=
"http://www.theora.org/
">Ogg
114 Theora
</a
>, and avoid MPEG-
4 and H
.264 if you can.
</p
>
119 <title>Best å ikke fortelle noen at streaming er nedlasting...
</title>
120 <link>http://people.skolelinux.org/pere/blog/Best____ikke_fortelle_noen_at_streaming_er_nedlasting___.html
</link>
121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best____ikke_fortelle_noen_at_streaming_er_nedlasting___.html
</guid>
122 <pubDate>Sat,
30 Oct
2010 11:
20:
00 +
0200</pubDate>
124 <p
>I dag la jeg inn en kommentar på en sak hos NRKBeta
125 <a href=
"http://nrkbeta.no/
2010/
10/
27/bakom-blindpassasjer-del-
1/
">om
126 hvordan TV-serien Blindpassasjer ble laget
</a
> i forbindelse med at
127 filmene NRK la ut ikke var tilgjengelig i et
128 <a href=
"http://www.digistan.org/open-standard:definition
">fritt og
129 åpent format
</a
>. Dette var det jeg skrev publiserte der
07:
39.
</p
>
131 <p
><blockquote
>
132 <p
>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
133 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
134 som dette, vet at det stort sett er mulig å lure ut ting med den
135 nødvendige forkunnskapen.
"</p
>
137 <p
>Haha. Å streame innhold er det samme som å laste ned innhold, så å
138 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
139 er å forlede leseren.
</p
>
141 <p
>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
142 vil tillate streaming men ikke nedlasting meningsløs.
</p
>
144 <p
>Anbefaler forresten å lese
145 <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
>
146 om hva som ville være konsekvensen hvis digitale avspillingssperrer
147 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
148 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
149 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
151 </blockquote
></p
>
153 <p
>Ca.
20 minutter senere får jeg følgende epost fra Anders Hofseth i
156 <p
><blockquote
>
157 <p
>From: Anders Hofseth
&lt;XXX@gmail.com
>
158 <br
>To:
"pere@hungry.com
" &lt;pere@hungry.com
>
159 <br
>Cc: Eirik Solheim
&lt;XXX@gmail.com
>, Jon Ståle Carlsen
&lt;XXX@gmail.com
>, Henrik Lied
&lt;XXX@gmail.com
>
160 <br
>Subject: Re: [NRKbeta] Kommentar:
"Bakom Blindpassasjer: del
1"
161 <br
>Date: Sat,
30 Oct
2010 07:
58:
44 +
0200</p
>
164 <br
>Det du forsøker dra igang er egentlig en interessant diskusjon,
165 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
166 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
167 særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p
>
169 <p
>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
170 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
171 konsekvensene vi beskriver ikke er noe du ønsker heller...
</p
>
174 <br
>-anders
</p
>
176 <p
>Ring meg om noe er uklart:
95XXXXXXX
</p
>
177 </blockquote
></p
>
179 <p
>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
180 over følgende svar. I og med at debatten er fjernet fra NRK Betas
181 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
182 Har fjernet epostadresser og telefonnummer til de involverte, for å
183 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.
</p
>
185 <p
><blockquote
>
186 <p
>From: Petter Reinholdtsen
&lt;pere@hungry.com
>
187 <br
>To: Anders Hofseth
&lt;XXX@gmail.com
>
188 <br
>Cc: Eirik Solheim
&lt;XXX@gmail.com
>,
189 <br
> Jon Ståle Carlsen
&lt;XXX@gmail.com
>,
190 <br
> Henrik Lied
&lt;XXX@gmail.com
>
191 <br
>Subject: Re: [NRKbeta] Kommentar:
"Bakom Blindpassasjer: del
1"
192 <br
>Date: Sat,
30 Oct
2010 08:
24:
34 +
0200</p
>
194 <p
>[Anders Hofseth]
195 <br
>> Hei Petter.
</p
>
197 <p
>Hei.
</p
>
199 <p
>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
200 <br
>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
201 <br
>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
202 <br
>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p
>
204 <p
>Godt å se at du er enig i at dette er en interessant diskusjon. Den
205 vil nok fortsette en stund til. :)
</p
>
207 <p
>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
208 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
209 fortsette å legge ut arkivmateriale.
</p
>
211 <p
>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
212 faktum, som er at streaming er det samme som nedlasting, og at innhold
213 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
216 <p
>Det du sier er jo at klarering av arkivmateriale for publisering på
217 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
218 Det er ikke et argument som holder vann. :)
</p
>
220 <p
>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
221 <br
>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
222 <br
>> konsekvensene vi beskriver ikke er noe du ønsker heller...
</p
>
224 <p
>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
225 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
226 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
227 godtar å forlede publikum. Ville heller at NRK krever at innhold som
228 skal sendes skal være uten bruksbegresninger og kan publiseres i
229 formater som heller ikke har bruksbegresninger (bruksbegresningene til
230 H
.264 burde få varselbjellene i NRK til å ringe).
</p
>
232 <p
>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
233 påstander om at
"streaming beskytter mot nedlasting
" som bare er egnet
234 til å bygge opp om en myte som er skadelig for samfunnet som helhet.
</p
>
236 <p
>Anbefaler
&lt;URL:
<a href=
"http://webmink.com/
2010/
09/
03/h-
264-and-foss/
">http://webmink.com/
2010/
09/
03/h-
264-and-foss/
</a
>> og en
238 &lt;URL:
<a href=
"http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</a
> >.
239 for å se hva slags bruksbegresninger H
.264 innebærer.
</p
>
241 <p
>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
242 kan brukes før rettighetshaverene også innser at de er med på å skade
243 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
244 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
245 langt på overtid.
</p
>
247 <p
>> Ring meg om noe er uklart: XXX
</p
>
249 <p
>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
250 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
251 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
252 for videre diskusjon hadde dere i mine øyne kommet fra det med
253 ryggraden på plass.
</p
>
255 <p
>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.
</p
>
257 <p
>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
258 &lt;URL:
<a href=
"http://www.archive.org/details/CopyingIsNotTheft
">http://www.archive.org/details/CopyingIsNotTheft
</a
> > og
259 &lt;URL:
<a href=
"http://patentabsurdity.com/
">http://patentabsurdity.com/
</a
> > hadde vært noe å kringkaste på
262 <p
>Vennlig hilsen,
264 <br
>Petter Reinholdtsen
</p
>
269 <title>The reply from Edgar Villanueva to Microsoft in Peru
</title>
270 <link>http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html
</link>
271 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html
</guid>
272 <pubDate>Sat,
25 Dec
2010 10:
50:
00 +
0100</pubDate>
274 <p
>A few days ago
275 <a href=
"http://www.idg.no/computerworld/article189879.ece
">an
276 article
</a
> in the Norwegian Computerworld magazine about how version
278 <a href=
"http://en.wikipedia.org/wiki/European_Interoperability_Framework
">European
279 Interoperability Framework
</a
> has been successfully lobbied by the
280 proprietary software industry to remove the focus on free software.
281 Nothing very surprising there, given
282 <a href=
"http://news.slashdot.org/story/
10/
03/
29/
2115235/Open-Source-Open-Standards-Under-Attack-In-Europe
">earlier
283 reports
</a
> on how Microsoft and others have stacked the committees in
284 this work. But I find this very sad. The definition of
285 <a href=
"http://www.nuug.no/dokumenter/standard-presse-def-
200506.txt
">an
286 open standard from version
1</a
> was very good, and something I
287 believe should be used also in the future, alongside
288 <a href=
"http://www.digistan.org/open-standard:definition
">the
289 definition from Digistan
</A
>. Version
2 have removed the open
290 standard definition from its content.
</p
>
292 <p
>Anyway, the news reminded me of the great reply sent by Dr. Edgar
293 Villanueva, congressman in Peru at the time, to Microsoft as a reply
294 to Microsofts attack on his proposal regarding the use of free software
295 in the public sector in Peru. As the text was not available from a
296 few of the URLs where it used to be available, I copy it here from
297 <a href=
"http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html
">my
298 source
</a
> to ensure it is available also in the future. Some
299 background information about that story is available in
300 <a href=
"http://www.linuxjournal.com/article/
6099">an article
</a
> from
301 Linux Journal in
2002.
</p
>
304 <p
>Lima,
8th of April,
2002<br
>
305 To: Señor JUAN ALBERTO GONZÁLEZ
<br
>
306 General Manager of Microsoft Perú
</p
>
308 <p
>Dear Sir:
</p
>
310 <p
>First of all, I thank you for your letter of March
25,
2002 in which you state the official position of Microsoft relative to Bill Number
1609, Free Software in Public Administration, which is indubitably inspired by the desire for Peru to find a suitable place in the global technological context. In the same spirit, and convinced that we will find the best solutions through an exchange of clear and open ideas, I will take this opportunity to reply to the commentaries included in your letter.
</p
>
312 <p
>While acknowledging that opinions such as yours constitute a significant contribution, it would have been even more worthwhile for me if, rather than formulating objections of a general nature (which we will analyze in detail later) you had gathered solid arguments for the advantages that proprietary software could bring to the Peruvian State, and to its citizens in general, since this would have allowed a more enlightening exchange in respect of each of our positions.
</p
>
314 <p
>With the aim of creating an orderly debate, we will assume that what you call
"open source software
" is what the Bill defines as
"free software
", since there exists software for which the source code is distributed together with the program, but which does not fall within the definition established by the Bill; and that what you call
"commercial software
" is what the Bill defines as
"proprietary
" or
"unfree
", given that there exists free software which is sold in the market for a price like any other good or service.
</p
>
316 <p
>It is also necessary to make it clear that the aim of the Bill we are discussing is not directly related to the amount of direct savings that can by made by using free software in state institutions. That is in any case a marginal aggregate value, but in no way is it the chief focus of the Bill. The basic principles which inspire the Bill are linked to the basic guarantees of a state of law, such as:
</p
>
320 <li
>Free access to public information by the citizen.
</li
>
321 <li
>Permanence of public data.
</li
>
322 <li
>Security of the State and citizens.
</li
>
326 <p
>To guarantee the free access of citizens to public information, it is indispensable that the encoding of data is not tied to a single provider. The use of standard and open formats gives a guarantee of this free access, if necessary through the creation of compatible free software.
</p
>
328 <p
>To guarantee the permanence of public data, it is necessary that the usability and maintenance of the software does not depend on the goodwill of the suppliers, or on the monopoly conditions imposed by them. For this reason the State needs systems the development of which can be guaranteed due to the availability of the source code.
</p
>
330 <p
>To guarantee national security or the security of the State, it is indispensable to be able to rely on systems without elements which allow control from a distance or the undesired transmission of information to third parties. Systems with source code freely accessible to the public are required to allow their inspection by the State itself, by the citizens, and by a large number of independent experts throughout the world. Our proposal brings further security, since the knowledge of the source code will eliminate the growing number of programs with *spy code*.
</p
>
332 <p
>In the same way, our proposal strengthens the security of the citizens, both in their role as legitimate owners of information managed by the state, and in their role as consumers. In this second case, by allowing the growth of a widespread availability of free software not containing *spy code* able to put at risk privacy and individual freedoms.
</p
>
334 <p
>In this sense, the Bill is limited to establishing the conditions under which the state bodies will obtain software in the future, that is, in a way compatible with these basic principles.
</p
>
337 <p
>From reading the Bill it will be clear that once passed:
<br
>
338 <li
>the law does not forbid the production of proprietary software
</li
>
339 <li
>the law does not forbid the sale of proprietary software
</li
>
340 <li
>the law does not specify which concrete software to use
</li
>
341 <li
>the law does not dictate the supplier from whom software will be bought
</li
>
342 <li
>the law does not limit the terms under which a software product can be licensed.
</li
>
346 <p
>What the Bill does express clearly, is that, for software to be acceptable for the state it is not enough that it is technically capable of fulfilling a task, but that further the contractual conditions must satisfy a series of requirements regarding the license, without which the State cannot guarantee the citizen adequate processing of his data, watching over its integrity, confidentiality, and accessibility throughout time, as these are very critical aspects for its normal functioning.
</p
>
348 <p
>We agree, Mr. Gonzalez, that information and communication technology have a significant impact on the quality of life of the citizens (whether it be positive or negative). We surely also agree that the basic values I have pointed out above are fundamental in a democratic state like Peru. So we are very interested to know of any other way of guaranteeing these principles, other than through the use of free software in the terms defined by the Bill.
</p
>
350 <p
>As for the observations you have made, we will now go on to analyze them in detail:
</p
>
352 <p
>Firstly, you point out that:
"1. The bill makes it compulsory for all public bodies to use only free software, that is to say open source software, which breaches the principles of equality before the law, that of non-discrimination and the right of free private enterprise, freedom of industry and of contract, protected by the constitution.
"</p
>
354 <p
>This understanding is in error. The Bill in no way affects the rights you list; it limits itself entirely to establishing conditions for the use of software on the part of state institutions, without in any way meddling in private sector transactions. It is a well established principle that the State does not enjoy the wide spectrum of contractual freedom of the private sector, as it is limited in its actions precisely by the requirement for transparency of public acts; and in this sense, the preservation of the greater common interest must prevail when legislating on the matter.
</p
>
356 <p
>The Bill protects equality under the law, since no natural or legal person is excluded from the right of offering these goods to the State under the conditions defined in the Bill and without more limitations than those established by the Law of State Contracts and Purchasing (T.U.O. by Supreme Decree No.
012-
2001-PCM).
</p
>
358 <p
>The Bill does not introduce any discrimination whatever, since it only establishes *how* the goods have to be provided (which is a state power) and not *who* has to provide them (which would effectively be discriminatory, if restrictions based on national origin, race religion, ideology, sexual preference etc. were imposed). On the contrary, the Bill is decidedly antidiscriminatory. This is so because by defining with no room for doubt the conditions for the provision of software, it prevents state bodies from using software which has a license including discriminatory conditions.
</p
>
360 <p
>It should be obvious from the preceding two paragraphs that the Bill does not harm free private enterprise, since the latter can always choose under what conditions it will produce software; some of these will be acceptable to the State, and others will not be since they contradict the guarantee of the basic principles listed above. This free initiative is of course compatible with the freedom of industry and freedom of contract (in the limited form in which the State can exercise the latter). Any private subject can produce software under the conditions which the State requires, or can refrain from doing so. Nobody is forced to adopt a model of production, but if they wish to provide software to the State, they must provide the mechanisms which guarantee the basic principles, and which are those described in the Bill.
</p
>
362 <p
>By way of an example: nothing in the text of the Bill would prevent your company offering the State bodies an office
"suite
", under the conditions defined in the Bill and setting the price that you consider satisfactory. If you did not, it would not be due to restrictions imposed by the law, but to business decisions relative to the method of commercializing your products, decisions with which the State is not involved.
</p
>
364 <p
>To continue; you note that:
" 2. The bill, by making the use of open source software compulsory, would establish discriminatory and non competitive practices in the contracting and purchasing by public bodies...
"</p
>
366 <p
>This statement is just a reiteration of the previous one, and so the response can be found above. However, let us concern ourselves for a moment with your comment regarding
"non-competitive ... practices.
"</p
>
368 <p
>Of course, in defining any kind of purchase, the buyer sets conditions which relate to the proposed use of the good or service. From the start, this excludes certain manufacturers from the possibility of competing, but does not exclude them
"a priori
", but rather based on a series of principles determined by the autonomous will of the purchaser, and so the process takes place in conformance with the law. And in the Bill it is established that *no one* is excluded from competing as far as he guarantees the fulfillment of the basic principles.
</p
>
370 <p
>Furthermore, the Bill *stimulates* competition, since it tends to generate a supply of software with better conditions of usability, and to better existing work, in a model of continuous improvement.
</p
>
372 <p
>On the other hand, the central aspect of competivity is the chance to provide better choices to the consumer. Now, it is impossible to ignore the fact that marketing does not play a neutral role when the product is offered on the market (since accepting the opposite would lead one to suppose that firms
' expenses in marketing lack any sense), and that therefore a significant expense under this heading can influence the decisions of the purchaser. This influence of marketing is in large measure reduced by the bill that we are backing, since the choice within the framework proposed is based on the *technical merits* of the product and not on the effort put into commercialization by the producer; in this sense, competitiveness is increased, since the smallest software producer can compete on equal terms with the most powerful corporations.
</p
>
374 <p
>It is necessary to stress that there is no position more anti-competitive than that of the big software producers, which frequently abuse their dominant position, since in innumerable cases they propose as a solution to problems raised by users:
"update your software to the new version
" (at the user
's expense, naturally); furthermore, it is common to find arbitrary cessation of technical help for products, which, in the provider
's judgment alone, are
"old
"; and so, to receive any kind of technical assistance, the user finds himself forced to migrate to new versions (with non-trivial costs, especially as changes in hardware platform are often involved). And as the whole infrastructure is based on proprietary data formats, the user stays
"trapped
" in the need to continue using products from the same supplier, or to make the huge effort to change to another environment (probably also proprietary).
</p
>
376 <p
>You add:
"3. So, by compelling the State to favor a business model based entirely on open source, the bill would only discourage the local and international manufacturing companies, which are the ones which really undertake important expenditures, create a significant number of direct and indirect jobs, as well as contributing to the GNP, as opposed to a model of open source software which tends to have an ever weaker economic impact, since it mainly creates jobs in the service sector.
"</p
>
378 <p
>I do not agree with your statement. Partly because of what you yourself point out in paragraph
6 of your letter, regarding the relative weight of services in the context of software use. This contradiction alone would invalidate your position. The service model, adopted by a large number of companies in the software industry, is much larger in economic terms, and with a tendency to increase, than the licensing of programs.
</p
>
380 <p
>On the other hand, the private sector of the economy has the widest possible freedom to choose the economic model which best suits its interests, even if this freedom of choice is often obscured subliminally by the disproportionate expenditure on marketing by the producers of proprietary software.
</p
>
382 <p
>In addition, a reading of your opinion would lead to the conclusion that the State market is crucial and essential for the proprietary software industry, to such a point that the choice made by the State in this bill would completely eliminate the market for these firms. If that is true, we can deduce that the State must be subsidizing the proprietary software industry. In the unlikely event that this were true, the State would have the right to apply the subsidies in the area it considered of greatest social value; it is undeniable, in this improbable hypothesis, that if the State decided to subsidize software, it would have to do so choosing the free over the proprietary, considering its social effect and the rational use of taxpayers money.
</p
>
384 <p
>In respect of the jobs generated by proprietary software in countries like ours, these mainly concern technical tasks of little aggregate value; at the local level, the technicians who provide support for proprietary software produced by transnational companies do not have the possibility of fixing bugs, not necessarily for lack of technical capability or of talent, but because they do not have access to the source code to fix it. With free software one creates more technically qualified employment and a framework of free competence where success is only tied to the ability to offer good technical support and quality of service, one stimulates the market, and one increases the shared fund of knowledge, opening up alternatives to generate services of greater total value and a higher quality level, to the benefit of all involved: producers, service organizations, and consumers.
</p
>
386 <p
>It is a common phenomenon in developing countries that local software industries obtain the majority of their takings in the service sector, or in the creation of
"ad hoc
" software. Therefore, any negative impact that the application of the Bill might have in this sector will be more than compensated by a growth in demand for services (as long as these are carried out to high quality standards). If the transnational software companies decide not to compete under these new rules of the game, it is likely that they will undergo some decrease in takings in terms of payment for licenses; however, considering that these firms continue to allege that much of the software used by the State has been illegally copied, one can see that the impact will not be very serious. Certainly, in any case their fortune will be determined by market laws, changes in which cannot be avoided; many firms traditionally associated with proprietary software have already set out on the road (supported by copious expense) of providing services associated with free software, which shows that the models are not mutually exclusive.
</p
>
388 <p
>With this bill the State is deciding that it needs to preserve certain fundamental values. And it is deciding this based on its sovereign power, without affecting any of the constitutional guarantees. If these values could be guaranteed without having to choose a particular economic model, the effects of the law would be even more beneficial. In any case, it should be clear that the State does not choose an economic model; if it happens that there only exists one economic model capable of providing software which provides the basic guarantee of these principles, this is because of historical circumstances, not because of an arbitrary choice of a given model.
</p
>
390 <p
>Your letter continues:
"4. The bill imposes the use of open source software without considering the dangers that this can bring from the point of view of security, guarantee, and possible violation of the intellectual property rights of third parties.
"</p
>
392 <p
>Alluding in an abstract way to
"the dangers this can bring
", without specifically mentioning a single one of these supposed dangers, shows at the least some lack of knowledge of the topic. So, allow me to enlighten you on these points.
</p
>
394 <p
>On security:
</p
>
396 <p
>National security has already been mentioned in general terms in the initial discussion of the basic principles of the bill. In more specific terms, relative to the security of the software itself, it is well known that all software (whether proprietary or free) contains errors or
"bugs
" (in programmers
' slang). But it is also well known that the bugs in free software are fewer, and are fixed much more quickly, than in proprietary software. It is not in vain that numerous public bodies responsible for the IT security of state systems in developed countries require the use of free software for the same conditions of security and efficiency.
</p
>
398 <p
>What is impossible to prove is that proprietary software is more secure than free, without the public and open inspection of the scientific community and users in general. This demonstration is impossible because the model of proprietary software itself prevents this analysis, so that any guarantee of security is based only on promises of good intentions (biased, by any reckoning) made by the producer itself, or its contractors.
</p
>
400 <p
>It should be remembered that in many cases, the licensing conditions include Non-Disclosure clauses which prevent the user from publicly revealing security flaws found in the licensed proprietary product.
</p
>
402 <p
>In respect of the guarantee:
</p
>
404 A
<p
>s you know perfectly well, or could find out by reading the
"End User License Agreement
" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS
'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.
</p
>
406 <p
>On Intellectual Property:
</p
>
408 <p
>Questions of intellectual property fall outside the scope of this bill, since they are covered by specific other laws. The model of free software in no way implies ignorance of these laws, and in fact the great majority of free software is covered by copyright. In reality, the inclusion of this question in your observations shows your confusion in respect of the legal framework in which free software is developed. The inclusion of the intellectual property of others in works claimed as one
's own is not a practice that has been noted in the free software community; whereas, unfortunately, it has been in the area of proprietary software. As an example, the condemnation by the Commercial Court of Nanterre, France, on
27th September
2001 of Microsoft Corp. to a penalty of
3 million francs in damages and interest, for violation of intellectual property (piracy, to use the unfortunate term that your firm commonly uses in its publicity).
</p
>
410 <p
>You go on to say that:
"The bill uses the concept of open source software incorrectly, since it does not necessarily imply that the software is free or of zero cost, and so arrives at mistaken conclusions regarding State savings, with no cost-benefit analysis to validate its position.
"</p
>
412 <p
>This observation is wrong; in principle, freedom and lack of cost are orthogonal concepts: there is software which is proprietary and charged for (for example, MS Office), software which is proprietary and free of charge (MS Internet Explorer), software which is free and charged for (Red Hat, SuSE etc GNU/Linux distributions), software which is free and not charged for (Apache, Open Office, Mozilla), and even software which can be licensed in a range of combinations (MySQL).
</p
>
414 <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
>
416 <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
>
418 <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
>
420 <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
>
422 <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
>
424 <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
>
426 <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
>
428 <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
>
430 <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
>
432 <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
>
434 <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
>
436 <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
>
438 <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
>
440 <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
>
442 <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
>
444 <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
>
446 <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
>
448 <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
>
450 <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
>
452 <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
>
454 <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
>
456 <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
>
458 <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
>
460 <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
>
462 <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
>
464 <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
>
466 <p
>Cordially,
<br
>
467 DR. EDGAR DAVID VILLANUEVA NUÑEZ
<br
>
468 Congressman of the Republic of Perú.
</p
>
474 <title>Is Ogg Theora a free and open standard?
</title>
475 <link>http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
</link>
476 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
</guid>
477 <pubDate>Sat,
25 Dec
2010 20:
25:
00 +
0100</pubDate>
479 <p
><a href=
"http://www.digistan.org/open-standard:definition
">The
480 Digistan definition
</a
> of a free and open standard reads like this:
</p
>
484 <p
>The Digital Standards Organization defines free and open standard
485 as follows:
</p
>
489 <li
>A free and open standard is immune to vendor capture at all stages
490 in its life-cycle. Immunity from vendor capture makes it possible to
491 freely use, improve upon, trust, and extend a standard over time.
</li
>
493 <li
>The standard is adopted and will be maintained by a not-for-profit
494 organisation, and its ongoing development occurs on the basis of an
495 open decision-making procedure available to all interested
498 <li
>The standard has been published and the standard specification
499 document is available freely. It must be permissible to all to copy,
500 distribute, and use it freely.
</li
>
502 <li
>The patents possibly present on (parts of) the standard are made
503 irrevocably available on a royalty-free basis.
</li
>
505 <li
>There are no constraints on the re-use of the standard.
</li
>
509 <p
>The economic outcome of a free and open standard, which can be
510 measured, is that it enables perfect competition between suppliers of
511 products based on the standard.
</p
>
514 <p
>For a while now I have tried to figure out of Ogg Theora is a free
515 and open standard according to this definition. Here is a short
516 writeup of what I have been able to gather so far. I brought up the
517 topic on the Xiph advocacy mailing list
518 <a href=
"http://lists.xiph.org/pipermail/advocacy/
2009-July/
001632.html
">in
519 July
2009</a
>, for those that want to see some background information.
520 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
521 the Ogg Theora specification fulfils the Digistan definition.
</p
>
523 <p
><strong
>Free from vendor capture?
</strong
></p
>
525 <p
>As far as I can see, there is no single vendor that can control the
526 Ogg Theora specification. It can be argued that the
527 <a href=
"http://www.xiph.org/
">Xiph foundation
</A
> is such vendor, but
528 given that it is a non-profit foundation with the expressed goal
529 making free and open protocols and standards available, it is not
530 obvious that this is a real risk. One issue with the Xiph
531 foundation is that its inner working (as in board member list, or who
532 control the foundation) are not easily available on the web. I
've
533 been unable to find out who is in the foundation board, and have not
534 seen any accounting information documenting how money is handled nor
535 where is is spent in the foundation. It is thus not obvious for an
536 external observer who control The Xiph foundation, and for all I know
537 it is possible for a single vendor to take control over the
538 specification. But it seem unlikely.
</p
>
540 <p
><strong
>Maintained by open not-for-profit organisation?
</strong
></p
>
542 <p
>Assuming that the Xiph foundation is the organisation its web pages
543 claim it to be, this point is fulfilled. If Xiph foundation is
544 controlled by a single vendor, it isn
't, but I have not found any
545 documentation indicating this.
</p
>
547 <p
>According to
548 <a href=
"http://media.hiof.no/diverse/fad/rapport_4.pdf
">a report
</a
>
549 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
550 government, the Xiph foundation is a non-commercial organisation and
551 the development process is open, transparent and non-Discrimatory.
552 Until proven otherwise, I believe it make most sense to believe the
553 report is correct.
</p
>
555 <p
><strong
>Specification freely available?
</strong
></p
>
557 <p
>The specification for the
<a href=
"http://www.xiph.org/ogg/doc/
">Ogg
558 container format
</a
> and both the
559 <a href=
"http://www.xiph.org/vorbis/doc/
">Vorbis
</a
> and
560 <a href=
"http://theora.org/doc/
">Theora
</a
> codeces are available on
561 the web. This are the terms in the Vorbis and Theora specification:
565 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
566 specifications, whether in private, public, or corporate
567 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
568 the right to set the Ogg [Vorbis/Theora] specification and certify
569 specification compliance.
573 <p
>The Ogg container format is specified in IETF
574 <a href=
"http://www.xiph.org/ogg/doc/rfc3533.txt
">RFC
3533</a
>, and
575 this is the term:
<p
>
579 <p
>This document and translations of it may be copied and furnished to
580 others, and derivative works that comment on or otherwise explain it
581 or assist in its implementation may be prepared, copied, published and
582 distributed, in whole or in part, without restriction of any kind,
583 provided that the above copyright notice and this paragraph are
584 included on all such copies and derivative works. However, this
585 document itself may not be modified in any way, such as by removing
586 the copyright notice or references to the Internet Society or other
587 Internet organizations, except as needed for the purpose of developing
588 Internet standards in which case the procedures for copyrights defined
589 in the Internet Standards process must be followed, or as required to
590 translate it into languages other than English.
</p
>
592 <p
>The limited permissions granted above are perpetual and will not be
593 revoked by the Internet Society or its successors or assigns.
</p
>
596 <p
>All these terms seem to allow unlimited distribution and use, an
597 this term seem to be fulfilled. There might be a problem with the
598 missing permission to distribute modified versions of the text, and
599 thus reuse it in other specifications. Not quite sure if that is a
600 requirement for the Digistan definition.
</p
>
602 <p
><strong
>Royalty-free?
</strong
></p
>
604 <p
>There are no known patent claims requiring royalties for the Ogg
606 <a href=
"http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=
65782">MPEG-LA
</a
>
608 <a href=
"http://yro.slashdot.org/story/
10/
04/
30/
237238/Steve-Jobs-Hints-At-Theora-Lawsuit
">Steve
609 Jobs
</a
> in Apple claim to know about some patent claims (submarine
610 patents) against the Theora format, but no-one else seem to believe
611 them. Both Opera Software and the Mozilla Foundation have looked into
612 this and decided to implement Ogg Theora support in their browsers
613 without paying any royalties. For now the claims from MPEG-LA and
614 Steve Jobs seem more like FUD to scare people to use the H
.264 codec
615 than any real problem with Ogg Theora.
</p
>
617 <p
><strong
>No constraints on re-use?
</strong
></p
>
619 <p
>I am not aware of any constraints on re-use.
</p
>
621 <p
><strong
>Conclusion
</strong
></p
>
623 <p
>3 of
5 requirements seem obviously fulfilled, and the remaining
2
624 depend on the governing structure of the Xiph foundation. Given the
625 background report used by the Norwegian government, I believe it is
626 safe to assume the last two requirements are fulfilled too, but it
627 would be nice if the Xiph foundation web site made it easier to verify
630 <p
>It would be nice to see other analysis of other specifications to
631 see if they are free and open standards.
</p
>
636 <title>The many definitions of a open standard
</title>
637 <link>http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html
</link>
638 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html
</guid>
639 <pubDate>Mon,
27 Dec
2010 14:
45:
00 +
0100</pubDate>
641 <p
>One of the reasons I like the Digistan definition of
642 "<a href=
"http://www.digistan.org/open-standard:definition
">Free and
643 Open Standard
</a
>" is that this is a new term, and thus the meaning of
644 the term has been decided by Digistan. The term
"Open Standard
" has
645 become so misunderstood that it is no longer very useful when talking
646 about standards. One end up discussing which definition is the best
647 one and with such frame the only one gaining are the proponents of
648 de-facto standards and proprietary solutions.
</p
>
650 <p
>But to give us an idea about the diversity of definitions of open
651 standards, here are a few that I know about. This list is not
652 complete, but can be a starting point for those that want to do a
653 complete survey. More definitions are available on the
654 <a href=
"http://en.wikipedia.org/wiki/Open_standard
">wikipedia
655 page
</a
>.
</p
>
657 <p
>First off is my favourite, the definition from the European
658 Interoperability Framework version
1.0. Really sad to notice that BSA
659 and others has succeeded in getting it removed from version
2.0 of the
660 framework by stacking the committee drafting the new version with
661 their own people. Anyway, the definition is still available and it
662 include the key properties needed to make sure everyone can use a
663 specification on equal terms.
</p
>
667 <p
>The following are the minimal characteristics that a specification
668 and its attendant documents must have in order to be considered an
669 open standard:
</p
>
673 <li
>The standard is adopted and will be maintained by a not-for-profit
674 organisation, and its ongoing development occurs on the basis of an
675 open decision-making procedure available to all interested parties
676 (consensus or majority decision etc.).
</li
>
678 <li
>The standard has been published and the standard specification
679 document is available either freely or at a nominal charge. It must be
680 permissible to all to copy, distribute and use it for no fee or at a
681 nominal fee.
</li
>
683 <li
>The intellectual property - i.e. patents possibly present - of
684 (parts of) the standard is made irrevocably available on a royalty-
685 free basis.
</li
>
687 <li
>There are no constraints on the re-use of the standard.
</li
>
692 <p
>Another one originates from my friends over at
693 <a href=
"http://www.dkuug.dk/
">DKUUG
</a
>, who coined and gathered
694 support for
<a href=
"http://www.aaben-standard.dk/
">this
695 definition
</a
> in
2004. It even made it into the Danish parlament as
696 <a href=
"http://www.ft.dk/dokumenter/tingdok.aspx?/samling/
20051/beslutningsforslag/B103/som_fremsat.htm
">their
697 definition of a open standard
</a
>. Another from a different part of
698 the Danish government is available from the wikipedia page.
</p
>
702 <p
>En åben standard opfylder følgende krav:
</p
>
706 <li
>Veldokumenteret med den fuldstændige specifikation offentligt
707 tilgængelig.
</li
>
709 <li
>Frit implementerbar uden økonomiske, politiske eller juridiske
710 begrænsninger på implementation og anvendelse.
</li
>
712 <li
>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
713 "standardiseringsorganisation
") via en åben proces.
</li
>
719 <p
>Then there is
<a href=
"http://www.fsfe.org/projects/os/def.html
">the
720 definition
</a
> from Free Software Foundation Europe.
</p
>
724 <p
>An Open Standard refers to a format or protocol that is
</p
>
728 <li
>subject to full public assessment and use without constraints in a
729 manner equally available to all parties;
</li
>
731 <li
>without any components or extensions that have dependencies on
732 formats or protocols that do not meet the definition of an Open
733 Standard themselves;
</li
>
735 <li
>free from legal or technical clauses that limit its utilisation by
736 any party or in any business model;
</li
>
738 <li
>managed and further developed independently of any single vendor
739 in a process open to the equal participation of competitors and third
742 <li
>available in multiple complete implementations by competing
743 vendors, or as a complete implementation equally available to all
750 <p
>A long time ago, SUN Microsystems, now bought by Oracle, created
752 <a href=
"http://blogs.sun.com/dennisding/resource/Open%
20Standard%
20Definition.pdf
">Open
753 Standards Checklist
</a
> with a fairly detailed description.
</p
>
756 <p
>Creation and Management of an Open Standard
760 <li
>Its development and management process must be collaborative and
765 <li
>Participation must be accessible to all those who wish to
766 participate and can meet fair and reasonable criteria
767 imposed by the organization under which it is developed
768 and managed.
</li
>
770 <li
>The processes must be documented and, through a known
771 method, can be changed through input from all
772 participants.
</li
>
774 <li
>The process must be based on formal and binding commitments for
775 the disclosure and licensing of intellectual property rights.
</li
>
777 <li
>Development and management should strive for consensus,
778 and an appeals process must be clearly outlined.
</li
>
780 <li
>The standard specification must be open to extensive
781 public review at least once in its life-cycle, with
782 comments duly discussed and acted upon, if required.
</li
>
790 <p
>Use and Licensing of an Open Standard
</p
>
793 <li
>The standard must describe an interface, not an implementation,
794 and the industry must be capable of creating multiple, competing
795 implementations to the interface described in the standard without
796 undue or restrictive constraints. Interfaces include APIs,
797 protocols, schemas, data formats and their encoding.
</li
>
799 <li
> The standard must not contain any proprietary
"hooks
" that create
800 a technical or economic barriers
</li
>
802 <li
>Faithful implementations of the standard must
803 interoperate. Interoperability means the ability of a computer
804 program to communicate and exchange information with other computer
805 programs and mutually to use the information which has been
806 exchanged. This includes the ability to use, convert, or exchange
807 file formats, protocols, schemas, interface information or
808 conventions, so as to permit the computer program to work with other
809 computer programs and users in all the ways in which they are
810 intended to function.
</li
>
812 <li
>It must be permissible for anyone to copy, distribute and read the
813 standard for a nominal fee, or even no fee. If there is a fee, it
814 must be low enough to not preclude widespread use.
</li
>
816 <li
>It must be possible for anyone to obtain free (no royalties or
817 fees; also known as
"royalty free
"), worldwide, non-exclusive and
818 perpetual licenses to all essential patent claims to make, use and
819 sell products based on the standard. The only exceptions are
820 terminations per the reciprocity and defensive suspension terms
821 outlined below. Essential patent claims include pending, unpublished
822 patents, published patents, and patent applications. The license is
823 only for the exact scope of the standard in question.
827 <li
> May be conditioned only on reciprocal licenses to any of
828 licensees
' patent claims essential to practice that standard
829 (also known as a reciprocity clause)
</li
>
831 <li
> May be terminated as to any licensee who sues the licensor
832 or any other licensee for infringement of patent claims
833 essential to practice that standard (also known as a
834 "defensive suspension
" clause)
</li
>
836 <li
> The same licensing terms are available to every potential
842 <li
>The licensing terms of an open standards must not preclude
843 implementations of that standard under open source licensing terms
844 or restricted licensing terms
</li
>
850 <p
>It is said that one of the nice things about standards is that
851 there are so many of them. As you can see, the same holds true for
852 open standard definitions. Most of the definitions have a lot in
853 common, and it is not really controversial what properties a open
854 standard should have, but the diversity of definitions have made it
855 possible for those that want to avoid a level marked field and real
856 competition to downplay the significance of open standards. I hope we
857 can turn this tide by focusing on the advantages of Free and Open
863 <title>What standards are Free and Open as defined by Digistan?
</title>
864 <link>http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html
</link>
865 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html
</guid>
866 <pubDate>Thu,
30 Dec
2010 23:
15:
00 +
0100</pubDate>
868 <p
>After trying to
869 <a href=
"http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
">compare
870 Ogg Theora
</a
> to
871 <a href=
"http://www.digistan.org/open-standard:definition
">the Digistan
872 definition
</a
> of a free and open standard, I concluded that this need
873 to be done for more standards and started on a framework for doing
874 this. As a start, I want to get the status for all the standards in
875 the Norwegian reference directory, which include UTF-
8, HTML, PDF, ODF,
876 JPEG, PNG, SVG and others. But to be able to complete this in a
877 reasonable time frame, I will need help.
</p
>
879 <p
>If you want to help out with this work, please visit
880 <a href=
"http://wiki.nuug.no/grupper/standard/digistan-analyse
">the
881 wiki pages I have set up for this
</a
>, and let me know that you want
882 to help out. The IRC channel #nuug on irc.freenode.net is a good
883 place to coordinate this for now, as it is the IRC channel for the
884 NUUG association where I have created the framework (I am the leader
885 of the Norwegian Unix User Group).
</p
>
887 <p
>The framework is still forming, and a lot is left to do. Do not be
888 scared by the sketchy form of the current pages. :)
</p
>
projects / homepage.git / blob