Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

use kramdown as the markdown engine

  • Loading branch information...
commit 891dfb42a0b52a4c716ecc05aaf768808c395182 1 parent 27e6ee8
Ben Balter benbalter authored
Showing with 138 additions and 140 deletions.
  1. +2 −1  _config.yml
  2. +8 −8 metadata-resources.md
  3. +66 −69 policy-memo.md
  4. +62 −62 schema.md
3  _config.yml
View
@@ -12,4 +12,5 @@ prose_url: http://prose.io
# default build settings for running locally, no need to edit
pymgemnts: true
-exclude: ["script", "vendor", "Gemfile", "Gemfile.lock", "config.ru", "Procfile", "Rakefile", "readme.md"]
+exclude: ["script", "vendor", "Gemfile", "Gemfile.lock", "config.ru", "Procfile", "Rakefile", "readme.md"]
+markdown: kramdown
16 metadata-resources.md
View
@@ -49,7 +49,7 @@ B) Translating a data file from another schema
If your agency has a JSON catalog with a different metadata schema and need to convert it to the prescribed schema needed for the data.json file, one can import the file into [Catalog Generator](http://project-open-data.github.com/catalog-generator/), adjust the metadata as needed and export the results again as the appropriately formatted JSON file.
-C) Utilizing CKAN
+C) Utilizing CKAN
[CKAN](http://www.CKAN.org) is a popular, open-source data catalog that can be installed independently or run as a service. Even if an agency hasn't begun a data catalog, adopting CKAN can provide a robust and feature-rich solution with which to begin maintaining an internal or external catalog. In addition to providing an effective means of organizing the agency's data catalog, CKAN provides several opportunities for generating the needed data.json file. CKAN provides a convenient CSV export that can then be imported into the [Catalog Generator](http://project-open-data.github.com/catalog-generator/) for conversion into an appropriately formatted JSON file. Alternatively, CKAN provides a JSON API of the data catalog which can then be altered to provide an automatic update for the appropriately formatted JSON file.
@@ -70,13 +70,13 @@ In order to generate appropriately formatted XML or RDFa Lite files, simply impo
"Common Core" Required Fields Equivalents
-----------------------------
-{.table .table-striped}
+{: .table .table-striped}
Field | *Data.gov* | *CKAN* | *RDFa Lite 1.1* | *Schema.org*
-------- | ------- | ------- | ------- | -------
+------- | ------- | ------- | ------- | -------
Title | *Title* | *title* | [dcterms:title](http://www.w3.org/TR/vocab-dcat/#property--title-1) | *sdo:name*
Description | *Description* | *notes* | [dcterms:description](http://www.w3.org/TR/vocab-dcat/#property--description-1) | *sdo:description*
Tags | *Keywords* | *tags* | [dcat:keyword](http://www.w3.org/TR/vocab-dcat/#property--keyword-tag) | *sdo:keywords*
-Last Update | *Date updated* | *revision_timestamp* | [dcterms:modified](http://www.w3.org/TR/vocab-dcat/#property--update-modification-date-1) | *sdo:dateModified*
+Last Update | *Date updated* | *revision_timestamp* | [dcterms:modified](http://www.w3.org/TR/vocab-dcat/#property--update-modification-date-1) | *sdo:dateModified*
Publisher | *Agency Name* | *owner_org* | [dcat:publisher](http://www.w3.org/TR/vocab-dcat/#property--publisher-1) | *sdo:publisher*
Contact Name | *Contact Name* | *maintainer* | [foaf:Person](http://www.w3.org/TR/vocab-dcat/#class--organization-person) | *sdo:Person*
Contact Email | *Contact Email Address* | *maintainer_email* | [foaf:mbox](http://xmlns.com/foaf/spec/#term_mbox) | *n/a*
@@ -86,9 +86,9 @@ Public Access Level | *n/a* | *n/a* | *n/a* | *n/a
"Common Core" Required if Applicable Fields
-------------------------------------------
-{.table .table-striped}
+{: .table .table-striped}
Field | *Data.gov* | *CKAN* | *RDFa Lite 1.1* | *Schema.org*
-------- | ------- | ------- | ------- | -------
+------- | ------- | ------- | ------- | -------
Data Dictionary | *Data Dictionary* | *data_dict* | [dcat:dataDictionary](http://www.w3.org/TR/vocab-dcat/#property--data-dictionary) | *n/a*
Download URL | *Access Point* | *res_url* | [dcat:accessURL](http://www.w3.org/TR/vocab-dcat/#property--access-download) | *sdo:contentUrl*
Endpoint | *Access Point* | *res_url* | [dcat:webService](http://www.w3.org/TR/vocab-dcat/#class--webservice) \* | *n/a*
@@ -100,9 +100,9 @@ Temporal | *Period of Coverage* | *n/a* | [dcterms:
Expanded Fields
---------------
-{.table .table-striped}
+{: .table .table-striped}
Field | *Data.gov* | *CKAN* | *RDFa Lite 1.1* | *Schema.org*
-------- | ------- | ------- | ------- | -------
+------- | ------- | ------- | ------- | -------
Release Date | *Date Released* | *n/a* | [dcterms:issued](http://www.w3.org/TR/vocab-dcat/#property--release-date) | *sdo:datePublished*
Frequency | *Frequency* | *n/a* | [dcterms:accrualPeriodicity](http://www.w3.org/TR/vocab-dcat/#property--frequency) | *n/a*
Language | *n/a* | *n/a* | [dcat:language](http://www.w3.org/TR/vocab-dcat/#property--language-1) | *sdo:inLanguage*
135 policy-memo.md
View
@@ -6,35 +6,32 @@ filename: policy-memo.md
id: policy-memo
---
-#   {.hidden}
-##   {.hidden}
-
**From:**
-* **Sylvia M. Burwell**<br />Director
+* **Sylvia M. Burwell**<br />Director
* **Steven VanRoekel**<br />Federal Chief Information Officer
* **Todd Park**<br />U.S. Chief Technology Officer
* **Dominic J. Mancini**<br />Deputy Administrator, Office of Information and Regulatory Affairs
-{#from}
+{: #from}
-**Subject:**{.from} Open Data Policy&#8212;Managing Information as an Asset
+**Subject:**{: .from} Open Data Policy&#8212;Managing Information as an Asset
* Table of Contents
{:toc}
-Information is a valuable national resource and a strategic asset to the Federal Government, its partners, and the public. In order to ensure that the Federal Government is taking full advantage of its information resources, executive departments and agencies (hereafter referred to as "agencies") must manage information as an asset throughout its life cycle to promote openness and interoperability, and properly safeguard systems and information. Managing government information as an asset will increase operational efficiencies, reduce costs, improve services, support mission needs, safeguard personal information, and increase public access to valuable government information.
+Information is a valuable national resource and a strategic asset to the Federal Government, its partners, and the public. In order to ensure that the Federal Government is taking full advantage of its information resources, executive departments and agencies (hereafter referred to as "agencies") must manage information as an asset throughout its life cycle to promote openness and interoperability, and properly safeguard systems and information. Managing government information as an asset will increase operational efficiencies, reduce costs, improve services, support mission needs, safeguard personal information, and increase public access to valuable government information.
Making information resources accessible, discoverable, and usable by the public can help fuel entrepreneurship, innovation, and scientific discovery &#8211; all of which improve Americans' lives and contribute significantly to job creation. For example, decades ago, the Federal Government made both weather data and the Global Positioning System (GPS) freely available to anyone. Since then, American entrepreneurs and innovators have used these resources to create navigation systems, weather newscasts and warning systems, location-based applications, precision farming tools, and much more.
-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.
+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/) 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.
+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.
To help build on these efforts, the President issued a Memorandum on May 23, 2012 entitled *Building a 21st Century Digital Government* [^5] that charged the Federal Chief Information Officer (CIO) with developing and implementing a comprehensive government-wide strategy to deliver better digital services to the American people. The resulting *Digital Government Strategy* [^6] outlined an information-centric approach to transform how the Federal Government builds and delivers digital services, and required OMB to develop guidance to increase the interoperability and openness of government information.
-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.
+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](mailto:datause@omb.eop.gov).
@@ -46,13 +43,13 @@ This attachment provides definitions and implementation guidance for M-13-13, *O
**Data:** For the purposes of this Memorandum, the term "data" refers to all structured information, unless otherwise noted. [^15]
-**Dataset:** For the purposes of this Memorandum, the term "dataset" refers to a collection of data presented in tabular or non-tabular form.
+**Dataset:** For the purposes of this Memorandum, the term "dataset" refers to a collection of data presented in tabular or non-tabular form.
**Fair Information Practice Principles**: The term "Fair Information Practice Principles" refers to the eight widely accepted principles for identifying and mitigating privacy impacts in information systems, programs and processes, delineated in the National Strategy for Trusted Identities in Cyberspace. [^16]
**Government information:** As defined in OMB Circular A-130, "government information" means information created, collected, processed, disseminated, or disposed of, by or for the Federal Government.
-**Information:** As defined in OMB Circular A-130, the term "information" means any communication or representation of knowledge such as facts, data, or opinions in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual forms.
+**Information:** As defined in OMB Circular A-130, the term "information" means any communication or representation of knowledge such as facts, data, or opinions in any medium or form, including textual, numerical, graphic, cartographic, narrative, or audiovisual forms.
**Information life cycle:** As defined in OMB Circular A-130, the term "information life cycle" means the stages through which information passes, typically characterized as creation or collection, processing, dissemination, use, storage, and disposition.
@@ -70,11 +67,11 @@ This attachment provides definitions and implementation guidance for M-13-13, *O
* *Reusable.* Open data are made available under an open license that places no restrictions on their use.
-* *Complete.* Open data are published in primary forms (i.e., as collected at the source), with the finest possible level of granularity that is practicable and permitted by law and other requirements. Derived or aggregate open data should also be published but must reference the primary data.
+* *Complete.* Open data are published in primary forms (i.e., as collected at the source), with the finest possible level of granularity that is practicable and permitted by law and other requirements. Derived or aggregate open data should also be published but must reference the primary data.
-* *Timely.* Open data are made available as quickly as necessary to preserve the value of the data. Frequency of release should account for key audiences and downstream needs.
+* *Timely.* Open data are made available as quickly as necessary to preserve the value of the data. Frequency of release should account for key audiences and downstream needs.
-* *Managed Post-Release.* A point of contact must be designated to assist with data use and to respond to complaints about adherence to these open data requirements.
+* *Managed Post-Release.* A point of contact must be designated to assist with data use and to respond to complaints about adherence to these open data requirements.
* *Project Open Data:* "Project Open Data," a new OMB and OSTP resource, is an online repository of tools, best practices, and schema to help agencies adopt the framework presented in this guidance. Project Open Data can be accessed at [project-open-data.github.io](/). [^18] Project Open Data will evolve over time as a community resource to facilitate adoption of open data practices. The repository includes definitions, code, checklists, case studies, and more, and enables collaboration across the Federal Government, in partnership with public developers, as applicable. Agencies can visit Project Open Data for a more comprehensive glossary of terms related to open data.
@@ -98,7 +95,7 @@ Agencies must use machine-readable and open formats for information as it is col
##### b. Use data standards
-Consistent with existing policies relating to Federal agencies' use of standards [^20] for information as it is collected or created, agencies must use standards in order to promote data interoperability and openness.
+Consistent with existing policies relating to Federal agencies' use of standards [^20] for information as it is collected or created, agencies must use standards in order to promote data interoperability and openness.
##### c. Ensure information stewardship through the use of open licenses
@@ -115,19 +112,19 @@ Through their acquisition and technology management processes, agencies must bui
1. The system design must be scalable, flexible, and facilitate extraction of data in multiple formats and for a range of uses as internal and external needs change, including potential uses not accounted for in the original design. In general, this will involve the use of standards and specifications in the system design that promote industry best practices for information sharing, and separation of data from the application layer to maximize data reuse opportunities and incorporation of future application or technology capabilities, in consultation with the best practices found in Project Open Data;
2. All data outputs associated with the system must meet the requirements described in part III, sections 1.a-e of this Memorandum and be accounted for in the data inventory described in part III section 3.a; and
-3. Data schema and dictionaries have been documented and shared with internal partners and the public, as applicable.
+3. Data schema and dictionaries have been documented and shared with internal partners and the public, as applicable.
-#### 3. Strengthen data management and release practices
+#### 3. Strengthen data management and release practices
To ensure that agency data assets are managed and maintained throughout their life cycle, agencies must adopt effective data asset portfolio management approaches. Within six (6) months of the date of this Memorandum, agencies and inter-agency groups must review and, where appropriate, revise existing policies and procedures to strengthen their data management and release practices to ensure consistency with the requirements in this Memorandum, and take the following actions:
##### a. Create and maintain an enterprise data inventory
-Agencies must update their inventory of agency information resources (as required by OMB Circular A-130) [^24] to include an enterprise data inventory, if it does not already exist, that accounts for datasets used in the agency's information systems. The inventory will be built out over time, with the ultimate goal of including all agency datasets, to the extent practicable. The inventory will indicate, as appropriate, if the agency has determined that the individual datasets may be made publicly available (i.e., release is permitted by law, subject to all privacy, confidentiality, security, and other valid requirements) and whether they are currently available to the public. The Senior Agency Official for Records Management should be consulted on integration with the records management process. Agencies should use the Data Reference Model from the Federal Enterprise Architecture [^25] to help create and maintain their inventory. Agencies must describe datasets within the inventory using the common core and extensible metadata (see part III, section 1.e).
+Agencies must update their inventory of agency information resources (as required by OMB Circular A-130) [^24] to include an enterprise data inventory, if it does not already exist, that accounts for datasets used in the agency's information systems. The inventory will be built out over time, with the ultimate goal of including all agency datasets, to the extent practicable. The inventory will indicate, as appropriate, if the agency has determined that the individual datasets may be made publicly available (i.e., release is permitted by law, subject to all privacy, confidentiality, security, and other valid requirements) and whether they are currently available to the public. The Senior Agency Official for Records Management should be consulted on integration with the records management process. Agencies should use the Data Reference Model from the Federal Enterprise Architecture [^25] to help create and maintain their inventory. Agencies must describe datasets within the inventory using the common core and extensible metadata (see part III, section 1.e).
##### 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
@@ -141,7 +138,7 @@ Agencies must ensure that roles and responsibilities are clearly designated for
2. Ensuring that data released to the public are open (as defined in part I), as appropriate, and a point of contact is designated to assist open data use and to respond to complaints about adherence to open data requirements;
-3. Engaging entrepreneurs and innovators in the private and nonprofit sectors to encourage and facilitate the use of agency data to build applications and services;
+3. Engaging entrepreneurs and innovators in the private and nonprofit sectors to encourage and facilitate the use of agency data to build applications and services;
4. Working with agency components to scale best practices from bureaus and offices that excel in open data practices across the enterprise;
@@ -151,9 +148,9 @@ Agencies must ensure that roles and responsibilities are clearly designated for
#### 4. Strengthen measures to ensure that privacy and confidentiality are fully protected and that data are properly secured
-Agencies must incorporate privacy analyses into each stage of the information's life cycle. In particular, agencies must review the information collected or created for valid restrictions to release to determine whether it can be made publicly available, consistent with the *Open Government Directive's* presumption in favor of openness, and to the extent permitted by law and subject to privacy, confidentiality pledge, security, trade secret, contractual, or other valid restrictions to release. If the agency determines that information should not be made publicly available on one of these grounds, the agency must document this determination in consultation with its Office of General Counsel or equivalent.
+Agencies must incorporate privacy analyses into each stage of the information's life cycle. In particular, agencies must review the information collected or created for valid restrictions to release to determine whether it can be made publicly available, consistent with the *Open Government Directive's* presumption in favor of openness, and to the extent permitted by law and subject to privacy, confidentiality pledge, security, trade secret, contractual, or other valid restrictions to release. If the agency determines that information should not be made publicly available on one of these grounds, the agency must document this determination in consultation with its Office of General Counsel or equivalent.
-As agencies consider whether or not information may be disclosed, they must also account for the "mosaic effect" of data aggregation. Agencies should note that the mosaic effect demands a risk-based analysis, often utilizing statistical methods whose parameters can change over time, depending on the nature of the information, the availability of other information, and the technology in place that could facilitate the process of identification. Because of the complexity of this analysis and the scope of data involved, agencies may choose to take advantage of entities in the Executive Branch that may have relevant expertise, including the staff of Data.gov. Ultimately, it is the responsibility of each agency to perform the necessary analysis and comply with all applicable laws, regulations, and policies. In some cases, this assessment may affect the amount, type, form, and detail of data released by agencies.
+As agencies consider whether or not information may be disclosed, they must also account for the "mosaic effect" of data aggregation. Agencies should note that the mosaic effect demands a risk-based analysis, often utilizing statistical methods whose parameters can change over time, depending on the nature of the information, the availability of other information, and the technology in place that could facilitate the process of identification. Because of the complexity of this analysis and the scope of data involved, agencies may choose to take advantage of entities in the Executive Branch that may have relevant expertise, including the staff of Data.gov. Ultimately, it is the responsibility of each agency to perform the necessary analysis and comply with all applicable laws, regulations, and policies. In some cases, this assessment may affect the amount, type, form, and detail of data released by agencies.
As OMB has noted, "The individual's right to privacy must be protected in Federal Government information activities involving personal information." [^27] As agencies consider security-related restrictions to release, they should focus on information confidentiality, integrity, and availability as part of the agency's overall risk management framework. They are required to incorporate the National Institute of Standards and Technology (NIST) Federal Information Processing Standard (FIPS) Publication 199 "Standards for Security Categorization of Federal Information and Information Systems," which includes guidance and definitions for confidentiality, integrity, and availability. [^28] Agencies should also consult with the Controlled Unclassified Information (CUI) program to ensure compliance with CUI requirements, [^29] the National Strategy for Information Sharing and Safeguarding, [^30] and the best practices found in Project Open Data. In addition to complying with the Privacy Act of 1974, the E-Government Act of 2002, FISMA, and CIPSEA, agencies should implement information policies based upon Fair Information Practice Principles and NIST guidance on Security and Privacy Controls for Federal Information Systems and Organizations. [^31] For example, agencies must:
@@ -169,15 +166,15 @@ As OMB has noted, "The individual's right to privacy must be protected in Federa
#### 5. Incorporate new interoperability and openness requirements into core agency processes
-Consistent with 44 U.S.C. 3506 (b)(2), agencies must develop and maintain an Information Resource Management (IRM) Strategic Plan. IRM Strategic Plans should align with the agency's Strategic Plan (as required by OMB Circular A-11), [^36] support the attainment of agency priority goals as mandated by the Government Performance and Results Modernization Act of 2010, [^37] provide a description of how IRM activities help accomplish agency missions, and ensure that IRM decisions are integrated with organizational planning, budget, procurement, financial management, human resources management, and program decisions. As part of the annual PortfolioStat process, [^38] agencies must update their IRM Strategic Plans to describe how they are meeting new and existing information life cycle management requirements. Specifically, agencies must describe how they have institutionalized and operationalized the interoperability and openness requirements in this Memorandum into their core processes across all applicable agency programs and stakeholders.
+Consistent with 44 U.S.C. 3506 (b)(2), agencies must develop and maintain an Information Resource Management (IRM) Strategic Plan. IRM Strategic Plans should align with the agency's Strategic Plan (as required by OMB Circular A-11), [^36] support the attainment of agency priority goals as mandated by the Government Performance and Results Modernization Act of 2010, [^37] provide a description of how IRM activities help accomplish agency missions, and ensure that IRM decisions are integrated with organizational planning, budget, procurement, financial management, human resources management, and program decisions. As part of the annual PortfolioStat process, [^38] agencies must update their IRM Strategic Plans to describe how they are meeting new and existing information life cycle management requirements. Specifically, agencies must describe how they have institutionalized and operationalized the interoperability and openness requirements in this Memorandum into their core processes across all applicable agency programs and stakeholders.
### IV. Implementation
-As agencies take steps to meet the requirements in this Memorandum, it is important to work strategically and prioritize those elements that can be addressed immediately, support mission-critical objectives, and result in more efficient use of taxpayer dollars.
+As agencies take steps to meet the requirements in this Memorandum, it is important to work strategically and prioritize those elements that can be addressed immediately, support mission-critical objectives, and result in more efficient use of taxpayer dollars.
Agencies should consider the following as they implement the requirements of this Memorandum:
-#### 1. Roles and Responsibilities
+#### 1. Roles and Responsibilities
The Clinger-Cohen Act of 1996 assigns agency CIOs statutory responsibility for promoting the effective and efficient design and operation of all major IRM processes within their agency. Accordingly, agency heads must ensure that CIOs are positioned with the responsibility and authority to implement the requirements of this Memorandum in coordination with the agency's Chief Acquisition Officer, Chief Financial Officer, Chief Technology Officer, Senior Agency Official for Geospatial Information, Senior Agency Official for Privacy (SAOP), Chief Information Security Officer (CISO), Senior Agency Official for Records Management, and Chief Freedom of Information Act (FOIA) Officer. The CIO should also work with the agency's public affairs staff, open government staff, web manager or digital strategist, program owners and other leadership, as applicable.
@@ -191,7 +188,7 @@ The Federal CIO will work with the United States Chief Technology Officer (CTO)
Policy implementation may require upfront investments depending on the maturity of existing information life cycle management processes at individual agencies. Agencies are encouraged to evaluate current processes and identify implementation opportunities that may result in more efficient use of taxpayer dollars. However, effective implementation should result in downstream cost savings for the enterprise through increased interoperability and accessibility of the agency's information resources. Therefore, these potential upfront investments should be considered in the context of their future benefits and be funded appropriately through the agency's capital planning and budget processes. Some of the requirements in this Memorandum may require additional tools and resources. Agencies should make progress commensurate with available tools and resources.
-In addition, tools, best practices, and schema to help agencies implement the requirements of this Memorandum can be found through the Digital Services Innovation Center and in Project Open Data.
+In addition, tools, best practices, and schema to help agencies implement the requirements of this Memorandum can be found through the Digital Services Innovation Center and in Project Open Data.
#### 4. Accountability Mechanisms
@@ -199,84 +196,84 @@ Progress on agency implementation of the actions required in this Memorandum wil
Nothing in this Memorandum shall be construed to affect existing requirements for review and clearance of pre-decisional information by OMB relating to legislative, budgetary, administrative, and regulatory materials. Moreover, nothing in this Memorandum shall be construed to reduce the protection of information whose release would threaten national security, invade personal privacy, breach confidentiality or contractual terms, violate the Trade Secrets Act, [^40] violate other statutory confidentiality requirements, [^41] or damage other compelling interests. This Memorandum is not intended to, and does not, create any right or benefit, substantive or procedural, enforceable at law or in equity by any party against the United States, its departments, agencies, or entities, its officers, employees, or agents, or any other person.
-[^1]: President Barack Obama, Memorandum on Transparency and Open Government (Jan. 21, 2009), *available at* <a>http://www.whitehouse.gov/the_press_office/TransparencyandOpenGovernment</a>.
+[^1]: President Barack Obama, Memorandum on Transparency and Open Government (Jan. 21, 2009), *available at* <a>http://www.whitehouse.gov/the_press_office/TransparencyandOpenGovernment</a>.
-[^2]: OMB Memorandum M-10-06, *Open Government Directive* (Dec. 8, 2009), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/memoranda_2010/m10-06.pdf</a>
+[^2]: OMB Memorandum M-10-06, *Open Government Directive* (Dec. 8, 2009), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/memoranda_2010/m10-06.pdf</a>
-[^3]: OMB Circular A-130, *available at* <a>http://www.whitehouse.gov/omb/Circulars_a130_a130trans4/</a>
+[^3]: OMB Circular A-130, *available at* <a>http://www.whitehouse.gov/omb/Circulars_a130_a130trans4/</a>
-[^4]: OMB Memorandum M-06-02, *Improving Public Access to and Dissemination of Government Information and Using the Federal Enterprise Architecture Data Reference Model* (Dec. 16, 2005), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2006/m06-02.pdf</a> **
+[^4]: OMB Memorandum M-06-02, *Improving Public Access to and Dissemination of Government Information and Using the Federal Enterprise Architecture Data Reference Model* (Dec. 16, 2005), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2006/m06-02.pdf</a> **
-[^5]: President Barack Obama, Memorandum on Building a 21st Century Digital Government (May 23, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/uploads/2012digital_mem_rel.pdf</a>
+[^5]: President Barack Obama, Memorandum on Building a 21st Century Digital Government (May 23, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/uploads/2012digital_mem_rel.pdf</a>
-[^6]: Office of Management and Budget, *Digital Government: Building a 21<sup>st</sup> Century Platform to Better Serve the American People* (May 23, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/egov/digital-government/digital-government-strategy.pdf</a>
+[^6]: Office of Management and Budget, *Digital Government: Building a 21<sup>st</sup> Century Platform to Better Serve the American People* (May 23, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/egov/digital-government/digital-government-strategy.pdf</a>
-[^7]: 44 U.S.C. § 3501 *et seq.*
+[^7]: 44 U.S.C. § 3501 *et seq.*
-[^8]: Pub. L. No. 107-347, 116 Stat. 2899 (2002) (codified as 44 U.S.C. § 3501 note).
+[^8]: Pub. L. No. 107-347, 116 Stat. 2899 (2002) (codified as 44 U.S.C. § 3501 note).
-[^9]: 5 U.S.C. § 552a.
+[^9]: 5 U.S.C. § 552a.
-[^10]: 44 U.S.C. § 3541, *et seq*.
+[^10]: 44 U.S.C. § 3541, *et seq*.
-[^11]: Section 503(a), Pub. L. No. 107-347, 116 Stat. 2899 (2002) (codified as 44 U.S.C. § 3501 note); *see also* Implementation Guidance for Title V of the E-Government Act, Confidential Information Protection and Statistical Efficiency Act of 2002 (CIPSEA), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/fedreg/2007/061507_cipsea_guidance.pdf</a>
+[^11]: Section 503(a), Pub. L. No. 107-347, 116 Stat. 2899 (2002) (codified as 44 U.S.C. § 3501 note); *see also* Implementation Guidance for Title V of the E-Government Act, Confidential Information Protection and Statistical Efficiency Act of 2002 (CIPSEA), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/fedreg/2007/061507_cipsea_guidance.pdf</a>
-[^12]: 5 USC 552(a)(2).
+[^12]: 5 USC 552(a)(2).
-[^13]: Pub. L. No. 106-554 (2000) (codified at 44 U.S.C. § 3504(d)(1) and 3516). *See also* OMB Memorandum M-12-18, *Managing Government Records Directive* (Aug. 24, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/2012/m-12-18.pdf</a>.
+[^13]: Pub. L. No. 106-554 (2000) (codified at 44 U.S.C. § 3504(d)(1) and 3516). *See also* OMB Memorandum M-12-18, *Managing Government Records Directive* (Aug. 24, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/2012/m-12-18.pdf</a>.
-[^14]: 44 U.S.C. Chapters 21, 22, 29, 31, and 33. *See also* 36 CFR Subchapter B &#8211; Records Management.
+[^14]: 44 U.S.C. Chapters 21, 22, 29, 31, and 33. *See also* 36 CFR Subchapter B &#8211; Records Management.
-[^15]: *Structured* information is to be contrasted with *unstructured* information (commonly referred to as "content") such as press releases and fact sheets. As described in the *Digital Government Strategy*, content may be converted to a structured format and treated as data. For example, a web-based fact sheet may be broken into the following component data pieces: the title, body text, images, and related links.
+[^15]: *Structured* information is to be contrasted with *unstructured* information (commonly referred to as "content") such as press releases and fact sheets. As described in the *Digital Government Strategy*, content may be converted to a structured format and treated as data. For example, a web-based fact sheet may be broken into the following component data pieces: the title, body text, images, and related links.
-[^16]: The White House, *National Strategy for Trusted Identities in Cyberspace* (April 2011), *available at* <a>http://www.whitehouse.gov/sites/default/files/rss_viewer/NSTICstrategy_041511.pdf</a>
+[^16]: The White House, *National Strategy for Trusted Identities in Cyberspace* (April 2011), *available at* <a>http://www.whitehouse.gov/sites/default/files/rss_viewer/NSTICstrategy_041511.pdf</a>
-[^17]: OMB Memorandum M-10-23, *Guidance for Agency Use of Third-Party Websites and Applications* (June 25, 2010), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/memoranda_2010/m10-23.pdf</a>
+[^17]: OMB Memorandum M-10-23, *Guidance for Agency Use of Third-Party Websites and Applications* (June 25, 2010), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/memoranda_2010/m10-23.pdf</a>
-[^18]: Links to the best practices developed in Project Open Data referenced in this memorandum can be found through the directory on this main page.
+[^18]: Links to the best practices developed in Project Open Data referenced in this memorandum can be found through the directory on this main page.
-[^19]: The requirements of this subsection build upon existing requirements in OMB Statistical Policy Directives No. 1 and No. 2, *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/inforeg/directive1.pdf</a> and <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/inforeg/directive2.pdf</a>.
+[^19]: The requirements of this subsection build upon existing requirements in OMB Statistical Policy Directives No. 1 and No. 2, *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/inforeg/directive1.pdf</a> and <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/inforeg/directive2.pdf</a>.
-[^20]: *See* OMB Circular A-119, *available at* <a>http://www.whitehouse.gov/omb/circulars_a119</a>, and OMB Memorandum M-12-08, *Principles for Federal Engagement in Standards Activities to Address National Priorities* (Jan 27, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/2012/m-12-08.pdf</a>
+[^20]: *See* OMB Circular A-119, *available at* <a>http://www.whitehouse.gov/omb/circulars_a119</a>, and OMB Memorandum M-12-08, *Principles for Federal Engagement in Standards Activities to Address National Priorities* (Jan 27, 2012), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/2012/m-12-08.pdf</a>
-[^21]: If a data user augments or alters original information that is attributed to the Federal Government, the user is responsible for making clear the source and nature of that augmentation.
+[^21]: If a data user augments or alters original information that is attributed to the Federal Government, the user is responsible for making clear the source and nature of that augmentation.
-[^22]: *See* Federal Acquisition Regulation (FAR) Subpart 27.4&#8212;Rights in Data and Copyrights, *available at* <a>https://acquisition.gov/far/current/html/Subpart%2027_4.html</a>
+[^22]: *See* Federal Acquisition Regulation (FAR) Subpart 27.4&#8212;Rights in Data and Copyrights, *available at* <a>https://acquisition.gov/far/current/html/Subpart%2027_4.html</a>
-[^23]: Office of Management and Budget, Common Approach to Federal Enterprise Architecture, *available at* http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/common_approach_to_federal_ea.pdf
+[^23]: Office of Management and Budget, Common Approach to Federal Enterprise Architecture, *available at* http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/common_approach_to_federal_ea.pdf
-[^24]: *See* OMB Circular A-130, section 8(b)(2)(a).
+[^24]: *See* OMB Circular A-130, section 8(b)(2)(a).
-[^25]: Office of Management and Budget, Federal Enterprise Architecture (FEA) Reference Models, *available at* <a>http://www.whitehouse.gov/omb/e-gov/fea</a>
+[^25]: Office of Management and Budget, Federal Enterprise Architecture (FEA) Reference Models, *available at* <a>http://www.whitehouse.gov/omb/e-gov/fea</a>
-[^26]: OMB Statistical Policy Directives 3 and 4 describe the schedule and manner in which data produced by the principal statistical agencies will be released. Statistical Policy Directive No. 4: Release and Dissemination of Statistical Products Produced by Federal Statistical Agencies, *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/fedreg/2008/030708_directive-4.pdf</a>; Statistical Policy Directive 3: Compilation, Release, and Evaluation of Principal Federal Economic Indicators, *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/inforeg/statpolicy/dir_3_fr_09251985.pdf</a>
+[^26]: OMB Statistical Policy Directives 3 and 4 describe the schedule and manner in which data produced by the principal statistical agencies will be released. Statistical Policy Directive No. 4: Release and Dissemination of Statistical Products Produced by Federal Statistical Agencies, *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/fedreg/2008/030708_directive-4.pdf</a>; Statistical Policy Directive 3: Compilation, Release, and Evaluation of Principal Federal Economic Indicators, *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/assets/omb/inforeg/statpolicy/dir_3_fr_09251985.pdf</a>
-[^27]: *See* OMB Circular A-130, *available at* <a>http://www.whitehouse.gov/omb/Circulars_a130_a130trans4/</a>
+[^27]: *See* OMB Circular A-130, *available at* <a>http://www.whitehouse.gov/omb/Circulars_a130_a130trans4/</a>
-[^28]: NIST FIPS Publication 199 "Standards for Security Categorization of Federal Information and Information Systems", *available at* <a>http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf</a>
+[^28]: NIST FIPS Publication 199 "Standards for Security Categorization of Federal Information and Information Systems", *available at* <a>http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf</a>
-[^29]: Executive Order 13556, Controlled Unclassified Information, *available at* <a>http://www.whitehouse.gov/the-press-office/2010/11/04/executive-order-13556-controlled-unclassified-information</a>.
+[^29]: Executive Order 13556, Controlled Unclassified Information, *available at* <a>http://www.whitehouse.gov/the-press-office/2010/11/04/executive-order-13556-controlled-unclassified-information</a>.
-[^30]: The White House, *National Strategy for Information Sharing and Safeguarding *(December 2011), *available at* <a>http://www.whitehouse.gov/the-press-office/2012/12/19/national-strategy-information-sharing-and-safeguarding</a>
+[^30]: The White House, *National Strategy for Information Sharing and Safeguarding *(December 2011), *available at* <a>http://www.whitehouse.gov/the-press-office/2012/12/19/national-strategy-information-sharing-and-safeguarding</a>
-[^31]: *See* NIST Special Publication 800-53 "Security and Privacy Controls for Federal Information Systems and Organizations", *available at* <a>http://csrc.nist.gov/publications/drafts/800-53-rev4/sp800-53-rev4-ipd.pdf</a>
+[^31]: *See* NIST Special Publication 800-53 "Security and Privacy Controls for Federal Information Systems and Organizations", *available at* <a>http://csrc.nist.gov/publications/drafts/800-53-rev4/sp800-53-rev4-ipd.pdf</a>
-[^32]: *See* OMB Circular A-130, section 8(a)(2).
+[^32]: *See* OMB Circular A-130, section 8(a)(2).
-[^33]: *See* OMB Circular A-130, section 8(a)(9)(b).
+[^33]: *See* OMB Circular A-130, section 8(a)(9)(b).
-[^34]: *See* OMB Circular A-130, section 8(a)(9)(c).
+[^34]: *See* OMB Circular A-130, section 8(a)(9)(c).
-[^35]: *See* OMB Circular A-130, section 8(a)(9)(a).
+[^35]: *See* OMB Circular A-130, section 8(a)(9)(a).
-[^36]: OMB Circular A-11, *available at* <a>http://www.whitehouse.gov/omb/circulars_a11_current_year_a11_toc</a>
+[^36]: OMB Circular A-11, *available at* <a>http://www.whitehouse.gov/omb/circulars_a11_current_year_a11_toc</a>
-[^37]: Pub. L. No. 111-352 (2011) (codified as 31 USC § 1120 note).
+[^37]: Pub. L. No. 111-352 (2011) (codified as 31 USC § 1120 note).
-[^38]: In March 2012 OMB established PortfolioStat accountability sessions, engaging directly with agency leadership to assess the maturity and effectiveness of current IT management practices and address management opportunities and challenges. For FY13 OMB PortfolioStat guidance, *see* OMB Memorandum M-13-09, *Fiscal Year 2013 PortfolioStat Guidance: Strengthening Federal IT Portfolio Management *(Mar. 27, 2013), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/2013/m-13-09.pdf</a>.
+[^38]: In March 2012 OMB established PortfolioStat accountability sessions, engaging directly with agency leadership to assess the maturity and effectiveness of current IT management practices and address management opportunities and challenges. For FY13 OMB PortfolioStat guidance, *see* OMB Memorandum M-13-09, *Fiscal Year 2013 PortfolioStat Guidance: Strengthening Federal IT Portfolio Management *(Mar. 27, 2013), *available at* <a>http://www.whitehouse.gov/sites/default/files/omb/memoranda/2013/m-13-09.pdf</a>.
-[^39]: OMB Memorandum M-05-08, *Designation of Senior Agency Officials for Privacy* (Feb. 11, 2005), *available at* <a>http://m.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-08.pdf</a>
+[^39]: OMB Memorandum M-05-08, *Designation of Senior Agency Officials for Privacy* (Feb. 11, 2005), *available at* <a>http://m.whitehouse.gov/sites/default/files/omb/assets/omb/memoranda/fy2005/m05-08.pdf</a>
-[^40]: 18 USC § 1905.
+[^40]: 18 USC § 1905.
-[^41]: *See* 13 U.S.C. §§ 8, 9 and 301(g) and 22 U.S.C. § 3104.
+[^41]: *See* 13 U.S.C. §§ 8, 9 and 301(g) and 22 U.S.C. § 3104.
124 schema.md
View
@@ -40,33 +40,33 @@ The following "common core" fields are required, to be used to describe each ent
*(Consult the 'Further Metadata Field Guidance' section lower in the page to learn more about the use of each element, including the range of valid entries where appropriate. Consult the [schema maps](/metadata-resources/#common_core_required_fields_equivalents) to find the equivalent Data.gov, RDFa Lite, and CKAN fields.)*
-{.table .table-striped}
-Field | Definition |JSON
+{: .table .table-striped}
+Field | Definition |JSON
------- | --------------- | --------------
-Title | Human-readable name of the asset. Should be in plain English and include sufficient detail to facilitate search and discovery. | title
-Description | Human-readable description (e.g., an abstract) with sufficient detail to enable a user to quickly understand whether the asset is of interest. | description
-Tags | Tags (or keywords) help users discover your dataset, please include terms that would be used by technical and non-technical users. | keyword
-Last Update | Most recent date on which the dataset was changed, updated or modified. | modified
-Publisher | The publishing agency. | publisher
-Contact Name | Contact person's name for the asset. | person
-Contact Email | Contact person's email address. | mbox
-Unique Identifier | A unique identifier for the dataset or API as maintained within an Agency catalog or database. | identifier
-Public Access Level | The degree to which this dataset **could** be made publicly-available, *regardless of whether it has been made available*. Choices: Public (is or *could be* made publicly available), Restricted (available under certain conditions), or Private (never able to be made publicly available) | accessLevel
+Title | Human-readable name of the asset. Should be in plain English and include sufficient detail to facilitate search and discovery. | title
+Description | Human-readable description (e.g., an abstract) with sufficient detail to enable a user to quickly understand whether the asset is of interest. | description
+Tags | Tags (or keywords) help users discover your dataset, please include terms that would be used by technical and non-technical users. | keyword
+Last Update | Most recent date on which the dataset was changed, updated or modified. | modified
+Publisher | The publishing agency. | publisher
+Contact Name | Contact person's name for the asset. | person
+Contact Email | Contact person's email address. | mbox
+Unique Identifier | A unique identifier for the dataset or API as maintained within an Agency catalog or database. | identifier
+Public Access Level | The degree to which this dataset **could** be made publicly-available, *regardless of whether it has been made available*. Choices: Public (is or *could be* made publicly available), Restricted (available under certain conditions), or Private (never able to be made publicly available) | accessLevel
"Common Core" Required-if-Applicable Fields
-------------------------------------------
The following fields must be used to describe each dataset if they are applicable:
-{.table .table-striped}
-Field | Definition |JSON
+{: .table .table-striped}
+Field | Definition |JSON
------- | --------------- | --------------
Data Dictionary | URL to the data dictionary for the dataset or API. Note that documentation other than a Data Dictionary can be referenced using Related Documents as shown in the expanded fields. | dataDictionary
-Download URL | URL providing direct access to the downloadable distribution of a dataset. | accessURL
-Endpoint | Endpoint of web service to access dataset. | webService
-Format | The file format or API type of the distribution. | format
-License | The license dataset or API is published with. See [Open Licenses](/open-licenses/) for more information. | license
-Spatial | The range of spatial applicability of a dataset. Could include a spatial region like a bounding box or a named place. | spatial
-Temporal | The range of temporal applicability of a dataset (i.e., a start and end date of applicability for the data). | temporal
+Download URL | URL providing direct access to the downloadable distribution of a dataset. | accessURL
+Endpoint | Endpoint of web service to access dataset. | webService
+Format | The file format or API type of the distribution. | format
+License | The license dataset or API is published with. See [Open Licenses](/open-licenses/) for more information. | license
+Spatial | The range of spatial applicability of a dataset. Could include a spatial region like a bounding box or a named place. | spatial
+Temporal | The range of temporal applicability of a dataset (i.e., a start and end date of applicability for the data). | temporal
Beyond Common Core -- Extending the Schema
------------------------------------------
@@ -76,26 +76,26 @@ Expanded Fields
---------------
Agencies are encouraged to use the following expanded fields when appropriate. Agencies may freely augment these fields with their own.
-{.table .table-striped}
-Field | Definition | JSON
------- | ------ | ----
-Release Date | Date of formal issuance. | issued
-Frequency | Frequency with which dataset is published. | accrualPeriodicity
-Language | The language of the dataset. | language
-Granularity | Level of granularity of the dataset. | granularity
-Data Quality | Whether the dataset meets the agency's Information Quality Guidelines (true/false). | dataQuality
-Category | Main thematic category of the dataset. | theme
-Related Documents | Related documents such as technical information about a dataset, developer documentation, etc. | references
-Size | The size of the downloadable dataset. | size
-Homepage URL | Alternative landing page used to redirect user to a contextual, Agency-hosted "homepage" for the Dataset or API when selecting this resource from the Data.gov user interface. | landingPage
-RSS Feed | URL for an RSS feed that provides access to the dataset. | feed
+{: .table .table-striped}
+Field | Definition | JSON
+------ | ------ | ----
+Release Date | Date of formal issuance. | issued
+Frequency | Frequency with which dataset is published. | accrualPeriodicity
+Language | The language of the dataset. | language
+Granularity | Level of granularity of the dataset. | granularity
+Data Quality | Whether the dataset meets the agency's Information Quality Guidelines (true/false). | dataQuality
+Category | Main thematic category of the dataset. | theme
+Related Documents | Related documents such as technical information about a dataset, developer documentation, etc. | references
+Size | The size of the downloadable dataset. | size
+Homepage URL | Alternative landing page used to redirect user to a contextual, Agency-hosted "homepage" for the Dataset or API when selecting this resource from the Data.gov user interface. | landingPage
+RSS Feed | URL for an RSS feed that provides access to the dataset. | feed
System of Records | If the systems is designated as a system of records under the Privacy Act of 1974, provide the URL to the System of Records Notice related to this dataset. | systemOfRecords
Further Metadata Field Guidance
-------------------------------
-{.table .table-striped}
+{: .table .table-striped}
Field | title
----- | -----
**Cardinality** | (1,1)
@@ -104,7 +104,7 @@ Field | title
**Usage Notes** | Acronyms should be avoided.
**Example** | `{"title":"Types of Vegetables"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **description**
----- | -----
**Cardinality** | (1,1)
@@ -113,7 +113,7 @@ Field | title
**Usage Notes** | This should be human-readable and understandable to an average person.
**Example** | `{"description":"This dataset contains a list of vegetables, including nutrition information and seasonality. Includes details on tomatoes, which are really fruit but considered a vegetable in this dataset."}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **dataDictionary**
----- | -----
**Cardinality** | (1,1)
@@ -122,7 +122,7 @@ Field | title
**Usage Notes** | -
**Example** | `{"dataDictionary":"http://www.agency.gov/vegetables/dictionary.html"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **accessURL**
----- | -----
**Cardinality** | (1,n)
@@ -131,7 +131,7 @@ Field | title
**Usage Notes** | This must be the **direct** download URL. Use **homepage** for landing or disambiguation pages, or **dataDictionary** for documentation pages.
**Example** | `{"accessURL":"http://www.agency.gov/vegetables/listofvegetables.csv"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **format**
----- | -----
**Cardinality** | (1,n)
@@ -140,7 +140,7 @@ Field | title
**Usage Notes** | This must describe the exact file available at **accessURL** using file extensions (e.g., CSV, XLS, XSLX, TSV, JSON, XML). For example, if the download file is a ZIP containing a CSV, the entry here is "ZIP".
**Example** | `{"format":"csv"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **keyword**
----- | -----
**Cardinality** | (1,n)
@@ -149,7 +149,7 @@ Field | title
**Usage Notes** | Separate keywords with commas.
**Example** | `{"keyword":"squash,vegetables,veggies,greens,leafy,spinach,kale,nutrition,tomatoes,tomatos"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **modified**
----- | -----
**Cardinality** | (1,1)
@@ -158,7 +158,7 @@ Field | title
**Usage Notes** | Dates should be formatted as YYYY-MM-DD. Specify "01" as the day if unknown. If this file is brand-new, enter the **issued** date here as well.
**Example** | `{"modified":"2012-01-15"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **publisher**
----- | -----
**Cardinality** | (1,1)
@@ -167,7 +167,7 @@ Field | title
**Usage Notes** | Departments and multi-unit agencies may use this field to describe which subordinate agency published this dataset.
**Example** | `{"publisher":"U.S. Department of Education"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **person**
----- | -----
**Cardinality** | (1,1)
@@ -176,7 +176,7 @@ Field | title
**Usage Notes** | Name should be formatted as Last, First
**Example** | `{"person":"Brown, John"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **mbox**
----- | -----
**Cardinality** | (1,1)
@@ -185,7 +185,7 @@ Field | title
**Usage Notes** | -
**Example** | `{"mbox":"joe@agency.gov"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **identifier**
----- | -----
**Cardinality** | (1,1)
@@ -194,7 +194,7 @@ Field | title
**Usage Notes** | This field allows third parties to maintain a consistent record for datasets even if title or URLs are updated. Agencies may integrate an existing system for maintaining unique identifiers or enter arbitrary characters for this field. However, each identifier **must** be unique across the agency's catalog and remain fixed. Characters should be alphanumeric.
**Example** | `{"identifier":"1344"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **accessLevel**
----- | -----
**Cardinality** | (1,1)
@@ -203,7 +203,7 @@ Field | title
**Usage Notes** | This field refers to degree to which this dataset *could be made available* to the public, regardless of whether it is currently available to the public. For example, if a member of the public can walk into your agency and obtain a dataset, that entry is **public** even if there are no files online. A *restricted* dataset is one only available under certain conditions or to certain audiences (such as researchers who sign a waiver). A private dataset is one that could never be made available to the public for privacy, security, or other reasons as determined by your agency.
**Example** | `{"accessLevel":"public"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **webService**
----- | -----
**Cardinality** | (0,1)
@@ -212,7 +212,7 @@ Field | title
**Usage Notes** | This field will serve to delineate the web services offered by an agency and will be used to aggregate cross-government API catalogs.
**Example** | `{"webService":"http://www.agency.gov/vegetables/vegetables.json"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **license**
----- | -----
**Cardinality** | (0,1)
@@ -221,7 +221,7 @@ Field | title
**Usage Notes** | See list of licenses.
**Example** | `{"license":""}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **spatial**
----- | -----
**Cardinality** | (0,1)
@@ -230,16 +230,16 @@ Field | title
**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}
+{: .table .table-striped}
**Field** | **temporal**
----- | -----
**Cardinality** | (0,1)
**Required** | Yes, if applicable
**Accepted Values** | See Usage Notes
-**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start date, end date} in the format YYYY-MM-DD hh:mm:ss using 24 hour clock time notation (e.g., 2011-02-14 12:00:00, 2013-02-14 12:00:00).
+**Usage Notes** | This field should contain an interval of time defined by start and end dates. Dates should be formatted as pairs of {start date, end date} in the format YYYY-MM-DD hh:mm:ss using 24 hour clock time notation (e.g., 2011-02-14 12:00:00, 2013-02-14 12:00:00).
**Example** | `{"temporal":"2000-01-15 00:45:00,2010-01-15 00:06:00"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **issued**
----- | -----
**Cardinality** | (0,1)
@@ -248,7 +248,7 @@ Field | title
**Usage Notes** | -
**Example** | `{"issued":"2001-01-15"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **accrualPeriodicity**
----- | -----
**Cardinality** | (0,1)
@@ -257,7 +257,7 @@ Field | title
**Usage Notes** | -
**Example** | `{"accrualPeriodicity":"yearly"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **language**
----- | -----
**Cardinality** | (0,n)
@@ -266,7 +266,7 @@ Field | title
**Usage Notes** | -
**Example** | `{"language":"English"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **granularity**
----- | -----
**Cardinality** | (0,1)
@@ -275,7 +275,7 @@ Field | title
**Usage Notes** | Typically geographical or temporal.
**Example** | `{"granularity":"vegetables"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **dataQuality**
----- | -----
**Cardinality** | (0,1)
@@ -284,7 +284,7 @@ Field | title
**Usage Notes** | Indicates whether a dataset conforms to the agency's information quality guidelines.
**Example** | `{"dataQuality":true}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **category**
----- | -----
**Cardinality** | (0,n)
@@ -293,7 +293,7 @@ Field | title
**Usage Notes** | Separate multiple categories with a comma. Could include [ISO Topic Categories](http://www.isotopicmaps.org/).
**Example** | `{"category":"vegetables"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **references**
----- | -----
**Cardinality** | (0,n)
@@ -302,7 +302,7 @@ Field | title
**Usage Notes** | Separate multiple URLs with a comma.
**Example** | `{"references":"http://www.agency.gov/fruits/fruits.csv,http://www.agency.gov/legumes/legumes.csv"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **distribution**
----- | -----
**Cardinality** | (0,n)
@@ -311,16 +311,16 @@ Field | title
**Usage Notes** | Distribution is a concatenation, as appropriate, of the following elements: download url, format, endpoint, language, size.
**Example** | `"distribution": [{"accessURL": "http://data.mcc.gov/example_resource/data.json", "format":"JSON", "size":"22mb"},{"accessURL":"http://data.mcc.gov/example_/data.xml", "format":"XML", "size":"24mb"}]`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **size**
----- | -----
**Cardinality** | (0,n)
**Required** | No
**Accepted Values** | See Usage Notes
-**Usage Notes** | Sizes should be formatted as (e.g.), 52kB, 140MB, 2GB.
+**Usage Notes** | Sizes should be formatted as (e.g.), 52kB, 140MB, 2GB.
**Example** | `{"size":"3MB"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **landingPage**
----- | -----
**Cardinality** | (0,1)
@@ -329,7 +329,7 @@ Field | title
**Usage Notes** | This field is not intended for an agency's homepage (e.g. www.agency.gov), but rather if a dataset has a human-friendly hub or landing page that users should be directed to for all resources tied to the dataset. This allows agencies to better specify what a visitor receives after selecting one of the agency's datasets on Data.gov or in third-party mashups.
**Example** | `{"landingPage":"http://www.agency.gov/vegetables"}`
-{.table .table-striped}
+{: .table .table-striped}
**Field** | **feed**
----- | -----
**Cardinality** | (0,n)
@@ -343,7 +343,7 @@ Rationale for Metadata Nomenclature
----------------------
We sought to be platform-independent and to align as much as possible with existing open standards.
-To that end, our JSON key names are directly drawn from [DCAT](http://www.w3.org/TR/vocab-dcat/), with two exceptions.
+To that end, our JSON key names are directly drawn from [DCAT](http://www.w3.org/TR/vocab-dcat/), with two exceptions.
We added the new **accessLevel** field to help easily sort datasets into our three existing categories: public, restricted, and private. This field means an agency can run a basic filter against its enterprise data catalog to generate a public-facing list of datasets that are, or *could one day be*, made publicly available (or, in the case of restricted data, available under certain conditions). This field also makes it easy for anyone to generate a list of datasets that *could* be made available but have not yet been released by filtering **accessLevel** to *public* and **accessURL** to *blank*.
Please sign in to comment.
Something went wrong with that request. Please try again.