Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft JSON-LD context for management API. #4255

Closed
wolf4ood opened this issue Jun 10, 2024 · 0 comments · Fixed by #4256
Closed

Draft JSON-LD context for management API. #4255

wolf4ood opened this issue Jun 10, 2024 · 0 comments · Fixed by #4256
Assignees
Labels
enhancement New feature or request

Comments

@wolf4ood
Copy link
Contributor

Feature Request

For improving the usability of management API we should draft a JSON-LD context for the management API that will be used in ingress/egress for all the requests/responses (catalog response excluded).

Currently we did improved the "usability" of JSON-LD (removing the need of prefixed properties) by using the @vocab in ingress and egress bound to the edc namespace (https://w3id.org/edc/v0.0.1/ns/). That works for removing the all edc relevant properties (even custom one) but it has some limitations.

For example if we want to enforce at JSON-LD level that a property should be an @id or that @container of the property is always a @set, that is not possible only with @vocab.

Also at the current state when dealing with the odrl policies we can use the odrl context in ingress but when reading out the policy definition the odrl policy contains always odrl prefixes.

Which Areas Would Be Affected?

management api

Why Is the Feature Desired?

dev experience

Are there any requirements?

Solution Proposal

Draft an experimental JSON-LD context of management api in a separated experimental extension that will register a new context url and cached file for the edc management api.

@wolf4ood wolf4ood added the enhancement New feature or request label Jun 10, 2024
@wolf4ood wolf4ood self-assigned this Jun 10, 2024
@github-actions github-actions bot added the triage all new issues awaiting classification label Jun 10, 2024
@wolf4ood wolf4ood removed the triage all new issues awaiting classification label Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant