From 952a5a49d5fd078f9a7f01e3bc5a1dd5e8632813 Mon Sep 17 00:00:00 2001 From: Jason Fox Date: Fri, 5 Apr 2024 16:39:28 +0200 Subject: [PATCH] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index c81412a..5f7190b 100644 --- a/README.md +++ b/README.md @@ -73,9 +73,9 @@ An exclusive registration must be fully specified. It always relates to specific - A **redirect** Context Source Registration also specifies that the registered context data is held in a location external to the Context Broker, but potentially multiple distinct redirect registrations can apply at the same time. > [!NOTE] -> **Exclusive** registrations remain as the default operation mode for NGSI-v2 simpler systems. However, since NGSI-v2 uses JSON, -> not JSON-LD, it is unable to function within a federated data space without the concept of `@context`. An NGSI-v2 context broker -> always forms the leaf node in a hierarchy. A comparision between NGSI-v2 and NGSI-LD registrations can be +> **Exclusive** registrations remain as the default operation mode for simpler NGSI-v2-based systems. However, since NGSI-v2 uses JSON - +> not JSON-LD - it is unable to function within a federated data space without the concept of `@context`. An NGSI-v2 context broker +> always forms the leaf node in a broker hierarchy. A comparision between NGSI-v2 and NGSI-LD registrations can be > found [here](https://github.com/FIWARE/tutorials.LD-Subscriptions-Registrations/). > > It remains possible to attach NGSI-v2 data sources into an NGSI-LD data space using a proxy serving a fixed `@context` - this is