Merge pull request #638 from f97gujo/master

Update some broken links

Author: adborden

business-case.md

@@ -16,6 +16,6 @@ Making data open and accessible in a standard, machine-readable format by defaul
 
 **Empower employees to make better-informed, data-driven decisions.** The new requirement to publish details about each dataset owned by your agency in a specific format will power a central search engine at [Data.gov](http://www.data.gov) that every single Federal employee (and member of the public) can use to easily locate data held, owned, and/or created by the Federal Government. Making it easier to find existing data is key to being able to then incorporate that data into your agency's everyday decision-making processes.
 
-**Positive attention from the public, media, and other agencies.** In recent years, [entire events](http://energy.gov/articles/energy-datapalooza-unleashing-power-open-data-advance-our-energy-future) [celebrating](http://www.ed.gov/blog/2013/01/education-datapalooza-unleashing-the-power-of-open-data-to-help-students-parents-and-teachers/) the release and use of open government data -- many hosted by the White House -- have taken place, with corresponding media coverage and international attention. The more data your agency makes available in easy-to-consume formats, the more opportunities for positive coverage of the availability and impact of those data and your agency's efforts.
+**Positive attention from the public, media, and other agencies.** In recent years, [entire events](http://energy.gov/articles/energy-datapalooza-unleashing-power-open-data-advance-our-energy-future) [celebrating](https://blog.ed.gov/2013/01/education-datapalooza-unleashing-the-power-of-open-data-to-help-students-parents-and-teachers/) the release and use of open government data -- many hosted by the White House -- have taken place, with corresponding media coverage and international attention. The more data your agency makes available in easy-to-consume formats, the more opportunities for positive coverage of the availability and impact of those data and your agency's efforts.
 
-**Generate revenue and create new jobs in the private sector.** McKinsey estimates that open health data alone adds over $300 billion to the economy each year. Entrepreneurs and non-profits integrate existing open government datasets in ways ranging from web apps that connect you with the nearest hospital in case of an emergency, with [information](http://www.healthdata.gov/question/what-types-applications-have-been-developed-using-healthdatagov-data) from Health and Human Services, to matching prospective college students with the most appropriate schools, based on [IPEDS](http://nces.ed.gov/ipeds/) data maintained by the Department of Education. Making more of your agency data publicly available in standards-compliant, machine-readable formats makes it easier for private sector companies and entrepreneurs to create new innovations fueled by your agency's data.
+**Generate revenue and create new jobs in the private sector.** McKinsey estimates that open health data alone adds over $300 billion to the economy each year. Entrepreneurs and non-profits integrate existing open government datasets in ways ranging from web apps that connect you with the nearest hospital in case of an emergency, with [information](https://www.data.gov/applications?app_agency=hhs-gov) from Health and Human Services, to matching prospective college students with the most appropriate schools, based on [IPEDS](http://nces.ed.gov/ipeds/) data maintained by the Department of Education. Making more of your agency data publicly available in standards-compliant, machine-readable formats makes it easier for private sector companies and entrepreneurs to create new innovations fueled by your agency's data.

implementation-guide.md

@@ -17,7 +17,7 @@ Following the November 30, 2013 deadline, agencies shall report progress on a qu
 
 ## I. Introduction
 
-The purpose of this guidance is to provide additional clarification and detailed requirements to assist agencies in carrying out the objectives of [Executive Order 13642](http://www.whitehouse.gov/the-press-office/2013/05/09/executive-order-making-open-and-machine-readable-new-default-government) of May 9, 2013, *Making Open and Machine Readable the New Default for Government Information* and [OMB Memorandum M-13-13](/policy-memo) *Open Data Policy-Managing Information as an Asset*.  Specifically, this document focuses on near-term efforts agencies must take to meet the following five initial requirements of M-13-13, which are due November 30, 2013 (six months from publication of M-13-13):
+The purpose of this guidance is to provide additional clarification and detailed requirements to assist agencies in carrying out the objectives of [Executive Order 13642](https://obamawhitehouse.archives.gov/the-press-office/2013/05/09/executive-order-making-open-and-machine-readable-new-default-government-) of May 9, 2013, *Making Open and Machine Readable the New Default for Government Information* and [OMB Memorandum M-13-13](/policy-memo) *Open Data Policy-Managing Information as an Asset*.  Specifically, this document focuses on near-term efforts agencies must take to meet the following five initial requirements of M-13-13, which are due November 30, 2013 (six months from publication of M-13-13):
 
 1. Create and maintain an Enterprise Data Inventory (Inventory)
 2. Create and maintain a Public Data Listing
@@ -58,11 +58,11 @@ Since agencies have varying levels of visibility into their data assets, the siz
 
 **Expand**: Expanding the inventory refers to adding additional data assets to the Inventory.  Agencies should develop their own strategy to expand the inventory and break down the work according to agency-defined classes of data<sup>[4](#footnote-4)</sup>.  Agencies should communicate their plans for expanding the Inventory in the Inventory Schedule (described in the minimum requirements). As agencies develop an Inventory Schedule, they may find it helpful to group their data assets into classes of data.  The following list provides examples of classes agencies may use as they schedule the expansion of the Inventory:
 
-* [Agency operating units](http://www.whitehouse.gov/sites/default/files/omb/assets/a11_current_year/app_c.pdf) (for example, bureaus or offices)
-* [Federal Program Inventory](http://goals.performance.gov/federalprograminventory) on Performance.gov
-* Common business areas or segments, such as those described in the [Business Reference Model](http://www.whitehouse.gov/omb/e-gov/fea) or the [Budget Function Codes](http://www.whitehouse.gov/sites/default/files/omb/assets/a11_current_year/s79.pdf) of budget accounts
-* Agency strategic objectives on Performance.gov and the [Performance Reference Model](http://www.whitehouse.gov/omb/e-gov/fea)
-* Types of data from [Data Reference Model](http://www.whitehouse.gov/omb/e-gov/fea)
+* Agency operating units (for example, bureaus or offices).
+* [Federal Program Inventory](https://obamaadministration.archives.performance.gov/federalprograminventory.html) on Performance.gov.
+* Common business areas or segments, such as those described in the [Business Reference Model](https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/brm_v3-1-service_codes_and_definitions_rev1_20130615.pdf) or the Budget Function Codes of budget accounts.
+* Agency strategic objectives on Performance.gov and the [Performance Reference Model.](https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/prm_2012_agencystrategicobjectivesv3.xlsx)
+* Types of data from [Data Reference Model.](https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/egov_docs/DRM_2_0_Final.pdf)
 * Existing listings of certain types of data assets, such as Information Collection Requests (ICR) submitted to OMB under the Paperwork Reduction Act (as listed on reginfo.gov<sup>[5](#footnote-5)</sup>) and/or files posted on the agency’s public website
 * Data assets already prioritized by the agency in response to other Administration initiatives<sup>[6](#footnote-6)</sup>
 * Primary related IT investments from the Federal IT Dashboard<sup>[7](#footnote-7)</sup>
@@ -178,7 +178,7 @@ The objectives of this activity are to:
 * Consult with agency’s Senior Agency Official for Privacy and general counsel regarding the barriers identified
 * Encourage dialogue regarding resources necessary to make more data assets public
 
-As part of an agency’s analysis to assign a general access level to each data asset<sup>[19](#footnote-19)</sup>,  agencies should consult section ##III.4 of the [OMB Memorandum M-13-13](/policy-memo),  and Executive Order 13556.  Specifically, agencies 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](http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf),"  which includes guidance and definitions for confidentiality, integrity, and availability. Agencies should also consult with the [Controlled Unclassified Information  (CUI)](http://www.whitehouse.gov/sites/default/files/docs/2012sharingstrategy_1.pdf) program to ensure compliance with CUI requirements, the National Strategy for Information Sharing and Safeguarding and the best practices found in Project Open Data.  In addition to complying with the Privacy Act of 1974, the Paperwork Reduction Act, the E-Government Act of 2002, the Federal Information Security Management Act (FISMA), and the Confidential Information Protection and Statistical Efficiency Act (CIPSEA), and other applicable laws, agencies should implement information policies based upon Fair Information Practice Principles, OMB guidance, and NIST guidance on Security and Privacy Controls for Federal Information Systems and Organizations.
+As part of an agency’s analysis to assign a general access level to each data asset<sup>[19](#footnote-19)</sup>,  agencies should consult section ##III.4 of the [OMB Memorandum M-13-13](/policy-memo),  and Executive Order 13556.  Specifically, agencies 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](http://csrc.nist.gov/publications/fips/fips199/FIPS-PUB-199-final.pdf),"  which includes guidance and definitions for confidentiality, integrity, and availability. Agencies should also consult with the [Controlled Unclassified Information  (CUI)](https://www.archives.gov/cui) program to ensure compliance with CUI requirements, the National Strategy for Information Sharing and Safeguarding and the best practices found in Project Open Data.  In addition to complying with the Privacy Act of 1974, the Paperwork Reduction Act, the E-Government Act of 2002, the Federal Information Security Management Act (FISMA), and the Confidential Information Protection and Statistical Efficiency Act (CIPSEA), and other applicable laws, agencies should implement information policies based upon Fair Information Practice Principles, OMB guidance, and NIST guidance on Security and Privacy Controls for Federal Information Systems and Organizations.
 
 * **Public**: Data asset is or could be made publicly available to all without restrictions.
 *The accessLevelComment field may be used to provide information on technical or resource barriers to increasing access to that data asset.*
@@ -187,7 +187,7 @@ As part of an agency’s analysis to assign a general access level to each data
 *One example, among many, is a data asset that can only be made available to select researchers under certain conditions, because the data asset contains sufficient granularity or linkages that make it possible to re-identify individuals, even though the data asset is stripped of Personally Identifiable Information (PII). Another example would be a data asset that contains PII and is made available to select researchers under strong legal protections. This category includes some but not all data assets designated as Controlled Unclassified Information (CUI), consistent with Executive Order 13556. The accessLevelComment field must be filled in with details on how one can obtain access.*
 
 * **Non-Public**: Data asset is not available to members of the public.
-*This category includes data assets that are only available for internal use by the Federal Government, such as by a single program, single agency, or across multiple agencies.  This category might include some but not all data assets designated as Controlled Unclassified Information (CUI), consistent with Executive Order 13556.  Some non-public data assets may still potentially be available to other intra-agency operating units and/or other government agencies, as discussed in [OMB Memorandum M-11-02: Sharing Data While Protecting Privacy](http://www.whitehouse.gov/sites/default/files/omb/memoranda/2011/m11-02.pdf).  The accessLevelComment field for non-public datasets must contain an explanation for the reasoning behind why these data cannot be made public.*
+*This category includes data assets that are only available for internal use by the Federal Government, such as by a single program, single agency, or across multiple agencies.  This category might include some but not all data assets designated as Controlled Unclassified Information (CUI), consistent with Executive Order 13556.  Some non-public data assets may still potentially be available to other intra-agency operating units and/or other government agencies, as discussed in [OMB Memorandum M-11-02: Sharing Data While Protecting Privacy](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2011/m11-02.pdf).  The accessLevelComment field for non-public datasets must contain an explanation for the reasoning behind why these data cannot be made public.*
 
 #### Minimum Requirements to Document if Data Cannot be Released
 
@@ -268,7 +268,7 @@ This section includes a high-level summary of agency actions and reporting requi
 
 <sup><a id="footnote-1">1</a></sup> Data Asset: A collection of data elements or datasets that make sense to group together. Each community of interest identifies the Data Assets specific to supporting the needs of their respective mission or business functions. Notably, a Data Asset is a deliberately abstract concept. A given Data Asset may represent an entire database consisting of multiple distinct entity classes, or may represent a single entity class.
 
-<sup><a id="footnote-2">2</a></sup> Programs from the Federal Program Inventory: http://goals.performance.gov/federalprograminventory
+<sup><a id="footnote-2">2</a></sup> Programs from the Federal Program Inventory: http://goals.performance.gov/federalprograminventory (dead link)
 
 <sup><a id="footnote-3">3</a></sup> Bureaus from OMB Circular A-11 Appendix C: http://www.whitehouse.gov/sites/default/files/omb/assets/a11_current_year/app_c.pdf
 

index.md

@@ -350,7 +350,7 @@ Federal agency Chief Data Officers. The Chief Data Officer’s role is part data
 
 #### FOIA Officers and Ombudsman
 Federal agency staff dedicated to handling Freedom of Information Act (FOIA) requests from industry and media. 
-*[The Office of Government Information Services (OGIS)](https://ogis.archives.gov/) at the National Archives and FOIA staff at agencies.*
+*[The Office of Government Information Services (OGIS)](https://www.archives.gov/ogis) at the National Archives and FOIA staff at agencies.*
 
 **Goal:** To monitor and measure the incoming demand for data and proactively release data in response to that signal.