@@ -26,10 +26,10 @@ The tutorial uses [cUrl](https://ec.haxx.se/) commands throughout, but is also a
26
26
- このチュートリアルは[ 日本語] ( README.ja.md ) でもご覧いただけます。
27
27
28
28
> [ !NOTE]
29
- > This tutorial is designed for ** NGSI-v2 ** developers looking to switch or upgrade systems to
30
- > ** NGSI-LD ** , if you are building a linked data system from scratch or you are not already familiar with ** NGSI-v2 ** then
31
- > it is recommmended that you look directly at the
32
- > [ NGSI-LD developers tutorial] ( https://ngsi-ld-tutorials.readthedocs.io/ ) documentation.
29
+ >
30
+ > This tutorial is designed for ** NGSI-v2 ** developers looking to switch or upgrade systems to ** NGSI-LD ** , if you are
31
+ > building a linked data system from scratch or you are not already familiar with ** NGSI-v2 ** then it is recommmended
32
+ > that you look directly at the [ NGSI-LD developers tutorial] ( https://ngsi-ld-tutorials.readthedocs.io/ ) documentation.
33
33
34
34
## Contents
35
35
@@ -495,12 +495,11 @@ According to the [defined data model](https://fiware.github.io/tutorials.Step-by
495
495
- The `address` attribute has the FQN `http://schema.org/address`
496
496
- The `category` attribute has the FQN `https://uri.fiware.org/ns/data-models#category`
497
497
498
- `type` and `location` are defined in the NGSI-LD Core Context :
498
+ `type` and `location` are defined in the NGSI-LD Core Context :
499
499
[`https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.6.jsonld`](https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.6.jsonld).
500
500
The other attributes are defined using the Tutorial's own Context :
501
- [`http://context/user-context.jsonld`](./data-models/user-context.jsonld).
502
- Both `category` and `address` are _common_ attributes the definitions of which are brought in from the FIWARE data
503
- models and `schema.org` respectively.
501
+ [`http://context/user-context.jsonld`](./data-models/user-context.jsonld). Both `category` and `address` are _common_
502
+ attributes the definitions of which are brought in from the FIWARE data models and `schema.org` respectively.
504
503
505
504
# ## Display all Products
506
505
@@ -819,8 +818,8 @@ Click on the image above to watch a video JSON-LD expansion and compaction with
819
818
820
819
# ## What other relationship information can be obtained from the data model?
821
820
822
- More information about `Relationships` can be obtained from the `@graph` of the linked data model had it been supplied. For `locatedIn` the
823
- relevant section definition is as follows :
821
+ More information about `Relationships` can be obtained from the `@graph` of the linked data model had it been supplied.
822
+ For `locatedIn` the relevant section definition is as follows :
824
823
825
824
` ` ` json
826
825
{
@@ -852,7 +851,7 @@ This example returns the `locatedIn` value associated with a given `Shelf` unit.
852
851
853
852
If the `id` and `type` of a data entity are known, a specific field can be requested by using the `attrs` parameter.
854
853
855
- # ### 7️⃣ Request:
854
+ # ### 7️⃣ Request:
856
855
857
856
` ` ` console
858
857
curl -G -X GET \
@@ -878,7 +877,7 @@ curl -G -X GET \
878
877
This example returns the `locatedIn` URNs of all **Shelf** entities found within `urn:ngsi-ld:Building:store001`. This
879
878
is purely an instance of using the `q` parameter to filter on attribute value
880
879
881
- # ### 8️⃣ Request:
880
+ # ### 8️⃣ Request:
882
881
883
882
` ` ` console
884
883
curl -G -X GET \
0 commit comments