[specs][s] changed full url to relative url Refs frictionlessdata/fri…

…ctionlessdata.io#413

data-package/README.md

@@ -247,7 +247,7 @@ A URL for the home on the web that is related to this data package.
 
 #### `version`
 
-a version string identifying the version of the package. It should conform to the [Semantic Versioning][semver] requirements and should follow the [Data Package Version](https://frictionlessdata.io/specs/patterns/#data-package-version) pattern.
+a version string identifying the version of the package. It should conform to the [Semantic Versioning][semver] requirements and should follow the [Data Package Version](/patterns/#data-package-version) pattern.
 
 #### `sources`
 

fiscal-data-package--budgets/README.md

@@ -52,7 +52,7 @@ The _ColumnTypes_ contained in this taxonomy contain:
 
 The canonic location for this taxonomy's _ColumnType_ definition - to be used in fiscal data package descriptors - is
 
-`https://frictionlessdata.io/taxonomies/fiscal/budgets.json`
+`https://specs.frictionlessdata.io/taxonomies/fiscal/budgets.json`
 
 ## The Taxonomy
 

fiscal-data-package--spending/README.md

@@ -43,7 +43,7 @@ The _ColumnTypes_ contained in this taxonomy contain:
 
 The canonic location for this taxonomy's _ColumnType_ definition - to be used in fiscal data package descriptors - is
 
-`https://frictionlessdata.io/taxonomies/fiscal/spending.json`
+`https://specs.frictionlessdata.io/taxonomies/fiscal/spending.json`
 
 ## The Taxonomy
 

fiscal-data-package/README.md

@@ -540,7 +540,7 @@ Finally we tie all of these resources together into the main table (also known a
           },
         ],
 ```
-Now, let's use the magic of [foreign keys](http://frictionlessdata.io/specs/table-schema/#foreign-keys) to connect the main table to all the secondary tables:
+Now, let's use the magic of [foreign keys](/table-schema/#foreign-keys) to connect the main table to all the secondary tables:
 ```yaml
         "foreignKeys": [
           {
@@ -949,7 +949,7 @@ So far it's quite straightforward (we omit the resources section for brevity).
 Now we define the _ColumnTypes_ that are being used in this specification.
 ```yaml
   "columnTypes": [
-    "https://frictionlessdata.io/taxonomies/fiscal/budgets.json",
+    "https://specs.frictionlessdata.io/taxonomies/fiscal/budgets.json",
 ```
 We start by specifying that we'll be using the budget taxonomy _ColumnTypes_, as described [here](./fiscal-data-package--budgets.md).
 

implementation/README.md

@@ -13,7 +13,7 @@ We prefer to focus on **actions** rather than features, feature sets, user stori
 
 ## Context
 
-While OKI and various other 3rd parties have been using the [Data Package family of specifications](http://frictionlessdata.io/specs/) with great success for several years, it has mostly been over the last 12 months that we are starting to see more mature libraries to implement the specifications at a "low level" for ease of reuse.
+While OKI and various other 3rd parties have been using the [Data Package family of specifications](/) with great success for several years, it has mostly been over the last 12 months that we are starting to see more mature libraries to implement the specifications at a "low level" for ease of reuse.
 
 At present, we consider the libraries maintained by Open Knowledge International in both Python and JavaScript to be reference implementations that serve as a guide for how to approach the specifications in code, and the type of actions that are enabled for users of the libraries. Further, we make extensive use of [JSON Schema](http://json-schema.org) to validate `descriptors` that are passed to these libraries. This enables significant reuse across implementations for descriptor validation logic.
 
@@ -29,10 +29,10 @@ The Data Package library can load and validate any `descriptor` for a **Data Pac
 
 #### References
 
-- [Data Package specification](http://frictionlessdata.io/specs/data-package/)
-- [Data Package Profiles](http://frictionlessdata.io/specs/data-package/#profiles)
-- [Tabular Data Package specification (the most commonly used and useful Profile)](http://frictionlessdata.io/specs/tabular-data-package/)
-- [JSON Schema Registry](http://frictionlessdata.io/schemas/registry.json)
+- [Data Package specification](/data-package/)
+- [Data Package Profiles](/data-package/#profiles)
+- [Tabular Data Package specification (the most commonly used and useful Profile)](/tabular-data-package/)
+- [JSON Schema Registry](/schemas/registry.json)
 - [JavaScript implementation](https://github.com/frictionlessdata/datapackage-js)
 - [Python implementation](https://github.com/frictionlessdata/datapackage-py)
 - [R implementation](https://github.com/christophergandrud/dpmr)
@@ -62,9 +62,9 @@ The Table Schema library can load and validate any Table Schema `descriptor`, al
 
 #### References
 
-- [Table Schema specification](http://frictionlessdata.io/specs/table-schema/)
-- [Tabular Data Resource specification](http://frictionlessdata.io/specs/tabular-data-resource/)
-- [JSON Schema Registry](http://frictionlessdata.io/schemas/registry.json)
+- [Table Schema specification](/table-schema/)
+- [Tabular Data Resource specification](/tabular-data-resource/)
+- [JSON Schema Registry](/schemas/registry.json)
 - [JavaScript implementation](https://github.com/frictionlessdata/tableschema-js)
 - [Python implementation](https://github.com/frictionlessdata/tableschema-py)
 

patterns/README.md

@@ -446,7 +446,7 @@ _In some cases, schemas are created after a legal text or some draft specificati
 
 ```
 {
-  "$schema": "https://frictionlessdata.io/schemas/table-schema.json",
+  "$schema": "https://specs.frictionlessdata.io/schemas/table-schema.json",
   "name": "irve",
   "title": "Infrastructures de recharge de véhicules électriques",
   "description": "Spécification du fichier d'échange relatif aux données concernant la localisation géographique et les caractéristiques techniques des stations et des points de recharge pour véhicules électriques",

profiles/README.md

@@ -41,7 +41,7 @@ We also publish the following Data Resource profiles:
 
 * [Tabular Data Resource][tdr]
 
-[registry]: http://frictionlessdata.io/schemas/registry.json
-[tdp]: http://frictionlessdata.io/specs/tabular-data-package/
-[fdp]: http://frictionlessdata.io/specs/fiscal-data-package/
-[tdr]: http://frictionlessdata.io/specs/tabular-data-resource/
+[registry]: /schemas/registry.json
+[tdp]: /tabular-data-package/
+[fdp]: /fiscal-data-package/
+[tdr]: /tabular-data-resource/

table-schema/README.md

@@ -379,7 +379,7 @@ The corresponding Table Schema is:
 
 The `constraints` property on Table Schema Fields can be used by consumers to list constraints for validating field values. For example, validating the data in a [Tabular Data Resource][tdr] against its Table Schema; or as a means to validate data being collected or updated via a data entry interface.
 
-[tdr]: http://frictionlessdata.io/specs/tabular-data-resource/
+[tdr]: http://specs.frictionlessdata.io/tabular-data-resource/
 
 All constraints `MUST` be tested against the logical representation of data, and the physical representation of constraint values `MAY` be primitive types as possible in JSON, or represented as strings that are castable with the `type` and `format` rules of the field.
 
@@ -692,7 +692,7 @@ An example of a self-referencing foreign key:
 
 **Comment**: Foreign Keys create links between one Table Schema and another Table Schema, and implicitly between the data tables described by those Table Schemas. If the foreign key is referring to another Table Schema how is that other Table Schema discovered? The answer is that a Table Schema will usually be embedded inside some larger descriptor for a dataset, in particular as the schema for a resource in the resources array of a [Data Package][dp]. It is the use of Table Schema in this way that permits a meaningful use of a non-empty `resource` property on the foreign key.
 
-[dp]: http://frictionlessdata.io/specs/data-package/
+[dp]: http://specs.frictionlessdata.io/data-package/
 
 ## Appendix: Related Work
 

tabular-data-package/README.md

@@ -30,7 +30,7 @@ The key features of this format are the following:
 
 As suggested by the name, Tabular Data Package extends and specializes the [Data Package][dp] spec for the specific case where the data is tabular.
 
-[dp]: http://frictionlessdata.io/specs/data-package/
+[dp]: /data-package/
 
 ## Why CSV
 
@@ -64,7 +64,7 @@ Tabular Data Package has the following requirements over and above those imposed
 - There `MUST` be a `profile` property with the value `tabular-data-package`
 - Each `resource` `MUST` be a [Tabular Data Resource][tdr]
 
-[tdr]: http://frictionlessdata.io/specs/tabular-data-resource/
+[tdr]: /tabular-data-resource/
 
 ### Example
 

tabular-data-resource/README.md

@@ -29,9 +29,9 @@ Tabular Data Resource extends [Data Resource][dr] in following key ways:
   JSON document containing the Table Schema
 * A new `dialect` property to describe the CSV dialect. This property follows the [CSV Dialect][cd] specification.
 
-[dr]: http://frictionlessdata.io/specs/data-resource/
-[ts]: http://frictionlessdata.io/specs/table-schema/
-[cd]: http://frictionlessdata.io/specs/csv-dialect/
+[dr]: http://specs.frictionlessdata.io/data-resource/
+[ts]: http://specs.frictionlessdata.io/table-schema/
+[cd]: http://specs.frictionlessdata.io/csv-dialect/
 
 ## Examples
 
@@ -173,7 +173,7 @@ If the CSV differs from this or the RFC in any other way regarding dialect (e.g.
 
 The value for the `dialect` property on a `resource` MUST be an `object` representing the dialect OR a `string` that identifies the location of the dialect.
 
-If a `string` it must be a [url-or-path](https://frictionlessdata.io/specs/data-resource/#url-or-path), that is a fully qualified http URL or a relative POSIX path. The file at the the location specified by this url-or-path string `MUST` be a JSON document containing the dialect.
+If a `string` it must be a [url-or-path](/data-resource/#url-or-path), that is a fully qualified http URL or a relative POSIX path. The file at the the location specified by this url-or-path string `MUST` be a JSON document containing the dialect.
 
 ### JSON Tabular Data