2013 08-27 okfn-glasgow_uk_gov_open_standards


Published on

A presentation given ad the first Glasgow OKFN meeting 27 August 2013

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • This presentation is about the UK Government Open Standards programme, the Open Standards website, and how you might get involved in the Open Standards development process
  • Some standards arise because of the way the world is, the way the world works, the way that things are. These standards are 'de facto'.
  • Other standards arise because of some rule imposed - they are 'de jure'
  • There is a history of the detail of standards being hard to find as the standards specifications are provided at a cost and under a restrictive license
  • Sometimes it is hard to understand why a standard exists at all - and it costs to find out
  • So in order to provide a level playing field to all as far as standards relating to software and data are concerned, the UK Government is embarking on a programme to develop a set of open standards that will be developed using an open process and will result in standards published at zero or close to zero cost - making them available to all
  • The process is overseen by a Board, with the assistance of a technical panel, but the interactions are public through the http://standards.data.gov.uk website - and anyone can register and get involved in the standards development process
  • The Board has some terms of reference with specific aims
  • The process of the development of a standard follows a clearly specified path
  • The path used is the Common Assessment Method for Standards and Specifications (CAMSS) which was developed by the EC IDABC programme
  • The Board has 5 key criteria to assess in the consideration of any proposed standard
  • So here are 2 examples of proposals for open standards
  • One on standards pertaining to describing and sharing information
  • And another on persistent resolvable identifiers
  • And here are another two open standards
  • 2013 08-27 okfn-glasgow_uk_gov_open_standards

    1. 1. UKGov Open Standards Peter Winstanley peter.winstanley@scotland.gsi.gov.uk #OKFN Glasgow 2013-08-27
    2. 2. A standard based on the way things are – de facto http://en.wikipedia.org/wiki/File:2scissors-clean.jpg
    3. 3. A standard based on a regulation – de jure http://upload.wikimedia.org/wikipedia/commons/8/8f/Drive-on-the-left-kent-1b.jpg
    4. 4. “A standard on the shop is not licensed to be copied or shared,…” Log in to access bibliographic, citation and full text of over 55,000 British, adopted European and International standards from your desktop. Standard as overhead, not as enabler
    5. 5. Are ISO 2602:1980 compliant ? Only 50 Swiss Francs for the PDF
    6. 6. https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles “Government IT must be open - open to the people and organisations that use our services and open to any provider, regardless of their size. “ “The publication of the Open Standards Principles is a fundamental step towards achieving a level playing field for open source and proprietary software and breaking our IT into smaller, more manageable components. “
    7. 7. http://standards.data.gov.uk/open-standards-engagement-process
    8. 8. What the Board will do 1. consider open standards recommendations that relate to software interoperability, data and document formats for use within government 2. make decisions on whether standards recommendations : • meet user need and business outcomes • enable a level playing field for open source and proprietary software • are implementable, mature and supported by the market • are adequately researched, impact of adoption is understood • support open data • aligned with the Open Standards Principles 3. consider whether a recommended standard should be adopted and/or made compulsory across government. 4. influence the work of standards developers to avoid the creation of standards where there is no unique need. Based on http://standards.data.gov.uk/meeting/open-standards-board-terms-reference
    9. 9. http://standards.data.gov.uk/
    10. 10. https://webgate.ec.europa.eu/fpfis/mwikis/idabc-camss/images/9/9c/CAMSS_-_High-Level_Process.jpg The CAMSS Process – a high level view Common Assessment Method for Standards and Specifications (CAMSS)
    11. 11. Assessment Criteria Applicability Openness & Rights Maturity Potential Market Support
    12. 12. Some Examples
    13. 13. Challenge: Describing and sharing our information If the Government is to make maximum use of the information we hold we must be able to find it, share it responsibly, trust it, know what we publish and allow users to locate and consume that information. We require rules to make sure we describe our information in a standardised way to support sharing and re-use, and to enable us to understand the information created by others. http://standards.data.gov.uk/challenge/describing-and-sharing-our-information
    14. 14. Challenge: Persistent resolvable identifiers Data re-users want to be able to identify things using identifiers that continue to mean the same thing over time, and that can be used to find out information about those things, so that they can easily understand and combine data from different sources about the same thing. Government currently uses a lot of codes and identifiers that can be opaque to people who want to understand the information government produces (including government itself). http://standards.data.gov.uk/challenge/persistent-resolvable-identifiers
    15. 15. Thank You