Accueil > licences libres > licences services > Open Software Service Definition (OSSD)

licences services

Open Software Service Definition (OSSD)

dimanche 11 septembre 2011

Le projet Open Definition soutenu par The Open Knowledge Foundation cherche à définir le concept d’ouvert lorsqu’il s’applique aux données, aux contenus et aux services. Il donne avec l’OSSD la définition de ce qu’est un service en ligne ouvert.

Open Definition
Defining the Open in Open Data, Open Content and Open Services

Open Definition provides criteria for openness in relation to data, content, and software services.

The Open Knowledge Definition (OKD) sets out principles to define ‘openness’ in knowledge – that’s any kind of content or data ‘from sonnets to statistics, genes to geodata’. The definition can be summed up in the statement that “A piece of content or data is open if anyone is free to use, reuse, and redistribute it — subject only, at most, to the requirement to attribute and share-alike.”.

The Open Software Service Definition (OSSD) defines ‘openness’ in relation to online (software) services. It can be summed up in the statement that “A service is open if its source code is Free/Open Source Software and non-personal data is open as in the Open Knowledge Definition (OKD).”.


Open Software Service Definition (OSSD)

Introduction
The Open Software Service Definition defines ‘open’ in relation to online (software) services.

An online service, also known under the title of Software as a Service (SaaS), is a service provided by a software application running online and making its facilities available to users over the Internet via an interface (be that HTML presented by a web-browser such as Firefox, via a web-API or by any other means).

With an online-service, in contrast to a traditional software application, users no longer need to ‘possess’ (own or license) the software to use it. Instead they can simply interact via a standard client (such as web-browser) and pay, where they do pay, for use of the ‘service’ rather than for ‘owning’ (or licensing) the application itself.

The Definition
An open software service is one :

  1. Whose data is open as defined by the Open Knowledge Definition with the exception that where the data is personal in nature the data need only be made available to the user (i.e. the owner of that account).
  2. Whose source code is :
    • Free/Open Source Software (that is available under a license in the OSI or FSF approved list — see note 3).
    • Made available to the users of the service.

Notes

  1. The Open Knowledge Definition requires technological openness. Thus, for example, the data shouldn’t be restricted by technological means such as access control and should be available in an open format.
  2. The OKD also requires that data should be accessible in some machine automatable manner (e.g. through a standardized open API or via download from a standard specified location).
  3. The OSI approved list is available at : http://www.opensource.org/licenses/ and the FSF list is at : http://www.gnu.org/philosophy/license-list.html
  4. For an online-service simply using an F/OSS licence is insufficient since the fact that users only interact with the service and never obtain the software renders many traditional F/OSS licences inoperative. Hence the need for the second requirement that the source code is made publicly available.
  5. APIs : all APIs associated with the service will be assumed to be open (that is their form may be copied freely by others). This would naturally follow from the fact that the code and data underlying any of the APIs are open.
  6. It is important that the service’s code need only be made available to its users so as not to impose excessive obligations on providers of open software services.

Acknowledgements
This definition was originally drafted thanks on the open definition discussion mailing list. A variety of people contributed to that effort as well as subsequent improvements and amendments including (in alphabetical order) :

  • Dave Crossland
  • Francis Irving
  • Thorsten Glaser
  • Rufus Pollock
  • Evan Prodromu
  • Kragen Sitaker
  • Luis Villa

Open Service Web Buttons

If you’re providing an online service that’s compliant with the Definition let people know by using an ‘Open Service’ web button :

To add a button to your site just copy and paste the following bit of html into the relevant page on your site (or into the general footer or sidebar) :

<!-- Open Service Link -->
<a href="http://opendefinition.org/ossd/">
<img alt# "This is an Open Software Service" border"0"
src="http://m.okfn.org/images/ok_buttons/os_80x15_blue.png"></a>
<!--
/Open Service Link -->

To use a different button (other than the blue one used in the example) just change the ‘src’ attribute to point to one of the other buttons :

PNG - 922 octets
PNG - 1 ko
PNG - 581 octets

Applying the Definition : Some Examples

To make clearer the import of the Open Software Service Definition we provide some illustrative examples :

Google Maps : Not Open
Note that despite the fact that Google Maps provide an ‘open’ API and that the service is currently available for ‘free’ it is not an ‘Open Service’. In particular :

  • Code : the code for running Google Maps (backend and frontend) is currently proprietary.
  • Data : the data (geodata etc) used in Google maps is currently proprietary (copyrighted or protected by DB rights).

Wikipedia : Open

  • Code : Mediawiki is currently F/OSS (and is made available)
  • Data : Content of Wikipedia is available under an ‘open’ licence.

Swivel : Not Open

  • Code : proprietary.
  • Data : Open (available under an open license)

Background and History

  • Version : v1.1
    • v1.1 2008-10-08 (integrated changes suggested by Dave Crossland and Thorsten Glaser)
    • v1.0 2008-07-14.
    • v1.0b (2008-06-30)
    • v0.4 : 2008-05 (tidying)
    • v0.3 : 2007-09
    • v0.2 : (first version on this site) : 2007-07
    • v0.1 : 2006-10
  • Development version (to which anyone can add comments)

This particular formulation originates from discussions taking place originally on the okfn-discuss mailing list in September and October 2006 (see in particular this post) but owes much to more recent (Summer 2007) discussions precipitated by activities at GUADEC 2007 (see [1], [2], [3], [4]).

  1. We Need an Open Service Definition — blog post on the OKFN blog by Francis Irving which references a post on Havoc Pennington’s blog
  2. Evaluating a Free/Open Service Definition (rough draft) posted by Luis Villa
  3. This ongoing thread on okfn-discuss — this includes comments from a variety of people including Luis Villa, Mike Linksvayer, Rufus Pollock, Francis Irving and Saul Albert.
  4. Free/Open Services Definition draft/discussion page — this is a draft definition put together by Luis Villa and posted on the GNOME ‘live’ wiki. In addition to the definition there is also an excellent listing on existing work and writing on this issue.