This is an important discussion and one where I hope we can evolve a useful
position. It has many similarities to the discussions which the Open
Knowledge Foundation and Science Commons have had over the last two years
trying to define what "Open Data" is. We have had legal input and a great
deal of informed input from people (Rufus Pollock, John Wilbanks, Peter
Suber and many more) whose major goal is to create a working approach for
data.

The bottom line is that licences are a very mixed blessing and that the
concept of "Community Norms" is primary (which is where I take the term
"community" from). I would argue that the BO is seeking to find some
community norms for what is an Open Standard in the practice of chemistry. I
do not believe that we can achieve a precise definition by which our
activities can be judged (in the same way that OKF/SC do not have precise
rules for Open Data, but they have principles - http://www.okfn.org,
http://en.wikipedia.org/wiki/Open_Knowledge_Foundation - that describe the
ethos of Openness).

I think it would be useful to try to define the general principles that
underlie open standards but it will take time. Here is the OKF Definition.
It has clear similarities to Open Source but is distinct. It will not
translate directly to what we require in BO, and any translation cannot be
arrived at in a few days.

Open Knowledge (NOT Open Standards)

1. *Access.* The work shall be available as a whole and at no more than a
reasonable reproduction cost, preferably downloading via the Internet
without charge. The work must also be available in a convenient and
modifiable form.

2. *Redistribution*. The license shall not restrict any party from selling
or giving away the work either on its own or as part of a package made from
works from many different sources. The license shall not require a royalty
or other fee for such sale or distribution.

3. *Reuse*. The license must allow for modifications and derivative works
and must allow them to be distributed under the terms of the original work.
The license may impose some form of attribution and integrity requirements:
see principle 5 (Attribution) and principle 6 (Integrity) below.

4. *Absence of Technological Restriction*. The work must be provided in such
a form that there are no technological obstacles to the performance of the
above activities. This can be achieved by the provision of the work in an
open data format, i.e. one whose specification is publicly and freely
available and which places no restrictions monetary or otherwise upon its
use.

5. *Attribution*.The license may require as a condition for redistribution
and re-use the attribution of the contributors and creators to the work. If
this condition is imposed it must not be onerous. For example if attribution
is required a list of those requiring attribution should accompany the work.

6. *Integrity*. The license may require as a condition for the work being
distributed in modified form that the resulting work carry a different name
or version number from the original work.

7. *No Discrimination Against Persons or Groups*. The license must not
discriminate against any person or group of persons.

8. *No Discrimination Against Fields of Endeavor*. The license must not
restrict anyone from making use of the work in a specific field of endeavor.
For example, it may not restrict the work from being used in a business, or
from being used for military research.

9. *Distribution of License*. The rights attached to the work must apply to
all to whom the work is redistributed without the need for execution of an
additional license by those parties.

10. *License Must Not Be Specific to a Package*. The rights attached to the
work must not depend on the work being part of a particular package. If the
work is extracted from that package and used or distributed within the terms
of the work's license, all parties to whom the work is redistributed should
have the same rights as those that are granted in conjunction with the
original package.

11. *License Must Not Restrict the Distribution of Other Works*. The license
must not place restrictions on other works that are distributed along with
the licensed work. For example, the license must not insist that all other
works distributed on the same medium are open.
For me many principles translate directly, others will be problematic. I
would expect that we will need to remove the word licence.

But there are clear touchstones. A protocol which is only available to
paying customers of a company (such as canonicalSMILES) cannot be regarded
as Open.

I think it will be valuable to see what other domains have to say about
this.

P

-- 
Peter Murray-Rust
Reader in Molecular Informatics
Unilever Centre, Dep. Of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-763069
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Blueobelisk-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/blueobelisk-discuss

Reply via email to