X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/58a41994561e591eccf11d4ac1f280db73ef6c4a..2303a53e3000b721cc73c3bfe81b6d2911b51a35:/blog/data/2010-12-27-open-standard.txt

diff --git a/blog/data/2010-12-27-open-standard.txt b/blog/data/2010-12-27-open-standard.txt
index 19b6cf9189..ae29973f3c 100644
--- a/blog/data/2010-12-27-open-standard.txt
+++ b/blog/data/2010-12-27-open-standard.txt
@@ -1,12 +1,12 @@
-Title: The many definitions of open standard
-Tags: english, standard
-Date: 2010-12-27 14:30
+Title: The many definitions of a open standard
+Tags: english, standard, digistan
+Date: 2010-12-27 14:45
 
 <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
+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>
@@ -53,7 +53,7 @@ free basis.</li>
 </ul>
 </blockquote>
 
-<p>Another one originates from by friends over at
+<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
@@ -122,21 +122,29 @@ Standards Checklist</a> with a fairly detailed description.</p>
 <ul>
 
 <li>Its development and management process must be collaborative and
-democratic:
+  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>The processes must be documented and, through a known method,
-            can be changed through input from all participants.
+
+         <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>Development and management should strive for consensus, and an
-            appeals process must be clearly outlined.
-         <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.
+            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>
@@ -145,43 +153,60 @@ democratic:
 
 <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> The standard must not contain any proprietary "hooks" that create a technical
-  or economic barriers
-<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
+
+<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>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>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.
+  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> 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> The same licensing terms are available to every potential licensor
+
+      <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>The licensing terms of an open standards must not preclude implementations
-  of that standard under open source licensing terms or restricted licensing
-  terms
+</li>
+
+<li>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>