curl -i -X PUT -H "Authorization: yourRepoApiKey" -H "Content-Type: text/turtle" --data @catalogue_jena_1.ttl localhost:8081/catalogues/jena_test_1

curl -i -X GET http://localhost:8081/catalogues

curl -i -X PUT -H "Authorization: yourRepoApiKey" -H "Content-Type: application/rdf+xml" --data @dataset.xml "localhost:8081/datasets?catalogue=jena_test_1&id=b3b8fcf0-e4d3-400e-a824-b89c3c388238"

curl -i -X GET -H "Authorization: yourRepoApiKey" -H "Content-Type: application/rdf+xml" "localhost:8081/datasets?catalogue=jena_test_1"

curl -i -X GET -H "Authorization: yourRepoApiKey" -H "Content-Type: application/rdf+xml" "localhost:8081/datasets/b3b8fcf0-e4d3-400e-a824-b89c3c388238?catalogue=jena_test_1"
curl -i -X GET -H "Authorization: yourRepoApiKey" "localhost:8081/datasets/b3b8fcf0-e4d3-400e-a824-b89c3c388238.rdf?catalogue=jena_test_1"

http://localhost:8081/datasets/b3b8fcf0-e4d3-400e-a824-b89c3c388238.rdf?catalogue=jena_test_1

curl -i -X DELETE -H "Authorization: yourRepoApiKey" "localhost:8081/datasets/b3b8fcf0-e4d3-400e-a824-b89c3c388238?catalogue=jena_test_1"

catalogue_jena_1.ttl

@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dc: <http://purl.org/dc/terms/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

<http://opendata.jena.de/id/catalogue/jens_test_catalogue_1>
  a dcat:Catalog ;
  dc:language <http://publications.europa.eu/resource/authority/language/DEU> ;
  dc:title "JenaTestCatalogue"@de ;
  dc:description "JenaTestCatalogueDescription"@de ;
  dc:type "dcat-ap"^^xsd:string .

As mentioned in #8 (comment), this is one of the two remaining issues encountered during recent integration work, i.e.:

Unsatisfied references in PiveauAdapter and PiveauRestConnector components.

Screenshots attached.

If two Models register a GraphQLQueryProvider only the first one is used.

During integration work done as part of #8, I applied a temporary solution for org.gecko.emf.persistence.jdbc bundle in order to force it to accept latest version of org.gecko.emf.utilities, as its import accepted only version up to 2.x, and latest version is 2.2.0.

This needs to be addressed in Gecko Persistence project itself directly, new release of that project created, and only then will it be possible to update these Gecko Persistence dependencies in MDO project and remove org.gecko.emf.persistence.jdbc from its local repository.

Create ecore models for IBIS services:

• GNSSLocationService
• CustomerInformationService

Check whether is possible with keycloak to login through basic auth flow and get back the jwt token programatically