Update links for v1.1 schema

faq.md

@@ -95,7 +95,7 @@ While ISO 32000 is an open standard, the Portable Document Format (PDF) does not
 
 ### What is the relationship of the metadata standard (specifically) to NIEM, ISE, FGDC, and other existing (especially official) government data standards?
 
-The [Project Open Data metadata schema](/schema/) is based on existing vocabularies and easily mapped to NIEM, Information Sharing Environment, and FGDC.
+The [Project Open Data metadata schema](/v1.1/schema) is based on existing vocabularies and easily mapped to NIEM, Information Sharing Environment, and FGDC.
 
 ### What is a "persistent identifier"?
 
@@ -107,9 +107,9 @@ The core metadata schema was the result of recommendations from a government-wid
 
 ### How can I recommend changes and improvements to the metadata schema?
 
-Submit a pull request for the [metadata schema](/schema/). 
+Submit a [new issue](https://github.com/project-open-data/project-open-data.github.io/issues/new) describing the change you would like to see.
 
-### Can I extend the metadata schema beyond the terms specified in the [Project Open Data metadata schema](/schema/)?
+### Can I extend the metadata schema beyond the terms specified in the [Project Open Data metadata schema](/v1.1/schema)?
 
 Yes, if your data management process includes rich metadata specific to the mission of your agency or the Line of Business in which your agency participates, publishing additional metadata that makes your data more useful to the public is welcomed and encouraged.  Note that Data.gov will be harvesting only the metadata in this published schema unless specific arrangements are in place (e.g. geospatial FGDC/ISO).
 
@@ -160,7 +160,7 @@ A wide variety of tools are available to manage a data catalog, whether public-f
 
 ### What formats are required/optional for the agency.gov/data file?
 
-JSON is required though there are several optional syntaxes that can also be used when publishing the data file. The syntax that is required to make the data readily available to developers is JSON (JavaScript Object Notation). Agencies should also create a data.html file for the human-browsable data homepage and may use RDFa Lite (Resource Description Framework) to mark-up each dataset's metadata using the [Project Open Data metadata schema](/schema/). Agencies may also choose to populate a metadata file using XML (eXtensible Markup Language). These alternate metadata files are optional but agencies must maintain the JSON version at agency.gov/data.json. [Tools](http://labs.data.gov) are available to transform any instance of the file into the alternative formats.
+JSON is required though there are several optional syntaxes that can also be used when publishing the data file. The syntax that is required to make the data readily available to developers is JSON (JavaScript Object Notation). Agencies should also create a data.html file for the human-browsable data homepage and may use RDFa Lite (Resource Description Framework) to mark-up each dataset's metadata using the [Project Open Data metadata schema](/v1.1/schema). Agencies may also choose to populate a metadata file using XML (eXtensible Markup Language). These alternate metadata files are optional but agencies must maintain the JSON version at agency.gov/data.json. [Tools](http://labs.data.gov) are available to transform any instance of the file into the alternative formats.
 
 ## Agency participation with Open Data
 

implementation-guide.md

@@ -38,14 +38,14 @@ This guidance introduces an Enterprise Data Inventory framework to provide agenc
 ### A. Create and Maintain an Enterprise Data Inventory
 
 #### Purpose
-To develop a clear and comprehensive understanding of what data assets they possess, Federal Agencies are required to create an Enterprise Data Inventory (Inventory) that accounts for all data assets created or collected by the agency.  This includes, but is not limited to, data assets used in the agency’s information systems. The Inventory must be enterprise-wide, accounting for data assets across programs<sup>[2](#footnote-2)</sup>  and bureaus<sup>[3](#footnote-3)</sup>,  and must use the required [Project Open Data metadata schema](/schema) available on Project Open Data.   After creating the Inventory, agencies should continually improve the usefulness of the Inventory by expanding, enriching, and opening the Inventory (concepts described in the framework below).
+To develop a clear and comprehensive understanding of what data assets they possess, Federal Agencies are required to create an Enterprise Data Inventory (Inventory) that accounts for all data assets created or collected by the agency.  This includes, but is not limited to, data assets used in the agency’s information systems. The Inventory must be enterprise-wide, accounting for data assets across programs<sup>[2](#footnote-2)</sup>  and bureaus<sup>[3](#footnote-3)</sup>,  and must use the required [Project Open Data metadata schema](/v1.1/schema) available on Project Open Data.   After creating the Inventory, agencies should continually improve the usefulness of the Inventory by expanding, enriching, and opening the Inventory (concepts described in the framework below).
 
 The objectives of this activity are to:
 
 * Build an internal inventory that accounts for data assets used in the agency' s information systems
 * Include data assets produced through agency contracts and cooperative agreements, and in some cases agency-funded grants; include data assets associated with, but not limited to, research, program administration, statistical, and financial activities
 * Indicate if the data may be made publicly available and if currently available
-* Describe the data with [Project Open Data metadata schema](/schema) available on Project Open Data.
+* Describe the data with [Project Open Data metadata schema](/v1.1/schema) available on Project Open Data.
 
 #### Framework to Create and Maintain the Enterprise Data Inventory: Expand, Enrich, Open
 Since agencies have varying levels of visibility into their data assets, the size and maturity of agencies’ Enterprise Data Inventories will differ across agencies. OMB will assess agency progress toward overall maturity of the Enterprise Data Inventory through the maturity areas of “Expand,” “Enrich,” and “Open.”

index.md

@@ -30,7 +30,7 @@ This section is a list of definitions and principles used to guide the project.
 
 2-4 [Open Licenses](open-licenses/) - The definition for open licenses.
 
-2-5 [Project Open Data Metadata Schema](schema/) - The schema used to describe datasets, APIs, and published data at agency.gov/data.
+2-5 [Project Open Data Metadata Schema](/v1.1/schema/) - The schema used to describe datasets, APIs, and published data at agency.gov/data.
 
 ----------------
 
@@ -66,9 +66,9 @@ This section is a list of ready-to-use solutions or tools that will help agencie
 
 4-6 [Catalog Generator](http://labs.data.gov/dashboard/datagov/csv_to_json) - Multi-format tool to generate and maintain agency.gov/data catalog files. - *[Alternative](http://project-open-data.github.com/catalog-generator/)*
 
-4-7 A data.json validator can help you check compliance with the POD schema. - *[Hosted](http://data.civicagency.org/validate)*
+4-7 [Data.json validator](http://labs.data.gov/dashboard/validate) can help you check compliance with the POD schema.
 
-4-8 [Project Open Data Dashboard](http://data.civicagency.org) - A dashboard to check the status of /data and /data.json at each agency. This also includes a validator.
+4-8 [Project Open Data Dashboard](http://labs.data.gov/dashboard/) - A dashboard to check the status of /data and /data.json at each agency. This also includes a validator.
 
 4-9 [Data.json File Merger](http://data.json.file.merger.ongithub.com/) - Allows the easy combination of multiple data.json files from component agencies or bureaus into one combined file.
 

metadata-changelog.md

@@ -11,6 +11,8 @@ This page lists changes to the Project Open Data metadata schema by version. Lat
 
 ### Version 1.1 _(DRAFT - as of 11/6/2014)_
 
+Changes made to establish the [v1.1 Schema](/v1.1/schema)
+
 ##### Catalog Required Fields
 * Adds required `conformsTo` field to specify the schema version ([#309](https://github.com/project-open-data/project-open-data.github.io/issues/309))
 * Adds required `dataset` field as a container for all datasets listed ([#309](https://github.com/project-open-data/project-open-data.github.io/issues/309))
@@ -57,7 +59,7 @@ This page lists changes to the Project Open Data metadata schema by version. Lat
 
 ### Version 1.0 FINAL - 9/20/2013
 
-####Updates to original draft metadata:
+Changes made to establish the [v1.0 Schema](/schema)
 
 ##### “Common Core” Required Fields
 * Aligns `modified` field to ISO 8601 of least resolution