LogoLogo
  • Overview
  • Introduction
    • What are open standards?
    • Types of open standards for data
    • Using open standards for data
    • When not to create a new standard
  • Value and Open Standards
    • Getting started
    • Economic impacts
    • Technological impacts
    • Spotlight: evaluating the need for open standards
  • Adopting Open Standards
    • Finding open standards
    • Choosing an open standard
  • Creating Open Standards
    • About creating open standards
    • The standards lifecycle
    • First steps
    • Scoping and starting
    • Development
    • Building community
    • Launch and adoption
    • Spotlight: supporting adoption of the OpenActive standards
  • Stewarding Open Standards
    • About stewarding open standards
    • Review
    • Governance
    • Roles and Responsibilities
    • Update or Retire
  • Useful Tools
    • Ecosystem Mapping
    • Open Standards for Data Canvas
    • Outputs and Activities Checklist
Powered by GitBook
On this page
  • Standards enable publication of new data
  • Case study: UK Department for International Development (DfID)
  • Standards produce better quality data
  • Case study: US Environmental Protection Agency
  • Standards encourage creation of new tools and services
  • Case study: Building and Land Development Specification

Was this helpful?

  1. Value and Open Standards

Technological impacts

This section unpacks the technological benefits of open standards, with focus on producing better quality data and encouraging the development of new tools and services

PreviousEconomic impactsNextSpotlight: evaluating the need for open standards

Last updated 3 years ago

Was this helpful?

Standards enable publication of new data

‘Which datasets should I publish?’ and ‘How should I publish them?’ are frequent questions from data publishers who are looking to publish open or shared data.

Open standards for data can:

  • help publishers identify datasets others are sharing

  • act as a guide to help publishers share data in consistent ways

  • make it easier for data users to reuse shared data

  • encourage publishers to share data that was previously closed

  • build publishers’ confidence that they are sharing useful data

  • encourage the development of new tools for data users and publishers

‌Publishing data in standard ways means existing standard tools can be used by the publisher and its stakeholders, as the following case study shows.

Case study: UK Department for International Development (DfID)

In 2010, DfID launched the (UKATG), committing the UK government to greater transparency and clarity on international aid spending.

‌Partner organisations receiving grants or contracts from DfID must publish tracking information using the International Aid Transparency Initiative ((), unless specifically exempted.

‌As part of a with and , DfID reported that new information was published by its partner organisation which helped it understand activity and aided making decisions in countries receiving aid.

Standards produce better quality data

Open standards encourage the development of tools and services to help data publishers produce good quality data, including tools to validate, preview and compare data.

‌Open standards can advise data publishers how often data should be published. Some standards include ways to share publication schedules, publication dates, location and methods of accessing data. Sharing this information makes it easier to trust published data.

A data publisher can publish good quality data without standards. However, open standards reduce barriers to data publication by allowing publishers to focus on sharing consistent and quality data.

Case study: US Environmental Protection Agency

As a federal agency protecting human health and the environment, the US Environmental Protection Agency (EPA) collects environmental data from a number of organisations.

Standards encourage creation of new tools and services

When data is published consistently, the time, cost and processes involved in using it are reduced.

‌Consistent publication encourages the creation of new tools and services that are designed to take advantage of data that conforms to a standard.

‌Tools and services can be developed to:

Case study: Building and Land Development Specification

‌Tools developed using BLDS:

In her book ‘’, Danette McGilvray defines data quality as “the degree to which data can be trusted for any required use”.

The EPA developed data standards and the (CDX) platform to address issues of data quality and cost. This describes the benefits of using , including improved consistency and reduction of redundant data.

‌For example, are required to . As each dataset is different, combining data about grants becomes a bespoke activity for each council.

‌support data publishers by making it easier to validate and publish data that conforms to the standard – for example, the for validating data published to the

support data users by making it easier to analyse and use data that conforms to the standard – for example, Development Gateway created tools to support using the

support developers by making it easier to access and use consistently formatted data that conforms to the standard – for example, Google developed tools for , that conform to the (GTFS)

‌The (BLDS) standard focuses on publishing building and construction permit data consistently in the US, where each state collects permit data differently. The standard was developed collectively by technology and building services companies in the private sector, and US state governments.

‌ developed a to extend access to land use information using the open standard for the public and developers

built a so data users can compare permits across regions

support data publishers on its platform

UK Aid Transparency Guarantee
IATI
data use pilot
Publish What You Fund
Development Gateway
Executing Data Quality Projects
Central Data Exchange
EPA case study
open standards for environmental data
353 councils in England
publish information about grants
Local Government Association
data validator
Brownfield Site Register Open Data Standard
procurement analytics
Open Contracting Data Standard
testing
merging or viewing files
General Transit Feed Specification
Building and Land Development Specification
Boulder County
pilot open data platform
Accela
year in review app
Socrata
sharing BLDS permit data