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 standard
</title>
5 <description>Entries tagged standard
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>ODF-bruk i staten, ikke helt på plass
</title>
11 <link>http://people.skolelinux.org/pere/blog/ODF_bruk_i_staten__ikke_helt_p__plass.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/ODF_bruk_i_staten__ikke_helt_p__plass.html
</guid>
13 <pubDate>Thu,
22 Jan
2009 23:
00:
00 +
0100</pubDate>
14 <description><p
>I går publiserte
15 <a href=
"http://universitas.no/nyhet/
52776/
">Universitas
</a
>,
16 <a href=
"http://www.dagensit.no/trender/article1588462.ece
">Dagens-IT
</a
>
17 og
<a href=
"http://www.idg.no/computerworld/article118622.ece
">Computerworld
18 Norge
</a
> en sak om at de ansatte ved Universitetet i Oslo ikke følger
19 regjeringens pålegg om å publisere i HTML, PDF eller ODF. Det er bra
20 at det kommer litt fokus på dette, og jeg håper noen journalister tar
21 en titt på de andre statlige instansene også.
</p
>
23 <p
>Skulle ønske det var en enkel måte å sjekke om ODF-dokumenter er i
24 henholdt til ODF-spesifikasjonen, og en måte å teste om programmer som
25 hevder å støtte ODF forstår alle delene av ODF-spesifikasjonen.
26 Kjenner kun til ufullstendige løsninger for slikt.
</p
>
31 <title>Fri og åpen standard, slik Digistan ser det
</title>
32 <link>http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html
</link>
33 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html
</guid>
34 <pubDate>Sat,
31 Jan
2009 23:
10:
00 +
0100</pubDate>
35 <description><p
>Det er mange ulike definisjoner om hva en åpen standard er for noe,
36 og NUUG hadde
<a href=
"http://www.nuug.no/dokumenter/standard-presse-def-
200506.txt
">en
37 pressemelding om dette sommeren
2005</a
>. Der ble definisjonen til
38 <a href=
"http://www.aaben-standard.dk/
">DKUUG
</a
>,
39 <a href=
"http://europa.eu.int/idabc/servlets/Doc?id=
19529">EU-kommissionens
40 European Interoperability Framework ( side
9)
</a
> og
41 <a href=
"http://www.teknologiradet.no/files/
7polert_copy.htm
">teknologirådet
</a
> omtalt.
</p
>
43 <p
>Siden den gang har regjeringens standardiseringsråd dukket opp, og de
44 ser ut til å har tatt utgangspunkt i EU-kommisjonens definisjon i
45 <a href=
"http://www.regjeringen.no/nb/dep/fad/kampanjer/standardiseringsradet/arbeidsmetodikk.html?id=
476407">sin
46 arbeidsmetodikk
</a
>. Personlig synes jeg det er en god ide, da
47 kravene som stilles der gjør at alle markedsaktører får like vilkår,
48 noe som kommer kundene til gode ved hjelp av økt konkurranse.
</p
>
50 <p
>I sommer kom det en ny definisjon på banen.
51 <a href=
"http://www.digistan.org/
">Digistan
</a
> lanserte
52 <a href=
"http://www.digistan.org/open-standard:definition
">en
53 definisjon på en fri og åpen standard
</a
>. Jeg liker måten de bryter
54 ut av diskusjonen om hva som kreves for å kalle noe en åpen standard
55 ved å legge på et ord og poengtere at en standard som er både åpen og
56 fri har noen spesielle krav. Her er den definisjonen etter rask
57 oversettelse fra engelsk til norsk av meg:
</p
>
60 <p
><strong
>Definisjonen av en fri og åpen standard
</strong
></p
>
62 <p
>Den digitale standardorganisasjonen definierer fri og åpen standard
65 <li
>En fri og åpen standard er immun for leverandørinnlåsing i alle
66 stadier av dens livssyklus. Immuniteten fra leverandørinnlåsing gjør
67 det mulig å fritt bruke, forbedre, stole på og utvide en standard over
69 <li
>Standarden er adoptert og vil bli vedlikeholdt av en ikke-kommersiell
70 organisasjon, og dens pågående utvikling gjøres med en åpen
71 beslutningsprosedyre som er tilgjengelig for alle som er interessert i
73 <li
>Standarden er publisert og spesifikasjonsdokumentet er fritt
74 tilgjengelig. Det må være tillatt for alle å kopiere, distribuere og
75 bruke den uten begresninger.
</li
>
76 <li
>Patentene som muligens gjelder (deler av) standarden er gjort
77 ugjenkallelig tilgjengelig uten krav om betaling.
</li
>
78 <li
>Det er ingen begresninger i gjenbruk av standarden.
</li
>
80 <p
>Det økonomiske resultatet av en fri og åpen standard, som kan
81 måles, er at det muliggjør perfekt konkurranse mellom leverandører av
82 produkter basert på standarden.
</p
>
85 <p
>(Tar gjerne imot forbedringer av oversettelsen.)
</p
>
90 <title>Hva er egentlig en åpen standard?
</title>
91 <link>http://people.skolelinux.org/pere/blog/Hva_er_egentlig_en__pen_standard_.html
</link>
92 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Hva_er_egentlig_en__pen_standard_.html
</guid>
93 <pubDate>Sat,
28 Mar
2009 10:
50:
00 +
0100</pubDate>
94 <description><p
>Jeg møter alle slags interessante mennesker på min vei, og et møte
95 jeg lærte mye av var å treffe på en svært kompetent IT-fyr som
96 benektet ting jeg anser som åpenbart og selvfølgelig når det gjelder
97 standarder. Det var interessant, da det fikk meg til å tenke litt
98 nøyere på hvilke mekanismer som ligger til grunn for at noe oppfattes
99 som en standard. Det hele startet med arbeid rundt integrering av NSS
100 LDAP mot Active Directory, og problemer som oppstår pga. at Active
101 Directory ikke følger LDAP-spesifikasjonen som dokumentert i RFCer fra
102 IETF (konkret, AD returnerer kun et subset av attributter hvis det er
103 mer enn
1500 atributter av en gitt type i et LDAP-objekt, og en må be
104 om resten i bolker av
1500). Jeg hevdet måten dette ble gjort på brøt
105 med LDAP-spesifikasjonen, og henviste til hvor i LDAP-spesifikasjonen
106 fra IETF det sto at oppførselen til AD ikke fulgte
107 LDAP-spesifikasjonen. AD-spesialisten overrasket meg da ved å
108 fortelle at IETF var ikke de som definerte LDAP-spesifikasjonen, og at
109 Active Directory ikke brøt den virkelige LDAP-spesifikasjonen som han
110 mente lå til grunn. Jeg ble spesielt overrasket over denne
111 tilnærmingen til problemstillingen, da til og med Microsoft så vidt
112 jeg kan se anerkjenner IETF som organisasjonen som definerer
113 LDAP-spesifikasjonen. Jeg fikk aldri spurt hvem han mente sto bak den
114 egentlige LDAP-spesifikasjonen, da det var irrelevant for problemet vi
115 måtte løse (få Linux og AD til å fungere sammen). Dette møtet
116 fortalte meg uansett at det ikke er gitt at alle aktører er enige om
117 hva en standard er, og hva som er kilden til en gitt standard. Det er
118 vanskelig å enes om felles standarder før en først enes om hvem som
119 bestemmer hva en gitt standard innebærer.
</p
>
121 <p
>Hva er så en standard? I sin abstrakte form er det noe å samles
122 om. På engelsk er en av betydningene fane brukt i krig, du vet, den
123 type fane en samlet seg rundt på kamplassen i riddertiden. En
124 standard definerer altså et felleskap, noen som har noe felles. Det
125 er naturligvis mange måter å utgjøre et felleskap på. En kan
126 f.eks. enes om å gjøre alt slik som Ole gjør det, og dermed si at Oles
127 oppførsel er standard. Hver gang Ole endrer oppførsel endrer også
128 standarden seg uten noe mer organisering og prosedyre. En variant av
129 dette er å gjøre slik som Ole har gjort det i stedet for slik Ole til
130 enhver til gjør noe. Dette er ofte litt enklere å forholde seg til,
131 da en slipper å sjekke med Ole hver gang for å vite hvordan ting skal
132 gjøres nå, men hvis det Ole gjorde noe dumt den gang en bestemte seg
133 for å følge Ole, så er det vanskeligere å få endret oppførsel for å
134 unngå dette dumme.
</p
>
136 <p
>En kan også ta det et skritt videre, og istedet for å basere seg på
137 enkeltpersoners oppførsel sette seg ned og bli enige om hvordan en
138 skal gjøre ting, dvs. lage et felleskap basert på konsensus. Dette
139 tar naturligvis litt mer tid (en må diskutere ting i forkant før en
140 kan sette igang), men det kan bidra til at den oppførselen en
141 planlegger å benytte seg av er mer gjennomtenkt. Det ender også
142 typisk opp med en beskrivelse av ønsket oppførsel som flere kan forstå
143 - da flere har vært involvert i å utarbeide beskrivelsen.
</p
>
145 <p
>Dette er dessverre ikke alt som trengs for å forstå hva en åpen
146 standard er for noe. Der alle kan se på hvordan folk oppfører seg, og
147 dermed har valget om de vil oppføre seg likt eller ikke, så er det
148 endel juridiske faktorer som gjør det hele mer komplisert -
149 opphavsretten og patentlovgivningen for å være helt konkret. For å gi
150 et eksempel. Hvis noen blir enige om å alltid plystre en bestemt
151 melodi når de møtes, for å identifisere hverandre, så kan
152 opphavsretten brukes til å styre hvem som får lov til å gjøre dette.
153 De har standardisert hvordan de kjenner igjen alle som følger denne
154 standarden, men ikke alle har nødvendigvis lov til å følge den.
155 Musikk er opphavsrettsbeskyttet, og fremføring av musikk i
156 offentligheten er opphavsmannens enerett (dvs. et monopol). Det vil i
157 sin ytterste konsekvens si at alle som skal plystre en
158 opphavsrettsbeskyttet melodi i det offentlige rom må ha godkjenning
159 fra opphavsmannen. Har en ikke dette, så bryter en loven og kan
160 straffes. Det er dermed mulig for opphavsmannen å kontrollere hvem
161 som får lov til å benytte seg av denne standarden. En annen variant
162 er hvis en standard er dokumentert, så er dokumentet som definerer
163 standarden (spesifikasjonen) beskyttet av opphavsretten, og det er
164 dermed mulig for rettighetsinnehaver å begrense tilgang til
165 spesifikasjonen, og slik styre hvem som kan ta i bruk standarden på
168 <p
>Der opphavsretten innvilger et monopol på kunstneriske uttrykk med
169 verkshøyde, innvilger patentlovgivningen monopol på ideer. Hvis en
170 slik patentert idé (fortrinnsvis uttrykt i en teknisk innretning, men
171 det er kompliserende faktorer som gjør at det ikke er et krav) trengs
172 for å ta i bruk en standard, så vil den som innehar patent kunne styre
173 hvem som får ta i bruk standarden. Det er dermed ikke gitt at alle
174 kan delta i et standard-felleskap, og hvis de kan delta, så er det
175 ikke sikkert at det er på like vilkår. F.eks. kan rettighetsinnehaver
176 sette vilkår som gjør at noen faller utenfor, det være seg av
177 finansielle, avtalemessige eller prinsipielle årsaker. Vanlige slike
178 vilkår er
"må betale litt for hver kunde/bruker
" som utelukker de som
179 gir bort en løsning gratis og
"må gi fra seg retten til å håndheve
180 sine egne patentrettigheter ovenfor rettighetshaver
" som utelukker
181 alle som ønsker å beholde den muligheten.
</p
>
183 <p
>En åpen standard innebærer for meg at alle kan få innsikt i en
184 komplett beskrivelse av oppførsel som standarden skal dekke, og at
185 ingen kan nektes å benytte seg av standarden. Noen mener at det
186 holder at alle med tilstrekkelig finansiering kan få tilgang til
187 spesifikasjonen og at en kun har finansielle krav til bruk.
188 Pga. denne konflikten har et nytt begrep spredt seg de siste årene,
189 nemlig fri og åpen standard, der en har gjort det klart at alle må ha
190 komplett og lik tilgang til spesifikasjoner og retten til å gjøre bruk
191 av en standard for at en standard skal kunne kalles fri og åpen.
</p
>
196 <title>Standardize on protocols and formats, not vendors and applications
</title>
197 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
198 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
199 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
200 <description><p
>Where I work at the University of Oslo, one decision stand out as a
201 very good one to form a long lived computer infrastructure. It is the
202 simple one, lost by many in todays computer industry: Standardize on
203 open network protocols and open exchange/storage formats, not applications.
204 Applications come and go, while protocols and files tend to stay, and
205 thus one want to make it easy to change application and vendor, while
206 avoiding conversion costs and locking users to a specific platform or
207 application.
</p
>
209 <p
>This approach make it possible to replace the client applications
210 independently of the server applications. One can even allow users to
211 use several different applications as long as they handle the selected
212 protocol and format. In the normal case, only one client application
213 is recommended and users only get help if they choose to use this
214 application, but those that want to deviate from the easy path are not
215 blocked from doing so.
</p
>
217 <p
>It also allow us to replace the server side without forcing the
218 users to replace their applications, and thus allow us to select the
219 best server implementation at any moment, when scale and resouce
220 requirements change.
</p
>
222 <p
>I strongly recommend standardizing - on open network protocols and
223 open formats, but I would never recommend standardizing on a single
224 application that do not use open network protocol or open formats.
</p
>
229 <title>Hvorfor jeg ikke bruker eFaktura
</title>
230 <link>http://people.skolelinux.org/pere/blog/Hvorfor_jeg_ikke_bruker_eFaktura.html
</link>
231 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Hvorfor_jeg_ikke_bruker_eFaktura.html
</guid>
232 <pubDate>Thu,
23 Apr
2009 23:
00:
00 +
0200</pubDate>
233 <description><p
>Telenors annonsering om å kreve
35 kroner i gebyr fra alle som
234 ønsker papirfaktura har satt sinnene i kok, og pressedekningen så
235 langt snakker om at eldre og folk som ikke behersker data vil få en
236 urimelig ekstrakostnad. Jeg tror ikke jeg passer inn i noen av de
237 kategoriene, men velger å holde meg unna eFaktura - som er det
238 Telenor ønsker å få folk over på - pga. systemets egenskaper.
</p
>
240 <p
>Slik jeg har sett eFaktura til forbrukere så langt, så sender
241 selger en elektronisk beskjed til kundens bank, som legger ut
242 informasjon om fakturaen i nettbanken for godkjenning. Personlig
243 ville jeg sett det som mer naturlig at det gikk en elektronisk beskjed
244 fra selger til kunde, dvs meg, og at jeg så kunne bruke den videre
245 mot banken eller andre hvis jeg ønsket dette. Mine innkjøp og
246 regninger er jo en sak mellom meg og mine leverandører, ikke en sak
247 mellom min bank og mine leverandører. Kun hvis jeg ønsker å betale
248 fakturaen skal banken involveres. En faktura bør jo inn i
249 regnskapet, og jeg ønsker mulighet til å legge det inn der. Når
250 fakturaen sendes til banken i stedet for meg, blir det vanskeligere.
251 Hele eFaktura-modellen virker på meg som en umyndiggjøring av meg
254 <p
>I tillegg har jeg ikke vært i stand til å finne
255 eFaktura-formatets spesifikasjon, og det ser ut til at utsending av
256 slike krever dyre avtaler med bankene for å få lov til å sende ut
257 eFaktura til kunder. Jeg ser vel helst at fakturering på
258 elektroniske formater kan gjøres f.eks. via epost eller HTTP uten å
259 måtte betale mellommenn for retten til å lever ut en faktura, og
260 liker rett og slett ikke dagens faktureringsmodeller.
</p
>
265 <title>Standarder fungerer best når en samler seg rundt dem
</title>
266 <link>http://people.skolelinux.org/pere/blog/Standarder_fungerer_best_n_r_en_samler_seg_rundt_dem.html
</link>
267 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standarder_fungerer_best_n_r_en_samler_seg_rundt_dem.html
</guid>
268 <pubDate>Tue,
19 May
2009 11:
30:
00 +
0200</pubDate>
269 <description><p
>En standard er noe man samler seg rundt, ut fra ideen om at en får
270 fordeler når mange står sammen. Jo flere som står sammen, jo
271 bedre. Når en vet dette, blir det litt merkelig å lese noen av
272 uttalelsene som er kommet inn til
273 <a href=
"http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2/horingsuttalelser.html?id=
549423">høringen
274 om versjon
2 av statens referansekatalog over standarder
</a
>. Blant
275 annet Abelia, NHO og Microsoft tror det er lurt med flere standarder
276 innenfor samme område. Det blir som å si at det er fint om Norge
277 standardiserte både på A4- og Letter-størrelser på arkene, ulik
278 sporvidde på jernbaneskinnene, meter og fot som lengemål, eller
279 høyre- og venstrekjøring - slik at en kan konkurrere på hvilken
280 standard som er best. De fleste forstår heldigvis at dette ikke
281 bidrar positivt.
</p
>
286 <title>Microsofts misvisende argumentasjon rundt multimediaformater
</title>
287 <link>http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html
</link>
288 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Microsofts_misvisende_argumentasjon_rundt_multimediaformater.html
</guid>
289 <pubDate>Fri,
26 Jun
2009 13:
30:
00 +
0200</pubDate>
290 <description><p
>I
291 <a href=
"http://www.regjeringen.no/upload/FAD/Vedlegg/Hoeringer/Refkat_V2/MicrosoftNorge.pdf
">Microsoft
292 sin høringsuttalelse
</a
> til
293 <a href=
"http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2.html?id=
549422">forslag
294 til versjon
2 av statens referansekatalog over standarder
</a
>, lirer
295 de av seg følgende FUD-perle:
</p
>
297 <p
><blockquote
>"Vorbis, OGG, Theora og FLAC er alle tekniske
298 spesifikasjoner overordnet styrt av xiph.org, som er en
299 ikke-kommersiell organisasjon. Etablerte og anerkjente
300 standardiseringsorganisasjoner, som Oasis, W3C og Ecma, har en godt
301 innarbeidet vedlikeholds- og forvaltningsprosess av en standard.
302 Det er derimot helt opp til hver enkelt organisasjon å bestemme
303 hvordan tekniske spesifikasjoner videreutvikles og endres, og disse
304 spesifikasjonene bør derfor ikke defineres som åpne
305 standarder.
"</blockquote
></p
>
307 <p
>De vokter seg vel for å nevne den anerkjente
308 standardiseringsorganisasjonen IETF, som er organisasjonen bak HTTP,
309 IP og det meste av protokoller på Internet, og RFC-standardene som
310 IETF står bak. Ogg er spesifisert i
311 <a href=
"http://ietf.org/rfc/rfc3533.txt
">RFC
3533</a
>, og er uten
312 tvil å anse som en åpen standard. Vorbis er
313 <a href=
"http://ietf.org/rfc/rfc5215.txt
">RFC
5215</a
>. Theora er
315 under standardisering via IETF, med
316 <a href=
"http://svn.xiph.org/trunk/theora/doc/draft-ietf-avt-rtp-theora-
00.txt
">siste
317 utkast publisert
2006-
07-
21</a
> (riktignok er dermed teksten ikke
318 skrevet i stein ennå, men det blir neppe endringer som ikke er
319 bakoverkompatibel). De kan være inne på noe når det gjelder FLAC da
320 jeg ikke finner tegn til at
<a
321 href=
"http://flac.sourceforge.net/format.html
">spesifikasjonen
322 tilgjengelig på web
</a
> er på tur via noen
323 standardiseringsorganisasjon, men i og med at folkene bak Ogg, Theora
324 og Vorbis også har involvert seg i Flac siden
2003, så ser jeg ikke
325 bort fra at også den organiseres via IETF. Jeg kjenner personlig lite
328 <p
>Uredelig argumentasjon bør en holde seg for god til å komme med,
329 spesielt når det er så enkelt i dagens Internet-hverdag å gå
330 misvisende påstander etter i sømmene.
</p
>
335 <title>Regjerningen forlater prinsippet om ingen royalty-betaling i standardkatalogen versjon
2</title>
336 <link>http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html
</link>
337 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Regjerningen_forlater_prinsippet_om_ingen_royalty_betaling_i_standardkatalogen_versjon_2.html
</guid>
338 <pubDate>Mon,
6 Jul
2009 21:
00:
00 +
0200</pubDate>
339 <description><p
>Jeg ble glad da regjeringen
340 <a href=
"http://www.digi.no/
817635/her-er-statens-nye-it-standarder
">annonserte
</a
>
342 <a href=
"http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Referansekatalogen_versjon2.pdf
">statens
343 referansekatalog over standarder
</a
>, men trist da jeg leste hva som
344 faktisk var vedtatt etter
345 <a href=
"http://www.regjeringen.no/nb/dep/fad/dok/horinger/horingsdokumenter/
2009/horing---referansekatalog-versjon-
2.html
">høringen
</a
>.
346 De fleste av de valgte åpne standardene er gode og vil bidra til at
347 alle kan delta på like vilkår i å lage løsninger for staten, men
348 noen av dem blokkerer for de som ikke har anledning til å benytte
349 spesifikasjoner som krever betaling for bruk (såkalt
350 royalty-betaling). Det gjelder spesifikt for H
.264 for video og MP3
351 for lyd. Så lenge bruk av disse var valgfritt mens Ogg Theora og Ogg
352 Vorbis var påkrevd, kunne alle som ønsket å spille av video og lyd
353 fra statens websider gjøre dette uten å måtte bruke programmer der
354 betaling for bruk var nødvendig. Når det nå er gjort valgfritt for
355 de statlige etatene å bruke enten H
.264 eller Theora (og MP3 eler
356 Vorbis), så vil en bli tvunget til å forholde seg til
357 royalty-belastede standarder for å få tilgang til videoen og
360 <p
>Det gjør meg veldig trist at regjeringen har forlatt prinsippet om
361 at alle standarder som ble valgt til å være påkrevd i katalogen skulle
362 være uten royalty-betaling. Jeg håper det ikke betyr at en har mistet
363 all forståelse for hvilke prinsipper som må følges for å oppnå
364 likeverdig konkurranse mellom aktørene i IT-bransjen. NUUG advarte
366 <a href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2
">sin
367 høringsuttalelse
</a
>, men ser ut til å ha blitt ignorert.
</p
>
369 <p
>Oppdatering
2012-
06-
29: Kom over
<ahref=
"
370 http://www.regjeringen.no/upload/FAD/Vedlegg/IKT-politikk/Refkat_v2.pdf
">en
371 rapport til FAD
</a
> fra da versjon
1 av katalogen ble vedtatt, og der
372 er det tydelig at problemstillingen var kjent og forstått.
</p
>
377 <title>Regjerningens oppsummering av høringen om standardkatalogen versjon
2</title>
378 <link>http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html
</link>
379 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Regjerningens_oppsummering_av_h_ringen_om_standardkatalogen_versjon_2.html
</guid>
380 <pubDate>Thu,
9 Jul
2009 14:
40:
00 +
0200</pubDate>
381 <description><p
>For å forstå mer om hvorfor standardkatalogens versjon
2 ble som
382 den ble, har jeg bedt om kopi fra FAD av dokumentene som ble lagt frem
383 for regjeringen da de tok sin avgjørelse. De er nå lagt ut på NUUGs
384 wiki, direkte tilgjengelig via
"<a
385 href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2?action=AttachFile
&do=get
&target=kongelig-resolusjon.pdf
">Referansekatalogen
386 v2.0 - Oppsummering av høring
</a
>" og
"<a
387 href=
"http://wiki.nuug.no/uttalelser/
200901-standardkatalog-v2?action=AttachFile
&do=get
&target=kongelig-resolusjon-katalogutkast.pdf
">Referansekatalog
388 for IT-standarder i offentlig sektor Versjon
2.0, dd.mm.åååå -
389 UTKAST
</a
>".
</p
>
391 <p
>Det er tre ting jeg merker meg i oppsummeringen fra
392 høringsuttalelsen da jeg skummet igjennom den. Det første er at
393 forståelsen av hvordan programvarepatenter påvirker fri
394 programvareutvikling også i Norge når en argumenterer med at
395 royalty-betaling ikke er et relevant problem i Norge. Det andre er at
396 FAD ikke har en prinsipiell forståelse av verdien av en enkelt
397 standard innenfor hvert område. Det siste er at påstander i
398 høringsuttalelsene ikke blir etterprøvd (f.eks. påstanden fra
399 Microsoft om hvordan Ogg blir standardisert og påstanden fra
400 politidirektoratet om patentproblemer i Theora).
</p
>
405 <title>ISO still hope to fix OOXML
</title>
406 <link>http://people.skolelinux.org/pere/blog/ISO_still_hope_to_fix_OOXML.html
</link>
407 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/ISO_still_hope_to_fix_OOXML.html
</guid>
408 <pubDate>Sat,
8 Aug
2009 14:
00:
00 +
0200</pubDate>
409 <description><p
>According to
<a
410 href=
"http://twerner.blogspot.com/
2009/
08/defects-of-office-open-xml.html
">a
411 blog post from Torsten Werner
</a
>, the current defect report for ISO
412 29500 (ISO OOXML) is
809 pages. His interesting point is that the
413 defect report is
71 pages more than the full ODF
1.1 specification.
414 Personally I find it more interesting that ISO still believe ISO OOXML
415 can be fixed in ISO. Personally, I believe it is broken beyon repair,
416 and I completely lack any trust in ISO for being able to get anywhere
417 close to solving the problems. I was part of the Norwegian committee
418 involved in the OOXML fast track process, and was not impressed with
419 Standard Norway and ISO in how they handled it.
</p
>
421 <p
>These days I focus on ODF instead, which seem like a specification
422 with the future ahead of it. We are working in NUUG to organise a ODF
423 seminar this autumn.
</p
>
428 <title>Relative popularity of document formats (MS Office vs. ODF)
</title>
429 <link>http://people.skolelinux.org/pere/blog/Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html
</link>
430 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Relative_popularity_of_document_formats__MS_Office_vs__ODF_.html
</guid>
431 <pubDate>Wed,
12 Aug
2009 15:
50:
00 +
0200</pubDate>
432 <description><p
>Just for fun, I did a search right now on Google for a few file ODF
433 and MS Office based formats (not to be mistaken for ISO or ECMA
434 OOXML), to get an idea of their relative usage. I searched using
435 'filetype:odt
' and equvalent terms, and got these results:
</P
>
438 <tr
><th
>Type
</th
><th
>ODF
</th
><th
>MS Office
</th
></tr
>
439 <tr
><td
>Tekst
</td
> <td
>odt:
282000</td
> <td
>docx:
308000</td
></tr
>
440 <tr
><td
>Presentasjon
</td
> <td
>odp:
75600</td
> <td
>pptx:
183000</td
></tr
>
441 <tr
><td
>Regneark
</td
> <td
>ods:
26500 </td
> <td
>xlsx:
145000</td
></tr
>
444 <p
>Next, I added a
'site:no
' limit to get the numbers for Norway, and
445 got these numbers:
</p
>
448 <tr
><th
>Type
</th
><th
>ODF
</th
><th
>MS Office
</th
></tr
>
449 <tr
><td
>Tekst
</td
> <td
>odt:
2480 </td
> <td
>docx:
4460</td
></tr
>
450 <tr
><td
>Presentasjon
</td
> <td
>odp:
299 </td
> <td
>pptx:
741</td
></tr
>
451 <tr
><td
>Regneark
</td
> <td
>ods:
187 </td
> <td
>xlsx:
372</td
></tr
>
454 <p
>I wonder how these numbers change over time.
</p
>
456 <p
>I am aware of Google returning different results and numbers based
457 on where the search is done, so I guess these numbers will differ if
458 they are conduced in another country. Because of this, I did the same
459 search from a machine in California, USA, a few minutes after the
460 search done from a machine here in Norway.
</p
>
464 <tr
><th
>Type
</th
><th
>ODF
</th
><th
>MS Office
</th
></tr
>
465 <tr
><td
>Tekst
</td
> <td
>odt:
129000</td
> <td
>docx:
308000</td
></tr
>
466 <tr
><td
>Presentasjon
</td
> <td
>odp:
44200</td
> <td
>pptx:
93900</td
></tr
>
467 <tr
><td
>Regneark
</td
> <td
>ods:
26500 </td
> <td
>xlsx:
82400</td
></tr
>
470 <p
>And with
'site:no
':
473 <tr
><th
>Type
</th
><th
>ODF
</th
><th
>MS Office
</th
></tr
>
474 <tr
><td
>Tekst
</td
> <td
>odt:
2480</td
> <td
>docx:
3410</td
></tr
>
475 <tr
><td
>Presentasjon
</td
> <td
>odp:
175</td
> <td
>pptx:
604</td
></tr
>
476 <tr
><td
>Regneark
</td
> <td
>ods:
186 </td
> <td
>xlsx:
296</td
></tr
>
479 <p
>Interesting difference, not sure what to conclude from these
485 <title>Danmark går for ODF?
</title>
486 <link>http://people.skolelinux.org/pere/blog/Danmark_g_r_for_ODF_.html
</link>
487 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Danmark_g_r_for_ODF_.html
</guid>
488 <pubDate>Fri,
29 Jan
2010 12:
00:
00 +
0100</pubDate>
489 <description><p
>Ble nettopp gjort oppmerksom på en
490 <a href=
"http://www.version2.dk/artikel/
13690-breaking-odf-vinder-dokumentformat-krigen
">nyhet fra Version2
</a
>
491 fra Danmark, der det hevdes at Folketinget har vedtatt at ODF skal
492 brukes som dokumentutvekslingsformat i Staten.
</p
>
494 <p
>Hyggelig lesning, spesielt hvis det viser seg at de av vedtatt
495 kravlisten for hva som skal aksepteres som referert i kommentarfeltet
497 <a href=
"http://www.version2.dk/artikel/
13693-er-ooxml-doemt-ude-her-er-kravene-til-en-offentlig-dokumentstandard
">en
498 annen artikkel
</a
> i samme nett-avis. Liker spesielt godt denne:
</p
>
500 <p
><blockquote
> Det skal demonstreres, at standarden i sin helhed kan
501 implementeres af alle direkte i sin helhed på flere
502 platforme.
</blockquote
></p
>
504 <p
>Noe slikt burde være et krav også i Norge.
</p
>
509 <title>A manual for standards wars...
</title>
510 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
512 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
513 <description><p
>Via the
514 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
515 of Rob Weir
</a
> I came across the very interesting essay named
516 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
517 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
518 following the standards wars of today.
</p
>
523 <title>Officeshots taking shape
</title>
524 <link>http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html
</link>
525 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html
</guid>
526 <pubDate>Sun,
13 Jun
2010 11:
40:
00 +
0200</pubDate>
527 <description><p
>For those of us caring about document exchange and
528 interoperability,
<a href=
"http://www.officeshots.org/
">OfficeShots
</a
>
529 is a great service. It is to ODF documents what
530 <a href=
"http://browsershots.org/
">BrowserShots
</a
> is for web
533 <p
>A while back, I was contacted by Knut Yrvin at the part of Nokia
534 that used to be Trolltech, who wanted to help the OfficeShots project
535 and wondered if the University of Oslo where I work would be
536 interested in supporting the project. I helped him to navigate his
537 request to the right people at work, and his request was answered with
538 a spot in the machine room with power and network connected, and Knut
539 arranged funding for a machine to fill the spot. The machine is
540 administrated by the OfficeShots people, so I do not have daily
541 contact with its progress, and thus from time to time check back to
542 see how the project is doing.
</p
>
544 <p
>Today I had a look, and was happy to see that the Dell box in our
545 machine room now is the host for several virtual machines running as
546 OfficeShots factories, and the project is able to render ODF documents
547 in
17 different document processing implementation on Linux and
548 Windows. This is great.
</p
>
553 <title>Terms of use for video produced by a Canon IXUS
130 digital camera
</title>
554 <link>http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</link>
555 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
</guid>
556 <pubDate>Thu,
9 Sep
2010 23:
55:
00 +
0200</pubDate>
557 <description><p
>A few days ago I had the mixed pleasure of bying a new digital
558 camera, a Canon IXUS
130. It was instructive and very disturbing to
559 be able to verify that also this camera producer have the nerve to
560 specify how I can or can not use the videos produced with the camera.
561 Even thought I was aware of the issue, the options with new cameras
562 are limited and I ended up bying the camera anyway. What is the
563 problem, you might ask? It is software patents, MPEG-
4, H
.264 and the
564 MPEG-LA that is the problem, and our right to record our experiences
565 without asking for permissions that is at risk.
567 <p
>On page
27 of the Danish instruction manual, this section is
571 <p
>This product is licensed under AT
&T patents for the MPEG-
4 standard
572 and may be used for encoding MPEG-
4 compliant video and/or decoding
573 MPEG-
4 compliant video that was encoded only (
1) for a personal and
574 non-commercial purpose or (
2) by a video provider licensed under the
575 AT
&T patents to provide MPEG-
4 compliant video.
</p
>
577 <p
>No license is granted or implied for any other use for MPEG-
4
581 <p
>In short, the camera producer have chosen to use technology
582 (MPEG-
4/H
.264) that is only provided if I used it for personal and
583 non-commercial purposes, or ask for permission from the organisations
584 holding the knowledge monopoly (patent) for technology used.
</p
>
586 <p
>This issue has been brewing for a while, and I recommend you to
588 "<a href=
"http://www.osnews.com/story/
23236/Why_Our_Civilization_s_Video_Art_and_Culture_is_Threatened_by_the_MPEG-LA
">Why
589 Our Civilization
's Video Art and Culture is Threatened by the
590 MPEG-LA
</a
>" by Eugenia Loli-Queru and
591 "<a href=
"http://webmink.com/
2010/
09/
03/h-
264-and-foss/
">H
.264 Is Not
592 The Sort Of Free That Matters
</a
>" by Simon Phipps to learn more about
593 the issue. The solution is to support the
594 <a href=
"http://www.digistan.org/open-standard:definition
">free and
595 open standards
</a
> for video, like
<a href=
"http://www.theora.org/
">Ogg
596 Theora
</a
>, and avoid MPEG-
4 and H
.264 if you can.
</p
>
601 <title>Standardkrav inn i anbudstekster?
</title>
602 <link>http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html
</link>
603 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardkrav_inn_i_anbudstekster_.html
</guid>
604 <pubDate>Sun,
17 Oct
2010 19:
30:
00 +
0200</pubDate>
605 <description><p
>Hvis det å følge standarder skal ha noen effekt overfor
606 leverandører, så må slike krav og ønsker komme inn i anbudstekster når
607 systemer kjøpes inn. Har ikke sett noen slike formuleringer i anbud
608 så langt, men har tenkt litt på hva som bør inn. Her er noen ideer og
609 forslag. Min drøm er at en kan sette krav til slik støtte i
610 anbudstekster, men så langt er det nok mer sannsynlig at en må nøye
611 seg med å skrive at det er en fordel om slik støtte er tilstede i
612 leveranser.
</p
>
614 <p
>Som systemadministrator på Universitetet er det typisk to områder
615 som er problematiske for meg. Det ene er admin-grensesnittene på
616 tjenermaskiner, som vi ønsker å bruke via ssh. Det andre er nettsider
617 som vi ønsker å bruke via en nettleser. For begge deler er det viktig
618 at protokollene og formatene som brukes følger standarder våre verktøy
621 <p
>De fleste har nå støtte for SSH som overføringsprotkoll for
622 admin-grensesnittet, men det er ikke tilstrekkelig for å kunne stille
623 inn f.eks BIOS og RAID-kontroller via ssh-forbindelsen. Det er flere
624 aktuelle protokoller for fremvisning av BIOS-oppsett og
625 oppstartmeldinger, og min anbefaling ville være å kreve
626 VT100-kompatibel protokoll, for å sikre at flest mulig
627 terminalemulatorer kan forstå hva som kommer fra admin-grensesnittet
628 via ssh. Andre aktuelle alternativer er ANSI-terminalemulering og
629 VT220. Kanskje en formulering ala dette i anbudsutlysninger vil
632 <p
><blockquote
>
633 BIOS og oppstartmeldinger i administrasjonsgrensesnittet til maskinen
634 bør/skal være tilgjengelig via SSH-protokollen som definert av IETF
635 (RFC
4251 mfl.) og følge terminalfremvisningprotokollen VT100 (ref?)
636 når en kobler seg til oppstart via ssh.
637 </blockquote
></p
>
639 <p
>Har ikke lykkes med å finne en god referanse for
640 VT100-spesifikasjonen.
</p
>
642 <p
>Når det gjelder nettsider, så er det det HTML, CSS og
643 JavaScript-spesifikasjonen til W3C som gjelder.
</p
>
645 <p
><blockquote
>
646 Alle systemets nettsider bør/skal være i henhold til statens
647 standardkatalogs krav om nettsider og følge HTML-standarden som
648 definert av W3C, og validere uten feil hos W3Cs HTML-validator
649 (http://validator.w3.org). Hvis det brukes CSS så bør/skal denne
650 validere uten feil hos W3Cs CSS-validator
651 (http://jigsaw.w3.org/css-validator/). Eventuelle JavaScript skal
652 være i henhold til EcmaScript-standarden. I tillegg til å følge de
653 overnevnte standardene skal websidene fungere i nettleserne (fyll inn
654 relevant liste for organisasjonen) Firefox
3.5, Internet Explorer
8,
656 </blockquote
></p
>
658 <p
>Vil et slikt avsnitt være konkret nok til å få leverandørene til å
659 lage nettsider som følger standardene og fungerer i flere
660 nettlesere?
</p
>
662 <p
>Tar svært gjerne imot innspill på dette temaet til aktive (at)
663 nuug.no, og er spesielt interessert i hva andre skriver i sine anbud
664 for å oppmuntre leverandører til å følge standardene. Kanskje NUUG
665 burde lage et dokument med forslag til standardformuleringer å ta med
666 i anbudsutlysninger?
</p
>
668 <p
>Oppdatering
2010-
12-
03: I følge Wikipedias oppføring om
669 <a href=
"http://en.wikipedia.org/wiki/ANSI_escape_code
">ANSI escape
670 code
</a
>, så bruker VT100-terminaler ECMA-
48-spesifikasjonen som
671 basis for sin oppførsel. Det kan dermed være et alternativ når en
672 skal spesifisere hvordan seriell-konsoll skal fungere.
</p
>
677 <title>Best å ikke fortelle noen at streaming er nedlasting...
</title>
678 <link>http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html
</link>
679 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Best___ikke_fortelle_noen_at_streaming_er_nedlasting___.html
</guid>
680 <pubDate>Sat,
30 Oct
2010 11:
20:
00 +
0200</pubDate>
681 <description><p
>I dag la jeg inn en kommentar på en sak hos NRKBeta
682 <a href=
"http://nrkbeta.no/
2010/
10/
27/bakom-blindpassasjer-del-
1/
">om
683 hvordan TV-serien Blindpassasjer ble laget
</a
> i forbindelse med at
684 filmene NRK la ut ikke var tilgjengelig i et
685 <a href=
"http://www.digistan.org/open-standard:definition
">fritt og
686 åpent format
</a
>. Dette var det jeg skrev publiserte der
07:
39.
</p
>
688 <p
><blockquote
>
689 <p
>"Vi fikk en kommentar rundt måten streamet innhold er beskyttet fra
690 nedlasting. Mange av oss som kan mer enn gjennomsnittet om systemer
691 som dette, vet at det stort sett er mulig å lure ut ting med den
692 nødvendige forkunnskapen.
"</p
>
694 <p
>Haha. Å streame innhold er det samme som å laste ned innhold, så å
695 beskytte en stream mot nedlasting er ikke mulig. Å skrive noe slikt
696 er å forlede leseren.
</p
>
698 <p
>Med den bakgrunn blir forklaringen om at noen rettighetshavere kun
699 vil tillate streaming men ikke nedlasting meningsløs.
</p
>
701 <p
>Anbefaler forresten å lese
702 <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
>
703 om hva som ville være konsekvensen hvis digitale avspillingssperrer
704 (DRM) fungerte. Det gjør de naturligvis ikke teknisk - det er jo
705 derfor de må ha totalitære juridiske beskyttelsesmekanismer på plass,
706 men det er skremmende hva samfunnet tillater og NRK er med på å bygge
708 </blockquote
></p
>
710 <p
>Ca.
20 minutter senere får jeg følgende epost fra Anders Hofseth i
713 <p
><blockquote
>
714 <p
>From: Anders Hofseth
&lt;XXX@gmail.com
>
715 <br
>To:
"pere@hungry.com
" &lt;pere@hungry.com
>
716 <br
>Cc: Eirik Solheim
&lt;XXX@gmail.com
>, Jon Ståle Carlsen
&lt;XXX@gmail.com
>, Henrik Lied
&lt;XXX@gmail.com
>
717 <br
>Subject: Re: [NRKbeta] Kommentar:
"Bakom Blindpassasjer: del
1"
718 <br
>Date: Sat,
30 Oct
2010 07:
58:
44 +
0200</p
>
721 <br
>Det du forsøker dra igang er egentlig en interessant diskusjon,
722 men om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt
723 om å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
724 særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p
>
726 <p
>Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er
727 fjernet og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
728 konsekvensene vi beskriver ikke er noe du ønsker heller...
</p
>
731 <br
>-anders
</p
>
733 <p
>Ring meg om noe er uklart:
95XXXXXXX
</p
>
734 </blockquote
></p
>
736 <p
>Ble så fascinert over denne holdningen, at jeg forfattet og sendte
737 over følgende svar. I og med at debatten er fjernet fra NRK Betas
738 kommentarfelt, så velger jeg å publisere her på bloggen min i stedet.
739 Har fjernet epostadresser og telefonnummer til de involverte, for å
740 unngå at de tiltrekker seg uønskede direkte kontaktforsøk.
</p
>
742 <p
><blockquote
>
743 <p
>From: Petter Reinholdtsen
&lt;pere@hungry.com
>
744 <br
>To: Anders Hofseth
&lt;XXX@gmail.com
>
745 <br
>Cc: Eirik Solheim
&lt;XXX@gmail.com
>,
746 <br
> Jon Ståle Carlsen
&lt;XXX@gmail.com
>,
747 <br
> Henrik Lied
&lt;XXX@gmail.com
>
748 <br
>Subject: Re: [NRKbeta] Kommentar:
"Bakom Blindpassasjer: del
1"
749 <br
>Date: Sat,
30 Oct
2010 08:
24:
34 +
0200</p
>
751 <p
>[Anders Hofseth]
752 <br
>> Hei Petter.
</p
>
754 <p
>Hei.
</p
>
756 <p
>> Det du forsøker dra igang er egentlig en interessant diskusjon, men
757 <br
>> om vi skal kjøre den i kommentarfeltet her, vil vi kunne bli bedt om
758 <br
>> å fjerne blindpassasjer fra nett- tv og det vil heller ikke bli
759 <br
>> særlig lett å klarere ut noe annet arkivmateriale på lang tid.
</p
>
761 <p
>Godt å se at du er enig i at dette er en interessant diskusjon. Den
762 vil nok fortsette en stund til. :)
</p
>
764 <p
>Må innrømme at jeg synes det er merkelig å lese at dere i NRK med
765 vitende og vilje ønsker å forlede rettighetshaverne for å kunne
766 fortsette å legge ut arkivmateriale.
</p
>
768 <p
>Kommentarer og diskusjoner i bloggene til NRK Beta påvirker jo ikke
769 faktum, som er at streaming er det samme som nedlasting, og at innhold
770 som er lagt ut på nett kan lagres lokalt for avspilling når en ønsker
773 <p
>Det du sier er jo at klarering av arkivmateriale for publisering på
774 web krever at en holder faktum skjult fra debattfeltet på NRKBeta.
775 Det er ikke et argument som holder vann. :)
</p
>
777 <p
>> Dette er en situasjon NRKbeta ikke ønsker, så kommentaren er fjernet
778 <br
>> og den delen av diskusjonen er avsluttet på nrkbeta, vi antar
779 <br
>> konsekvensene vi beskriver ikke er noe du ønsker heller...
</p
>
781 <p
>Personlig ønsker jeg at NRK skal slutte å stikke hodet i sanden og
782 heller være åpne på hvordan virkeligheten fungerer, samt ta opp kampen
783 mot de som vil låse kulturen inne. Jeg synes det er en skam at NRK
784 godtar å forlede publikum. Ville heller at NRK krever at innhold som
785 skal sendes skal være uten bruksbegresninger og kan publiseres i
786 formater som heller ikke har bruksbegresninger (bruksbegresningene til
787 H
.264 burde få varselbjellene i NRK til å ringe).
</p
>
789 <p
>At NRK er med på DRM-tåkeleggingen og at det kommer feilaktive
790 påstander om at
"streaming beskytter mot nedlasting
" som bare er egnet
791 til å bygge opp om en myte som er skadelig for samfunnet som helhet.
</p
>
793 <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
795 &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
> >.
796 for å se hva slags bruksbegresninger H
.264 innebærer.
</p
>
798 <p
>Hvis dette innebærer at NRK må være åpne med at arkivmaterialet ikke
799 kan brukes før rettighetshaverene også innser at de er med på å skade
800 samfunnets kultur og kollektive hukommelse, så får en i hvert fall
801 synliggjort konsekvensene og antagelig mer flammer på en debatt som er
802 langt på overtid.
</p
>
804 <p
>> Ring meg om noe er uklart: XXX
</p
>
806 <p
>Intet uklart, men ikke imponert over måten dere håndterer debatten på.
807 Hadde du i stedet kommet med et tilsvar i kommentarfeltet der en
808 gjorde det klart at blindpassasjer-blogpostingen ikke var riktig sted
809 for videre diskusjon hadde dere i mine øyne kommet fra det med
810 ryggraden på plass.
</p
>
812 <p
>PS: Interessant å se at NRK-ansatte ikke bruker NRK-epostadresser.
</p
>
814 <p
>Som en liten avslutning, her er noen litt morsomme innslag om temaet.
815 &lt;URL:
<a href=
"http://www.archive.org/details/CopyingIsNotTheft
">http://www.archive.org/details/CopyingIsNotTheft
</a
> > og
816 &lt;URL:
<a href=
"http://patentabsurdity.com/
">http://patentabsurdity.com/
</a
> > hadde vært noe å kringkaste på
819 <p
>Vennlig hilsen,
821 <br
>Petter Reinholdtsen
</p
>
826 <title>Officeshots still going strong
</title>
827 <link>http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html
</link>
828 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html
</guid>
829 <pubDate>Sat,
25 Dec
2010 09:
40:
00 +
0100</pubDate>
830 <description><p
>Half a year ago I
831 <a href=
"http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html
">wrote
832 a bit
</a
> about
<a href=
"http://www.officeshots.org/
">OfficeShots
</a
>,
833 a web service to allow anyone to test how ODF documents are handled by
834 the different programs reading and writing the ODF format.
</p
>
836 <p
>I just had a look at the service, and it seem to be going strong.
837 Very interesting to see the results reported in the gallery, how
838 different Office implementations handle different ODF features. Sad
839 to see that KOffice was not doing it very well, and happy to see that
840 LibreOffice has been tested already (but sadly not listed as a option
841 for OfficeShots users yet). I am glad to see that the ODF community
842 got such a great test tool available.
</p
>
847 <title>The reply from Edgar Villanueva to Microsoft in Peru
</title>
848 <link>http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html
</link>
849 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html
</guid>
850 <pubDate>Sat,
25 Dec
2010 10:
50:
00 +
0100</pubDate>
851 <description><p
>A few days ago
852 <a href=
"http://www.idg.no/computerworld/article189879.ece
">an
853 article
</a
> in the Norwegian Computerworld magazine about how version
855 <a href=
"http://en.wikipedia.org/wiki/European_Interoperability_Framework
">European
856 Interoperability Framework
</a
> has been successfully lobbied by the
857 proprietary software industry to remove the focus on free software.
858 Nothing very surprising there, given
859 <a href=
"http://news.slashdot.org/story/
10/
03/
29/
2115235/Open-Source-Open-Standards-Under-Attack-In-Europe
">earlier
860 reports
</a
> on how Microsoft and others have stacked the committees in
861 this work. But I find this very sad. The definition of
862 <a href=
"http://www.nuug.no/dokumenter/standard-presse-def-
200506.txt
">an
863 open standard from version
1</a
> was very good, and something I
864 believe should be used also in the future, alongside
865 <a href=
"http://www.digistan.org/open-standard:definition
">the
866 definition from Digistan
</A
>. Version
2 have removed the open
867 standard definition from its content.
</p
>
869 <p
>Anyway, the news reminded me of the great reply sent by Dr. Edgar
870 Villanueva, congressman in Peru at the time, to Microsoft as a reply
871 to Microsofts attack on his proposal regarding the use of free software
872 in the public sector in Peru. As the text was not available from a
873 few of the URLs where it used to be available, I copy it here from
874 <a href=
"http://gnuwin.epfl.ch/articles/en/reponseperou/villanueva_to_ms.html
">my
875 source
</a
> to ensure it is available also in the future. Some
876 background information about that story is available in
877 <a href=
"http://www.linuxjournal.com/article/
6099">an article
</a
> from
878 Linux Journal in
2002.
</p
>
881 <p
>Lima,
8th of April,
2002<br
>
882 To: Señor JUAN ALBERTO GONZÁLEZ
<br
>
883 General Manager of Microsoft Perú
</p
>
885 <p
>Dear Sir:
</p
>
887 <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
>
889 <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
>
891 <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
>
893 <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
>
897 <li
>Free access to public information by the citizen.
</li
>
898 <li
>Permanence of public data.
</li
>
899 <li
>Security of the State and citizens.
</li
>
903 <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
>
905 <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
>
907 <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
>
909 <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
>
911 <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
>
914 <p
>From reading the Bill it will be clear that once passed:
<br
>
915 <li
>the law does not forbid the production of proprietary software
</li
>
916 <li
>the law does not forbid the sale of proprietary software
</li
>
917 <li
>the law does not specify which concrete software to use
</li
>
918 <li
>the law does not dictate the supplier from whom software will be bought
</li
>
919 <li
>the law does not limit the terms under which a software product can be licensed.
</li
>
923 <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
>
925 <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
>
927 <p
>As for the observations you have made, we will now go on to analyze them in detail:
</p
>
929 <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
>
931 <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
>
933 <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
>
935 <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
>
937 <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
>
939 <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
>
941 <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
>
943 <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
>
945 <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
>
947 <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
>
949 <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
>
951 <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
>
953 <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
>
955 <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
>
957 <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
>
959 <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
>
961 <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
>
963 <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
>
965 <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
>
967 <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
>
969 <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
>
971 <p
>On security:
</p
>
973 <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
>
975 <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
>
977 <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
>
979 <p
>In respect of the guarantee:
</p
>
981 <p
>As you know perfectly well, or could find out by reading the
"End User License Agreement
" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS
'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.
</p
>
983 <p
>On Intellectual Property:
</p
>
985 <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
>
987 <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
>
989 <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
>
991 <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
>
993 <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
>
995 <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
>
997 <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
>
999 <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
>
1001 <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
>
1003 <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
>
1005 <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
>
1007 <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
>
1009 <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
>
1011 <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
>
1013 <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
>
1015 <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
>
1017 <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
>
1019 <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
>
1021 <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
>
1023 <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
>
1025 <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
>
1027 <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
>
1029 <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
>
1031 <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
>
1033 <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
>
1035 <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
>
1037 <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
>
1039 <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
>
1041 <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
>
1043 <p
>Cordially,
<br
>
1044 DR. EDGAR DAVID VILLANUEVA NUÑEZ
<br
>
1045 Congressman of the Republic of Perú.
</p
>
1051 <title>Is Ogg Theora a free and open standard?
</title>
1052 <link>http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
</link>
1053 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
</guid>
1054 <pubDate>Sat,
25 Dec
2010 20:
25:
00 +
0100</pubDate>
1055 <description><p
><a href=
"http://www.digistan.org/open-standard:definition
">The
1056 Digistan definition
</a
> of a free and open standard reads like this:
</p
>
1060 <p
>The Digital Standards Organization defines free and open standard
1061 as follows:
</p
>
1065 <li
>A free and open standard is immune to vendor capture at all stages
1066 in its life-cycle. Immunity from vendor capture makes it possible to
1067 freely use, improve upon, trust, and extend a standard over time.
</li
>
1069 <li
>The standard is adopted and will be maintained by a not-for-profit
1070 organisation, and its ongoing development occurs on the basis of an
1071 open decision-making procedure available to all interested
1074 <li
>The standard has been published and the standard specification
1075 document is available freely. It must be permissible to all to copy,
1076 distribute, and use it freely.
</li
>
1078 <li
>The patents possibly present on (parts of) the standard are made
1079 irrevocably available on a royalty-free basis.
</li
>
1081 <li
>There are no constraints on the re-use of the standard.
</li
>
1085 <p
>The economic outcome of a free and open standard, which can be
1086 measured, is that it enables perfect competition between suppliers of
1087 products based on the standard.
</p
>
1090 <p
>For a while now I have tried to figure out of Ogg Theora is a free
1091 and open standard according to this definition. Here is a short
1092 writeup of what I have been able to gather so far. I brought up the
1093 topic on the Xiph advocacy mailing list
1094 <a href=
"http://lists.xiph.org/pipermail/advocacy/
2009-July/
001632.html
">in
1095 July
2009</a
>, for those that want to see some background information.
1096 According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
1097 the Ogg Theora specification fulfils the Digistan definition.
</p
>
1099 <p
><strong
>Free from vendor capture?
</strong
></p
>
1101 <p
>As far as I can see, there is no single vendor that can control the
1102 Ogg Theora specification. It can be argued that the
1103 <a href=
"http://www.xiph.org/
">Xiph foundation
</A
> is such vendor, but
1104 given that it is a non-profit foundation with the expressed goal
1105 making free and open protocols and standards available, it is not
1106 obvious that this is a real risk. One issue with the Xiph
1107 foundation is that its inner working (as in board member list, or who
1108 control the foundation) are not easily available on the web. I
've
1109 been unable to find out who is in the foundation board, and have not
1110 seen any accounting information documenting how money is handled nor
1111 where is is spent in the foundation. It is thus not obvious for an
1112 external observer who control The Xiph foundation, and for all I know
1113 it is possible for a single vendor to take control over the
1114 specification. But it seem unlikely.
</p
>
1116 <p
><strong
>Maintained by open not-for-profit organisation?
</strong
></p
>
1118 <p
>Assuming that the Xiph foundation is the organisation its web pages
1119 claim it to be, this point is fulfilled. If Xiph foundation is
1120 controlled by a single vendor, it isn
't, but I have not found any
1121 documentation indicating this.
</p
>
1123 <p
>According to
1124 <a href=
"http://media.hiof.no/diverse/fad/rapport_4.pdf
">a report
</a
>
1125 prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
1126 government, the Xiph foundation is a non-commercial organisation and
1127 the development process is open, transparent and non-Discrimatory.
1128 Until proven otherwise, I believe it make most sense to believe the
1129 report is correct.
</p
>
1131 <p
><strong
>Specification freely available?
</strong
></p
>
1133 <p
>The specification for the
<a href=
"http://www.xiph.org/ogg/doc/
">Ogg
1134 container format
</a
> and both the
1135 <a href=
"http://www.xiph.org/vorbis/doc/
">Vorbis
</a
> and
1136 <a href=
"http://theora.org/doc/
">Theora
</a
> codeces are available on
1137 the web. This are the terms in the Vorbis and Theora specification:
1141 Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
1142 specifications, whether in private, public, or corporate
1143 capacity. However, the Xiph.Org Foundation and the Ogg project reserve
1144 the right to set the Ogg [Vorbis/Theora] specification and certify
1145 specification compliance.
1149 <p
>The Ogg container format is specified in IETF
1150 <a href=
"http://www.xiph.org/ogg/doc/rfc3533.txt
">RFC
3533</a
>, and
1151 this is the term:
<p
>
1155 <p
>This document and translations of it may be copied and furnished to
1156 others, and derivative works that comment on or otherwise explain it
1157 or assist in its implementation may be prepared, copied, published and
1158 distributed, in whole or in part, without restriction of any kind,
1159 provided that the above copyright notice and this paragraph are
1160 included on all such copies and derivative works. However, this
1161 document itself may not be modified in any way, such as by removing
1162 the copyright notice or references to the Internet Society or other
1163 Internet organizations, except as needed for the purpose of developing
1164 Internet standards in which case the procedures for copyrights defined
1165 in the Internet Standards process must be followed, or as required to
1166 translate it into languages other than English.
</p
>
1168 <p
>The limited permissions granted above are perpetual and will not be
1169 revoked by the Internet Society or its successors or assigns.
</p
>
1172 <p
>All these terms seem to allow unlimited distribution and use, an
1173 this term seem to be fulfilled. There might be a problem with the
1174 missing permission to distribute modified versions of the text, and
1175 thus reuse it in other specifications. Not quite sure if that is a
1176 requirement for the Digistan definition.
</p
>
1178 <p
><strong
>Royalty-free?
</strong
></p
>
1180 <p
>There are no known patent claims requiring royalties for the Ogg
1182 <a href=
"http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=
65782">MPEG-LA
</a
>
1184 <a href=
"http://yro.slashdot.org/story/
10/
04/
30/
237238/Steve-Jobs-Hints-At-Theora-Lawsuit
">Steve
1185 Jobs
</a
> in Apple claim to know about some patent claims (submarine
1186 patents) against the Theora format, but no-one else seem to believe
1187 them. Both Opera Software and the Mozilla Foundation have looked into
1188 this and decided to implement Ogg Theora support in their browsers
1189 without paying any royalties. For now the claims from MPEG-LA and
1190 Steve Jobs seem more like FUD to scare people to use the H
.264 codec
1191 than any real problem with Ogg Theora.
</p
>
1193 <p
><strong
>No constraints on re-use?
</strong
></p
>
1195 <p
>I am not aware of any constraints on re-use.
</p
>
1197 <p
><strong
>Conclusion
</strong
></p
>
1199 <p
>3 of
5 requirements seem obviously fulfilled, and the remaining
2
1200 depend on the governing structure of the Xiph foundation. Given the
1201 background report used by the Norwegian government, I believe it is
1202 safe to assume the last two requirements are fulfilled too, but it
1203 would be nice if the Xiph foundation web site made it easier to verify
1206 <p
>It would be nice to see other analysis of other specifications to
1207 see if they are free and open standards.
</p
>
1212 <title>The many definitions of a open standard
</title>
1213 <link>http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html
</link>
1214 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html
</guid>
1215 <pubDate>Mon,
27 Dec
2010 14:
45:
00 +
0100</pubDate>
1216 <description><p
>One of the reasons I like the Digistan definition of
1217 "<a href=
"http://www.digistan.org/open-standard:definition
">Free and
1218 Open Standard
</a
>" is that this is a new term, and thus the meaning of
1219 the term has been decided by Digistan. The term
"Open Standard
" has
1220 become so misunderstood that it is no longer very useful when talking
1221 about standards. One end up discussing which definition is the best
1222 one and with such frame the only one gaining are the proponents of
1223 de-facto standards and proprietary solutions.
</p
>
1225 <p
>But to give us an idea about the diversity of definitions of open
1226 standards, here are a few that I know about. This list is not
1227 complete, but can be a starting point for those that want to do a
1228 complete survey. More definitions are available on the
1229 <a href=
"http://en.wikipedia.org/wiki/Open_standard
">wikipedia
1230 page
</a
>.
</p
>
1232 <p
>First off is my favourite, the definition from the European
1233 Interoperability Framework version
1.0. Really sad to notice that BSA
1234 and others has succeeded in getting it removed from version
2.0 of the
1235 framework by stacking the committee drafting the new version with
1236 their own people. Anyway, the definition is still available and it
1237 include the key properties needed to make sure everyone can use a
1238 specification on equal terms.
</p
>
1242 <p
>The following are the minimal characteristics that a specification
1243 and its attendant documents must have in order to be considered an
1244 open standard:
</p
>
1248 <li
>The standard is adopted and will be maintained by a not-for-profit
1249 organisation, and its ongoing development occurs on the basis of an
1250 open decision-making procedure available to all interested parties
1251 (consensus or majority decision etc.).
</li
>
1253 <li
>The standard has been published and the standard specification
1254 document is available either freely or at a nominal charge. It must be
1255 permissible to all to copy, distribute and use it for no fee or at a
1256 nominal fee.
</li
>
1258 <li
>The intellectual property - i.e. patents possibly present - of
1259 (parts of) the standard is made irrevocably available on a royalty-
1260 free basis.
</li
>
1262 <li
>There are no constraints on the re-use of the standard.
</li
>
1267 <p
>Another one originates from my friends over at
1268 <a href=
"http://www.dkuug.dk/
">DKUUG
</a
>, who coined and gathered
1269 support for
<a href=
"http://www.aaben-standard.dk/
">this
1270 definition
</a
> in
2004. It even made it into the Danish parlament as
1271 <a href=
"http://www.ft.dk/dokumenter/tingdok.aspx?/samling/
20051/beslutningsforslag/B103/som_fremsat.htm
">their
1272 definition of a open standard
</a
>. Another from a different part of
1273 the Danish government is available from the wikipedia page.
</p
>
1277 <p
>En åben standard opfylder følgende krav:
</p
>
1281 <li
>Veldokumenteret med den fuldstændige specifikation offentligt
1282 tilgængelig.
</li
>
1284 <li
>Frit implementerbar uden økonomiske, politiske eller juridiske
1285 begrænsninger på implementation og anvendelse.
</li
>
1287 <li
>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
1288 "standardiseringsorganisation
") via en åben proces.
</li
>
1294 <p
>Then there is
<a href=
"http://www.fsfe.org/projects/os/def.html
">the
1295 definition
</a
> from Free Software Foundation Europe.
</p
>
1299 <p
>An Open Standard refers to a format or protocol that is
</p
>
1303 <li
>subject to full public assessment and use without constraints in a
1304 manner equally available to all parties;
</li
>
1306 <li
>without any components or extensions that have dependencies on
1307 formats or protocols that do not meet the definition of an Open
1308 Standard themselves;
</li
>
1310 <li
>free from legal or technical clauses that limit its utilisation by
1311 any party or in any business model;
</li
>
1313 <li
>managed and further developed independently of any single vendor
1314 in a process open to the equal participation of competitors and third
1317 <li
>available in multiple complete implementations by competing
1318 vendors, or as a complete implementation equally available to all
1325 <p
>A long time ago, SUN Microsystems, now bought by Oracle, created
1327 <a href=
"http://blogs.sun.com/dennisding/resource/Open%
20Standard%
20Definition.pdf
">Open
1328 Standards Checklist
</a
> with a fairly detailed description.
</p
>
1331 <p
>Creation and Management of an Open Standard
1335 <li
>Its development and management process must be collaborative and
1340 <li
>Participation must be accessible to all those who wish to
1341 participate and can meet fair and reasonable criteria
1342 imposed by the organization under which it is developed
1343 and managed.
</li
>
1345 <li
>The processes must be documented and, through a known
1346 method, can be changed through input from all
1347 participants.
</li
>
1349 <li
>The process must be based on formal and binding commitments for
1350 the disclosure and licensing of intellectual property rights.
</li
>
1352 <li
>Development and management should strive for consensus,
1353 and an appeals process must be clearly outlined.
</li
>
1355 <li
>The standard specification must be open to extensive
1356 public review at least once in its life-cycle, with
1357 comments duly discussed and acted upon, if required.
</li
>
1365 <p
>Use and Licensing of an Open Standard
</p
>
1368 <li
>The standard must describe an interface, not an implementation,
1369 and the industry must be capable of creating multiple, competing
1370 implementations to the interface described in the standard without
1371 undue or restrictive constraints. Interfaces include APIs,
1372 protocols, schemas, data formats and their encoding.
</li
>
1374 <li
> The standard must not contain any proprietary
"hooks
" that create
1375 a technical or economic barriers
</li
>
1377 <li
>Faithful implementations of the standard must
1378 interoperate. Interoperability means the ability of a computer
1379 program to communicate and exchange information with other computer
1380 programs and mutually to use the information which has been
1381 exchanged. This includes the ability to use, convert, or exchange
1382 file formats, protocols, schemas, interface information or
1383 conventions, so as to permit the computer program to work with other
1384 computer programs and users in all the ways in which they are
1385 intended to function.
</li
>
1387 <li
>It must be permissible for anyone to copy, distribute and read the
1388 standard for a nominal fee, or even no fee. If there is a fee, it
1389 must be low enough to not preclude widespread use.
</li
>
1391 <li
>It must be possible for anyone to obtain free (no royalties or
1392 fees; also known as
"royalty free
"), worldwide, non-exclusive and
1393 perpetual licenses to all essential patent claims to make, use and
1394 sell products based on the standard. The only exceptions are
1395 terminations per the reciprocity and defensive suspension terms
1396 outlined below. Essential patent claims include pending, unpublished
1397 patents, published patents, and patent applications. The license is
1398 only for the exact scope of the standard in question.
1402 <li
> May be conditioned only on reciprocal licenses to any of
1403 licensees
' patent claims essential to practice that standard
1404 (also known as a reciprocity clause)
</li
>
1406 <li
> May be terminated as to any licensee who sues the licensor
1407 or any other licensee for infringement of patent claims
1408 essential to practice that standard (also known as a
1409 "defensive suspension
" clause)
</li
>
1411 <li
> The same licensing terms are available to every potential
1417 <li
>The licensing terms of an open standards must not preclude
1418 implementations of that standard under open source licensing terms
1419 or restricted licensing terms
</li
>
1425 <p
>It is said that one of the nice things about standards is that
1426 there are so many of them. As you can see, the same holds true for
1427 open standard definitions. Most of the definitions have a lot in
1428 common, and it is not really controversial what properties a open
1429 standard should have, but the diversity of definitions have made it
1430 possible for those that want to avoid a level marked field and real
1431 competition to downplay the significance of open standards. I hope we
1432 can turn this tide by focusing on the advantages of Free and Open
1433 Standards.
</p
>
1438 <title>What standards are Free and Open as defined by Digistan?
</title>
1439 <link>http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html
</link>
1440 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html
</guid>
1441 <pubDate>Thu,
30 Dec
2010 23:
15:
00 +
0100</pubDate>
1442 <description><p
>After trying to
1443 <a href=
"http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html
">compare
1444 Ogg Theora
</a
> to
1445 <a href=
"http://www.digistan.org/open-standard:definition
">the Digistan
1446 definition
</a
> of a free and open standard, I concluded that this need
1447 to be done for more standards and started on a framework for doing
1448 this. As a start, I want to get the status for all the standards in
1449 the Norwegian reference directory, which include UTF-
8, HTML, PDF, ODF,
1450 JPEG, PNG, SVG and others. But to be able to complete this in a
1451 reasonable time frame, I will need help.
</p
>
1453 <p
>If you want to help out with this work, please visit
1454 <a href=
"http://wiki.nuug.no/grupper/standard/digistan-analyse
">the
1455 wiki pages I have set up for this
</a
>, and let me know that you want
1456 to help out. The IRC channel #nuug on irc.freenode.net is a good
1457 place to coordinate this for now, as it is the IRC channel for the
1458 NUUG association where I have created the framework (I am the leader
1459 of the Norwegian Unix User Group).
</p
>
1461 <p
>The framework is still forming, and a lot is left to do. Do not be
1462 scared by the sketchy form of the current pages. :)
</p
>
1467 <title>Chrome plan to drop H
.264 support for HTML5
&lt;video
&gt;
</title>
1468 <link>http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html
</link>
1469 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Chrome_plan_to_drop_H_264_support_for_HTML5__lt_video_gt_.html
</guid>
1470 <pubDate>Wed,
12 Jan
2011 22:
10:
00 +
0100</pubDate>
1471 <description><p
>Today I discovered
1472 <a href=
"http://www.digi.no/
860070/google-dropper-h264-stotten-i-chrome
">via
1473 digi.no
</a
> that the Chrome developers, in a surprising announcement,
1474 <a href=
"http://blog.chromium.org/
2011/
01/html-video-codec-support-in-chrome.html
">yesterday
1475 announced
</a
> plans to drop H
.264 support for HTML5
&lt;video
&gt; in
1476 the browser. The argument used is that H
.264 is not a
"completely
1477 open
" codec technology. If you believe H
.264 was free for everyone
1478 to use, I recommend having a look at the essay
1479 "<a href=
"http://webmink.com/essays/h-
264/
">H
.264 – Not The Kind Of
1480 Free That Matters
</a
>". It is not free of cost for creators of video
1481 tools, nor those of us that want to publish on the Internet, and the
1482 terms provided by MPEG-LA excludes free software projects from
1483 licensing the patents needed for H
.264. Some background information
1484 on the Google announcement is available from
1485 <a href=
"http://www.osnews.com/story/
24243/Google_To_Drop_H264_Support_from_Chrome
">OSnews
</a
>.
1486 A good read. :)
</p
>
1488 <p
>Personally, I believe it is great that Google is taking a stand to
1489 promote equal terms for everyone when it comes to video publishing on
1490 the Internet. This can only be done by publishing using free and open
1491 standards, which is only possible if the web browsers provide support
1492 for these free and open standards. At the moment there seem to be two
1493 camps in the web browser world when it come to video support. Some
1494 browsers support H
.264, and others support
1495 <a href=
"http://www.theora.org/
">Ogg Theora
</a
> and
1496 <a href=
"http://www.webmproject.org/
">WebM
</a
>
1497 (
<a href=
"http://www.diracvideo.org/
">Dirac
</a
> is not really an option
1498 yet), forcing those of us that want to publish video on the Internet
1499 and which can not accept the terms of use presented by MPEG-LA for
1500 H
.264 to not reach all potential viewers.
1501 Wikipedia keep
<a href=
"http://en.wikipedia.org/wiki/HTML5_video
">an
1502 updated summary
</a
> of the current browser support.
</p
>
1504 <p
>Not surprising, several people would prefer Google to keep
1505 promoting H
.264, and John Gruber
1506 <a href=
"http://daringfireball.net/
2011/
01/simple_questions
">presents
1507 the mind set
</a
> of these people quite well. His rhetorical questions
1508 provoked a reply from Thom Holwerda with another set of questions
1509 <a href=
"http://www.osnews.com/story/
24245/
10_Questions_for_John_Gruber_Regarding_H_264_WebM
">presenting
1510 the issues with H
.264</a
>. Both are worth a read.
</p
>
1512 <p
>Some argue that if Google is dropping H
.264 because it isn
't free,
1513 they should also drop support for the Adobe Flash plugin. This
1514 argument was covered by Simon Phipps in
1515 <a href=
"http://blogs.computerworlduk.com/simon-says/
2011/
01/google-and-h264---far-from-hypocritical/index.htm
">todays
1516 blog post
</a
>, which I find to put the issue in context. To me it
1517 make perfect sense to drop native H
.264 support for HTML5 in the
1518 browser while still allowing plugins.
</p
>
1520 <p
>I suspect the reason this announcement make so many people protest,
1521 is that all the users and promoters of H
.264 suddenly get an uneasy
1522 feeling that they might be backing the wrong horse. A lot of TV
1523 broadcasters have been moving to H
.264 the last few years, and a lot
1524 of money has been invested in hardware based on the belief that they
1525 could use the same video format for both broadcasting and web
1526 publishing. Suddenly this belief is shaken.
</p
>
1528 <p
>An interesting question is why Google is doing this. While the
1529 presented argument might be true enough, I believe Google would only
1530 present the argument if the change make sense from a business
1531 perspective. One reason might be that they are currently negotiating
1532 with MPEG-LA over royalties or usage terms, and giving MPEG-LA the
1533 feeling that dropping H
.264 completely from Chroome, Youtube and
1534 Google Video would improve the negotiation position of Google.
1535 Another reason might be that Google want to save money by not having
1536 to pay the video tax to MPEG-LA at all, and thus want to move to a
1537 video format not requiring royalties at all. A third reason might be
1538 that the Chrome development team simply want to avoid the
1539 Chrome/Chromium split to get more help with the development of Chrome.
1540 I guess time will tell.
</p
>
1542 <p
>Update
2011-
01-
15: The Google Chrome team provided
1543 <a href=
"http://blog.chromium.org/
2011/
01/more-about-chrome-html-video-codec.html
">more
1544 background and information on the move
</a
> it a blog post yesterday.
</p
>
1549 <title>The video format most supported in web browsers?
</title>
1550 <link>http://people.skolelinux.org/pere/blog/The_video_format_most_supported_in_web_browsers_.html
</link>
1551 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_video_format_most_supported_in_web_browsers_.html
</guid>
1552 <pubDate>Sun,
16 Jan
2011 00:
20:
00 +
0100</pubDate>
1553 <description><p
>The video format struggle on the web continues, and the three
1554 contenders seem to be Ogg Theora, H
.264 and WebM. Most video sites
1555 seem to use H
.264, while others use Ogg Theora. Interestingly enough,
1556 the comments I see give me the feeling that a lot of people believe
1557 H
.264 is the most supported video format in browsers, but according to
1558 the Wikipedia article on
1559 <a href=
"http://en.wikipedia.org/wiki/HTML5_video
">HTML5 video
</a
>,
1560 this is not true. Check out the nice table of supprted formats in
1561 different browsers there. The format supported by most browsers is
1562 Ogg Theora, supported by released versions of Mozilla Firefox, Google
1563 Chrome, Chromium, Opera, Konqueror, Epiphany, Origyn Web Browser and
1564 BOLT browser, while not supported by Internet Explorer nor Safari.
1565 The runner up is WebM supported by released versions of Google Chrome
1566 Chromium Opera and Origyn Web Browser, and test versions of Mozilla
1567 Firefox. H
.264 is supported by released versions of Safari, Origyn
1568 Web Browser and BOLT browser, and the test version of Internet
1569 Explorer. Those wanting Ogg Theora support in Internet Explorer and
1570 Safari can install plugins to get it.
</p
>
1572 <p
>To me, the simple conclusion from this is that to reach most users
1573 without any extra software installed, one uses Ogg Theora with the
1574 HTML5 video tag. Of course to reach all those without a browser
1575 handling HTML5, one need fallback mechanisms. In
1576 <a href=
"http://www.nuug.no/
">NUUG
</a
>, we provide first fallback to a
1577 plugin capable of playing MPEG1 video, and those without such support
1578 we have a second fallback to the Cortado java applet playing Ogg
1579 Theora. This seem to work quite well, as can be seen in an
<a
1580 href=
"http://www.nuug.no/aktiviteter/
20110111-semantic-web/
">example
1581 from last week
</a
>.
</p
>
1583 <p
>The reason Ogg Theora is the most supported format, and H
.264 is
1584 the least supported is simple. Implementing and using H
.264
1585 require royalty payment to MPEG-LA, and the terms of use from MPEG-LA
1586 are incompatible with free software licensing. If you believed H
.264
1587 was without royalties and license terms, check out
1588 "<a href=
"http://webmink.com/essays/h-
264/
">H
.264 – Not The Kind Of
1589 Free That Matters
</a
>" by Simon Phipps.
</p
>
1591 <p
>A incomplete list of sites providing video in Ogg Theora is
1593 <a href=
"http://wiki.xiph.org/index.php/List_of_Theora_videos
">the
1594 Xiph.org wiki
</a
>, if you want to have a look. I
'm not aware of a
1595 similar list for WebM nor H
.264.
</p
>
1597 <p
>Update
2011-
01-
16 09:
40: A question from Tollef on IRC made me
1598 realise that I failed to make it clear enough this text is about the
1599 &lt;video
&gt; tag support in browsers and not the video support
1600 provided by external plugins like the Flash plugins.
</p
>
1605 <title>RAND terms - non-reasonable and discriminatory
</title>
1606 <link>http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html
</link>
1607 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/RAND_terms___non_reasonable_and_discriminatory.html
</guid>
1608 <pubDate>Thu,
19 Apr
2012 22:
20:
00 +
0200</pubDate>
1609 <description><p
>Here in Norway, the
1610 <a href=
"http://www.regjeringen.no/nb/dep/fad.html?id=
339"> Ministry of
1611 Government Administration, Reform and Church Affairs
</a
> is behind
1612 a
<a href=
"http://standard.difi.no/forvaltningsstandarder
">directory of
1613 standards
</a
> that are recommended or mandatory for use by the
1614 government. When the directory was created, the people behind it made
1615 an effort to ensure that everyone would be able to implement the
1616 standards and compete on equal terms to supply software and solutions
1617 to the government. Free software and non-free software could compete
1618 on the same level.
</p
>
1620 <p
>But recently, some standards with RAND
1621 (
<a href=
"http://en.wikipedia.org/wiki/Reasonable_and_non-discriminatory_licensing
">Reasonable
1622 And Non-Discriminatory
</a
>) terms have made their way into the
1623 directory. And while this might not sound too bad, the fact is that
1624 standard specifications with RAND terms often block free software from
1625 implementing them. The reasonable part of RAND mean that the cost per
1626 user/unit is low,and the non-discriminatory part mean that everyone
1627 willing to pay will get a license. Both sound great in theory. In
1628 practice, to get such license one need to be able to count users, and
1629 be able to pay a small amount of money per unit or user. By
1630 definition, users of free software do not need to register their use.
1631 So counting users or units is not possible for free software projects.
1632 And given that people will use the software without handing any money
1633 to the author, it is not really economically possible for a free
1634 software author to pay a small amount of money to license the rights
1635 to implement a standard when the income available is zero. The result
1636 in these situations is that free software are locked out from
1637 implementing standards with RAND terms.
</p
>
1639 <p
>Because of this, when I see someone claiming the terms of a
1640 standard is reasonable and non-discriminatory, all I can think of is
1641 how this really is non-reasonable and discriminatory. Because free
1642 software developers are working in a global market, it does not really
1643 help to know that software patents are not supposed to be enforceable
1644 in Norway. The patent regimes in other countries affect us even here.
1645 I really hope the people behind the standard directory will pay more
1646 attention to these issues in the future.
</p
>
1648 <p
>You can find more on the issues with RAND, FRAND and RAND-Z terms
1650 (
<a href=
"http://blogs.computerworlduk.com/simon-says/
2010/
11/rand-not-so-reasonable/
">RAND:
1651 Not So Reasonable?
</a
>).
</p
>
1653 <p
>Update
2012-
04-
21: Just came across a
1654 <a href=
"http://blogs.computerworlduk.com/open-enterprise/
2012/
04/of-microsoft-netscape-patents-and-open-standards/index.htm
">blog
1655 post from Glyn Moody
</a
> over at Computer World UK warning about the
1656 same issue, and urging people to speak out to the UK government. I
1657 can only urge Norwegian users to do the same for
1658 <a href=
"http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder
">the
1659 hearing taking place at the moment
</a
> (respond before
2012-
04-
27).
1660 It proposes to require video conferencing standards including
1661 specifications with RAND terms.
</p
>
1666 <title>HTC One X - Your video? What do you mean?
</title>
1667 <link>http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html
</link>
1668 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/HTC_One_X___Your_video___What_do_you_mean_.html
</guid>
1669 <pubDate>Thu,
26 Apr
2012 13:
20:
00 +
0200</pubDate>
1670 <description><p
>In
<a href=
"http://www.idg.no/computerworld/article243690.ece
">an
1671 article today
</a
> published by Computerworld Norway, the photographer
1672 <a href=
"http://www.urke.com/eirik/
">Eirik Helland Urke
</a
> reports
1673 that the video editor application included with
1674 <a href=
"http://www.htc.com/www/smartphones/htc-one-x/#specs
">HTC One
1675 X
</a
> have some quite surprising terms of use. The article is mostly
1676 based on the twitter message from mister Urke, stating:
1678 <p
><blockquote
>
1679 "<a href=
"http://twitter.com/urke/status/
194062269724897280">Drøy
1680 brukeravtale: HTC kan bruke MINE redigerte videoer kommersielt. Selv
1681 kan jeg KUN bruke dem privat.
</a
>"
1682 </blockquote
></p
>
1684 <p
>I quickly translated it to this English message:
</p
>
1686 <p
><blockquote
>
1687 "Arrogant user agreement: HTC can use MY edited videos
1688 commercially. Although I can ONLY use them privately.
"
1689 </blockquote
></p
>
1691 <p
>I
've been unable to find the text of the license term myself, but
1692 suspect it is a variation of the MPEG-LA terms I
1693 <a href=
"http://people.skolelinux.org/pere/blog/Terms_of_use_for_video_produced_by_a_Canon_IXUS_130_digital_camera.html
">discovered
1694 with my Canon IXUS
130</a
>. The HTC One X specification specifies that
1695 the recording format of the phone is .amr for audio and .mp3 for
1697 <a href=
"http://en.wikipedia.org/wiki/Adaptive_Multi-Rate_audio_codec#Licensing_and_patent_issues
">Adaptive
1698 Multi-Rate audio codec
</a
> with patents which according to the
1699 Wikipedia article require an license agreement with
1700 <a href=
"http://www.voiceage.com/
">VoiceAge
</a
>. MP4 is
1701 <a href=
"http://en.wikipedia.org/wiki/H
.264/MPEG-
4_AVC#Patent_licensing
">MPEG4 with
1702 H
.264</a
>, which according to Wikipedia require a licence agreement
1703 with
<a href=
"http://www.mpegla.com/
">MPEG-LA
</a
>.
</p
>
1705 <p
>I know why I prefer
1706 <a href=
"http://www.digistan.org/open-standard:definition
">free and open
1707 standards
</a
> also for video.
</p
>
1712 <title>NUUGs leverer høringsuttalelse om v3.1 av statens referansekatalog
</title>
1713 <link>http://people.skolelinux.org/pere/blog/NUUGs_leverer_h_ringsuttalelse_om_v3_1_av_statens_referansekatalog.html
</link>
1714 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/NUUGs_leverer_h_ringsuttalelse_om_v3_1_av_statens_referansekatalog.html
</guid>
1715 <pubDate>Fri,
27 Apr
2012 15:
30:
00 +
0200</pubDate>
1716 <description><p
>NUUG-styremedlem Hans-Petter Fjeld
1717 <a href=
"https://plus.google.com/u/
0/
110394259537201279374/posts/AGzRmAuFdW1
">meldte
1718 nettopp
</a
> at han har sendt inn
<a href=
"http://www.nuug.no/
">NUUG
</a
>s
1719 høringsuttalelse angående Difi sin standardkatalog v3.1. Jeg er veldig
1720 glad for at så mange bidro og sikret at vår stemme blir hørt i denne
1721 høringen. Anbefaler alle å lese våre
1722 <a href=
"http://wiki.nuug.no/uttalelser/
201204-standardkatalog-v3.1
">to
1723 sider med innspill
</a
>.
</p
>
1728 <title>OpenOffice.org fungerer da fint for blinde?
</title>
1729 <link>http://people.skolelinux.org/pere/blog/OpenOffice_org_fungerer_da_fint_for_blinde_.html
</link>
1730 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/OpenOffice_org_fungerer_da_fint_for_blinde_.html
</guid>
1731 <pubDate>Mon,
21 May
2012 23:
20:
00 +
0200</pubDate>
1732 <description><p
>De siste dagene har høringsuttalelsene om DIFIs forslag til
1733 standardkatalog v3.1 blitt
1734 <a href=
"http://www.standard.difi.no/hoyring/hoyring-om-nye-anbefalte-it-standarder?tab=comments
">publisert
1735 på DIFIs nettside
</a
>, og jeg kunne der glede meg over at
1736 <a href=
"http://wiki.nuug.no/uttalelser/
201204-standardkatalog-v3.1
">NUUGs
</a
>
1737 uttalelse er kommet med. En uttalelse som overrasker og forvirrer meg
1739 <a href=
"http://www.standard.difi.no/filearchive/norges-blindeforbund.pdf
">den
1740 fra Norges Blindeforbund
</a
>, som
5 år etter at Klaus Knopper sammen
1741 med sin blinde kone blant annet
1742 <a href=
"http://www.nuug.no/aktiviteter/
20071211-accessibility/
">demonstrerte
1743 høyttalende OpenOffice.org på nynorsk for blinde
</a
> på et NUUG-møte.
</p
>
1745 <p
><a href=
"https://www.blindeforbundet.no/
">Norges Blindeforbund
</a
>
1746 skriver følgende, som for meg virker å være formulert på sviktende
1749 <p
><blockquote
>
1750 <p
>Bruk av fri programvare
1752 <p
>I FRIPROGSENTERET, RAPPORT
2009-
02: Universell utforming
1753 <a href=
"http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf
">http://www.kunnskapsbazaren.no/filer/Friprogsenteret-Rapport-Universell_utforming.pdf
</a
>
1754 sies det
"Det finnes i dag ikke mange fri programvare-rammeverk eller
1755 generelle løsninger som støtter tilgjengelighet eller som er
1756 universelt utformet.
"</p
>
1758 <p
>Til tross for at det gjennom prinsippene i fri programvare åpnes
1759 for større frihet til selv å påvirke programvareløsninger i retning av
1760 universell utforming viser praksis at virkeligheten er en annen.
1761 Mange av de mest alminnelige frie programvarepakkene mangler delvis
1762 eller fullstendig tilgjengelighet for mennesker med nedsatt
1763 syn. Eksempler på dette er OpenOffice og LibreOffice m.fl.
</p
>
1765 <p
>En annen utfordring ved bruk av fri programvare kan være manglende
1766 kundestøtte og muligheter til opplæring i bruk av løsningen. Svaksynte
1767 og blinde har et høyere behov for denne typen støtte enn andre brukere
1768 ettersom mange av dem har behov for tilleggsprogramvare som skal
1769 fungere sammen med den opprinnelige programvaren, og ettersom man ikke
1770 har de samme muligheter for overblikk over grensesnittet som en seende
1771 bruker. I tillegg til dette kommer de mer tilgjengelighetstekniske
1772 utfordringene som ofte må løses i samarbeid med
1773 programvareleverandør/produsent.
</p
>
1775 <p
>Fri programvare er ikke på samme måte underlagt lovgivning gjennom
1776 for eksempel diskriminerings og tilgjengelighetsloven ettersom det
1777 ikke alltid finnes en produsent/tilbyder av tjenesten eller produktet.
</p
>
1779 <p
>Norges Blindeforbund krever at universell utforming og
1780 brukskvalitet tas med som viktige hensyn i utredninger som ligger til
1781 grunn for valg av standarder som primært leder brukeren mot fri
1782 programvare. Et eksempel på dette er bruk av dokumentformatet ODF som
1783 leder brukeren i retning av OpenOffice, som er helt eller delvis
1784 utilgjengelig for svaksynte og blinde – noe avhengig av plattform og
1785 hjelpemiddelprogramvare.
</p
>
1787 </blockquote
></p
>
1789 <p
>Jeg håper noen involvert i OpenOffice.org og/eller LibreOffice tar
1790 kontakt med Norges Blindeforbund og oppklarer det som for meg virker å
1791 være en misforståelse, i og med at OpenOffice.org så vidt jeg vet
1792 fungerer fint også for blinde.
</p
>
1794 <p
>Jeg ble minnet på problemstillingen da jeg leste Slashdot-saken om
1795 "<a href=
"http://linux.slashdot.org/story/
12/
05/
21/
1417221/the-state-of-linux-accessibility
">The
1796 State of Linux Accessibility
</a
>", som også hevder at Linux fungerer
1797 utmerket for blinde.
</p
>
1802 <title>The cost of ODF and OOXML
</title>
1803 <link>http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html
</link>
1804 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html
</guid>
1805 <pubDate>Sat,
26 May
2012 18:
00:
00 +
0200</pubDate>
1806 <description><p
>I just come across a blog post from Glyn Moody reporting the
1807 claimed cost from Microsoft on requiring ODF to be used by the UK
1808 government. I just sent him an email to let him know that his
1809 assumption are most likely wrong. Sharing it here in case some of my
1810 blog readers have seem the same numbers float around in the UK.
</p
>
1812 <p
><blockquote
> <p
>Hi. I just noted your
1813 <a href=
"http://blogs.computerworlduk.com/open-enterprise/
2012/
04/does-microsoft-office-lock-in-cost-the-uk-government-
500-million/index.htm
">http://blogs.computerworlduk.com/open-enterprise/
2012/
04/does-microsoft-office-lock-in-cost-the-uk-government-
500-million/index.htm
</a
>
1816 <p
><blockquote
>"They
're all in Danish, not unreasonably, but even
1817 with the help of Google Translate I can
't find any figures about the
1818 savings of
"moving to a flexible two standard
" as claimed by the
1819 Microsoft email. But I assume it is backed up somewhere, so let
's take
1820 it, and the £
500 million figure for the UK, on trust.
"
1821 </blockquote
></p
>
1823 <p
>I can tell you that the Danish reports are inflated. I believe it is
1824 the same reports that were used in the Norwegian debate around
2007,
1825 and Gisle Hannemyr (a well known IT commentator in Norway) had a look
1826 at the content. In short, the reason it is claimed that using ODF
1827 will be so costly, is based on the assumption that this mean every
1828 existing document need to be converted from one of the MS Office
1829 formats to ODF, transferred to the receiver, and converted back from
1830 ODF to one of the MS Office formats, and that the conversion will cost
1831 10 minutes of work time for both the sender and the receiver. In
1832 reality the sender would have a tool capable of saving to ODF, and the
1833 receiver would have a tool capable of reading it, and the time spent
1834 would at most be a few seconds for saving and loading, not
20 minutes
1835 of wasted effort.
</p
>
1837 <p
>Microsoft claimed all these costs were saved by allowing people to
1838 transfer the original files from MS Office instead of spending
10
1839 minutes converting to ODF. :)
</p
>
1842 <a href=
"http://hannemyr.com/no/ms12_vl02.php
">http://hannemyr.com/no/ms12_vl02.php
</a
>
1844 <a href=
"http://hannemyr.com/no/ms12.php
">http://hannemyr.com/no/ms12.php
</a
>
1845 for background information. Norwegian only, sorry. :)
</p
>
1846 </blockquote
></p
>
1851 <title>Trenger en avtale med MPEG-LA for å publisere og kringkaste H
.264-video?
</title>
1852 <link>http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html
</link>
1853 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html
</guid>
1854 <pubDate>Thu,
21 Jun
2012 13:
40:
00 +
0200</pubDate>
1855 <description><p
>Trengs det avtale med MPEG-LA for å ha lovlig rett til å
1856 distribuere og kringkaste video i MPEG4 eller med videokodingen H
.264?
1857 <a href=
"http://webmink.com/essays/h-
264/
">H
.264 og MPEG4 er jo ikke en
1858 fri og åpen standard
</a
> i henhold til
1859 <a href=
"http://people.skolelinux.org/pere/blog/Fri_og__pen_standard__slik_Digistan_ser_det.html
">definisjonen
1860 til Digistan
</a
>, så i enkelte land er det ingen tvil om at du må ha
1861 en slik avtale, men jeg må innrømme at jeg ikke vet om det også
1862 gjelder Norge. Det ser uansett ut til å være en juridisk interessant
1863 problemstilling. Men jeg tenkte her om dagen som så, at hvis det er
1864 nødvendig, så har store aktører som
1865 <a href=
"http://www.nrk.no/
">NRK
</a
> og
1866 <a href=
"http://www.regjeringen.no/
">regjeringen
</a
> skaffet seg en
1867 slik avtale. Jeg har derfor sendt forespørsel til begge (for
1868 regjeringen sin del er det Departementenes Servicesenter som gjør
1869 jobben), og bedt om kopi av eventuelle avtaler de har om bruk av MPEG
1870 og/eller H
.264 med MPEG-LA eller andre aktører som opererer på vegne
1871 av MPEG-LA. Her er kopi av eposten jeg har sendt til
1872 <a href=
"http://www.dss.dep.no/
">Departementenes Servicesenter
</a
>.
1873 Forespørselen til NRK er veldig lik.
</p
>
1875 <p
><blockquote
>
1877 <p
>Date: Tue,
19 Jun
2012 15:
18:
33 +
0200
1878 <br
>From: Petter Reinholdtsen
1879 <br
>To: postmottak@dss.dep.no
1880 <br
>Subject: Innsynsbegjæring om MPEG/H
.264-relaterte avtaler
1882 <p
>Hei. Jeg ber herved om innsyn og kopi av dokumenter i DSS relatert
1883 til avtaler rundt bruk av videoformatene MPEG og H
.264. Jeg er
1884 spesielt interessert i å vite om DSS har lisensavtale med MPEG-LA
1885 eller noen som representerer MPEG-LA i Norge.
</p
>
1887 <p
>MPEG og H
.264 er videoformater som brukes både til kringkasting
1888 (f.eks. i bakkenett og kabel-TV) og videopublisering på web, deriblant
1889 via Adobe Flash. MPEG-LA,
&lt;URL:
1890 <a href=
"http://www.mpeg-la.com/
">http://www.mpeg-la.com/
</a
> &gt;, er
1891 en organisasjon som har fått oppgaven, av de kjente rettighetshavere
1892 av immaterielle rettigheter knyttet til MPEG og H
.264, å selge
1893 bruksrett for MPEG og H
.264.
</p
>
1895 <p
>Via regjeringen.no kringkastes med MPEG og H
.264-baserte
1896 videoformater, og dette ser ut til å være organisert av DSS. Jeg
1897 antar dermed at DSS har avtale med en eller annen aktør om dette.
</p
>
1899 <p
>F.eks. har Adobe Premiere Pro har følgende klausul i følge
&lt;URL:
1900 <a href=
"http://news.cnet.com/
8301-
30685_3-
20000101-
264.html
">http://news.cnet.com/
8301-
30685_3-
20000101-
264.html
</a
>
1903 <p
><blockquote
>
1905 <p
>6.17. AVC DISTRIBUTION. The following notice applies to software
1906 containing AVC import and export functionality: THIS PRODUCT IS
1907 LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL AND
1908 NON-COMMERCIAL USE OF A CONSUMER TO (a) ENCODE VIDEO IN COMPLIANCE
1909 WITH THE AVC STANDARD (
"AVC VIDEO
") AND/OR (b) DECODE AVC VIDEO THAT
1910 WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL AND NON-COMMERCIAL
1911 ACTIVITY AND/OR AVC VIDEO THAT WAS OBTAINED FROM A VIDEO PROVIDER
1912 LICENSED TO PROVIDE AVC VIDEO. NO LICENSE IS GRANTED OR SHALL BE
1913 IMPLIED FOR ANY OTHER USE. ADDITIONAL INFORMATION MAY BE OBTAINED
1914 FROM MPEG LA L.L.C. SEE
1915 <a href=
"http://www.mpegla.com
">http://www.mpegla.com
</a
>.
</p
>
1917 </blockquote
></p
>
1919 <p
>Her er det kun
"non-commercial
" og
"personal and non-commercial
"
1920 aktivitet som er tillatt uten ekstra avtale med MPEG-LA.
</p
>
1922 <p
>Et annet tilsvarende eksempel er Apple Final Cut Pro, som har
1923 følgende klausul i følge
&lt;URL:
1924 <a href=
"http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf
">http://images.apple.com/legal/sla/docs/finalcutstudio2.pdf
</a
>
1927 <p
><blockquote
>
1929 <p
>15. Merknad om H
.264/AVC. Hvis Apple-programvaren inneholder
1930 funksjonalitet for AVC-koding og/eller AVC-dekoding, krever
1931 kommersiell bruk ekstra lisensiering og følgende gjelder:
1932 AVC-FUNKSJONALITETEN I DETTE PRODUKTET KAN KUN ANVENDES AV
1933 FORBRUKERE OG KUN FOR PERSONLIG OG IKKE- KOMMERSIELL BRUK TIL (i)
1934 KODING AV VIDEO I OVERENSSTEMMELSE MED AVC-STANDARDEN (
"AVC-VIDEO
")
1935 OG/ELLER (ii) DEKODING AV AVC-VIDEO SOM ER KODET AV EN FORBRUKER TIL
1936 PERSONLIG OG IKKE-KOMMERSIELL BRUK OG/ELLER DEKODING AV AVC-VIDEO
1937 FRA EN VIDEOLEVERANDØR SOM HAR LISENS TIL Å TILBY
1938 AVC-VIDEO. INFORMASJON OM ANNEN BRUK OG LISENSIERING KAN INNHENTES
1939 FRA MPEG LA L.L.C. SE HTTP://WWW.MPEGLA.COM.
</p
>
1940 </blockquote
></p
>
1942 <p
>Tilsvarende gjelder for andre programvarepakker, kamera, etc som
1943 bruker MPEG og H
.264, at en må ha en avtale med MPEG-LA for å ha lov
1944 til å bruke programmet/utstyret hvis en skal lage noe annet enn
1945 private filmer og i ikke-kommersiell virksomhet.
</p
>
1947 <p
>Jeg er altså interessert i kopi av avtaler DSS har som gjør at en
1948 ikke er begrenset av de generelle bruksvilkårene som gjelder for
1949 utstyr som bruker MPEG og/eller H
.264.
</p
>
1950 </blockquote
></p
>
1952 <p
>Nå venter jeg spent på svaret. Jeg planlegger å blogge om svaret
1958 <title>NRK nekter å finne og utlevere eventuell avtale med MPEG-LA
</title>
1959 <link>http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html
</link>
1960 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html
</guid>
1961 <pubDate>Mon,
25 Jun
2012 15:
10:
00 +
0200</pubDate>
1962 <description><p
>Jeg fikk nettopp svar fra NRK på
1963 <a href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html
">min
1964 forespørsel om kopi av avtale
</a
> med MPEG-LA eller andre om bruk av
1965 MPEG og/eller H
.264. Svaret har fått saksreferanse
2011/
371 (mon tro
1966 hva slags sak fra
2011 dette er?) hos NRK og lyder som følger:
</p
>
1968 <p
><blockquote
>
1970 <p
><strong
>Svar på innsynsbegjæring i MPEG / H
.264-relaterte
1971 avtaler
</strong
></p
>
1973 <p
>Viser til innsynsbegjæring av
19. juni
2012. Kravet om innsyn
1974 gjelder avtale som gjør at NRK «ikke er begrenset av de generelle
1975 bruksvilkårene som gjelder for utstyr som bruker MPEG og/eller
1978 <p
>I henhold til offentleglova §
28 annet ledd må innsynskravet gjelde
1979 en bestemt sak eller i rimelig utstrekning saker av en bestemt
1980 sak. Det er på det rene at det aktuelle innsynskravet ikke gjelder en
1981 bestemt sak. Spørsmålet som reiser seg er om identifiseringsgraden er
1982 tilstrekkelig. I Justisdepartementets «Rettleiar til offentleglova»
1983 står følgende:
</p
>
1985 <p
>«Kravet om at innsynskravet må gjelde ei bestemt sak er til hinder
1986 for at eit innsynskrav kan gjelde alle saker av ein bestemt art, utan
1987 at den enkelte saka blir identifisert. Ein kan med andre ord i
1988 utgangspunktet ikkje krevje innsyn i til dømes alle saker om
1989 utsleppsløyve hos Statens forureiningstilsyn frå dei siste tre åra,
1990 med mindre ein identifiserer kvar enkelt sak, til dømes med tilvising
1991 til dato, partar eller liknande.»
</p
>
1993 <p
>Vedrørende denne begrensningen har Justisdepartementet uttalt
1994 følgende (Lovavdelingens uttalelser JDLOV-
2010-
3295):
</p
>
1996 <p
><em
>«Bakgrunnen for avgrensinga av kva innsynskravet kan gjelde,
1997 er fyrst og fremst at meir generelle innsynskrav, utan noka form for
1998 identifikasjon av kva ein eigentleg ynskjer, ville vere svært
1999 vanskelege å handsame for forvaltninga.»
</em
></p
>
2001 <p
>I samme sak uttaler Lovavdelingen følgende:
</p
>
2003 <p
><em
>«Det følgjer vidare av offentleglova §
28 andre ledd at det `i
2004 rimeleg utstrekning
' kan krevjast innsyn i `saker av ein bestemt
2005 art
'. Vilkåret om at eit innsynskrav berre `i rimeleg utstrekning
' kan
2006 gjelde saker av ein bestemt art, er i hovudsak knytt til kor
2007 arbeidskrevjande det vil vere å finne fram til dei aktuelle
2008 dokumenta. I tillegg reknar vi med at vilkåret kan gje grunnlag for å
2009 nekte innsyn i tilfelle der innsynskravet er så omfattande (gjeld så
2010 mange dokument) at arbeidsmengda som ville gått med til å handsame
2011 det, er større enn det ein `i rimeleg utstrekning
' kan krevje (sjølv
2012 om det nok skal mykje til).»
</em
></p
>
2014 <p
>NRK har ikke noen egen sammenstilling over avtaler innenfor
2015 bestemte områder som omtales i innsynsbegjæringen. De måtte søkes på
2016 vanlig måte. I tillegg finnes ikke noen automatisert måte å finne
2017 avtaler som «ikke er begrenset av de generelle bruksvilkårene som
2018 gjelder for utstyr som bruker MPEG og/eller H
.264». En slik
2019 gjennomgang av avtaler måtte gjøres manuelt av en person med
2020 spesialistkunnskap. Dette vil kreve at NRK avsetter omfattende
2021 ressurser for å finne frem relevante avtaler og for deretter å vurdere
2022 om de dekkes av det innsynsbegjæringen omfattes.
</p
>
2024 <p
>På bakgrunn av dette nekter NRK innsyn, med den begrunnelsen at
2025 innsynskravet er så omfattende at arbeidsmengden for å håndtere kravet
2026 vil være langt større enn det som i rimelig utstrekning kan kreves i
2027 henhold til offentleglova §
28 annet ledd.
</p
>
2029 <p
>Avslag på deres innsynsbegjæring kan påklages til Kultur- og
2030 kirkedepartementet innen tre uker fra det tidspunkt avslaget kommer
2031 frem til mottakeren, i henhold til reglene i offentleglova §
32,
2032 jf. forvaltningsloven kapittel VI. Klagen skal stiles til Kultur- og
2033 kirkedepartementet, og sendes til NRK.
</p
>
2035 <p
>NRK er imidlertid etter Offentleglova forpliktet å gi ut journaler,
2036 slik at en eventuell søknad om innsyn kan tydeligere identifisere
2037 hvilke dokumenter som det ønskes innsyn i. NRKs offentlige journaler
2038 for inneværende og forrige måned ligger ute på
2039 NRK.no/innsyn. Journaler som går lengre tilbake i tid, kan sendes ut
2040 på forespørsel til innsyn (at) nrk.no.
</p
>
2043 <br
>Dokumentarkivet i NRK
2044 <br
>v/ Elin Brandsrud
2045 <br
>Tel. direkte:
23 04 29 29
2046 <br
>Post: RBM3, Postboks
8500 Majorstuen,
0340 Oslo
2047 <br
>innsyn (at) nrk.no
</p
>
2049 </blockquote
></p
>
2052 <a href=
"http://people.skolelinux.org/pere/blog/images/
2012-
06-
25-video-mpegla-nrk.pdf
">i
2053 PDF-form som vedlegg på epost
</a
>. Jeg er litt usikker på hvordan jeg
2054 best går videre for å bli klok, men jeg har jo i hvert fall tre uker
2055 på å vurdere om jeg skal klage. Enten må nok forespørselen
2056 reformuleres eller så må jeg vel klage. Synes jo det er merkelig at
2057 NRK ikke har bedre kontroll med hvilke avtaler de har inngått. Det
2058 burde jo være noen i ledelsen som vet om de har signert en avtale med
2059 MPEG-LA eller ikke...
</p
>
2061 <p
>Oppdatering
2012-
06-
25 20:
20: Et google-søk på
"2011/
371 nrk
"
2062 sendte meg til postjournalen for
2063 <a href=
"http://nrk.no/contentfile/file/
1.8212365!offentligjournal19062012.pdf
">2012-
06-
19</a
>
2065 <a href=
"http://nrk.no/contentfile/file/
1.8214156!offentligjournal20062012.pdf
">2012-
06-
20</a
>
2066 hos NRK som viser mine forespørsler og viser at sakens tittel hos NRK
2067 er
"Graphic Systems Regions MA
2378/
10E
". Videre søk etter
"Graphic
2068 Systems Regions
" viser at dette er saken til et anbud om
2069 "<a href=
"http://no.mercell.com/m/mts/Tender/
27179412.aspx
">a graphics
2070 system for
12 or
13 sites broadcasting regional news
</a
>" hos Mercell
2071 Sourcing Service, også omtalt på
2072 <a href=
"http://www.publictenders.net/tender/
595705">Public
2073 Tenders
</a
> og
2074 <a href=
"http://www.doffin.no/search/show/search_view.aspx?ID=JAN155521
">Doffin
</a
>.
2075 Jeg er dog usikker på hvordan dette er relatert til min
2076 forespørsel.
</p
>
2078 <p
>Oppdatering
2012-
06-
25 22:
40: Ble tipset av Kieran Kunhya, fra
2080 <a href=
"http://code.google.com/p/open-broadcast-encoder/
">Open
2081 Broadcast Encoder
</a
>, at listen over de som har lisensavtale med
2083 <a href=
"http://www.mpeg-la.com/main/programs/AVC/Pages/Licensees.aspx
">tilgjengelig
2084 på web
</a
>. Veldig fint å oppdage hvor den finnes, da jeg må ha lett
2085 etter feil ting da jeg forsøke å finne den. Der står ikke NRK, men
2086 flere andre
"Broadcasting Company
"-oppføringer. Lurer på om det betyr
2087 at NRK ikke trenger avtale, eller noe helt annet?
</p
>
2092 <title>MPEG-LA mener NRK må ha avtale med dem for å kringkaste og publisere H
.264-video
</title>
2093 <link>http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html
</link>
2094 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html
</guid>
2095 <pubDate>Thu,
28 Jun
2012 20:
00:
00 +
0200</pubDate>
2096 <description><p
>Etter at NRK
2097 <a href=
"http://people.skolelinux.org/pere/blog/NRK_nekter___finne_og_utlevere_eventuell_avtale_med_MPEG_LA.html
">nektet
2098 å spore opp eventuell avtale med MPEG-LA
</a
> eller andre om bruk av
2099 MPEG/H
.264-video etter at jeg
<a
2100 href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html
">ba
2101 om innsyn i slike avtaler
</a
>, tenkte jeg at i stedet for å forsøke å
2102 få NRK til å finne en slik avtale, så burde det være like enkelt å
2103 spørre MPEG-LA om de hadde avtale med NRK. Spørsmålet ble sendt før
2104 jeg fikk tips fra Kieran Kunhya om hvor listen over lisensinnehavere
2105 "in Good Standing
" befant seg. MPEG-LA svarte meg i dag, og kan
2106 fortelle at NRK ikke har noen avtale med dem, så da er i det minste det
2107 slått fast. Ikke overraskende mener MPEG-LA at det trengs en avtale
2108 med MPEG-LA for å streame H
.264, men deres rammer er jo
2109 rettstilstanden i USA og ikke Norge. Jeg tar dermed den delen av
2110 svaret med en klype salt. Jeg er dermed fortsatt ikke klok på om det
2111 trengs en avtale, og hvis det trengs en avtale her i Norge, heller
2112 ikke sikker på om NRK har en avtale med noen andre enn MPEG-LA som
2113 gjør at de ikke trenger avtale direkte med MPEG-LA. Jeg håper NRKs
2114 jurister har vurdert dette, og at det er mulig å få tilgang til
2115 vurderingen uansett om de trenger en avtale eller ikke.
</p
>
2117 <p
>Her er epostutvekslingen med MPEG-LA så langt. Håper ikke
2118 utvekslingen fører til NRK plutselig får en litt uventet pakke fra
2121 <p
><blockquote
>
2122 <p
>Date: Mon,
25 Jun
2012 15:
29:
37 +
0200
2123 <br
>From: Petter Reinholdtsen
&lt;pere (at) hungry.com
&gt;
2124 <br
>To: licensing-web (at) mpegla.com
2125 <br
>Subject: Do NRK have a license agreement with MPEG-LA?
</p
>
2127 <p
>Hi. I have a small question for you, that I hope it is OK that I
2130 <p
>Is there any license agreements between MPEG-LA and NRK,
&lt;URL:
2131 <a href=
"http://www.nrk.no/
">http://www.nrk.no/
</a
> &gt;, the
2132 Norwegian national broadcasting cooperation? I am not sure if they
2133 need one, and am just curious if such agreeement exist.
</p
>
2135 <p
>The postal address is
</p
>
2137 <p
><blockquote
>
2139 <br
>Postbox
8500, Majorstuen
2142 </blockquote
></p
>
2144 <p
>if it make it easier for you to locate such agreement.
</p
>
2146 <p
>Can you tell me how many entities in Norway have an agreement with
2147 MPEG-LA, and the name of these entities?
</p
>
2150 <br
>Happy hacking
2151 <br
>Petter Reinholdtsen
2152 </blockquote
></p
>
2154 <p
>I dag, to dager senere, fikk jeg følgende svar:
</p
>
2156 <p
><blockquote
>
2157 <p
>Date: Thu,
28 Jun
2012 14:
11:
17 +
0000
2158 <br
>From: Ryan Rodriguez
&lt;RRodriguez (at) mpegla.com
>
2159 <br
>To: Petter Reinholdtsen
&lt;pere (at) hungry.com
>
2160 <br
>CC: MD Administration
&lt;MDAdministration (at) mpegla.com
>
2161 <br
>Subject: RE: Do NRK have a license agreement with MPEG-LA?
</p
>
2163 <p
>Dear Mr. Reinholdtsen,
</p
>
2165 <p
>Thank you for your message and for your interest in MPEG LA. We
2166 appreciate hearing from you and I will be happy to assist you.
</p
>
2168 <p
>To begin, I will assume that you are referring to AVC/H
.264
2169 technology in your message below, as this technology is commonly used
2170 in the transmission of video content. In that case, please allow me
2171 to briefly summarize the coverage provided by our AVC Patent Portfolio
2174 <P
>Our AVC License provides coverage for end products and video
2175 services that make use of AVC/H
.264 technology. Accordingly, the
2176 party offering such end products and video to End Users concludes the
2177 AVC License and is responsible for paying the applicable royalties
2178 associated with the end products/video they offer.
</p
>
2180 <p
>While the Norwegian Broadcast Corporation (NRK) is not currently a
2181 Licensee to MPEG LA
's AVC License (or any other Portfolio License
2182 offered by MPEG LA), if NRK offers AVC Video to End Users for
2183 remuneration (for example, Title-by-Title, Subscription, Free
2184 Television, or Internet Broadcast AVC Video), then NRK will need to
2185 conclude the AVC License and may be responsible for paying applicable
2186 royalties associated with the AVC Video it distributes.
</p
>
2188 <p
>Today I will send you a FedEx package containing a copy of our AVC
2189 License for your review. You should receive the License document
2190 within the next few days.
</p
>
2192 <p
>Meanwhile, MPEG LA currently has several Norwegian Licensees that
2193 can be found under the
"Licensees
" header within the respective
2194 portion of our website. For example, you may find our list of
2195 Licensees in Good Standing to our AVC License in the AVC portion of
2197 <a href=
"http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx
">http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx
</a
></p
>
2199 <p
>I hope the above information is helpful. If you have additional
2200 questions or need further assistance with the AVC License, please feel
2201 free to contact me directly. I look forward to hearing from you again
2204 <p
>Best regards,
</p
>
2206 <p
>Ryan
</p
>
2208 <p
>Ryan M. Rodriguez
2209 <br
>Licensing Associate
2211 <br
>5425 Wisconsin Avenue
2213 <br
>Chevy Chase, MD
20815
2215 <br
>Phone: +
1 (
301)
986-
6660 x211
2216 <br
>Fax: +
1 (
301)
986-
8575
2217 <br
>Email: rrodriguez (at) mpegla.com
</p
>
2219 </blockquote
></p
>
2221 <p
>Meldingen om utsendt FedEx-pakke var så merkelig at jeg
2222 øyeblikkelig sendte svar tilbake og spurte hva i alle dager han mente,
2223 da han jo ikke hadde fått noen postadresse som nådde meg.
</p
>
2225 <p
><blockquote
>
2227 <p
>Date: Thu,
28 Jun
2012 16:
36:
15 +
0200
2228 <br
>From: Petter Reinholdtsen
&lt;pere (at) hungry.com
&gt;
2229 <br
>To: Ryan Rodriguez
&lt;RRodriguez (at) mpegla.com
&gt;
2230 <br
>Cc: MD Administration
&lt;MDAdministration (at) mpegla.com
&gt;
2231 <br
>Subject: Re: Do NRK have a license agreement with MPEG-LA?
</p
>
2233 <p
>[Ryan Rodriguez]
2234 <br
>&gt; Dear Mr. Reinholdtsen,
</p
>
2236 <p
>Thank you for your quick reply.
</p
>
2238 <p
>&gt; Today I will send you a FedEx package containing a copy of our AVC
2239 <br
>&gt; License for your review. You should receive the License document
2240 <br
>&gt; within the next few days.
</p
>
2242 <p
>The part about sending a FedEx package confused me, though. I did not
2243 <br
>give you my address, nor am I associated with NRK in any way, so I hope
2244 <br
>you did not try to send me a package using the address of NRK. If you
2245 <br
>would send me the Internet address of to the document, it would be more
2246 <br
>useful to me to be able to download it as an electronic document.
</p
>
2248 <p
>&gt; Meanwhile, MPEG LA currently has several Norwegian Licensees that can
2249 <br
>&gt; be found under the
"Licensees
" header within the respective portion
2250 <br
>&gt; of our website. For example, you may find our list of Licensees in
2251 <br
>&gt; Good Standing to our AVC License in the AVC portion of our website,
2252 <br
>&gt; http://www.mpegla.com/main/programs/AVC/Pages/Licensees.aspx
</p
>
2254 <p
>How can I recognize the Norwegian licensees?
</p
>
2257 <br
>Happy hacking
2258 <br
>Petter Reinholdtsen
</p
>
2259 </blockquote
></p
>
2261 <p
>Selv om jeg svarte kun noen minutter etter at jeg fikk eposten fra
2262 MPEG-LA, fikk jeg eposten under som automatisk var beskjed på min
2263 siste epost. Får håpe noen likevel følger opp
"FedEx-pakken
". For å
2264 øke sjansen for at noen revurderer utsending av pakke uten mottaker,
2265 videresendte jeg min epost til swolf (at) mpegla.com, så får vi se.
2266 Har ikke hørt noe mer
3 timer senere, så jeg mistenker at ingen leste
2267 min epost tidsnok.
</p
>
2269 <p
><blockquote
>
2271 <p
>Date: Thu,
28 Jun
2012 14:
36:
20 +
0000
2272 <br
>From: Ryan Rodriguez
&lt;RRodriguez (at) mpegla.com
&gt;
2273 <br
>To: Petter Reinholdtsen
&lt;pere (at) hungry.com
&gt;
2274 <br
>Subject: Automatic reply: Do NRK have a license agreement with MPEG-LA?
</p
>
2276 <p
>Thank you for your message.
</p
>
2278 <p
>I will be out of the office until Thursday, July
5 and will respond
2279 to all messages upon my return. If this is a matter that requires
2280 immediate attention, please contact Sidney Wolf (swolf (at)
2281 mpegla.com)
</p
>
2283 <p
>Best regards,
</p
>
2285 <p
>Ryan
</p
>
2287 <p
>Ryan M. Rodriguez
2288 <br
>Licensing Associate
2289 <br
>MPEG LA
</p
>
2291 </blockquote
></p
>
2293 <p
>Litt klokere, men fortsatt ikke klok på mitt opprinnelige spørsmål,
2294 som er om en trenger avtale med MPEG-LA for å publisere eller
2295 kringkaste H
.264-video i Norge.
</p
>
2300 <title>Departementenes servicesenter har ingen avtale om bruk av H
.264 med MPEG-LA
</title>
2301 <link>http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html
</link>
2302 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Departementenes_servicesenter_har_ingen_avtale_om_bruk_av_H_264_med_MPEG_LA.html
</guid>
2303 <pubDate>Fri,
29 Jun
2012 09:
40:
00 +
0200</pubDate>
2304 <description><p
>Da fikk jeg nettopp svar fra
2305 <a href=
"http://www.dss.dep.no/
">Departementenes servicesenter
</a
>
2307 <a href=
"http://people.skolelinux.org/pere/blog/Trenger_en_avtale_med_MPEG_LA_for___publisere_og_kringkaste_H_264_video_.html
">mitt
2308 spørsmål om avtale rundt bruk av H
.264</a
>. De har ingen avtale med
2309 MPEG LA eller dets representanter. Her er svaret.
2311 <p
><blockquote
>
2313 <p
>Date: Fri,
29 Jun
2012 07:
04:
42 +
0000
2314 <br
>From: Nielsen Mette Haga
&lt;Mette-Haga.Nielsen (at) dss.dep.no
&gt;
2315 <br
>To: Petter Reinholdtsen
&lt;petter.reinholdtsen (at) ...
&gt;
2316 <br
>CC: Postmottak
&lt;Postmottak (at) dss.dep.no
&gt;
2317 <br
>Subject: SV: Innsynsbegjæring om MPEG/H
.264-relaterte avtaler
</p
>
2319 <p
>DSS har ikke inngått noen egen lisensavtale med MPEG-LA eller noen som
2320 representerer MPEG-LA i Norge. Videoløsningen på regjeringen.no er
2321 levert av Smartcom:tv. Lisensforholdet rundt H
.264 er ikke omtalt i
2322 vår avtale med Smartcom.
</p
>
2324 <p
>Vennlig hilsen
</p
>
2326 <p
>Mette Haga Nielsen
2327 <br
>Fung. seksjonssjef
</p
>
2329 <p
>Departementenes servicesenter
</p
>
2331 <p
>Informasjonsforvaltning
2333 <p
>Mobil
93 09 83 51
2334 <br
>E-post mette-haga.nielsen (at) dss.dep.no
</p
>
2335 </blockquote
></p
>
2337 <p
>Hvis den norske regjeringen representert ved DSS ikke har slik
2338 avtale, så kan en kanskje konkludere med at det ikke trengs? Jeg er
2339 ikke trygg på at det er god juridisk grunn å stå på, men det er i det
2340 minste interessant å vite at hverken NRK eller DSS har funnet det
2341 nødvendig å ha avtale om bruk av H
.264.
</p
>
2343 <p
>Det forklarer ikke hvordan de kan ignorere bruksvilkårene knyttet
2344 til bruk av opphavsrettsbeskyttet materiale de bruker til
2345 videoproduksjon, med mindre slike vilkår kan ignoreres av selskaper og
2346 privatpersoner i Norge. Har de lov til å bryte vilkårene, eller har
2347 de brutt dem og så langt sluppet unna med det? Jeg aner ikke.
</p
>
2352 <title>DIFI foreslår å kaste ut ODF og ta inn OOXML fra statens standardkatalog
</title>
2353 <link>http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html
</link>
2354 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/DIFI_foresl_r___kaste_ut_ODF_og_ta_inn_OOXML_fra_statens_standardkatalog.html
</guid>
2355 <pubDate>Fri,
29 Jun
2012 18:
00:
00 +
0200</pubDate>
2356 <description><p
>DIFI har nettopp annonsert høring om revisjon av
2357 <a href=
"http://www.standard.difi.no/forvaltningsstandarder
">standardkatalogen
</a
>,
2358 og endelig har Microsoft fått viljen sin. Se
2359 <a href=
"http://www.standard.difi.no/hoyring/forslag-om-endring-av-forskrift-om-it-standarder-i-offentlig-forvaltning
">høringssiden
</a
>
2360 for hele teksten.
</p
>
2362 <p
>Her er forslaget i sin helhet:
</p
>
2364 <p
><blockquote
>
2365 <p
>3.2 Revisjon av krav til redigerbare dokumenter
</p
>
2367 <p
>I første versjon av referansekatalogen i
2007 ble det satt krav om
2368 Open Document Format (ODF), versjon
1.1 (OASIS,
1.2.2007) for
2369 redigerbare dokumenter. Kravet var obligatorisk for stat og sterkt
2370 anbefalt for kommunal sektor. I
2009 ble kravet gjort obligatorisk for
2371 hele offentlig sektor i
2372 <a href=
"http://www.lovdata.no/for/sf/fa/xa-
20090925-
1222.html
">forskrift
2373 om IT-standarder i forvaltningen
</a
>. Anvendelsesområdet for kravet
2374 har vært begrenset til publisering av dokumenter som skal bearbeides
2375 videre (§
4 nr.
1 andre ledd). I
2011 ble anvendelsesområdet utvidet
2376 til å omfatte utveksling av dokumenter beregnet for redigering som
2377 vedlegg til e-post (§
4 nr.
2).
</p
>
2379 <p
>Office Open XML ISO/IEC
29500:
2011 (OOXML) er et dokumentformat
2380 opprinnelig utviklet av Microsoft med tilsvarende anvendelsesområde
2381 som ODF. Formatet er blant annet tatt i bruk i nyere versjoner av
2382 kontorstøtteprogamvaren MS Office. Difi har foretatt en
2383 <a href=
"http://www.standard.difi.no/filearchive/revisjonsvurdering-standarder-for-redigerbare-dokumenter-v1-
0.pdf
">revisjonsvurdering
</a
>
2384 av krav som stilles til redigerbare dokumenter i Forskrift om
2385 IT-standarder i forvaltningen, og anbefaler at kravet til ODF
2386 fjernes. Dette innebærer at det ikke stilles krav til dokumentformater
2387 for redigerbare dokumenter ved publisering på offentlige virksomheters
2388 nettsider og for redigerbare vedlegg til e-post som sendes fra
2389 offentlige virksomheter til innbyggere og næringsliv. Offentlige
2390 virksomheter vil dermed stå fritt til å publisere eller sende
2391 redigerbare dokumenter i det format som ivaretar brukernes behov
2394 <p
>Forslaget innebærer at krav til ODF utgår §
4 nr.
1 tredje ledd og
2395 §
4 nr.
2 første ledd
</p
>
2397 <P
>Imidlertid bør det stilles strengere krav til hvilke formater
2398 offentlige virksomheter plikter å motta redigerbare dokumenter. Vi
2399 mener at det ikke bør skilles mellom mottak av redigerbare dokumenter
2400 som sendes i ODF eller OOXML3, som begge er åpne standarder. Dette
2401 medfører at innbyggere og næringsliv skal kunne basere sitt valg av
2402 programvare på egne behov og ikke på de valg offentlige virksomheter
2403 tar. Kravet vil omfatte hele offentlig sektor, herunder
2404 utdanningssektoren, hvor det kanskje er størst bruk av ODF. Kravet er
2405 foreslått som ny §
4 nr
.2 andre ledd
</p
>
2406 </blockquote
></p
>
2408 <P
>De satser vel på at det hele blir glemt over sommeren, og at de
2409 fleste har glemt Standard Norge og ISOs fallitt fra da OOXML ble
2410 jukset igjennom som ISO-standard. Jeg håper mine lesere sender inn
2411 høringsuttalelser til høringen.
</p
>
2413 <p
>Anbefaler alle å friske opp sine argumenter ved å lese
2414 <a href=
"http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html
">svaret
2415 fra senator Edgar Villanueva til Microsoft i Peru
</a
>. Det er en
2416 klassisk tekst som er like gyldig i dag som da det ble skrevet.
</p
>
2422 <title>Mer oppfølging fra MPEG-LA om avtale med dem for å kringkaste og publisere H
.264-video
</title>
2423 <link>http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html
</link>
2424 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Mer_oppf_lging_fra_MPEG_LA_om_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html
</guid>
2425 <pubDate>Thu,
5 Jul
2012 23:
50:
00 +
0200</pubDate>
2426 <description><p
>I føljetongen om H
.264
2427 <a href=
"http://people.skolelinux.org/pere/blog/MPEG_LA_mener_NRK_m__ha_avtale_med_dem_for___kringkaste_og_publisere_H_264_video.html
">forlot
2428 jeg leserne i undring
</a
> om hvor pakken fra MPEG-LA tok veien, og om
2429 hvilke selskaper i Norge som har avtale med MPEG-LA. Da Ryan hos
2430 MPEG-LA dro på ferie sendte jeg min melding videre til hans kollega,
2431 og dagen etter fikk jeg følgende svar derfra:
</p
>
2433 <p
><blockquote
>
2434 <p
>Date: Fri,
29 Jun
2012 18:
32:
34 +
0000
2435 <br
>From: Sidney Wolf
&lt;SWolf (at) mpegla.com
&gt;
2436 <br
>To: Petter Reinholdtsen
&lt;pere (at) hungry.com
&gt;
2437 <br
>Cc: Ryan Rodriguez
&lt;RRodriguez (at) mpegla.com
&gt;
2438 <br
>Subject: RE: Do NRK have a license agreement with MPEG-LA?
</p
>
2440 <p
>Dear Mr. Reinholdtsen,
</p
>
2442 <p
>Thank you for your message. As you know, Ryan is currently our of the
2443 office, so it will be my pleasure to assist you.
</p
>
2445 <p
>Per your request, attached please find an electronic copy of the
2446 AVC Patent Portfolio License. Please note that the electronic copy of
2447 the License is provided as a convenience and for informational
2448 purposes only. When concluding the Licenses, only the hard copies
2449 provided by MPEG LA may be used.
</p
>
2451 <p
>To your question, MPEG LA lists our Licensees on our website
2452 according to each program. The lists are in alphabetical order, so it
2453 is very easy to search.
</p
>
2455 <p
>I hope that this was helpful. If we can be of additional
2456 assistance, please let me know.
</p
>
2458 <p
>Kind regards,
</p
>
2460 <p
>Sidney A. Wolf
2461 <br
>Manager, Global Licensing
2462 <br
>MPEG LA
</p
>
2463 </blockquote
></p
>
2465 <p
>Selv om et epostvedlegg er nyttig for mottakeren, så håpet jeg å få
2466 et dokument jeg kunne dele med alle leserne av bloggen min, og ikke et
2467 som må deles på individuell basis. Opphavsretten krever godkjenning
2468 fra rettighetsinnehaver før en kan gjøre slikt, så dermed fulgte jeg
2469 opp med et spørsmål om dette var greit.
</p
>
2471 <p
><blockquote
>
2472 <p
>Date: Wed,
4 Jul
2012 20:
25:
06 +
0200
2473 <br
>From: Petter Reinholdtsen
&lt;pere (at) hungry.com
&gt;
2474 <br
>To: Sidney Wolf
&lt;SWolf (at) mpegla.com
&gt;
2475 <br
>Cc: Ryan Rodriguez
&lt;RRodriguez (at) mpegla.com
&gt;
2476 <br
>Subject: Re: Do NRK have a license agreement with MPEG-LA?
</p
>
2478 <p
>Thank you for your reply.
</p
>
2480 <p
>[Sidney Wolf]
2481 <br
>&gt; Per your request, attached please find an electronic copy of the AVC
2482 <br
>&gt; Patent Portfolio License. Please note that the electronic copy of
2483 <br
>&gt; the License is provided as a convenience and for informational
2484 <br
>&gt; purposes only. When concluding the Licenses, only the hard copies
2485 <br
>&gt; provided by MPEG LA may be used.
</p
>
2487 <p
>This is useful for me to learn, but the reason I asked for the
2488 Internet address of the licensing document was to ensure I could
2489 publish a link to it when I discuss the topic of H
.264 licensing here
2490 in Norway, and allow others to verify my observations. I can not do
2491 the same with an email attachment. Thus I would like to ask you if it
2492 is OK with MPEG LA that I publish this document on the Internet for
2493 others to read?
</p
>
2495 <p
>&gt; To your question, MPEG LA lists our Licensees on our website
2496 <br
>&gt; according to each program. The lists are in alphabetical order, so
2497 <br
>&gt; it is very easy to search.
</p
>
2499 <p
>I am afraid this do not help me locate Norwegian companies in the
2500 list of Licensees. I do not know the name of all companies and
2501 organisations in Norway, and thus do not know how to locate the
2502 Norwegian ones on that list.
</p
>
2504 <p
>&gt; I hope that this was helpful. If we can be of additional assistance,
2505 <br
>&gt; please let me know.
</p
>
2507 <p
>Absoutely helpful to learn more about how MPEG LA handle licensing.
</p
>
2510 <br
>Happy hacking
2511 <br
>Petter Reinholdtsen
</p
>
2512 </blockquote
></p
>
2514 <p
>Jeg håpet også at det skulle være mulig å få vite hvilke av de
2515 mange hundre som har avtale med MPEG-LA om bruk av H
.264 som holdt til
2516 i Norge. Begge mine håp falt i grus med svaret fra MPEG-LA.
2518 <p
><blockquote
>
2519 <p
>Date: Thu,
5 Jul
2012 17:
42:
39 +
0000
2520 <br
>From: Sidney Wolf
&lt;SWolf (at) mpegla.com
&gt;
2521 <br
>To:
'Petter Reinholdtsen
' &lt;pere (at) hungry.com
&gt;
2522 <br
>Cc: Ryan Rodriguez
&lt;RRodriguez (at) mpegla.com
&gt;
2523 <br
>Subject: RE: Do NRK have a license agreement with MPEG-LA?
</p
>
2525 <p
>Dear Mr. Reinholdtsen,
</p
>
2527 <p
>Thank you for your reply.
</p
>
2529 <p
>We appreciate the additional explanation you have provided and for
2530 asking our permission to publish the electronic copy of the License in
2531 advance of doing so. Typically, MPEG LA prefers to distribute the
2532 electronic copies of our Licenses to interested parties. Therefore,
2533 please feel free to send interested parties to the AVC portion of our
2534 website, http://www.mpegla.com/main/programs/AVC/Pages/Intro.aspx for
2535 their further reference.
</p
>
2537 <p
>As previously mentioned, MPEG LA maintains a list of Licensees in good
2538 standing on our website according to each program. Due to the large
2539 volume of Licensees, it would be administratively impractical to
2540 provide this level of detail to interested parties. Therefore, I am
2541 afraid we are not in a position to assist you with your request.
</p
>
2543 <p
>Kind regards,
</p
>
2545 <p
>Sidney A. Wolf
2546 <br
>Manager, Global Licensing
2547 <br
>MPEG LA
</p
>
2548 </blockquote
></p
>
2550 <p
>Men takket være epostvedlegget kunne jeg søke på Google etter
2551 setningen
"WHEREAS, a video standard commonly referred to as AVC has
2552 been defined and is referred to in this Agreement as the “AVC
2553 Standard” (as more fully defined herein below)
" som finnes i avtalen,
2554 og lokalisere en kopi fra
2007 av
2555 <a href=
"http://www.sec.gov/Archives/edgar/data/
1342960/
000119312509050004/dex1024.htm
">lisensavtalen
2556 mellom MPEG-LA og DivX, Inc.
</a
>, slik at mine lesere kan se hvordan
2557 avtalen så ut da. Jeg har ikke sammenlignet tekstene for å se om noe
2558 har endret seg siden den tid, men satser på at teksten er representativ.
</p
>
2560 <p
>Jeg aner fortsatt ikke hvor FedEx tok veien med pakken fra
2563 <p
>Update
2012-
07-
06: Jeg er visst ikke den første som forsøker å få
2564 klarhet i problemstillinger rundt H
.264, og kom nettopp over en veldig
2565 interessant bloggpost fra
2010 hos LibreVideo med tittelen
2566 "<ahref=
"http://www.librevideo.org/blog/
2010/
06/
14/mpeg-la-answers-some-questions-about-avch-
264-licensing/
">MPEG-LA
2567 answers some questions about AVC/H
.264 licensing
</a
>. Anbefales!
</p
>
projects / homepage.git / blob