project-open-data · gbinal · Apr 8, 2015 · Oct 2, 2014 · Oct 2, 2014 · Oct 2, 2014
diff --git a/_config.yml b/_config.yml
@@ -1,13 +1,13 @@
 #document settings
 title: Project Open Data
 desc: "Open Data Policy — Managing Information as an Asset"
-url: https://project-open-data.cio.gov/
-repo_name: project-open-data.github.io
-branch: master
+url: https://project-open-data.cio.gov
 
 #global settings, no need to change these
 root_url: https://project-open-data.cio.gov
 org_name: project-open-data
+repo_name: project-open-data.github.io
+branch: master
 
 # default build settings for running locally, no need to edit
 pymgemnts: true

diff --git a/_includes/header.html b/_includes/header.html
@@ -15,6 +15,8 @@
   <link rel="stylesheet" href="/assets/css/bootstrap.css">
   <link rel="stylesheet" href="/assets/css/site.css">
 
+  <link rel="canonical" href="{{ site.url }}{{ page.url }}" />
+
   {% capture edit_url %}https://github.com/{{ site.org_name }}/{{ site.repo_name }}/edit/{{ site.branch }}/{{ page.path }}{% endcapture %}
 
 </head>

diff --git a/federal-awards-faq.md b/federal-awards-faq.md
@@ -89,7 +89,7 @@ For example, if a deliverable consists of an assessment or end-state report and
 As agencies contemplate the purchase of systems that will process data, the requirements in Section 3 of M-13-13 must be considered. These requirements provide for a life-cycle view of effective and efficient information management by requiring that information is collected in a way that supports downstream processing, and that systems are built to support interoperability and information accessibility, including regular access or exporting of the data as a standard requirement of such systems. Addressing these considerations early in the acquisition process will protect against the costly retrofitting that is often involved in retrieving data from legacy platform-dependent systems.
 
 #### Q14: How difficult is it for agency personnel to transform machine-readable data into a platform-independent format? Is requiring data in a platform-independent format likely to drive up deliverable cost? Who can provide guidance on making the decision regarding who should convert the data?
-A: A number of tools are available to transform data from proprietary formats to platform independent formats. [Project Open Data](http://project-open-data.github.io/) has collected a number of such tools. Many of these tools are easy to operate and require very little investment of time or effort. As such, they can be used either by a contractor (if the contract specifies delivery in a platform independent format) or by Federal employees (if the contract specifies delivery in a proprietary format). 
+A: A number of tools are available to transform data from proprietary formats to platform independent formats. [Project Open Data](/) has collected a number of such tools. Many of these tools are easy to operate and require very little investment of time or effort. As such, they can be used either by a contractor (if the contract specifies delivery in a platform independent format) or by Federal employees (if the contract specifies delivery in a proprietary format).
 Your agency CIO is responsible for leading the open data initiative in your agency as well as working with the interagency working group on this effort.  Your agency may determine that having the agency translate the delivered data is most cost effective so we encourage you to work with your CIO on this effort.
 
 ####Q15: Are there any Federal Acquisition Regulation (FAR) provisions that might affect an agency’s authority to publish data provided as a contract deliverable?

diff --git a/glossary.md b/glossary.md
@@ -53,11 +53,11 @@ A value or set of values representing a specific concept or concepts. Data becom
 
 ### /Data page
 
-A hub for data discovery which provides a common location that lists and links to an organization’s datasets.  Such a hub is often located at www.example.com/data.  —*[source](http://project-open-data.github.io/policy-memo/)*
+A hub for data discovery which provides a common location that lists and links to an organization’s datasets.  Such a hub is often located at www.example.com/data.  —*[source](/policy-memo/)*
 
 ### 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.  -*[source](http://project-open-data.github.io/implementation-guide/#footnote-1)*
+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.  -*[source](/implementation-guide/#footnote-1)*
 
 ### Dataset
 

diff --git a/implementation-guide.md b/implementation-guide.md
@@ -19,7 +19,7 @@ The purpose of this guidance is to provide additional clarification and detailed
 4. Document if data cannot be released
 5. Clarify roles and responsibilities for promoting efficient and effective data release
 
-Agencies will establish an open data infrastructure by implementing this guidance and Memorandum [M-13-13](/policy-memo) and taking advantage of the resources provided on [Project Open Data](http://project-open-data.github.io).    Once established, agencies will continue to evolve the infrastructure by identifying and adding new data assets<sup>[1](#footnote-1)</sup>,  enriching the description of those data assets through improved metadata, and increasing the amount of data shared with other agencies and the public.  
+Agencies will establish an open data infrastructure by implementing this guidance and Memorandum [M-13-13](/policy-memo) and taking advantage of the resources provided on [Project Open Data](/).    Once established, agencies will continue to evolve the infrastructure by identifying and adding new data assets<sup>[1](#footnote-1)</sup>,  enriching the description of those data assets through improved metadata, and increasing the amount of data shared with other agencies and the public.
 
 At a minimum, a successful open data infrastructure must:
 

diff --git a/licenses.md b/licenses.md
@@ -52,4 +52,3 @@ When agencies purchase data or content from third-party vendors, care must be ta
 * *[Copyright and Other Rights Pertaining to U.S. Government Works](http://www.usa.gov/copyright.shtml)*
 * *[Licensing Policies, Principles, and Resources: Examples of how government has addressed open licensing questions](https://project-open-data.cio.gov/licensing-resources/)*
 * *[Extended list of conformant licenses](http://opendefinition.org/licenses/)*
-
diff --git a/licensing-resources.md b/licensing-resources.md
@@ -71,7 +71,7 @@ This Source Code Policy, forked from the DoD/CFPB policy, includes a new "Commun
 An educational resource for government employees and government contractors to understand the policies and legal issues relating to the use of open source software in the DoD.  Much of the information collected there is applicable to other Federal agencies.   The FAQ covers a range of issues, including:  DoD policy on OSS, general information about OSS, OSS licenses, release of government software as OSS, and OSS-like approaches used within the Federal government.
 * [Working Version of the FAQs](http://risacher.github.io/DoD-OSS-FAQ/)
 
-###[How to FOSS Your Government Project](http://bit.ly/HowToFOSS)
+###[How to FOSS Your Government Project](https://bit.ly/HowToFOSS)
 *National Security Agency & DoD CIO*
 
 A checklist developed at NSA to document the internal processes required to release government-developed software as open source software.  It provides a detailed example for other agencies to use as a starting point.  The original document contained a number of NSA-specific processes, the linked document is a "template" version that removes the specifics, and leaves just the outline and advisory material.

diff --git a/policy-docs.md b/policy-docs.md
@@ -11,10 +11,10 @@ This section offers examples of policy documents (memos, guidance, manuals, etc)
 
 * Department of Health and Human Services, "[The Health Data Initiative Strategy and Execution Plan](https://docs.google.com/document/d/1FyKD_JLmFNLKgw5wjJOSn-F84SZi3cdOUg-1LUYFGIA/pub?embedded=true)".  This document, released on October 23, 2013 [on HealthData.gov](http://healthdata.gov/blog/health-data-initiative-strategy-execution-plan-released-and-ready-feedback) serves as the Department's data milestones for 2014-2016.
 * Department of Health and Human Services, "[Health Data Initiative Next Steps](https://s3.amazonaws.com/file_hosting/HDI+Memo+KGS+8+1+11.pdf)".  Memo from Secretary Kathleen Sebelius to agency heads, released on August 1, 2011.
-* Department of Housing and Urban Development, "[Open Data Policy - Managing HUD's Data as a Strategic Information Asset](http://project-open-data.github.io/assets/docs/Memo_from_the_Acting_Deputy%20Secretary_et_alia_Open_Data_Policy.pdf)".  This memo, released on April 30, 2014, describes HUD's efforts to manage and share data with the public.  
+* Department of Housing and Urban Development, "[Open Data Policy - Managing HUD's Data as a Strategic Information Asset](/assets/docs/Memo_from_the_Acting_Deputy%20Secretary_et_alia_Open_Data_Policy.pdf)".  This memo, released on April 30, 2014, describes HUD's efforts to manage and share data with the public.
 * Department of the Interior, "[Memo Re: Implementation of DOI Open Data Policy"](/assets/docs/MEMO_RE_IMPLEMENTATION_OF_DOI_OPEN_DATA_POLICY.pdf)". This memo served as the official DOI announcement to all Department Bureaus and Offices of the near-term requirements of M-13-13, and also called for the creation of a Data Services Board to oversee data lifecycle management moving forward.
 * Department of State, [Open Data Plan](http://www.state.gov/documents/organization/217997.pdf).  This document describes how the Department of State will meet the requirements of m-13-13.
-* Department of Veterans Affairs, "[Open Data - Quarterly Data Asset Collection Requirements](http://project-open-data.github.io/assets/docs/Data_Asset_Collection_Memo-02_21_14.pdf)". Memo from the Acting Assistant Secretary for Policy and Planning to Under Secretaries, Assistant Secretaries and Other Key Officials, released on February 26, 2014.      
+* Department of Veterans Affairs, "[Open Data - Quarterly Data Asset Collection Requirements](/assets/docs/Data_Asset_Collection_Memo-02_21_14.pdf)". Memo from the Acting Assistant Secretary for Policy and Planning to Under Secretaries, Assistant Secretaries and Other Key Officials, released on February 26, 2014.
 * Environmental Protection Agency, "[Open Data Policy Implementation Plan](http://www.epa.gov/digitalstrategy/pdf/EPA_OpenDataPolicy_ImplementationPlan_2013Nov26.pdf)".  This report documents EPA's implementation plan and current progress in meeting the requirements set forth in the White House “Open Data Policy –Managing Information as an Asset” Memorandum M-13-13.
 * General Services Administration, ["Increasing Data Sharing, Transparency and Reuse at GSA"](https://s3.amazonaws.com/file_hosting/263508-Data+sharing+memo-FINAL.pdf).  This document, released on February 14, 2014, outlined to all agency staff the role of OMB Memorandum M-13-13 within the agency.
 * National Aeronautics and Space Administration, [Data and Information Policy for NASA's Earth Science Program](http://science.nasa.gov/earth-science/earth-science-data/data-information-policy/).  A set of data exchange and access principles adopted by NASA for its Earth Science program.

diff --git a/policy-memo.md b/policy-memo.md
@@ -73,7 +73,7 @@ This attachment provides definitions and implementation guidance for M-13-13, *O
 
 * *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.
+* *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.cio.gov](/). [^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.
 
 ### II. Scope
 

diff --git a/schema.md b/schema.md
@@ -31,7 +31,7 @@ Metadata is structured information that describes, explains, locates, or otherwi
 
 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 information documenting the structure, processing history, quality, relationships, and other properties of a dataset. Making metadata machine readable greatly increases its utility, but requires more detailed standardization, defining not only field names, but also how information is encoded in the metadata fields.
 
-Establishing a common vocabulary is the key to communication. The **common core metadata** specified in this memorandum is based on [DCAT](http://www.w3.org/TR/vocab-dcat/), a hierarchical vocabulary specific to datasets. This specification defines three levels of metadata elements: Required, Required-if (conditionally required), and Expanded fields.  These elements were selected to represent information that is most often looked for on the web. To assist users of other metadata standards, [mappings](http://project-open-data.github.io/metadata-resources/#common_core_required_fields_equivalents) to equivalent elements in other standards are provided.  
+Establishing a common vocabulary is the key to communication. The **common core metadata** specified in this memorandum is based on [DCAT](http://www.w3.org/TR/vocab-dcat/), a hierarchical vocabulary specific to datasets. This specification defines three levels of metadata elements: Required, Required-if (conditionally required), and Expanded fields.  These elements were selected to represent information that is most often looked for on the web. To assist users of other metadata standards, [mappings](/metadata-resources/#common_core_required_fields_equivalents) to equivalent elements in other standards are provided.
 
 What to Document -- Datasets and Web APIs
 -------------------------------------
@@ -121,7 +121,6 @@ references				| Related Documents   | Related documents such as technical inform
 issued					| Release Date        | Date of formal issuance.
 systemOfRecords			| 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.
 
-
 Further Metadata Field Guidance (alphabetical by field)
 -------------------------------
Original file line number	Diff line number	Diff line change
Expand Up		@@ -52,4 +52,3 @@ When agencies purchase data or content from third-party vendors, care must be ta
		* [Copyright and Other Rights Pertaining to U.S. Government Works](http://www.usa.gov/copyright.shtml)
		* [Licensing Policies, Principles, and Resources: Examples of how government has addressed open licensing questions](https://project-open-data.cio.gov/licensing-resources/)
		* [Extended list of conformant licenses](http://opendefinition.org/licenses/)