Skip to content

feat: store ODRL authorization policy and allow public read#92

Open
mirdono wants to merge 3 commits intodevelopmentfrom
feat/store-odrl-authorisation-policy
Open

feat: store ODRL authorization policy and allow public read#92
mirdono wants to merge 3 commits intodevelopmentfrom
feat/store-odrl-authorisation-policy

Conversation

@mirdono
Copy link
Copy Markdown
Member

@mirdono mirdono commented May 4, 2026

Insert the app's authorization policy into the triplestore and the data publicly readable.

A migration inserts the data into a new graph, http://mu.semte.ch/graphs/odrl-authorization-policy, to keep it separate from other data and to make any future updates easier.
The sparql-parser configuration is extended with entities covering the different resources types in an ODRL authorization policy (i.e. itself). Note, there was already an asset defined for SHACL node shapes, so this was reused.

How to test

  1. Checkout the branch of this PR
  2. Restart the database service to load the updated policy
  3. Restart the migrations service to execute the added migration
  4. Browse to the yasgui frontend's mock-login and login: http://yasgui.localhost/mock-login
  5. Querying for data for ODRL data should give as results the data in the authorization policy. For example, the following query should list all triples for the defined ODRL asset collections.
PREFIX odrl: <http://www.w3.org/ns/odrl/2/>
SELECT DISTINCT ?s ?p ?o
WHERE {
  ?s a odrl:AssetCollection ;
    ?p ?o .
}

Related tickets

  • LBRON-1459

mirdono added 3 commits May 4, 2026 16:13
We will store our ODRL authorization in the triplestore so that it can be
consumed from their by others.  This first extends the policy with the
appropriate entities to allow public read access to the policy data that will be inserted.
Add a migration containing a copy of the ODRL authorization policy, thereby
inserting this into the triplestore.  This migration is just a copy of
sparql-parser's `config.ttl`, with an unnecessary comment removed to avoid
confusion.
@mirdono mirdono added the enhancement New feature or request label May 4, 2026
@mirdono mirdono self-assigned this May 4, 2026
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 this pull request may close these issues.

1 participant