publish the ODRL parts of dcat descriptions on ldes, also publish the mu-auth config on ldes

[Rahien]

Description

This publishes the ODRL parts of dcat descriptions and the mu-auth config on the ldes feed.

The ODRL policies connected to the DCAT datasets are essential if users want to know what is allowed/required regarding the datasets they find in the federating catalog.

Publishing the mu-auth config is more a nice-to-have thing, for people who want even more details on what they can or can't do with the sparql endpoints published by the decide stack.

How to test

You can test this by making use of the dcat federation setup: https://github.com/lblod/app-decide-federating-catalog.

• clone the federating dcat app
• on the dev server, checkout this branch and republish the dcat feed
• locally, in the federating dcat app, use this config for the ldes-client:

const config = {
  endpoints: [
    {
      name: 'public',
      LDES_BASE: 'https://ds.decide-dev.s.redhost.be/ldes/public/',
      FIRST_PAGE: 'https://ds.decide-dev.s.redhost.be/ldes/public/1',
      STATUS_GRAPH: 'http://mu.semte.ch/graphs/ldes/decide-public-status',
      TARGET_GRAPH: 'http://mu.semte.ch/graphs/ldes/decide-public',
      BATCH_GRAPH: 'http://mu.semte.ch/graphs/ldes/decide-public-batch',
    },
    {
      name: 'public-test',
      LDES_BASE: 'https://ds.decide.lblod.info/ldes/public/',
      FIRST_PAGE: 'https://ds.decide.lblod.info/ldes/public/1',
      STATUS_GRAPH: 'http://mu.semte.ch/graphs/ldes/decide-public-test-status',
      TARGET_GRAPH: 'http://mu.semte.ch/graphs/ldes/decide-public-test',
      BATCH_GRAPH: 'http://mu.semte.ch/graphs/ldes/decide-public-test-batch',
    },
  ],
};

export default config;

This will harvest both the dev and test ldes streams

• wait until the federation is done, you can tell by the new ttl files appearing in your federated ldes-feed/public directory
• then run the following queries to verify that the content made it to your federating catalog:

  PREFIX odrl: <http://www.w3.org/ns/odrl/2/>
  SELECT * WHERE {
    graph ?g {
      ?s a odrl:Permission.
    }
  } order by ?s

This should only show items in your decide-public graph as test doesn't publish odrl policies yet

  PREFIX dcat: <http://www.w3.org/ns/dcat#>
  SELECT * WHERE {
    graph ?g {
      ?s a dcat:Dataset.
    }
  } order by ?s

This should show the datasets in both target graphs

• verify the contents of the stream on dev, it should show all odrl types/properties attached to the dcat instances and all items in the mu-auth config
• verify the dcat interface, it shouldn't show any duplicates as the data from dev and test is the same