- Introduction
- Using the final setup
- Building and running
- The localhost setup case
- Prerequisites for the localhost setup case
- Environment variables for the localhost setup case
- Building the localhost setup case
- Running the localhost setup case
- Adding pod contents for the additional use cases to the localhost setup case
- Using the localhost setup case
- Stopping the localhost setup case
- The public Docker based setup case
- Prerequisites for the public Docker based setup case
- Environment variables for the public Docker based setup case
- Building the public Docker based setup case
- Running the public Docker based setup case
- Adding pod contents for the additional use cases to the public Docker based setup case
- Using the public Docker based setup case
- Bonus: local Generic Data Viewer for querying public pods
- Stopping the public Docker based setup case
- The localhost setup case
- Other documentation resources
This repository contains the implementation of an Open Circularity Platform as part of the Onto-DESIDE Horizon Europe project.
We demonstrate the Open Circularity Platform through some example use cases:
- example use case within the Construction domain;
- example use case within the Textile domain;
- some additional use cases:
- extended example use case within the Textile domain, with data using the CEON ontology and with verifiable credentials;
- evaluation use cases within different domains.
This repository supports different setup cases. Some are only valid during development. The final and publicly available setup of the Open Circularity Platform relies on Docker containers and Docker Compose and illustrates the decentralized nature of the Solid-based data sharing platform.
Within the platform, we have set up:
- multiple data providers each publishing their data behind a secure access layer using Solid pods,
- a Generic Data Viewer providing an easy to use Web UI to execute queries on these Solid pods,
- a Comunica Webclient providing a more technical Web UI to execute similar or user-modified queries on these Solid pods.
During the setup-flow, Solid pods are created and prefilled with example WebIDs and other Resource Description Framework (RDF) formatted data.
During the usage-flow, an end user navigates to one of the Web UIs to query the data.
The final setup is available online and needs no further action prior to usage.
To use this Generic Data Viewer, navigate to https://onto-deside.ilabt.imec.be/viewer/.
The list of predefined queries is shown in expandible groups at the left side.
Some queries may require you to login as one of the actors, described in the use cases.
That is because read permissions to resources may be restricted to specific actors, as can be seen in the overview of permissions.
Find actors' email addresses and passwords in the overview of actors' WebIDs, emails and passwords.
To login, click on the icon in the top right.
To execute a query, click on it in the dashboard.
This screenshot shows the result of a query about Texon's components and materials.
The result shown was obtained when logged in to identity provider https://onto-deside.ilabt.imec.be/css5 as [email protected].
This Comunica Webclient is intended for viewing low level details of the results of some predefined queries or for experimenting with new queries derived from these predefined queries.
To use this Comunica Webclient, navigate to https://onto-deside.ilabt.imec.be/webclient/.
Some predefined queries are available in the Type or pick a query: field.
The above remark about queries vs. logging in applies here too.
The login dialogue is available after clicking the Settings asterisk (top right.)
This screenshot demonstrates querying Lindner Group's products. The result shown was obtained when logged in to identity provider https://onto-deside.ilabt.imec.be/css1 as [email protected].
All predefined queries are configured to work on a predefined list of datasources (Solid pods in our case). Selecting a query preloads the Choose datasources: dialogue.
It is possible to add your own Solid pod to the list, as illustrated here ("any additional Solid pod").
If you don't have a pod yet:
- you can obtain one following the Solid project instructions
- or try out Solid pods with the SolidLab Pod Playground (be warned for this one: "The pods and data on the instance is removed daily and there are no guarantees regarding uptime.").
To add an external Solid pod to the list of datasources in the Comunica Webclient, place the cursor in the field 'Choose datasources'.
Next type the baseURL of an additional Solid pod and confirm with the <Return> key.
The additional datasource will be taken into account when the query is executed, and the datasource will be available as a preset datasource from here on.
We split up this section for the different setup cases.
Unless specified otherwise, execute all commands below from a bash shell in the repository root.
The different setup cases depend on common files.
Some common files read environment variables, that need to be set upfront by sourcing the environment variables files.
Some files cannot read environment variables. In these cases derived files are created from common templates.
- a bash shell
- Node >= 18 with npm
- yarn classic
- Java version 17, e.g. 17.0.10-tem
Execute this command in any terminal window, before executing any other command in the remainder of this section:
source env-localhostBefore continuing, make sure the result of a previous build isn't running. See Stopping the localhost setup case.
Next, execute:
# install node dependencies
yarn install
# all further build actions
./scripts/setup/finalize-setup.shRun with new pod contents (mandatory for first run):
./scripts/local-run/start-csss.shRe-run with existing pod contents (requires a previous run and stop):
./scripts/local-run/start-csss.sh -rThe commands above start the pods on the localhost in the background and wait until they are all ready (listening). This takes some time to complete.
The pods log files can be consulted at ./local-run/*.log.
The pods data can be viewed at ./local-run/data/css*/.
This assumes the following additional prerequisites to the localhost setup case:
- Docker Engine was installed.
- Docker host networking is available. See also here.
Execute:
./scripts/stuff-pods/stuff-pods.shUsing the localhost setup case is similar to using the final setup, with the following differences:
- The included Generic Data Viewer:
-
needs to be started as follows in a separate terminal window:
cd ../applied-in-architecture-generic-data-viewer-react-admin/main npm run dev -
and can be used at the localhost port reported in the output of above command.
-
- The included Comunica Webclient is not available here.
./scripts/local-run/stop-csss.sh- a bash shell
- Node >= 18 with npm
- yarn classic
- Java version 17, e.g. 17.0.10-tem
- Docker Engine and Docker Compose
- Depending on your platform, different installation guides are available from the above links.
Execute this command in any terminal window, before executing any other command in the remainder of this section:
source env-docker-publicBefore continuing, make sure the result of a previous build isn't running. See Stopping the public Docker based setup case.
Next, execute:
# install node dependencies
yarn install
# all further build actions
./scripts/setup/finalize-setup.shRun with new pod contents (mandatory for first run):
docker compose --profile backend --profile frontend --profile extra-pod up --waitRe-run with existing pod contents (requires a previous run and stop):
docker compose -f docker-compose-public-restart.yml --profile backend --profile frontend --profile extra-pod up --waitThe commands above start all services in a Docker environment and and wait until they are all ready (listening). This takes some time to complete.
Optional: if you're interested in what's happening while these commands execute, you may open a new terminal window and in it, execute:
docker compose --profile backend --profile frontend --profile extra-pod logs -fThe following command may be executed on the server or on any other computer fulfilling the prerequisites and having access to the public pods, if all above steps where executed before.
Execute:
./scripts/stuff-pods/stuff-pods.shUsage was explained already above in using the final setup.
There is one pleasant side effect of building the public Docker based setup case: the Generic Data Viewer described in Running the localhost setup case is also available here at the localhost. This time however it addresses the public pods! This is very convenient for further query experiments on the data in the public pods... For more info, see The modified Generic Data Viewer.
docker compose --profile backend --profile frontend --profile extra-pod down -t 0