Skip to content

Commit ceaa713

Browse files
jason-foxjason-fox
committed
Update ESTI links
1 parent 8d197c2 commit ceaa713

24 files changed

Lines changed: 52 additions & 52 deletions

‎docs/application-mashups.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ The specific architecture of each section of the tutorial is discussed below.
121121
<h3>Wirecloud Configuration</h3>
122122

123123
```yaml
124-
image: fiware/wirecloud
124+
image: quay.io/fiware/wirecloud
125125
container_name: fiware-wirecloud
126126
hostname: wirecloud
127127
ports:

‎docs/context-providers.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ of the associated `docker-compose.yml` file:
107107

108108
```yaml
109109
tutorial:
110-
image: fiware/tutorials.context-provider
110+
image: quay.io/fiware/tutorials.context-provider
111111
hostname: context-provider
112112
container_name: fiware-tutorial
113113
networks:

‎docs/crud-operations.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ The necessary configuration information can be seen in the services section of t
7575

7676
```yaml
7777
orion:
78-
image: fiware/orion:latest
78+
image: quay.io/fiware/orion:latest
7979
hostname: orion
8080
container_name: orion
8181
depends_on:
@@ -149,7 +149,7 @@ Once an `<entity-id>` is known within the context, individual data entities can
149149
`/v2/entities/<entity-id>` endpoint.
150150

151151
It is recommended that entity identifiers should be URNs following the
152-
[NGSI-LD specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf),
152+
[NGSI-LD specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_cim009v010701p.pdf),
153153
therefore each `id` is a URN which follows a standard format: `urn:ngsi-ld:<entity-type>:<entity-id>`. This helps to
154154
make every `id` in the context data unique.
155155

‎docs/custom-iot-agent.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ section of the associated `docker-compose.yml` file:
128128

129129
```yaml
130130
tutorial:
131-
image: fiware/tutorials.context-provider
131+
image: quay.io/fiware/tutorials.context-provider
132132
hostname: iot-sensors
133133
container_name: fiware-tutorial
134134
networks:
@@ -182,7 +182,7 @@ instantiated using a `docker-compose.yaml` file. The necessary configuration can
182182

183183
```yaml
184184
iot-agent:
185-
image: fiware/iotagent-xml
185+
image: quay.io/fiware/iotagent-xml
186186
build:
187187
context: iot-agent
188188
dockerfile: Dockerfile
@@ -416,7 +416,7 @@ not hold sufficient information.
416416
### Provisioning a Sensor
417417

418418
It is common good practice to use URNs following the NGSI-LD
419-
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf) when creating
419+
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_cim009v010701p.pdf) when creating
420420
entities. Furthermore, it is easier to understand meaningful names when defining data attributes. These mappings can be
421421
defined by provisioning a device individually.
422422

‎docs/entity-relationships.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ The necessary configuration information can be seen in the services section of t
7676

7777
```yaml
7878
orion:
79-
image: fiware/orion:latest
79+
image: quay.io/fiware/orion:latest
8080
hostname: orion
8181
container_name: fiware-orion
8282
depends_on:
@@ -283,7 +283,7 @@ curl -iX POST \
283283
```
284284

285285
In both cases we have encoded each entity `id` according to the NGSI-LD
286-
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf) - the proposal
286+
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_cim009v010701p.pdf) - the proposal
287287
is that each `id` is a URN follows a standard format: `urn:ngsi-ld:<entity-type>:<entity-id>`. This will mean that every
288288
`id` in the system will be unique.
289289

‎docs/getting-started.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -291,7 +291,7 @@ In this case we only have one entity type - **Store**
291291
#### Entity IDs should be a URN following NGSI-LD guidelines
292292

293293
NGSI-LD has recently been published as a full ETSI
294-
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf), the proposal is
294+
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_cim009v010701p.pdf), the proposal is
295295
that each `id` is a URN follows a standard format: `urn:ngsi-ld:<entity-type>:<entity-id>`. This will mean that every
296296
`id` in the system will be unique
297297

‎docs/historic-context-flume.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ mongo-db:
168168

169169
```yaml
170170
cygnus:
171-
image: fiware/cygnus-ngsi:latest
171+
image: quay.io/fiware/cygnus-ngsi:latest
172172
hostname: cygnus
173173
container_name: fiware-cygnus
174174
depends_on:
@@ -559,7 +559,7 @@ The `postgres-db` container is driven by environment variables as shown:
559559

560560
```yaml
561561
cygnus:
562-
image: fiware/cygnus-ngsi:latest
562+
image: quay.io/fiware/cygnus-ngsi:latest
563563
hostname: cygnus
564564
container_name: fiware-cygnus
565565
networks:
@@ -897,7 +897,7 @@ The `mysql-db` container is driven by environment variables as shown:
897897

898898
```yaml
899899
cygnus:
900-
image: fiware/cygnus-ngsi:latest
900+
image: quay.io/fiware/cygnus-ngsi:latest
901901
hostname: cygnus
902902
container_name: fiware-cygnus
903903
networks:
@@ -1197,7 +1197,7 @@ persistence and holding data related to the Orion Context Broker and the IoT Age
11971197

11981198
```yaml
11991199
cygnus:
1200-
image: fiware/cygnus-ngsi:latest
1200+
image: quay.io/fiware/cygnus-ngsi:latest
12011201
hostname: cygnus
12021202
container_name: fiware-cygnus
12031203
depends_on:

‎docs/identity-management.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ The specific architecture of each section of the tutorial is discussed below.
9999

100100
```yaml
101101
keyrock:
102-
image: fiware/idm
102+
image: quay.io/fiware/idm
103103
container_name: fiware-keyrock
104104
hostname: keyrock
105105
depends_on:

‎docs/iot-agent-json.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -181,7 +181,7 @@ section of the associated `docker-compose.yml` file:
181181

182182
```yaml
183183
tutorial:
184-
image: fiware/tutorials.context-provider
184+
image: quay.io/fiware/tutorials.context-provider
185185
hostname: iot-sensors
186186
container_name: fiware-tutorial
187187
networks:
@@ -232,7 +232,7 @@ tagged `fiware/iotagent-json`. The necessary configuration can be seen below:
232232

233233
```yaml
234234
iot-agent:
235-
image: fiware/iotagent-json:latest
235+
image: quay.io/fiware/iotagent-json:latest
236236
hostname: iot-agent
237237
container_name: fiware-iot-agent
238238
depends_on:
@@ -456,7 +456,7 @@ however it has been included here for completeness.
456456
### Provisioning a Sensor
457457

458458
It is common good practice to use URNs following the NGSI-LD
459-
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf) when creating
459+
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_cim009v010701p.pdf) when creating
460460
entities. Furthermore, it is easier to understand meaningful names when defining data attributes. These mappings can be
461461
defined by provisioning a device individually.
462462

‎docs/iot-agent.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ section of the associated `docker-compose.yml` file:
172172

173173
```yaml
174174
tutorial:
175-
image: fiware/tutorials.context-provider
175+
image: quay.io/fiware/tutorials.context-provider
176176
hostname: iot-sensors
177177
container_name: fiware-tutorial
178178
networks:
@@ -221,7 +221,7 @@ tagged `fiware/iotagent-ul`. The necessary configuration can be seen below:
221221

222222
```yaml
223223
iot-agent:
224-
image: fiware/iotagent-ul:latest
224+
image: quay.io/fiware/iotagent-ul:latest
225225
hostname: iot-agent
226226
container_name: fiware-iot-agent
227227
depends_on:
@@ -443,7 +443,7 @@ however it has been included here for completeness.
443443
### Provisioning a Sensor
444444

445445
It is common good practice to use URNs following the NGSI-LD
446-
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.06.01_60/gs_CIM009v010601p.pdf) when creating
446+
[specification](https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_cim009v010701p.pdf) when creating
447447
entities. Furthermore, it is easier to understand meaningful names when defining data attributes. These mappings can be
448448
defined by provisioning a device individually.
449449

0 commit comments

Comments
 (0)