# Technological impacts ## 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 [UK Aid Transparency Guarantee](https://www.gov.uk/government/publications/2010-to-2015-government-policy-overseas-aid-transparency/2010-to-2015-government-policy-overseas-aid-transparency) (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 ([IATI](https://www.aidtransparency.net/)(), unless specifically exempted. ‌As part of a [data use pilot](http://www.developmentgateway.org/blog/iati-data-future-success-progress-and-challenges) with [Publish What You Fund](http://www.publishwhatyoufund.org/) and [Development Gateway](http://www.developmentgateway.org/), 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 In her book ‘[Executing Data Quality Projects](http://www.gfalls.com/ten-steps-data-quality-book)’, Danette McGilvray defines data quality as “the degree to which data can be trusted for any required use”. 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. The EPA developed data standards and the [Central Data Exchange](http://www.epa.gov/cdx) (CDX) platform to address issues of data quality and cost. This [EPA case study](https://project-open-data.cio.gov/epa-case-study/) describes the benefits of using [open standards for environmental data](https://www.epa.gov/data-standards), including improved consistency and reduction of redundant data. ## Standards encourage creation of new tools and services When data is published consistently, the time, cost and processes involved in using it are reduced. ‌For example, [353 councils in England](https://www.gov.uk/government/uploads/system/uploads/attachment_data/file/491463/List_of_councils_in_England.pdf) are required to [publish information about grants](https://www.gov.uk/government/publications/local-government-transparency-code-2015). As each dataset is different, combining data about grants becomes a bespoke activity for each council. ‌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: * ‌**support data publishers** by making it easier to validate and publish data that conforms to the standard – for example, the [Local Government Association](http://www.local.gov.uk/) [data validator](http://validator.opendata.esd.org.uk/brownfieldlandregister2017) for validating data published to the [Brownfield Site Register Open Data Standard](https://www.gov.uk/government/publications/brownfield-land-registers-data-standard) * **support data users** by making it easier to analyse and use data that conforms to the standard – for example, Development Gateway created [procurement analytics](http://www.developmentgateway.org/expertise/contracting) tools to support using the [Open Contracting Data Standard](http://standard.open-contracting.org/) * **support developers** by making it easier to access and use consistently formatted data that conforms to the standard – for example, Google developed tools for [testing](https://github.com/google/transitfeed/wiki/ScheduleViewer), [merging or viewing files](https://github.com/google/transitfeed/wiki) that conform to the [General Transit Feed Specification](https://developers.google.com/transit/gtfs/) (GTFS) ### Case study: Building and Land Development Specification ‌The [Building and Land Development Specification](http://permitdata.org/) (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. ‌Tools developed using BLDS: * ‌[Boulder County](https://www.bouldercounty.org/) developed a [pilot open data platform](https://content.govdelivery.com/accounts/COBOULDER/bulletins/13f0802) to extend access to land use information using the open standard for the public and developers * [Accela](https://www.accela.com/) built a [year in review app](https://devblog.accela.com/2015/12/23/2015-the-year-in-building-permits/#more-452) so data users can compare permits across regions * [Socrata](https://socrata.com/) support data publishers [sharing BLDS permit data](https://permits.partner.socrata.com/) on its platform --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://open-data-institute.gitbook.io/open-standards-1ary-2ary-education/value-and-open-standards/technological-impacts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.