Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
jason-fox authored Apr 5, 2024
1 parent 789c6c8 commit d2b6ee6
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,9 +73,13 @@ 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 are the default operation mode for NGSI-v2 context brokers. NGSI-v2 is JSON based (not JSON-LD)
> and an NGSI-v2 context broker is always a leaf node in a hierarchy. A compare and contrast between NGSI-v2 and NGSI-LD
> registrations can be found [here](https://github.com/FIWARE/tutorials.LD-Subscriptions-Registrations/)
> **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
> 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
> described in more detail [here](https://github.com/FIWARE/tutorials.Linked-Data/tree/NGSI-LD)
## Entities within a Farm Information Management System

Expand Down

0 comments on commit d2b6ee6

Please sign in to comment.