-<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 useful very 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 by 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>
-</div>
- <div class="tags">
-
-
-
- Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
-
- </div>
- </div>
- <div class="padding"></div>
-
- <div class="entry">
- <div class="title"><a href="http://people.skolelinux.org/pere/blog/Is_Ogg_Theora_a_free_and_open_standard_.html">Is Ogg Theora a free and open standard?</a></div>
- <div class="date">2010-12-25 20:25</div>
- <div class="body">
-<p><a href="http://www.digistan.org/open-standard:definition">The
-Digistan definition</a> of a free and open standard reads like this:</p>
-
-<blockquote>
-
-<p>The Digital Standards Organization defines free and open standard
-as follows:</p>
-
-<ol>
-
-<li>A free and open standard is immune to vendor capture at all stages
-in its life-cycle. Immunity from vendor capture makes it possible to
-freely use, improve upon, trust, and extend a standard over time.</li>
-
-<li>The standard is adopted and will be maintained by a not-for-profit
-organisation, and its ongoing development occurs on the basis of an
-open decision-making procedure available to all interested
-parties.</li>
-
-<li>The standard has been published and the standard specification
-document is available freely. It must be permissible to all to copy,
-distribute, and use it freely.</li>
-
-<li>The patents possibly present on (parts of) the standard are made
-irrevocably available on a royalty-free basis.</li>
-
-<li>There are no constraints on the re-use of the standard.</li>
-
-</ol>
-
-<p>The economic outcome of a free and open standard, which can be
-measured, is that it enables perfect competition between suppliers of
-products based on the standard.</p>
-</blockquote>
-
-<p>For a while now I have tried to figure out of Ogg Theora is a free
-and open standard according to this definition. Here is a short
-writeup of what I have been able to gather so far. I brought up the
-topic on the Xiph advocacy mailing list
-<a href="http://lists.xiph.org/pipermail/advocacy/2009-July/001632.html">in
-July 2009</a>, for those that want to see some background information.
-According to Ivo Emanuel Gonçalves and Monty Montgomery on that list
-the Ogg Theora specification fulfils the Digistan definition.</p>
-
-<p><strong>Free from vendor capture?</strong></p>
-
-<p>As far as I can see, there is no single vendor that can control the
-Ogg Theora specification. It can be argued that the
-<a href="http://www.xiph.org/">Xiph foundation</A> is such vendor, but
-given that it is a non-profit foundation with the expressed goal
-making free and open protocols and standards available, it is not
-obvious that this is a real risk. One issue with the Xiph
-foundation is that its inner working (as in board member list, or who
-control the foundation) are not easily available on the web. I've
-been unable to find out who is in the foundation board, and have not
-seen any accounting information documenting how money is handled nor
-where is is spent in the foundation. It is thus not obvious for an
-external observer who control The Xiph foundation, and for all I know
-it is possible for a single vendor to take control over the
-specification. But it seem unlikely.</p>
-
-<p><strong>Maintained by open not-for-profit organisation?</strong></p>
-
-<p>Assuming that the Xiph foundation is the organisation its web pages
-claim it to be, this point is fulfilled. If Xiph foundation is
-controlled by a single vendor, it isn't, but I have not found any
-documentation indicating this.</p>
-
-<p>According to
-<a href="http://media.hiof.no/diverse/fad/rapport_4.pdf">a report</a>
-prepared by Audun Vaaler og Børre Ludvigsen for the Norwegian
-government, the Xiph foundation is a non-commercial organisation and
-the development process is open, transparent and non-Discrimatory.
-Until proven otherwise, I believe it make most sense to believe the
-report is correct.</p>
-
-<p><strong>Specification freely available?</strong></p>
-
-<p>The specification for the <a href="http://www.xiph.org/ogg/doc/">Ogg
-container format</a> and both the
-<a href="http://www.xiph.org/vorbis/doc/">Vorbis</a> and
-<a href="http://theora.org/doc/">Theora</a> codeces are available on
-the web. This are the terms in the Vorbis and Theora specification:
-
-<blockquote>
-
-Anyone may freely use and distribute the Ogg and [Vorbis/Theora]
-specifications, whether in private, public, or corporate
-capacity. However, the Xiph.Org Foundation and the Ogg project reserve
-the right to set the Ogg [Vorbis/Theora] specification and certify
-specification compliance.
-
-</blockquote>
-
-<p>The Ogg container format is specified in IETF
-<a href="http://www.xiph.org/ogg/doc/rfc3533.txt">RFC 3533</a>, and
-this is the term:<p>
-
-<blockquote>
-
-<p>This document and translations of it may be copied and furnished to
-others, and derivative works that comment on or otherwise explain it
-or assist in its implementation may be prepared, copied, published and
-distributed, in whole or in part, without restriction of any kind,
-provided that the above copyright notice and this paragraph are
-included on all such copies and derivative works. However, this
-document itself may not be modified in any way, such as by removing
-the copyright notice or references to the Internet Society or other
-Internet organizations, except as needed for the purpose of developing
-Internet standards in which case the procedures for copyrights defined
-in the Internet Standards process must be followed, or as required to
-translate it into languages other than English.</p>
-
-<p>The limited permissions granted above are perpetual and will not be
-revoked by the Internet Society or its successors or assigns.</p>
-</blockquote>
-
-<p>All these terms seem to allow unlimited distribution and use, an
-this term seem to be fulfilled. There might be a problem with the
-missing permission to distribute modified versions of the text, and
-thus reuse it in other specifications. Not quite sure if that is a
-requirement for the Digistan definition.</p>
-
-<p><strong>Royalty-free?</strong></p>
-
-<p>There are no known patent claims requiring royalties for the Ogg
-Theora format.
-<a href="http://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=65782">MPEG-LA</a>
-and
-<a href="http://yro.slashdot.org/story/10/04/30/237238/Steve-Jobs-Hints-At-Theora-Lawsuit">Steve
-Jobs</a> in Apple claim to know about some patent claims (submarine
-patents) against the Theora format, but no-one else seem to believe
-them. Both Opera Software and the Mozilla Foundation have looked into
-this and decided to implement Ogg Theora support in their browsers
-without paying any royalties. For now the claims from MPEG-LA and
-Steve Jobs seem more like FUD to scare people to use the H.264 codec
-than any real problem with Ogg Theora.
-
-<p><strong>No constraints on re-use?</strong></p>
-
-<p>I am not aware of any constraints on re-use.</p>
-
-<p><strong>Conclusion</strong></p>
-
-<p>3 of 5 requirements seem obviously fulfilled, and the remaining 2
-depend on the governing structure of the Xiph foundation. Given the
-background report used by the Norwegian government, I believe it is
-safe to assume the last two requirements are fulfilled too, but it
-would be nice if the Xiph foundation web site made it easier to verify
-this.</p>
-
-<p>It would be nice to see other analysis of other specifications to
-see if they are free and open standards.</p>
+<p>I går lanserte vi i <a href="http://www.nuug.no/">foreningen NUUG</a>
+<a href="http://www.fiksgatami.no/">FiksGataMi</a>, med
+<a href="http://lists.nuug.no/pipermail/interesserte/2011-March/000457.html">pressemelding
+på epost</a> til alle NUUGs annonseringsliste, medlemmene, alle
+landets redaksjoner og alle landets kommuner og fylkeskommuner.
+Responsen har vært formidabel, og vi har en enorm baklogg av
+henvendelser å følge opp. Vi jobber oss sakte men sikkert igjennom
+stabelen. Alt sendes til NUUGs RT-instans slik at ingen blir glemt.
+Hvis du har kommentarer og spørsmål, bruk
+<a href="http://www.fiksgatami.no/contact">kontaktfeltet</a> på
+FiksGatami, eller send epost til adressen som er oppgitt der.</p>
+
+<p>Pr nå er det kommet inn over 600 problemer som er rapportert videre
+til kommuner og fylker. Jeg hentet ut fordelingen på kategorier nå
+nettopp, for å se hva som opptar innbyggerne rundt om i det ganske
+land. Det er mest aktivitet i Trondheim, fulgt av Oslo og Bergen, men
+godt over 100 kommuner og fylker har fått meldinger fra innbyggerne
+via FiksGatami så langt.</p>
+
+<table>
+<tr><th>count</th><th>category</th></tr>
+<tr><td>398</td><td>Hull i vei</td></tr>
+<tr><td> 83</td><td>Gater/Veier</td></tr>
+<tr><td> 65</td><td>Snøbrøyting</td></tr>
+<tr><td> 54</td><td>Gatelys</td></tr>
+<tr><td> 46</td><td>Annet</td></tr>
+<tr><td> 30</td><td>Fortau/gangstier</td></tr>
+<tr><td> 17</td><td>Tette avløpsrister</td></tr>
+<tr><td> 10</td><td>Trafikkskilter</td></tr>
+<tr><td> 7</td><td>Parkering</td></tr>
+<tr><td> 7</td><td>Forlatte kjøretøy</td></tr>
+<tr><td> 4</td><td>Trafikklys</td></tr>
+<tr><td> 4</td><td>Sykkelveier</td></tr>
+<tr><td> 4</td><td>Forsøpling</td></tr>
+<tr><td> 3</td><td>Buss- og togstopp</td></tr>
+<tr><td> 3</td><td>Vannforsyning</td></tr>
+<tr><td> 3</td><td>Universell utforming</td></tr>
+<tr><td> 3</td><td>Trær</td></tr>
+<tr><td> 2</td><td>Graffiti/tagging</td></tr>
+<tr><td> 2</td><td>Dumpet skrot</td></tr>
+<tr><td> 1</td><td>Park/landskap</td></tr>
+<tr><td> 1</td><td>Ulovlige oppslag</td></tr>
+<tr><td> 1</td><td>Offentlige toaletter</td></td></tr>
+</table>
+
+<p>Det gjenstår endel jobb med skalering før vi er fornøyd med
+ytelsen, og så må vi få skrevet litt mer informasjon til kommunene om
+hvordan systemet fungerer, slik at de vet mer hvordan de kan bidra til
+å gjøre brukeropplevelsen for innbyggerne enda bedre.</p>
+
+<p>Til de som synes sitt lokalområde har dårlig kart, så er det bare
+en ting å si. Bidra til å gjør <a href="">OpenStreetmap</a> bedre ved
+å tegne inn ditt lokalområde! Eller få det offentlige til å gi ut
+bedre kartdata uten bruksbegrensninger. :)</p>
+
+<p>Jeg vil presentere FiksGataMi under
+<a href="http://www.goopen.no/fiksgatami-no/">Go Open 2011</a>, så vi
+ses kanskje der?</p>
projects / homepage.git / blobdiff