<link>http://people.skolelinux.org/pere/blog/Student_group_continue_the_work_on_my_Reprap_3D_printer.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Student_group_continue_the_work_on_my_Reprap_3D_printer.html</guid>
<pubDate>Thu, 9 Dec 2010 19:30:00 +0100</pubDate>
- <description>
-<p>A few days ago, I was introduces to some students in the robot
+ <description><p>A few days ago, I was introduces to some students in the robot
student assosiation <a href="http://www.robotica.no/">Robotica
Osloensis</a> at the University of Oslo where I work, who planned to
get their own 3D printer. They wanted to learn from me based on my
<item>
<title>Martin Bekkelund: En stille bønn om Datalagringsdirektivet</title>
- <link>http://people.skolelinux.org/pere/blog/Martin_Bekkelund__En_stille_b__nn_om_Datalagringsdirektivet.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Martin_Bekkelund__En_stille_b__nn_om_Datalagringsdirektivet.html</guid>
+ <link>http://people.skolelinux.org/pere/blog/Martin_Bekkelund__En_stille_b_nn_om_Datalagringsdirektivet.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Martin_Bekkelund__En_stille_b_nn_om_Datalagringsdirektivet.html</guid>
<pubDate>Thu, 9 Dec 2010 21:25:00 +0100</pubDate>
- <description>
-<p><a href="http://www.bekkelund.net/">Martin Bekkelund</a> ved
+ <description><p><a href="http://www.bekkelund.net/">Martin Bekkelund</a> ved
<a href="http://www.friprog.no/">friprog-senteret</a> har skrevet
følgende
<a href="http://www.bekkelund.net/2010/12/09/en-stille-bonn/">korte
<link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
<pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
- <description>
-<p>With this weeks lawless
+ <description><p>With this weeks lawless
<a href="http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html">governmental
attacks</a> on Wikileak and
<a href="http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech">free
<item>
<title>Pornoskannerne på flyplassene bedrer visst ikke sikkerheten</title>
- <link>http://people.skolelinux.org/pere/blog/Pornoskannerne_p___flyplassene_bedrer_visst_ikke_sikkerheten.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Pornoskannerne_p___flyplassene_bedrer_visst_ikke_sikkerheten.html</guid>
+ <link>http://people.skolelinux.org/pere/blog/Pornoskannerne_p__flyplassene_bedrer_visst_ikke_sikkerheten.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Pornoskannerne_p__flyplassene_bedrer_visst_ikke_sikkerheten.html</guid>
<pubDate>Sat, 11 Dec 2010 10:45:00 +0100</pubDate>
- <description>
-<p>Via <a href="http://webmink.com/2010/12/10/links-for-2010-12-10/">en
+ <description><p>Via <a href="http://webmink.com/2010/12/10/links-for-2010-12-10/">en
blogpost fra Simon Phipps i går</a>, fant jeg en referanse til
<a href="http://www.washingtontimes.com/news/2010/dec/9/exposed-tsas-x-rated-scanner-fraud/">en
artikkel i Washington Times</a> som igjen refererer til en artikkel i
<link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
<pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
- <description>
-<p>As I continue to explore
+ <description><p>As I continue to explore
<a href="http://www.bitcoin.org/">BitCoin</a>, I've starting to wonder
what properties the system have, and how it will be affected by laws
and regulations here in Norway. Here are some random notes.</p>
<link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
<pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
- <description>
-<p>The last few days I have spent at work here at the <a
-href="http://www.uio.no/">University of oslo</a> testing if the new
+ <description><p>The last few days I have spent at work here at the <a
+href="http://www.uio.no/">University of Oslo</a> testing if the new
batch of computers will work with Linux. Every year for the last few
-years the university have organized shared bid of a few thousand
+years the university have organised shared bid of a few thousand
computers, and this year HP won the bid. Two different desktops and
five different laptops are on the list this year. We in the UNIX
group want to know which one of these computers work well with RHEL
memory modules lying around, and stick them in and see if Gnome/KDE
notice this.</li>
-<li>For laptops, is suspecd/hibernate working? I'm testing if the
+<li>For laptops, is suspend/hibernate working? I'm testing if the
special button work, and if the laptop continue to work after
resume.</li>
fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
can see, I have most machines left to test. One interesting
-observation is that Ubuntu Lucid has almost twice the framerate than
+observation is that Ubuntu Lucid has almost twice the frame rate than
RHEL6 with glxgears. No idea why.</p>
</description>
</item>
<item>
<title>165 norske overvåkningskamera registert så langt i OpenStreetmap.org</title>
- <link>http://people.skolelinux.org/pere/blog/165_norske_overv__kningskamera_registert_s___langt_i_OpenStreetmap_org.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/165_norske_overv__kningskamera_registert_s___langt_i_OpenStreetmap_org.html</guid>
+ <link>http://people.skolelinux.org/pere/blog/165_norske_overv_kningskamera_registert_s__langt_i_OpenStreetmap_org.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/165_norske_overv_kningskamera_registert_s__langt_i_OpenStreetmap_org.html</guid>
<pubDate>Fri, 24 Dec 2010 11:20:00 +0100</pubDate>
- <description>
-<p>Jeg flikket litt på OpenStreetmap.org i går, og oppdaget ved en
+ <description><p>Jeg flikket litt på OpenStreetmap.org i går, og oppdaget ved en
tilfeldighet at det er en rekke noder som representerer
overvåkningskamera som ikke blir med på kartet med overvåkningskamera
i Norge som
<link>http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Officeshots_still_going_strong.html</guid>
<pubDate>Sat, 25 Dec 2010 09:40:00 +0100</pubDate>
- <description>
-<p>Half a year ago I
+ <description><p>Half a year ago I
<a href="http://people.skolelinux.org/pere/blog/Officeshots_taking_shape.html">wrote
a bit</a> about <a href="http://www.officeshots.org/">OfficeShots</a>,
a web service to allow anyone to test how ODF documents are handled by
<link>http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_reply_from_Edgar_Villanueva_to_Microsoft_in_Peru.html</guid>
<pubDate>Sat, 25 Dec 2010 10:50:00 +0100</pubDate>
- <description>
-<p>A few days ago
+ <description><p>A few days ago
<a href="http://www.idg.no/computerworld/article189879.ece">an
article</a> in the Norwegian Computerworld magazine about how version
2.0 of
<p>In respect of the guarantee:</p>
-A<p>s you know perfectly well, or could find out by reading the "End User License Agreement" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.</p>
+<p>As you know perfectly well, or could find out by reading the "End User License Agreement" of the products you license, in the great majority of cases the guarantees are limited to replacement of the storage medium in case of defects, but in no case is compensation given for direct or indirect damages, loss of profits, etc... If as a result of a security bug in one of your products, not fixed in time by yourselves, an attacker managed to compromise crucial State systems, what guarantees, reparations and compensation would your company make in accordance with your licensing conditions? The guarantees of proprietary software, inasmuch as programs are delivered ``AS IS'', that is, in the state in which they are, with no additional responsibility of the provider in respect of function, in no way differ from those normal with free software.</p>
<p>On Intellectual Property:</p>
<link>http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html</link>
<guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html</guid>
<pubDate>Sat, 25 Dec 2010 20:25:00 +0100</pubDate>
- <description>
-<p><a href="http://www.digistan.org/open-standard:definition">The
+ <description><p><a href="http://www.digistan.org/open-standard:definition">The
Digistan definition</a> of a free and open standard reads like this:</p>
<blockquote>
documentation indicating this.</p>
<p>According to
-<ahref="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
+<a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
government, the Xiph foundation is a non-commercial organisation and
the development process is open, transparent and non-Discrimatory.
this and decided to implement Ogg Theora support in their browsers
without paying any royalties. For now the claims from MPEG-LA and
Steve Jobs seem more like FUD to scare people to use the H.264 codec
-than any real problem with Ogg Theora.
+than any real problem with Ogg Theora.</p>
<p><strong>No constraints on re-use?</strong></p>
</description>
</item>
+ <item>
+ <title>The many definitions of a open standard</title>
+ <link>http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_many_definitions_of_a_open_standard.html</guid>
+ <pubDate>Mon, 27 Dec 2010 14:45:00 +0100</pubDate>
+ <description><p>One of the reasons I like the Digistan definition of
+"<a href="http://www.digistan.org/open-standard:definition">Free and
+Open Standard</a>" is that this is a new term, and thus the meaning of
+the term has been decided by Digistan. The term "Open Standard" has
+become so misunderstood that it is no longer very useful when talking
+about standards. One end up discussing which definition is the best
+one and with such frame the only one gaining are the proponents of
+de-facto standards and proprietary solutions.</p>
+
+<p>But to give us an idea about the diversity of definitions of open
+standards, here are a few that I know about. This list is not
+complete, but can be a starting point for those that want to do a
+complete survey. More definitions are available on the
+<a href="http://en.wikipedia.org/wiki/Open_standard">wikipedia
+page</a>.</p>
+
+<p>First off is my favourite, the definition from the European
+Interoperability Framework version 1.0. Really sad to notice that BSA
+and others has succeeded in getting it removed from version 2.0 of the
+framework by stacking the committee drafting the new version with
+their own people. Anyway, the definition is still available and it
+include the key properties needed to make sure everyone can use a
+specification on equal terms.</p>
+
+<blockquote>
+
+<p>The following are the minimal characteristics that a specification
+and its attendant documents must have in order to be considered an
+open standard:</p>
+
+<ul>
+
+<li>The standard is adopted and will be maintained by a not-for-profit
+organisation, and its ongoing development occurs on the basis of an
+open decision-making procedure available to all interested parties
+(consensus or majority decision etc.).</li>
+
+<li>The standard has been published and the standard specification
+document is available either freely or at a nominal charge. It must be
+permissible to all to copy, distribute and use it for no fee or at a
+nominal fee.</li>
+
+<li>The intellectual property - i.e. patents possibly present - of
+(parts of) the standard is made irrevocably available on a royalty-
+free basis.</li>
+
+<li>There are no constraints on the re-use of the standard.</li>
+
+</ul>
+</blockquote>
+
+<p>Another one originates from my friends over at
+<a href="http://www.dkuug.dk/">DKUUG</a>, who coined and gathered
+support for <a href="http://www.aaben-standard.dk/">this
+definition</a> in 2004. It even made it into the Danish parlament as
+<a href="http://www.ft.dk/dokumenter/tingdok.aspx?/samling/20051/beslutningsforslag/B103/som_fremsat.htm">their
+definition of a open standard</a>. Another from a different part of
+the Danish government is available from the wikipedia page.</p>
+
+<blockquote>
+
+<p>En åben standard opfylder følgende krav:</p>
+
+<ol>
+
+<li>Veldokumenteret med den fuldstændige specifikation offentligt
+tilgængelig.</li>
+
+<li>Frit implementerbar uden økonomiske, politiske eller juridiske
+begrænsninger på implementation og anvendelse.</li>
+
+<li>Standardiseret og vedligeholdt i et åbent forum (en såkaldt
+"standardiseringsorganisation") via en åben proces.</li>
+
+</ol>
+
+</blockquote>
+
+<p>Then there is <a href="http://www.fsfe.org/projects/os/def.html">the
+definition</a> from Free Software Foundation Europe.</p>
+
+<blockquote>
+
+<p>An Open Standard refers to a format or protocol that is</p>
+
+<ol>
+
+<li>subject to full public assessment and use without constraints in a
+manner equally available to all parties;</li>
+
+<li>without any components or extensions that have dependencies on
+formats or protocols that do not meet the definition of an Open
+Standard themselves;</li>
+
+<li>free from legal or technical clauses that limit its utilisation by
+any party or in any business model;</li>
+
+<li>managed and further developed independently of any single vendor
+in a process open to the equal participation of competitors and third
+parties;</li>
+
+<li>available in multiple complete implementations by competing
+vendors, or as a complete implementation equally available to all
+parties.</li>
+
+</ol>
+
+</blockquote>
+
+<p>A long time ago, SUN Microsystems, now bought by Oracle, created
+its
+<a href="http://blogs.sun.com/dennisding/resource/Open%20Standard%20Definition.pdf">Open
+Standards Checklist</a> with a fairly detailed description.</p>
+
+<blockquote>
+<p>Creation and Management of an Open Standard
+
+<ul>
+
+<li>Its development and management process must be collaborative and
+ democratic:
+
+ <ul>
+
+ <li>Participation must be accessible to all those who wish to
+ participate and can meet fair and reasonable criteria
+ imposed by the organization under which it is developed
+ and managed.</li>
+
+ <li>The processes must be documented and, through a known
+ method, can be changed through input from all
+ participants.</li>
+
+ <li>The process must be based on formal and binding commitments for
+ the disclosure and licensing of intellectual property rights.</li>
+
+ <li>Development and management should strive for consensus,
+ and an appeals process must be clearly outlined.</li>
+
+ <li>The standard specification must be open to extensive
+ public review at least once in its life-cycle, with
+ comments duly discussed and acted upon, if required.</li>
+
+ </ul>
+
+</li>
+
+</ul>
+
+<p>Use and Licensing of an Open Standard</p>
+<ul>
+
+<li>The standard must describe an interface, not an implementation,
+ and the industry must be capable of creating multiple, competing
+ implementations to the interface described in the standard without
+ undue or restrictive constraints. Interfaces include APIs,
+ protocols, schemas, data formats and their encoding.</li>
+
+<li> The standard must not contain any proprietary "hooks" that create
+ a technical or economic barriers</li>
+
+<li>Faithful implementations of the standard must
+ interoperate. Interoperability means the ability of a computer
+ program to communicate and exchange information with other computer
+ programs and mutually to use the information which has been
+ exchanged. This includes the ability to use, convert, or exchange
+ file formats, protocols, schemas, interface information or
+ conventions, so as to permit the computer program to work with other
+ computer programs and users in all the ways in which they are
+ intended to function.</li>
+
+<li>It must be permissible for anyone to copy, distribute and read the
+ standard for a nominal fee, or even no fee. If there is a fee, it
+ must be low enough to not preclude widespread use.</li>
+
+<li>It must be possible for anyone to obtain free (no royalties or
+ fees; also known as "royalty free"), worldwide, non-exclusive and
+ perpetual licenses to all essential patent claims to make, use and
+ sell products based on the standard. The only exceptions are
+ terminations per the reciprocity and defensive suspension terms
+ outlined below. Essential patent claims include pending, unpublished
+ patents, published patents, and patent applications. The license is
+ only for the exact scope of the standard in question.
+
+ <ul>
+
+ <li> May be conditioned only on reciprocal licenses to any of
+ licensees' patent claims essential to practice that standard
+ (also known as a reciprocity clause)</li>
+
+ <li> May be terminated as to any licensee who sues the licensor
+ or any other licensee for infringement of patent claims
+ essential to practice that standard (also known as a
+ "defensive suspension" clause)</li>
+
+ <li> The same licensing terms are available to every potential
+ licensor</li>
+
+ </ul>
+</li>
+
+<li>The licensing terms of an open standards must not preclude
+ implementations of that standard under open source licensing terms
+ or restricted licensing terms</li>
+
+</ul>
+
+</blockquote>
+
+<p>It is said that one of the nice things about standards is that
+there are so many of them. As you can see, the same holds true for
+open standard definitions. Most of the definitions have a lot in
+common, and it is not really controversial what properties a open
+standard should have, but the diversity of definitions have made it
+possible for those that want to avoid a level marked field and real
+competition to downplay the significance of open standards. I hope we
+can turn this tide by focusing on the advantages of Free and Open
+Standards.</p>
+</description>
+ </item>
+
+ <item>
+ <title>What standards are Free and Open as defined by Digistan?</title>
+ <link>http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_standards_are_Free_and_Open_as_defined_by_Digistan_.html</guid>
+ <pubDate>Thu, 30 Dec 2010 23:15:00 +0100</pubDate>
+ <description><p>After trying to
+<a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">compare
+Ogg Theora</a> to
+<a href="http://www.digistan.org/open-standard:definition">the Digistan
+definition</a> of a free and open standard, I concluded that this need
+to be done for more standards and started on a framework for doing
+this. As a start, I want to get the status for all the standards in
+the Norwegian reference directory, which include UTF-8, HTML, PDF, ODF,
+JPEG, PNG, SVG and others. But to be able to complete this in a
+reasonable time frame, I will need help.</p>
+
+<p>If you want to help out with this work, please visit
+<a href="http://wiki.nuug.no/grupper/standard/digistan-analyse">the
+wiki pages I have set up for this</a>, and let me know that you want
+to help out. The IRC channel #nuug on irc.freenode.net is a good
+place to coordinate this for now, as it is the IRC channel for the
+NUUG association where I have created the framework (I am the leader
+of the Norwegian Unix User Group).</p>
+
+<p>The framework is still forming, and a lot is left to do. Do not be
+scared by the sketchy form of the current pages. :)</p>
+</description>
+ </item>
+
</channel>
</rss>
projects / homepage.git / blobdiff