| 4 Dec 2023 |
|  Roberto García (UdL) changed their display name from Roberto Garcíarogargon to Roberto García. | 23:28:38 |
| Roberto García (UdL) changed their display name from Roberto García to Roberto García (UdL). | 23:31:09 |
| 5 Dec 2023 |
 langec | Hi Maharshi Suchak Fabian Scheidt and other interested developers, I documented the discussion on whether or not the Catalogue should skip certain validation steps (e.g., schema validation) in the presence of a compliance credential at https://gitlab.eclipse.org/eclipse/xfsc/cat/fc-service/-/issues/204 – feel free to add to the discussion there. | 07:54:37 |
 Fabian Scheidt | Thank you :)
As mentioned: I think this is step 2. We should first get integration with compliance and CES working and then work on optimizations. | 07:56:20 |
| langec | Thanks Fabian Scheidt for pointing out this – quoting you: "we have built a little visualization for our Catalogue contents. It uses OpenCypher
https://federated-catalog-viewer.gaiax4roms.hotsprings.io/" | 07:56:22 |
 schulzest | Hello together,
I would like to inform you that I have tagged now the OCM-Engine to v1 in eclipse (https://gitlab.eclipse.org/eclipse/xfsc/ocm/ocm-engine/-/tree/v1?ref_type=tags) to prepare the merges of new features from spec phase 2. This includes architectural changes, new features etc. which can lead to broken changes. Be aware, that you should refer for workshops and experiments to v1, otherwise you can have unexpected behavior in the time of development. If you see any blockers, concerns etc. Please inform me or Lauresha. The merge will begin Thursday.
Regards,
Steffen
| 09:59:14 |
| Fabian Scheidt | Thanks for sharing :)
If I recall correctly, the folks from Gaia-X 4 PLC-AAD have a way more sophisticated implementation. | 10:00:40 |
| 6 Dec 2023 |
 robertschubert | Totally agree, also there should be an answer regarding domain specific types as described in https://gitlab.com/gaia-x/lab/compliance/gx-compliance/-/issues/58 | 10:24:46 |
| 7 Dec 2023 |
| langec | Hi Ewann Gavard (Gaia-X AISBL) and colleagues, what is the right way of obtaining the SHACL shape for a specific class from the Gaia-X Registry? I tried this, but it didn't work:
- https://registry.gaia-x.eu/v1/api/trusted-shape-registry/v1/shapes/implemented told me, e.g., "DataResource"
- So, I tried https://registry.gaia-x.eu/v1/api/trusted-shape-registry/v1/shapes/jsonld/DataResource, but then got a 404.
In the method GET .../shapes/jsonld/{key}, what is "key" supposed to look like?
| 08:15:24 |
 Ewann Gavard (Gaia-X AISBL) | In reply to @langec:matrix.org
Hi Ewann Gavard (Gaia-X AISBL) and colleagues, what is the right way of obtaining the SHACL shape for a specific class from the Gaia-X Registry? I tried this, but it didn't work:
- https://registry.gaia-x.eu/v1/api/trusted-shape-registry/v1/shapes/implemented told me, e.g., "DataResource"
- So, I tried https://registry.gaia-x.eu/v1/api/trusted-shape-registry/v1/shapes/jsonld/DataResource, but then got a 404.
In the method GET .../shapes/jsonld/{key}, what is "key" supposed to look like?
Hello Christoph,
Everything is in a single shape, trustframework.
You can retrieve it with this like https://registry.gaia-x.eu/v1/api/trusted-shape-registry/v1/shapes/trustframework
The /jsonld is just used by the Shacl engine and only returns the shape in jsonLD (should be the jsonld context but we did not have it properly made at the time) | 08:17:17 |
| 8 Dec 2023 |
| robertschubert | Hi langec and Fabian Scheidt ,
yes, we created a simple catalog browser which connects to the XFSC federated catalog running also in our infrastructure:
https://metadatasearch.gxfs.gx4fm.org/
There we are also using cypher queries.
Moreover we started to implement an extention of the XFSC portal (https://gitlab.eclipse.org/eclipse/xfsc/por) to connect to the XFSC catalogue. The react code base of the portal seemed to be a solid baseline for us. Once ready I will be able to show it in a community meeting. | 07:45:55 |
|  Fabian Gast joined the room. | 09:04:38 |
|  Andrew Kenworthy joined the room. | 11:32:07 |
 lenasauermann | Hi everyone,
i order to be able to load Self Description in the FC that are compatible with the Gaia-X Compliance Service/Wizard/etc., I tried to add the gx ontology with the miminum base classes Particpant, DataResource and ServiceOffering to the FC by making them a subclass of the matching classes in gax-core ontology. For Participant and ServiceOffering this is working so far. But for gx:DataResource as a subclass of gax-core:Resource, I get the following error:
{
"code": "conflict_error",
"message": "Schema redefines existing terms"
}
What might be the problem here?
| 15:52:39 |
 Denis Sukhoroslov | it means gx:DataResource is already defined somewhere | 15:55:47 |
| lenasauermann | But it's not... Or at least I don't see it in the response of /schemas/latest?type=ontology | 16:06:19 |
| Denis Sukhoroslov | then please open an issue in gitlab. | 16:10:51 |
| Denis Sukhoroslov | please attach your custom schema and explain your steps in detail | 16:12:08 |
| Denis Sukhoroslov | but DataResource is defined in the gax-trust-framework | 16:23:21 |
| lenasauermann | Yeah, but not with the prefix gx | 16:27:17 |
| lenasauermann | What I just saw:
We use as a base for our gx shapes this https://registry.lab.gaia-x.eu/development/api/trusted-shape-registry/v1/shapes/jsonld/trustframework#
Here Particpant and ServiceOffering have for the shape the naming gx:ParticipantShape and gx:ServiceOfferingShape. But the shape DataResource is just named gx:DataResource... might tthat cause any problemy even though it's a shape and not an ontology | 16:29:16 |
| Denis Sukhoroslov | probably yes. I'm not an expert in schemas. langec , Paul Moosmann could you have a look also? | 16:32:04 |
| lenasauermann | Deleted the shape and now I can upload the ontology. So that was the issue. Then I should make a issue for the registry to get that fixed there | 16:39:28 |
| 11 Dec 2023 |
| Ewann Gavard (Gaia-X AISBL) | Hello lenasauermann AFAIK, there's not requirement for a shape to contain the word Shape in its id. Furthermore, the shape you mention is enforced by the js-shacl engine without any inconvenience. And I personally tested with pyshacl and this internal ID without Shape causes no trouble. Maybe the problem lies in the FC project implementation you mention ? | 14:56:34 |
| lenasauermann | Hi Ewann Gavard (Gaia-X AISBL) That's true: you don't need the word Shape. But besides the SHACL-Shape, the FC also needs the ontology for a specific class and it seems like that the FC can't have the same named definition gx:DataResource in the shapes and the ontology | 15:01:42 |
| 12 Dec 2023 |
| Denis Sukhoroslov | FYI: finally, Harbor registry was configured for FC project. The latest version can be pooled as node-654e3bca7fbeeed18f81d7c7.ps-xaas.io/catalogue/fc-service-server:1.3.0-SNAPSHOT | 06:33:25 |
| Denis Sukhoroslov | * FYI: finally, Harbor registry was configured for FC project. The latest version can be pulled as node-654e3bca7fbeeed18f81d7c7.ps-xaas.io/catalogue/fc-service-server:1.3.0-SNAPSHOT | 06:48:59 |
|  Kurt Garloff changed their display name from Kurt Garloff to Kurt Garloff (SCS). | 08:37:28 |
|  yukai-sun joined the room. | 10:28:29 |
|  max-ffstudios joined the room. | 13:17:34 |
