Why are Identity API payloads not in JSON-LD format? #697
Answered
by
wolf4ood
thomasrutger
asked this question in
Q&A
-
|
I've noticed that the Identity API doesn't use JSON-LD — neither in its request bodies nor in its responses. This stands out because the Management API of the Control Plane does use JSON-LD consistently for both requests and responses. Is there a particular reason JSON-LD was not adopted for the Identity API? |
Beta Was this translation helpful? Give feedback.
Answered by
wolf4ood
Apr 2, 2025
Replies: 1 comment
-
|
the main reason is extensibility and adoption of JSON-LD technologies in the control plane like Asset extensibility, DCat, DSP and ODRL. In the Identity API there is need of such extensibility and integrations |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
thomasrutger
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @thomasrutger
the main reason is extensibility and adoption of JSON-LD technologies in the control plane like Asset extensibility, DCat, DSP and ODRL.
In the Identity API there is need of such extensibility and integrations