Amend data model links

Author: jason-fox

context-provider/README.md

@@ -119,7 +119,7 @@ The mapping path element is assumes that mappings are defined in the path as fol
     -   `windSpeed` NGSI attribute maps to `wind_speed` attribute on the API data
 
 For the full guidelines see the
-[FIWARE Data Models](https://fiware-datamodels.readthedocs.io/en/latest/guidelines/index.html)
+[Smart Data Models](https://smartdatamodels.org/)
 
 ## Health Check Endpoints
 

docs/application-mashups.md

@@ -426,8 +426,8 @@ Amend the coordinates setting as shown below and click accept.
 
 ![](https://fiware.github.io/tutorials.Application-Mashup/img/ngsi-to-poi-settings.png)
 
-According to the FIWARE Data Models
-[Guidelines](https://fiware-datamodels.readthedocs.io/en/latest/guidelines/index.html#modelling-location) an attribute
+According to the Smart Data Models
+[Guidelines](https://smartdatamodels.org/) an attribute
 called `location` should be used for geographical coordinates. Coordinates should be encoded using GeoJSON. Since this
 convention has been used for the tutorial data, the widget knows how to extract a location from the `Store` entity.
 
@@ -463,5 +463,5 @@ Clicking on the POIs retrieves additional data from each stores.
 
 Currently the data is displayed as unformatted JSON. This is because the `Store` context data entities with the tutorial
 example are not using a standard FIWARE data model. If a standard data model such as
-[Building](https://fiware-datamodels.readthedocs.io/en/latest/Building/Building/doc/spec/index.html) had been used the
+[Building](https://github.com/smart-data-models/dataModel.Building) had been used the
 data would be formatted in an appropriate manner and a **Building** specific icon would be used.

docs/entity-relationships.md

@@ -320,9 +320,9 @@ As you can see there are currently three additional property attributes present
 In databases, foreign keys are often used to designate a one-to-many relationship - for example every shelf is found in
 a single store and a single store can hold many shelving units. In order to remember this information we need to add an
 association relationship similar to a foreign key. Batch processing can again be used to amend the existing the
-**Shelf** entities to add a `refStore` attribute holding the relationship to each store. According to the FIWARE Data
-Modelling Guidelines on
-[linked data](https://fiware-datamodels.readthedocs.io/en/latest/guidelines/index.html#modelling-linked-data), when an
+**Shelf** entities to add a `refStore` attribute holding the relationship to each store. According to the Smart Data
+Models Guidelines on
+[linked data](https://smartdatamodels.org/), when an
 entity attribute is used as a link to other entities it should be named with the prefix `ref` plus the name of the
 target (linked) entity type.
 

docs/getting-started.md

@@ -264,7 +264,7 @@ curl -iX POST \
 
 Although the each data entity within your context will vary according to your use case, the common structure within each
 data entity should be standardized order to promote reuse. The full FIWARE data model guidelines can be found
-[here](https://fiware-datamodels.readthedocs.io/en/latest/guidelines/index.html). This tutorial demonstrates the usage
+[here](https://smartdatamodels.org/). This tutorial demonstrates the usage
 of the following recommendations:
 
 #### All terms are defined in American English

docs/linked-data.md

@@ -71,7 +71,7 @@ JSON-LD introduces the concept of the `@context` element which provides addition
 interpret the rest of the data with more clarity and depth.
 
 Furthermore the JSON-LD specification enables you to define a unique `@type` associating a well-defined
-[data model](https://fiware-datamodels.readthedocs.io/en/latest/guidelines/index.html) to the data itself.
+[data model](https://smartdatamodels.org/) to the data itself.
 
 ### Video: What is JSON-LD?
 
@@ -118,7 +118,7 @@ Once again, _entity_ can be considered to be the core element. Every entity must
 often a [URN](https://en.wikipedia.org/wiki/Uniform_resource_name), there is also a `type`, used to define the structure
 of the data held, which must also be a URI. This URI should correspond to a well-defined data model which can be found
 on the web. For example the URI `https://uri.fiware.org/ns/data-models#Building` is used to define common data model for
-a [Building](https://fiware-datamodels.readthedocs.io/en/latest/Building/Building/doc/spec/index.html).
+a [Building](https://github.com/smart-data-models/dataModel.Building).
 
 _Entities_ can have _properties_ and _relationships_. Ideally the name of each _property_ should also be a well defined
 URI which corresponds to a common concept found across the web (e.g. `http://schema.org/address` is a common URI for the
@@ -284,7 +284,7 @@ from multiple sources and remove ambiguity when comparing data coming from diffe
 
 Creating linked data using fully qualified names throughout would be painful, as each attribute would need to be a URI,
 so JSON-LD introduces the idea of an `@context` attribute which can hold pointers to context definitions. To add a
-FIWARE [Building](https://fiware-datamodels.readthedocs.io/en/latest/Building/Building/doc/spec/index.html) data entity,
+FIWARE [Building](https://github.com/smart-data-models/dataModel.Building) data entity,
 the following `@context` would be required
 
 ```json
@@ -293,7 +293,7 @@ the following `@context` would be required
     "type": "Building",
     ...  other data attributes
     "@context": [
-        "https://fiware.github.io/data-models/context.jsonld",
+        "https://smartdatamodels.org/context.jsonld",
         "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.3.jsonld"
     ]
 }
@@ -306,11 +306,11 @@ refers to the Core `@context` of NGSI-LD, this defines element such as `id` and
 entities, as well as defining terms such as `Property` and `Relationship`. The core context is so fundamental to
 NGSI-LD, that it is added by default to any `@context` sent to a request.
 
-### FIWARE Data Models
+### Smart Data Models
 
-[https://fiware.github.io/data-models/context.jsonld](https://fiware.github.io/data-models/context.jsonld) refers to the
-definition of standard data models supplied by FIWARE. Adding this to the `@context` will load the definitions of all
-the [data models](https://fiwaredata-models.readthedocs.io) defined by the FIWARE Foundation in collaboration with other
+[https://smartdatamodels.org/context.jsonld](https://smartdatamodels.org/context.jsonld) refers to the
+definition of standard data models supplied by the Smart Data Models project. Adding this to the `@context` will load the definitions of all
+the [data models](https://smartdatamodels.org/) defined by the FIWARE Foundation in collaboration with other
 organizations such as [GSMA](https://www.gsma.com/) and [TM Forum](https://www.tmforum.org/). A summary of the FQNs
 related to **Building** can be seen below:
 
@@ -372,7 +372,7 @@ curl -iX POST \
         "value": "Bösebrücke Einkauf"
     },
     "@context": [
-        "https://fiware.github.io/data-models/context.jsonld",
+        "https://smartdatamodels.org/context.jsonld",
         "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.3.jsonld"
     ]
 }'
@@ -381,7 +381,7 @@ curl -iX POST \
 The first request will take some time, as the context broker must navigate and load all of the files mentioned in the
 `@context`.
 
-> **Note**: if `https://fiware.github.io/data-models/context.jsonld` is unavailable for some reason the request will
+> **Note**: if `https://smartdatamodels.org/context.jsonld` is unavailable for some reason the request will
 > fail
 >
 > For a working production system it is essential that the `@context` files are always available to ensure third parties
@@ -428,7 +428,7 @@ curl -iX POST \
         "value": "Checkpoint Markt"
     },
     "@context": [
-        "https://fiware.github.io/data-models/context.jsonld",
+        "https://smartdatamodels.org/context.jsonld",
         "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.3.jsonld"
     ]
 }'
@@ -638,7 +638,7 @@ A [`Link` header](https://www.w3.org/wiki/LinkHeader) must be supplied to associ
 with the FQN `https://uri.fiware.org/ns/data-models#Building`. The full link header syntax can be seen below:
 
 ```text
-Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json
+Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json
 ```
 
 The standard HTTP `Link` header allows metadata (in this case the `@context`) to be passed in without actually touching
@@ -649,7 +649,7 @@ the resource in question. In the case of NGSI-LD, the metadata is a file in `app
 ```bash
 curl -G -X GET \
   'http://localhost:1026/ngsi-ld/v1/entities' \
-    -H 'Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"' \
+    -H 'Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"' \
     'http://localhost:1026/ngsi-ld/v1/entities' \
     -H 'Accept: application/ld+json' \
     -d 'type=Building' \
@@ -679,7 +679,7 @@ used as the `@context` returned in the response.
             "type": "Point",
             "coordinates": [13.3986, 52.5547]
         },
-        "@context": "https://fiware.github.io/data-models/context.jsonld"
+        "@context": "https://smartdatamodels.org/context.jsonld"
     },
     {
         "id": "urn:ngsi-ld:Building:store002",
@@ -696,7 +696,7 @@ used as the `@context` returned in the response.
             "type": "Point",
             "coordinates": [13.3903, 52.5075]
         },
-        "@context": "https://fiware.github.io/data-models/context.jsonld"
+        "@context": "https://smartdatamodels.org/context.jsonld"
     }
 ]
 ```
@@ -712,7 +712,7 @@ the `q` parameter - if a string has spaces in it, it can be URL encoded and held
 ```bash
 curl -G -X GET \
     'http://localhost:1026/ngsi-ld/v1/entities' \
-    -H 'Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
+    -H 'Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
     -H 'Accept: application/ld+json' \
     -d 'type=Building' \
     -d 'q=name==%22Checkpoint%20Markt%22' \
@@ -721,12 +721,12 @@ curl -G -X GET \
 
 #### Response:
 
-The `Link` header `https://fiware.github.io/data-models/context.jsonld` holds an array of `@context` as shown:
+The `Link` header `https://smartdatamodels.org/context.jsonld` holds an array of `@context` as shown:
 
 ```json
 {
     "@context": [
-        "https://fiware.github.io/data-models/context.jsonld",
+        "https://smartdatamodels.org/context.jsonld",
         "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.3.jsonld"
     ]
 }
@@ -754,7 +754,7 @@ JSON-LD as shown:
             "type": "Point",
             "coordinates": [13.3903, 52.5075]
         },
-        "@context": "https://fiware.github.io/data-models/context.jsonld"
+        "@context": "https://smartdatamodels.org/context.jsonld"
     }
 ]
 ```
@@ -770,7 +770,7 @@ done using the `q` parameter, comma separating the acceptable values.
 ```bash
 curl -G -X GET \
     'http://localhost:1026/ngsi-ld/v1/entities' \
-    -H 'Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
+    -H 'Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
     -H 'Accept: application/ld+json' \
     -d 'type=Building' \
     -d 'q=category==%22commercial%22,%22office%22 \
@@ -798,7 +798,7 @@ The response is returned in JSON-LD format with short form attribute names:
             "type": "Point",
             "coordinates": [13.3986, 52.5547]
         },
-        "@context": "https://fiware.github.io/data-models/context.jsonld"
+        "@context": "https://smartdatamodels.org/context.jsonld"
     },
     {
         "id": "urn:ngsi-ld:Building:store002",
@@ -815,7 +815,7 @@ The response is returned in JSON-LD format with short form attribute names:
             "type": "Point",
             "coordinates": [13.3903, 52.5075]
         },
-        "@context": "https://fiware.github.io/data-models/context.jsonld"
+        "@context": "https://smartdatamodels.org/context.jsonld"
     }
 ]
 ```
@@ -832,7 +832,7 @@ Filtering can be done using the `q` parameter - sub-attributes are annotated usi
 ```bash
 curl -G -X GET \
     'http://localhost:1026/ngsi-ld/v1/entities' \
-    -H 'Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
+    -H 'Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
     -H 'Accept: application/ld+json' \
     -d 'type=Building' \
     -d 'q=address[addressLocality]==%22Kreuzberg%22' \
@@ -860,7 +860,7 @@ Use of the `Link` header and the `options=keyValues` parameter reduces the respo
             "type": "Point",
             "coordinates": [13.3903, 52.5075]
         },
-        "@context": "https://fiware.github.io/data-models/context.jsonld"
+        "@context": "https://smartdatamodels.org/context.jsonld"
     }
 ]
 ```
@@ -878,7 +878,7 @@ This supersedes the `mq` parameter from NGSI v2.
 ```bash
 curl -G -X GET \
     'http://localhost:1026/ngsi-ld/v1/entities' \
-    -H 'Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
+    -H 'Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"'
     -H 'Accept: application/json' \
     -d 'type=Building' \
     -d 'q=address.verified==true' \
@@ -942,7 +942,7 @@ If another attribute is to be used, an additional `geoproperty` parameter is req
 ```bash
 curl -G -X GET \
   'http://localhost:1026/ngsi-ld/v1/entities' \
-  -H 'Link: <https://fiware.github.io/data-models/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/json"'
+  -H 'Link: <https://smartdatamodels.org/context.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/json"'
   -H 'Accept: application/json' \
   -d 'type=Building' \
   -d 'geometry=Point' \

docs/relationships-linked-data.md

@@ -82,7 +82,7 @@ described below:
 
 -   The [**Store** model](https://fiware.github.io/tutorials.Step-by-Step/schema/Store/) is now based on and extends the
     FIWARE
-    [**Building** model](https://fiware-datamodels.readthedocs.io/en/latest/Building/Building/doc/spec/index.html). This
+    [**Building** model](https://github.com/smart-data-models/dataModel.Building). This
     ensures that it offers standard properties for `name`, `address` and category.
     -   A Building will hold `furniture` this is a 1-many relationship.
         -   Building ➡ Shelf.
@@ -348,8 +348,8 @@ computer readable JSON-LD `@context` Data Models is included in the request.
 
 ### Display all Buildings
 
-The Stores of the supermarket have been created using the FIWARE
-[**Building** model](https://fiware-datamodels.readthedocs.io/en/latest/Building/Building/doc/spec/index.html) and the
+The Stores of the supermarket have been created using the Smart data
+[**Building** model](https://github.com/smart-data-models/dataModel.Building) and the
 enumerated value of this type is `fiware:Building` which expands to `https://uri.fiware.org/ns/datamodels%23Building`.
 It is therefore possible to request all building entities without supplying a known context.