diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9b4149a7..2db115c0 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,7 +2,7 @@ ## How to Contribute -This project constitutes a collaborative work ("open source"). Federal employees and members of the public are encouraged to improve the project by contributing. For more information, please see [the faq](faq.md) +This project constitutes a collaborative work ("open source"). Federal employees and members of the public are encouraged to improve the project by contributing. For more information, please see [the faq](/faq/) Contributions can be made, primarily in two ways: @@ -40,8 +40,8 @@ Project Open Data runs on GitHub pages and automatically regenerates as a static ## Licensing -By contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users under [the same terms under which the project is licensed](readme.md#licensing). +By contributing to this project, you grant a world-wide, royalty-free, perpetual, irrevocable, non-exclusive, transferable license to all users under [the same terms under which the project is licensed](README.md#licensing). ## Privacy -All comments, messages, pull requests, and other submissions received through official White House pages including this GitHub page may be subject to archiving requirements. See the [readme](readme.md#privacy) for more information. \ No newline at end of file +All comments, messages, pull requests, and other submissions received through official White House pages including this GitHub page may be subject to archiving requirements. See the [readme](README.md#privacy) for more information. \ No newline at end of file diff --git a/api-basics.md b/api-basics.md index b8bba48d..4ff2c850 100644 --- a/api-basics.md +++ b/api-basics.md @@ -64,8 +64,10 @@ APIs are driven by a set of specific technologies, making them easily understood Since REST takes advantage of the same Internet mechanisms that are used to view regular web pages it has many advantages, resulting in faster implementations and easier for developers to understand. REST APIs allow you to take data and functionality available on your website and make these resources available through a Web API. Then, instead of returning HTML to represent these resources, the API returns data in one of two possible formats: -* [Extensible Markup Language (XML)](http://apievangelist.com/buildingblocks/extensible_markup_language_(xml) -* [JavaScript Object Notation (JSON)](http://apievangelist.com/buildingblocks/javascript_object_notation_(json) + Developers can then take this data and use in web and mobile applications. However XML and JSON are easily consumed by spreadsheets and other tools non-developers can use as well, making APIs accessible by anyone. diff --git a/glossary.md b/glossary.md index 1e904be6..c08589be 100644 --- a/glossary.md +++ b/glossary.md @@ -133,7 +133,7 @@ A standard developed or adopted by voluntary consensus standards bodies, both do ### Parameter -A special kind of variable, used in a subroutine to refer to one of the pieces of data provided as input to the subroutine. The semantics for how parameters can be declared and how the arguments get passed to the parameters of subroutines are defined by the language, but the details of how this is represented in any particular computer system depend on the calling conventions of that system. —*[source](http://en.wikipedia.org/wiki/Parameter_(computer_science))* +A special kind of variable, used in a subroutine to refer to one of the pieces of data provided as input to the subroutine. The semantics for how parameters can be declared and how the arguments get passed to the parameters of subroutines are defined by the language, but the details of how this is represented in any particular computer system depend on the calling conventions of that system. —*source* ### RDF diff --git a/implementation-guide.md b/implementation-guide.md index 9128e00e..48dab89d 100644 --- a/implementation-guide.md +++ b/implementation-guide.md @@ -7,7 +7,7 @@ filename: implementation-guide.md ## 1) Create and maintain an enterprise data inventory -*[Due by 11/9/13]* +*\[Due by 11/9/13\]* Maintain a complete listing of all datasets owned, managed, collected, and/or created by your agency, described in a common format. @@ -23,12 +23,12 @@ This listing can be maintained in a Data Management System (DMS) such as the ope * Develop and communicate a clear path for listing newly created or acquired datasets into the enterprise data inventory. * The more employees who can contribute to the enterprise data inventory, whether by submitting feedback or by actually being able to log in and update listings in the agency DMS, the more accurate and complete your metadata will be. * While it may initially seem that maintaining your agency data inventory in a single spreadsheet is the simplest solution, this is often not the case. A central spreadsheet is difficult for more than one person to maintain, easily leading to errors and omissions. -* In addition to the required [common core metadata](/schema), work with your agency and topical experts to develop an expanded set of metadata fields that make sense for your vertical. Many already exist; explore [Schema.org](http://www.schema.org) as a starting point. +* In addition to the required [common core metadata](/schema/), work with your agency and topical experts to develop an expanded set of metadata fields that make sense for your vertical. Many already exist; explore [Schema.org](http://www.schema.org) as a starting point. * Your agency can and should use this central inventory listing as an internal search tool to increase awareness of data collections already in existence and to prevent duplicative research efforts. For example, a search of this inventory may reveal that the combination of two existing datasets could produce the results sought by a proposed new collection. ## 2) Create and maintain a public data inventory -*[Due by 11/9/13]* +*\[Due by 11/9/13\]* Maintain a publicly accessible listing of all datasets maintained by your agency for harvesting by a central Data.gov search engine and the public at large. @@ -38,7 +38,7 @@ While agencies are only required to list datasets with an "Access Level" value o Document any datasets or metadata in your enterprise data inventory that your agency does not believe can be made publicly available, in consultation with your Office of General Counsel or its equivalent. -Publish your agency’s enterprise data inventory, with the aforementioned information removed, to a file located at [agency].gov/data.json and described using (at minimum) the [common core metadata](http://project-open-data.github.io/schema/). This file itself must be listed as a dataset within itself (see [an example of format](http://project-open-data.github.io/examples/catalog-sample-extended.json) ); if you have multiple data.json files across your agency, include all of them in the top-level data.json at agency.gov/data.json. +Publish your agency’s enterprise data inventory, with the aforementioned information removed, to a file located at \[agency\].gov/data.json and described using (at minimum) the [common core metadata](http://project-open-data.github.io/schema/). This file itself must be listed as a dataset within itself (see [an example of format](http://project-open-data.github.io/examples/catalog-sample-extended.json) ); if you have multiple data.json files across your agency, include all of them in the top-level data.json at agency.gov/data.json. While you could manually create this file in a text editor, it is recommended that you use one of the tools provided to generate this file automatically from your existing DMS or enterprise inventory file. @@ -51,7 +51,7 @@ While you could manually create this file in a text editor, it is recommended th ### C) Best Practices and Examples -* Using the [common core metadata](http://project-open-data.github.io/schema) to describe your enterprise data inventory makes it very simple to use that inventory for your public inventory. +* Using the [common core metadata](http://project-open-data.github.io/schema/) to describe your enterprise data inventory makes it very simple to use that inventory for your public inventory. * A detailed and descriptive title, description, and set of keywords for each dataset is the difference between customers finding your data and no one finding your data. Since agency data catalogs are harvested and searchable on Data.gov, accurate and thorough metadata is the best way to connect customers with your data. * Consider including restricted and non-public datasets in your public data inventory listing. Remember that this file contains metadata about the data and not the data themselves. * When you include restricted datasets in your public data inventory, include specific information on how customers can request and qualify for access to those data. @@ -59,11 +59,11 @@ While you could manually create this file in a text editor, it is recommended th ### D) Resources -* [Common Core Metadata](/schema) +* [Common Core Metadata](/schema/) ## 3) Engage with customers to help facilitate and prioritize data release -*[Due by 11/9/13]* +*\[Due by 11/9/13\]* ### Minimum Required for Compliance @@ -82,7 +82,7 @@ Create a process to solicit feedback from customers about existing and potential ## 4) Clarify Roles and Responsibilities -*[Due by 11/9/13]* +*\[Due by 11/9/13\]* ### A) Minimum Required for Compliance @@ -119,7 +119,7 @@ Additionally, you should include information on: * [44 USC 3506 (b)(2)](http://www.gpo.gov/fdsys/granule/USCODE-2011-title44/USCODE-2011-title44-chap35-subchapI-sec3506/content-detail.html) * [OMB Circular A-11](http://www.whitehouse.gov/omb/circulars_a11_current_year_a11_toc) -* [OMB FY 13 PortfolioStat Guidance] (http://www.whitehouse.gov/blog/2013/03/27/portfoliostat-20-driving-better-management-and-efficiency-federal-it) +* [OMB FY 13 PortfolioStat Guidance](http://www.whitehouse.gov/blog/2013/03/27/portfoliostat-20-driving-better-management-and-efficiency-federal-it)

Ongoing

@@ -132,7 +132,7 @@ Collect or create information (data) in a way that supports downstream informati * Collect data electronically whenever possible. * Choose or build data collections tool that: - - Export data in machine-readable formats. Consult [this list](faq.md) for suggested machine-readable formats. + - Export data in machine-readable formats. Consult [this list](/faq/) for suggested machine-readable formats. - Use existing open data standards, if available. * Apply an open license, in consultation with best practices, to information as it is collected or created so that if data are made public there are no restrictions on the use or re-use of these data. * Collect the minimum amount of data needed to achieve your stated goals, in order to avoid having to remove additional personally-identifiable information later in the collection or release process. @@ -163,7 +163,7 @@ Collect or create information (data) in a way that supports downstream informati ### A) Minimum Required for Compliance * Review information for privacy, confidentiality pledge, security, and other restrictions to release. -* Make the data available in a machine-readable format. See [this list](http://project-open-data.github.io/faq.md) of commonly accepted machine-readable formats. Where appropriate, provide access to the data via an API. +* Make the data available in a machine-readable format. See [this list](/faq/) of commonly accepted machine-readable formats. Where appropriate, provide access to the data via an API. * Post the data files in an Internet-accessible location, listing this location the dataset’s entry in your agency inventory listing. ### B) Tools diff --git a/index.md b/index.md index c46edc2c..614a0478 100644 --- a/index.md +++ b/index.md @@ -36,13 +36,13 @@ This section is a list of definitions and principles used to guide the project. Implementation guidance for open data practices. -3-1 [U.S. Government Policy on Open Data](policy-memo/) - Full text of the memorandum. +3-1 [U.S. Government Policy on Open Data](/policy-memo/) - Full text of the memorandum. -3-2 [Implementation Guide](implementation-guide/) - Detailed descriptions and guidance for each step of implementing the policy. +3-2 [Implementation Guide](/implementation-guide/) - Detailed descriptions and guidance for each step of implementing the policy. -3-3 [Public Data Listing](catalog) - The specific guidance for publishing the Open Data Catalog at the agency.gov/data page. +3-3 [Public Data Listing](/catalog/) - The specific guidance for publishing the Open Data Catalog at the agency.gov/data page. -3-4 [Frequently Asked Questions](faq) - A growing list of common questions and answers to facilitate adoption of open data projects. +3-4 [Frequently Asked Questions](/faq/) - A growing list of common questions and answers to facilitate adoption of open data projects. ---------------- @@ -111,7 +111,7 @@ Case studies of novel or best practices from agencies who are leading in open da 6-7 [National Renewable Energy Laboratory API program](http://developer.nrel.gov/api-case-study/) - An agency perspective on developing APIs for general use and in particular building the case for the internal re-use of the resources. -6-8 [USAID Crowdsourcing to Open Data] (http://transition.usaid.gov/our_work/economic_growth_and_trade/development_credit/pdfs/2012/USAIDCrowdsourcingCaseStudy.pdf) - A case study that shows how USAID invited the "crowd" to clean and geocode a USAID dataset in order to open and map the data. +6-8 [USAID Crowdsourcing to Open Data](http://transition.usaid.gov/our_work/economic_growth_and_trade/development_credit/pdfs/2012/USAIDCrowdsourcingCaseStudy.pdf) - A case study that shows how USAID invited the "crowd" to clean and geocode a USAID dataset in order to open and map the data. **For Developers: [View all appendices](http://github.com/project-open-data/) (and source)** diff --git a/metadata-resources.md b/metadata-resources.md index fda95311..b3f8c23c 100644 --- a/metadata-resources.md +++ b/metadata-resources.md @@ -5,7 +5,7 @@ permalink: /metadata-resources/ filename: metadata-resources.md --- -This section provides further background and resources to assist agencies in implementing the [common core metadata schema](schema/). +This section provides further background and resources to assist agencies in implementing the [common core metadata schema](/schema/). ### Template Data Files diff --git a/policy-memo.md b/policy-memo.md index d2d9a146..07de9ee8 100644 --- a/policy-memo.md +++ b/policy-memo.md @@ -28,7 +28,7 @@ Making information resources accessible, discoverable, and usable by the public Pursuant to the Executive Order of May 9, 2013, *Making Open and Machine Readable the New Default for Government Information*, this Memorandum establishes a framework to help institutionalize the principles of effective information management at each stage of the information's life cycle to promote interoperability and openness. Whether or not particular information can be made public, agencies can apply this framework to all information resources to promote efficiency and produce value. -Specifically, this Memorandum requires agencies to collect or create information in a way that supports downstream information processing and dissemination activities. This includes using machine-readable and open formats, data standards, and [common core and extensible metadata](schema.md) for all new information creation and collection efforts. It also includes agencies ensuring information stewardship through the use of open licenses and review of information for privacy, confidentiality, security, or other restrictions to release. Additionally, it involves agencies building or modernizing information systems in a way that maximizes interoperability and information accessibility, maintains internal and external data asset inventories, enhances information safeguards, and clarifies information management responsibilities. +Specifically, this Memorandum requires agencies to collect or create information in a way that supports downstream information processing and dissemination activities. This includes using machine-readable and open formats, data standards, and [common core and extensible metadata](/schema/) for all new information creation and collection efforts. It also includes agencies ensuring information stewardship through the use of open licenses and review of information for privacy, confidentiality, security, or other restrictions to release. Additionally, it involves agencies building or modernizing information systems in a way that maximizes interoperability and information accessibility, maintains internal and external data asset inventories, enhances information safeguards, and clarifies information management responsibilities. The Federal Government has already made significant progress in improving its management of information resources to increase interoperability and openness. The President's Memorandum on *Transparency and Open Government*[^1] instructed agencies to take specific actions to implement the principles of transparency, participation, and collaboration, and the Office of Management and Budget's (OMB) *Open Government Directive*[^2] required agencies to expand access to information by making it available online in open formats. OMB has also developed policies to help agencies incorporate sound information practices, including OMB Circular A-130[^3] and OMB Memorandum M-06-02.[^4] In addition, the Federal Government launched [Data.gov](http://www.data.gov), an online platform designed to increase access to Federal datasets. The publication of thousands of data assets through [Data.gov](http://www.data.gov) has enabled the development of numerous products and services that benefit the public. @@ -36,7 +36,7 @@ To help build on these efforts, the President issued a Memorandum on May 23, 201 This Memorandum is designed to be consistent with existing requirements in the Paperwork Reduction Act,[^7] the E-Government Act of 2002,[^8] the Privacy Act of 1974,[^9] the Federal Information Security Management Act of 2002 (FISMA),[^10] the Confidential Information Protection and Statistical Efficiency Act of 2002 (CIPSEA),[^11] the Freedom of Information Act,[^12] the Information Quality Act,[^13] the Federal Records Act,[^14] and existing OMB and Office of Science and Technology Policy (OSTP) guidance. -If agencies have any questions regarding this Memorandum, please direct them to OMB at [datause@omb.eop.gov](datause@omb.eop.gov). +If agencies have any questions regarding this Memorandum, please direct them to OMB at [datause@omb.eop.gov](mailto:datause@omb.eop.gov). --- @@ -106,7 +106,7 @@ Agencies must apply open licenses, in consultation with the best practices found ##### d. Use common core and extensible metadata -Agencies must describe information using [common core metadata](schema.md), in consultation with the best practices found in Project Open Data, as it is collected and created. Metadata should also include information about origin, linked data, geographic location, time series continuations, data quality, and other relevant indices that reveal relationships between datasets and allow the public to determine the fitness of the data source. Agencies may expand upon the basic common metadata based on standards, specifications, or formats developed within different communities (e.g., financial, health, geospatial, law enforcement). Groups that develop and promulgate these metadata specifications must review them for compliance with the common core metadata standard, specifications, and formats. +Agencies must describe information using [common core metadata](/schema/), in consultation with the best practices found in Project Open Data, as it is collected and created. Metadata should also include information about origin, linked data, geographic location, time series continuations, data quality, and other relevant indices that reveal relationships between datasets and allow the public to determine the fitness of the data source. Agencies may expand upon the basic common metadata based on standards, specifications, or formats developed within different communities (e.g., financial, health, geospatial, law enforcement). Groups that develop and promulgate these metadata specifications must review them for compliance with the common core metadata standard, specifications, and formats. #### 2. Build information systems to support interoperability and information accessibility @@ -127,11 +127,11 @@ Agencies must update their inventory of agency information resources (as require ##### b. Create and maintain a public data listing -Any datasets in the agency's enterprise data inventory that can be made publicly available must be listed at www.[agency].gov/data in a human- and machine-readable format that enables automatic aggregation by Data.gov and other services (known as "harvestable files"), to the extent practicable. This should include datasets that can be made publicly available but have not yet been released. This public data listing should also include, to the extent permitted by law and existing terms and conditions, datasets that were produced through agency-funded grants, contracts, and cooperative agreements (excluding any data submitted primarily for the purpose of contract monitoring and administration), and, where feasible, be accompanied by standard citation information, preferably in the form of a persistent identifier. The public data listing will be built out over time, with the ultimate goal of including all agency datasets that can be made publicly available. See Project Open Data for best practices, tools, and schema to implement the public data listing and harvestable files. +Any datasets in the agency's enterprise data inventory that can be made publicly available must be listed at www.\[agency\].gov/data in a human- and machine-readable format that enables automatic aggregation by Data.gov and other services (known as "harvestable files"), to the extent practicable. This should include datasets that can be made publicly available but have not yet been released. This public data listing should also include, to the extent permitted by law and existing terms and conditions, datasets that were produced through agency-funded grants, contracts, and cooperative agreements (excluding any data submitted primarily for the purpose of contract monitoring and administration), and, where feasible, be accompanied by standard citation information, preferably in the form of a persistent identifier. The public data listing will be built out over time, with the ultimate goal of including all agency datasets that can be made publicly available. See Project Open Data for best practices, tools, and schema to implement the public data listing and harvestable files. ##### c. Create a process to engage with customers to help facilitate and prioritize data release -Agencies must create a process to engage with customers, through their www.[agency].gov/data pages and other necessary means, to solicit help in prioritizing the release of datasets and determining the most usable and appropriate formats for release.[^26] Agencies should make data available in multiple formats according to their customer needs. For example, high-volume datasets of interest to developers should be released using bulk downloads as well as Application Programming Interfaces (APIs). In addition, customer engagement efforts should help agencies prioritize efforts to improve the discoverability and usability of datasets that have already been released to the public but are not yet fully "open" (e.g., they are only available in closed, inaccessible formats). See Project Open Data for best practices and tools that can be used to implement customer engagement efforts. +Agencies must create a process to engage with customers, through their www.\[agency\].gov/data pages and other necessary means, to solicit help in prioritizing the release of datasets and determining the most usable and appropriate formats for release.[^26] Agencies should make data available in multiple formats according to their customer needs. For example, high-volume datasets of interest to developers should be released using bulk downloads as well as Application Programming Interfaces (APIs). In addition, customer engagement efforts should help agencies prioritize efforts to improve the discoverability and usability of datasets that have already been released to the public but are not yet fully "open" (e.g., they are only available in closed, inaccessible formats). See Project Open Data for best practices and tools that can be used to implement customer engagement efforts. ##### d. Clarify roles and responsibilities for promoting efficient and effective data release practices diff --git a/schema.md b/schema.md index 31f3a463..28216508 100644 --- a/schema.md +++ b/schema.md @@ -12,7 +12,7 @@ Standard Metadata Vocabulary ---------------------------- Metadata are selected fields or elements which describe data. The challenge is to define the standard metadata fields and the names of those fields so that the consumer of the data has sufficient information to process and understand the data. The more information that can be conveyed in a standardized regular format, the more valuable data becomes. Metadata can range from basic to advanced, from allowing one to discover the mere fact that a certain data asset exists and is about a general subject all the way to providing detailed semantic information that enables a high degree of machine readability. Making the metadata machine readable greatly increases its openness and utility. -Establishing a common vocabulary is the key to any communication, including communication between machines. [DCAT](http://www.w3.org/TR/vocab-dcat/) is a hierarchical vocabulary specific to datasets that serves as the basis for the **[common core metadata](http://project-open-data.github.io/schema/)** required in this memorandum. The standard consists of a number of schemas (hierarchical vocabulary terms) that represent things that are most often looked for on the web, with [mappings](http://project-open-data.github.io/metadata-resources#common_core_required_fields_equivalents) to their equivalents in other standards. +Establishing a common vocabulary is the key to any communication, including communication between machines. [DCAT](http://www.w3.org/TR/vocab-dcat/) is a hierarchical vocabulary specific to datasets that serves as the basis for the **[common core metadata](http://project-open-data.github.io/schema/)** required in this memorandum. The standard consists of a number of schemas (hierarchical vocabulary terms) that represent things that are most often looked for on the web, with [mappings](http://project-open-data.github.io/metadata-resources/#common_core_required_fields_equivalents) to their equivalents in other standards. What to Document -- Datasets and APIs @@ -225,7 +225,7 @@ Field | title **Cardinality** | (0,1) **Required** | Yes, if the dataset is spatial **Accepted Values** | See Usage Notes -**Usage Notes** | This field should contain one of the following types of content: (1) a bounding coordinate box for the dataset represented in latitude / longitude pairs where the coordinates are specified in decimal degrees and in the order of: minimum longitude, minimum latitude, maximum longitude, maximum latitude; (2) a latitude / longitude pair (in decimal degrees) representing a point where the dataset is relevant; (3) a geographic feature expressed in [Geography Markup Language using the Simple Features Profile](http://www.ogcnetwork.net/gml-sf); or (4) a geographic feature from the [GeoNames database](www.geonames.org). +**Usage Notes** | This field should contain one of the following types of content: (1) a bounding coordinate box for the dataset represented in latitude / longitude pairs where the coordinates are specified in decimal degrees and in the order of: minimum longitude, minimum latitude, maximum longitude, maximum latitude; (2) a latitude / longitude pair (in decimal degrees) representing a point where the dataset is relevant; (3) a geographic feature expressed in [Geography Markup Language using the Simple Features Profile](http://www.ogcnetwork.net/gml-sf); or (4) a geographic feature from the [GeoNames database](http://www.geonames.org). **Example** | `{"spatial":"Lincoln, Nebraska"}` {.table .table-striped} diff --git a/transportation-case-study.md b/transportation-case-study.md index de6ae884..360224c6 100644 --- a/transportation-case-study.md +++ b/transportation-case-study.md @@ -24,7 +24,7 @@ In response to the [Open Government Directive](http://www.whitehouse.gov/sites/d * **Policy**: Provide guidelines for identifying datasets and prioritizing them for release. Institute standing policies for approving, publishing, and managing releases. * **Inventory**: Build list of source information systems using budget exhibits. Compare these against data already released on websites and against information collections. Utilize these lists to develop a complete inventory of datasets, prioritize it, and sequence data for release. -DOT detailed the results of its strategic action plan on its open government [Web page](http://www.dot.gov/open). The Department sustained efforts in building its data inventory, responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance with a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT Draft Enforcement and Compliance Data Report - 05-18-2011 - OCR.pdf) that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. DOT’s [flagship initiative](http://www.dot.gov/open/plan-chapter3#Section 3.1) in its [second Open Government Plan](http://www.dot.gov/sites/dot.dev/files/docs/open-gov-v2_0.pdf), released in April 2012, is [Safety.Data.gov](http://safety.data.gov/), is intended to create momentum behind the productive use of safety-related datasets, enabling the public to make better safety-related decisions using both current statistical descriptions and explanations of the environment that will affect our future. Safety.Data.gov will tap into the innovation of application developers, the immediacy of the internet, and information that the Federal Government collects to enable informed decisions that will enhance public safety and improve public health in the United States. +DOT detailed the results of its strategic action plan on its open government [Web page](http://www.dot.gov/open). The Department sustained efforts in building its data inventory, responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance with a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf) that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. DOT’s [flagship initiative](http://www.dot.gov/open/plan-chapter3#sec3-1) in its [second Open Government Plan](http://www.dot.gov/sites/dot.dev/files/docs/open-gov-v2_0.pdf), released in April 2012, is [Safety.Data.gov](http://safety.data.gov/), is intended to create momentum behind the productive use of safety-related datasets, enabling the public to make better safety-related decisions using both current statistical descriptions and explanations of the environment that will affect our future. Safety.Data.gov will tap into the innovation of application developers, the immediacy of the internet, and information that the Federal Government collects to enable informed decisions that will enhance public safety and improve public health in the United States. ## Challenge @@ -52,7 +52,7 @@ Content releasability is determined with value, quality, security, privacy, and ## Results -The DOT has released [765 datasets or tools](https://explore.data.gov/browse?Dataset-Summary_Agency=Department+of+Transportation) to Data.gov. The processes and policies that have been established under DOT’s approach to Open Government helped DOT build a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT Draft Enforcement and Compliance Data Report - 05-18-2011 - OCR.pdf) responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. In May of 2012, DOT, in partnership with the Department of Justice, Department of Labor, and the Consumer Product Safety Commission, launched [Safety.Data.gov](http://safety.data.gov/) with 713 datasets, four (4) mobile apps, 14 resources and public domain software tools, and three (3) challenges or competitions. In September 2012, we held the first safety datapalooza, and the community now has 869 datasets, 10 mobile apps, and six (6) challenges or competitions encouraging public use of safety data from around the government. +The DOT has released [765 datasets or tools](https://explore.data.gov/browse?Dataset-Summary_Agency=Department+of+Transportation) to Data.gov. The processes and policies that have been established under DOT’s approach to Open Government helped DOT build a comprehensive [plan](http://www.dot.gov/sites/dot.dev/files/docs/DOT%20Draft%20Enforcement%20and%20Compliance%20Data%20Report%20-%2005-18-2011%20-%20OCR.pdf) responding to the President’s [memorandum](http://www.gpo.gov/fdsys/pkg/DCPD-201100032/pdf/DCPD-201100032.pdf) on regulatory compliance that was [recognized](http://sunlightfoundation.com/blog/2011/08/31/two-suggestions-for-the-us-national-action-plan/) as a model for other agencies to follow. In May of 2012, DOT, in partnership with the Department of Justice, Department of Labor, and the Consumer Product Safety Commission, launched [Safety.Data.gov](http://safety.data.gov/) with 713 datasets, four (4) mobile apps, 14 resources and public domain software tools, and three (3) challenges or competitions. In September 2012, we held the first safety datapalooza, and the community now has 869 datasets, 10 mobile apps, and six (6) challenges or competitions encouraging public use of safety data from around the government. DOT has already recognized benefits as a result of regulatory transparency efforts. For example, for the first time, FMCSA has begun releasing the information behind its Safety Measurement System (SMS) to the public in bulk, downloadable formats. Business and private citizens are mining this data for potential opportunities. For instance, a windshield repair company looking to grow its business is mining FMCSA information about safety violations to identify new customers. DOT and the public realize a benefit because the commercial vehicle operator customer is using a safer vehicle and operating in compliance with Federal Motor Carrier Safety Regulations. In addition, DOT has pursued innovation in its data release practices: * FMCSA released an [API](https://mobile.fmcsa.dot.gov/developer/home.page) and [mobile application](https://www.fmcsa.dot.gov/safety-security/saferbus/saferbus.aspx) to help people easily access a bus