-
**Describe the bug**
Registering a resource that has been created by bootstrapping fails with the following error:
```
{
"reason": {
"properties": null,
"@id": "https://w3id.org/idsa…
-
**Describe the bug**
Broker search shows this:
**To Reproduce**
When you inpu…
-
A shared resource can be shared simultaneously to a list of data consumer connectors without depositing additional resources.
Therefore the user should be able to add multiple connector IDs to the po…
-
When using v6.0.0:
1-DataApp A linked to Connector A: creates a resource offer with contract, rule, representation, and one artifact.
2-DataApp B linked to Connector B: DataApp B asks Connector B to…
-
This repository needs a LICENSE file to clarify conditions for re-use.
My own suggestion is always an MIT or Apache 2 license, but the use of IDSA components may require a GPL license. In any case,…
-
Hi,
the equals method for Constraints does not seem to work. I had a quick look and believe the problem lies with the RdfResource. It does not override the equals method.
Here a simple setup:
```…
-
Currently a Connector can only register to one DAPS, hence only be participant at one dataspace. However it would be essential to be able to participate with one connector multiple dataspaces, hence i…
wjost updated
3 years ago
-
Tried to register the DSC at the IDS broker:
POST https://localhost:8080/api/ids/connector/update?recipient=https://broker.ids.isst.fraunhofer.de/infrastructure
API call responds with error: 500 - A…
-
We have used the docker-compose pull and as we are using a local DAPS we have used mvn clean package to create a new local broker-core image.
These gives us a build failure when using the last 4.2.8-…
-
Hi,
when we try too deserialize a permission like following this does not result in a permission but only in the contained Post Duty.
Changing from Rule.class to Permission.class does fix the probl…