Sender | Message | Time |
---|---|---|
26 Jan 2024 | ||
urtza | Redacted or Malformed Event | 10:49:09 |
urtza | In reply to @maharshisuchak:matrix.orgThanks for your answer. By not attending the workshop and not deploying the entire infrastructure, I collected the information about exercise 1 directly and cloned the main branch. I could see that it seemed strange to me that the code was from 9 months ago and the creation of the participant was not entirely correct, so I started to modify the code and obtain the VP of the participant correctly but I was missing the call to the CES. Seeing your answer, I already entered another directory of the "Cloud setup" workshop and via the instructions on cloning to the "gaia-x-update" branch, in that code I already see the call to CES. Sorry for the inconvenience caused and thank you for the information received in your response. | 10:50:47 |
Maharshi Suchak | glad to know you could see the updates. Always happy to help :-) | 12:16:27 |
Tim | Hello everyone, we've been facing persistent issues with the OCM and its connections to the PostgreSQL database. Our deployments span various infrastructures and involve different PostgreSQL versions. What's particularly perplexing is that we can successfully set up the OCM, and it typically operates smoothly for 1-3 days—handling connections, issuing VCs, and verification—only to suddenly cease functioning. This occurs without any changes in configuration. The root cause appears to be an abrupt loss of connection or access rights to the database. Most of our instances utilize a managed database, and unfortunately, we're unable to access the logs there. The puzzling aspect is the brief period during which everything works before coming to a halt. To address these issues, our usual remediation steps involve killing all OCM-related pods, clearing the database (including recreating schemas), and then continuing until the problem reoccurs. Any insights into what might be causing these errors or suggestions for a more effective resolution would be greatly appreciated. Of course, if anyone else has faced or is currently facing similar problems, we would love to hear about your experiences and solutions. Have a nice weekend. | 13:43:58 |
27 Jan 2024 | ||
JustinAnthony | It could be that the database service used is not a "Reserved instance" or it has reached the IOPS limit (3200 max for example in Azure). Logs should be available at the service website "activity log" | 13:15:08 |
schulzest | Tim: in the existing OCM v1, is a gap in the Storage Handling of Hyperledger Indy which results in inconsistencies from time to time. This is solved now in spec phase two in v2, please cross check this version to solve that long term | 21:17:46 |
29 Jan 2024 | ||
Tim | thanks JustinAnthony we really have very very few transactions, and unfortunately, logs are at a very low level (basically no important information) from our service provider | 09:31:28 |
Tim | * thanks JustinAnthony we really have very very few transactions, and unfortunately, logs are at a very low level (basically no important information) from our service provider, and it appears to happen as well on a local instance (really just for testing, very limited) | 09:32:01 |
Tim | thanks schulzest , do you have by chance a reference ticket from Indy for the issue to dig deeper? Is it reallistic to happen every few days? | 09:33:21 |
1 Feb 2024 | ||
marc.b | Hi everyone, project MERLOT created a Java-Spring based library to simplify interactions with the XFSC federated catalog as well as credential creation/signature: https://github.com/merlot-education/gxfscatalog-library . I think this might be particularly interesting for other Gaia-X related projects that might just be starting out with using the catalog. | 12:53:40 |
Kai Meinke (deltaDAO AG) | I am not sure about the linked credential models linked in the repo description. I have seen the credential schemata with gax: in the linked library which would not work with the shapes in Gaia-X Digital Clearing Houses, see: https://registry.lab.gaia-x.eu/development/api/trusted-shape-registry/v1/shapes/jsonld/trustframework# Maybe I am looking at the wrong sources here? https://github.com/merlot-education/gxfscatalog-library/tree/main/src/main/java/eu/merloteducation/gxfscataloglibrary/models/selfdescriptions/gax | 18:53:44 |
Kai Meinke (deltaDAO AG) | For example: gax-trust-framework:registrationNumber does not match the current framework. The registration number is given through a credential, not in the participant VC. | 18:54:52 |
Kai Meinke (deltaDAO AG) | There is also no "legalForm" in Gaia-X participant credentials. | 18:55:35 |
Kai Meinke (deltaDAO AG) | Might be I am looking at the wrong source here which could be outdated, so I am curious. | 18:56:15 |
Marcel Louwers (Marispace-X) | Hi, who of the funded projects did also receive a letter regarding the GXFS implementations and architecture document 23.10 as part of the "Nebenbestimmungen" ? | 21:06:49 |
2 Feb 2024 | ||
marc.b | Indeed the provided models are based on an older version of the schemas which can be found at https://gitlab.com/gaia-x/technical-committee/service-characteristics/-/tree/v22.10 . This was done in this way since the MERLOT project started out with this version and hasn't changed to the newer "gx:" schemas due to previous incompatibilities with the catalog itself. | 09:22:35 |
marc.b | There is however nothing that would stop someone from replacing the provided models with models based on the new schemas if this is required for their project :) | 09:23:35 |
marc.b | * Indeed the provided models are based on an older version of the schemas which can be found at https://gitlab.com/gaia-x/technical-committee/service-characteristics/-/tree/v22.10 . This was done in this way since the MERLOT project started out with this version and hasn't changed to the newer "gx:" schemas due to previous incompatibilities with the sd-creation-wizard and the catalog itself. | 09:24:19 |
marc.b | * Indeed the provided models are based on an older version of the schemas which can be found at https://gitlab.com/gaia-x/technical-committee/service-characteristics/-/tree/v22.10 . This was done in this way since the MERLOT project started out with this version and hasn't changed to the newer "gx:" schemas so far due to previous incompatibilities with the sd-creation-wizard and the catalog itself. | 09:27:10 |
Kai Meinke (deltaDAO AG) | Thank you for the explanation. Totally understandable. Just be aware that gax is not used in Gaia-X at all and can't be used for semantic interoperability with other Gaia-X projects. If this is desired the mentioned changes need to be made. Some projects did this very successfully with the XFSC components already so nobody needs to start from scratch. | 11:41:55 |
Michael Ziegelmeir | All of you should have. If you have questions regarding the update please reach out directly to BNetzA or acatech | 11:59:42 |
6 Feb 2024 | ||
Paul Moosmann | Dear XFSC Community, for anyone interested in scientific conttibutions I would like to forward this information regarding an upcoming workshop on the topic of Semantics in Dataspaces: CFP: The 2nd International Workshop on Semantics in Dataspaces (SDS 2024) @ESWC24, May 26-27 in Crete, Greece You are cordially invited to contribute to our upcoming workshop, The Second International Workshop on Semantics in Dataspaces (SDS 2024), MAY 26 or 27, 2024, to be held in conjunction with the ESWC24 in Crete, Greece. https://dbis.rwth-aachen.de/SDS24/ | 09:56:16 |
Paul Moosmann | Regarding the discussion "gx" vs "gax": Please remember that these are only prefixes and the prefix as such shouldn't matter. What is important is the namespace that is defined behind the prefix. | 10:53:19 |
Paul Moosmann | * Regarding the discussion "gx" vs "gax": Please remember that these are only prefixes and the prefix as such shouldn't matter. What is important is the URI that is defined by the prefix. | 10:54:54 |
Kai Meinke (deltaDAO AG) | Sure, but they also hint towards some legacy semantics. Just used this as abbreviation. | 18:30:38 |
7 Feb 2024 | ||
Giovanni Coppa joined the room. | 10:33:51 | |
29 Feb 2024 | ||
lauresha | Dear Community, We warmly invite you to Save the Date for XFSC Tech Workshop #7 taking place on 12 June 2024 at Institut für digitale Zukunftstechnologien e.V. in Hürth. The XFSC Tech Workshop wil showcast the latest advancements in XFSC Specification Phase 2. This one-day on-site event aims to present an exclusive look at the XFSC components, new features, and the implementation of XFSC Specification Phase 2. Attendees can expect to delve into the innovative developments of Spec 2, gaining valuable insights and a firsthand impression of the groundbreaking components. Join us as we unravel the future of XFSC technology and explore the next frontier in component development. You want to be part of the workshop? Feel free to register below! https://www.gxfs.eu/xfsc-tech-workshop-7/ | 09:55:38 |
Maharshi Suchak | Dear community, I won't be able to join the call today. However, here is the update on the task we are working on. We have completed the analysis and taken the code of validating the SHAPES against SHACL however, there is some issue due to updates from Gaia-X which is not allowing us successfully complete the validation. Hopefully by next week we will have an update on this. Thank you | 12:03:16 |
6 Mar 2024 | ||
@gioco:matrix.org joined the room. | 20:54:51 | |
15 Mar 2024 | ||
lauresha | Dear Community, I hope all of you are doing well. We're excited to announce that Gaia-X Tech-X and Hackathon #7 are scheduled to take place on Thursday, May 23rd, and Friday, May 24th at the European Convention Center in Luxembourg. We warmly invite your participation. If you have any ideas or topics related to XFSC and Gaia-X that you'd like to contribute, please don't hesitate to reach out to me via email at lauresha.memeti@eco.de. Together, we can collaborate on developing proposals. For deadlines and detailed instructions, kindly refer to the following link: https://gitlab.com/gaia-x/gaia-x-community/gx-hackathon/tech-x-2024-and-hackathon-7/-/wikis/home Looking forward to your involvement! Best regards, Lauresha | 08:36:23 |