Sender | Message | Time |
---|---|---|
18 Dec 2023 | ||
Yassir AHLA joined the room. | 16:18:36 | |
19 Dec 2023 | ||
Paulo Cabrita changed their display name from pcabrita to Paulo Cabrita. | 14:58:27 | |
22 Dec 2023 | ||
Kai Meinke (deltaDAO AG) | It was great to hear that Talao/Altme, Sphereon and T-Systems will work with the Gaia-X Lab Devs on the OIDC4VP/OIDC4VCI interop profile as the credential exchange and issuance for Gaia-X will now be done initially this way! After two years this removal of fragmentation and towards interoperability will truly be a gamechanger imho. Once the first wallets are able to receive credentials from the wizard I expect a lot of acceleration in 2024. | 12:22:12 |
Kai Meinke (deltaDAO AG) | I wish all of the community members and builders fantastic and refreshing days of digital detox and a great start into the new year! | 12:23:24 |
3 Jan 2024 | ||
lauresha | Wishing the entire community a joyous New Year and hoping for a year filled with success and prosperity ahead! 🍻🎉🚀 With warm regards, GXFS Team | 08:58:05 |
Kai Meinke (deltaDAO AG) | Have a wonderful, healthy, and productive 2024! Lets build. | 10:31:55 |
Kurt Garloff | 🎆 | 15:08:25 |
11 Jan 2024 | ||
lauresha | Dear all, looking forward seeing many of you in our upcoming workshop , In Frankfurt :) For the ones that are not updated: all information, program and registration available here: https://lnkd.in/efP8uBgf | 10:09:53 |
Robert "Robbie" Jost (Dataport ext ARCH) changed their display name from Robert Jost (Dataport) to Robert "Robbie" Jost (Dataport). | 14:10:38 | |
15 Jan 2024 | ||
Yannick Bidois (Cofinity-X) joined the room. | 08:54:49 | |
Yannick Bidois (Cofinity-X) changed their display name from yannickbidois to Yannick Bidois. | 08:55:42 | |
Yannick Bidois (Cofinity-X) changed their display name from Yannick Bidois to Yannick Bidois (Cofinity-X). | 08:56:48 | |
Yannick Bidois (Cofinity-X) | In reply to @lauresha:matrix.orglauresha: Looking forward to this workshop folks! | 08:58:31 |
Yannick Bidois (Cofinity-X) | Anything we could read or learn about beforehand to get the most out of it? | 09:00:04 |
lauresha | In reply to @yannickbidois:matrix.orgPlease download the agenda here :https://www.gxfs.eu/gxfs-tech-workshop-6/, The workshop focus in on TRAIN component- Train repo is here: https://gitlab.eclipse.org/eclipse/xfsc/train , and specification also general overview of TRAIN can be found here: https://gitlab.eclipse.org/eclipse/xfsc/xfsc-spec-2/-/blob/main/Spec2Overview.md?ref_type=heads :) | 15:39:44 |
Yannick Bidois (Cofinity-X) | Thanks lauresha | 16:15:02 |
19 Jan 2024 | ||
Paul Moosmann | Good afternoon XFSC Community, At the beginning of this week Pierre Gronlier shared a set of questions in order to collect some requirements for the Credential Event Service from its potential users. Since I know that some members of this chat are currently involved in discussions regarding the CES (e.g. Fabian Scheidt lenasauermann robertschubert Maharshi Suchaklangec ) I wanted to share the questions here with you: """ #1 Should the service stay publicly open (no onboarding required) and freely accessible for publication (pull/GET)? #2 Should the service stay publicly open (no onboarding required) and freely accessible for consumption (push/POST)? #3 Should the service ensuring consistency of the published information ? (At a given time, should 2 users, independently of their location on Earth and network connection pull the same information from the service.) #4 Should the service always be available (excluding downtime for maintenance), or is it ok for the service to be unavailable for a period of time to synchronise its content ? #5 Should the service be limited to push/pull Gaia-X Compliance credential only or should it support any valid credential ? #6 Insert here additional functional requirements. This work will be tracked here https://gaia-x.atlassian.net/browse/GXTCR-9 A future thread will be triggered for Catalogue functional requirements. Please note: the CES does not transmit actual data in credentials, but only the IDs of credentials. So if anyone has any input regarding current or future requirements for the CES please comment them here, I will then collect all feedback. Thanks! | 14:26:19 |
Paul Moosmann | * Good afternoon XFSC Community, At the beginning of this week Pierre Gronlier shared a set of questions in order to collect some requirements for the Credential Event Service from its potential users. Since I know that some members of this chat are currently involved in discussions regarding the CES (e.g. Fabian Scheidt lenasauermann robertschubert Maharshi Suchaklangec ) I wanted to share the questions here with you: """ #1 Should the service stay publicly open (no onboarding required) and freely accessible for publication (pull/GET)? #2 Should the service stay publicly open (no onboarding required) and freely accessible for consumption (push/POST)? #3 Should the service ensuring consistency of the published information ? (At a given time, should 2 users, independently of their location on Earth and network connection pull the same information from the service.) #4 Should the service always be available (excluding downtime for maintenance), or is it ok for the service to be unavailable for a period of time to synchronise its content ? #5 Should the service be limited to push/pull Gaia-X Compliance credential only or should it support any valid credential ? #6 Insert here additional functional requirements. Please note: the CES does not transmit actual data in credentials, but only the IDs of credentials. So if anyone has any input regarding current or future requirements for the CES please comment them here, I will then collect all feedback. Thanks! | 14:26:38 |
Kai Meinke (deltaDAO AG) | #1 YES, important to grow traction and allow the networking of services. #2 YES, important to grow traction and allow the onboarding of services #3 YES, consensus and integrity is crucial to receive accurate information. #4 YES, availability is important to support adoption. #5 Only Gaia-X compliance credentials, this is not a full catalogue replacement, but a compliance index and register. | 15:31:22 |
Fabian Scheidt | #1 MAYBE. If we decide that CES should not only distribute compliance credentials, I think it's reasonable to add some sort of onboarding to avoid spam. This could be as simple as allowing submission from every issuer who has previously submitted a valid compliance credential. #2 YES, to make it easy to consume contents. #3 MAYBE. Eventual consistency is sufficient. In addition, the order of credential submissions does not matter. #4 YES, with eventual consistency without order, synchonization can happen in the background. #5 NO, it should support other credentials. Following the discussion in Issue 58 of the compliance service, compliance credentials will no longer be able to contain domain-specific additions. However, we do need domain-specific additions in our catalogues and don't want to introduce a secondary distribution mechanims, duplicating the CES functionality (or even replacing it). | 15:49:57 |
Fabian Scheidt | * #1 MAYBE. If we decide that CES should not only distribute compliance credentials, I think it's reasonable to add some sort of onboarding to avoid spam. This could be as simple as allowing submission from every issuer who has previously submitted a valid compliance credential. #2 YES, to make it easy to consume contents. #3 MAYBE. Eventual consistency is sufficient. In addition, the order of credential submissions does not matter. #4 YES, with eventual consistency without order, synchonization can happen in the background. #5 NO, it should support other credentials. Following the discussion in Issue 58 of the compliance service, compliance credentials will no longer be able to contain domain-specific additions. However, we do need domain-specific additions in our catalogues and don't want to introduce a secondary distribution mechanims, duplicating the CES functionality (or even replacing it). #6 We could think about adding some filter mechanism to only receive credentials that are interesting/relevant. | 16:00:46 |
Fabian Scheidt | * #1 MAYBE. If we decide that CES should not only distribute compliance credentials, I think it's reasonable to add some sort of onboarding to avoid spam. This could be as simple as allowing submission from every issuer who has previously submitted a valid compliance credential. #2 YES, to make it easy to consume contents. #3 MAYBE. Eventual consistency is sufficient. In addition, the order of credential submissions does not matter. #4 YES, with eventual consistency without order, synchonization can happen in the background. #5 NO, it should support other credentials. Following the discussion in Issue 58 of the compliance service, compliance credentials will no longer be able to contain domain-specific additions. However, we do need domain-specific additions in our catalogues and don't want to introduce a secondary distribution mechanims, duplicating the CES functionality (or even replacing it). #6 We could think about adding some filter mechanism to only receive credentials that are interesting/relevant. | 16:02:29 |
Fabian Scheidt | * #1 MAYBE. If we decide that CES should not only distribute compliance credentials, I think it's reasonable to add some sort of onboarding to avoid spam. This could be as simple as allowing submission from every issuer who has previously submitted a valid compliance credential. #2 YES, to make it easy to consume contents. #3 MAYBE. Eventual consistency is sufficient. In addition, the order of credential submissions does not matter. #4 YES, with eventual consistency without order, synchonization can happen in the background. #5 NO, it should support other credentials. Following the discussion in Issue 58 of the compliance service, compliance credentials will no longer be able to contain domain-specific additions. However, we do need domain-specific additions in our catalogues and don't want to introduce a secondary distribution mechanims, duplicating the CES functionality (or even replacing it). #6 We could think about adding some filter mechanism to only receive credentials that are interesting/relevant. | 16:02:47 |
Kurt Garloff | #3 and #4 may need some trade-offs if we believe in the CAP theorem. I guess we could live with allowing slightly outdated data to be served should the network connectivity be struggling and thus live with eventual consistency. #1 and #2: I would not want to limit read access (get) except throttling to fend off DoS, but we will eventually have to control write access (put/post). | 19:04:44 |
Kai Meinke (deltaDAO AG) | Which is the reason why DLT introduced write fees (protection) and archive/read only nodes for serving replicated data. | 19:16:16 |
Kurt Garloff | Sounds like a reasonable approach to me. Unless the fees are high... | 19:43:20 |
Kai Meinke (deltaDAO AG) | That is for the data space authority or the federators to decide, or through free auction. But I do not want to derail the topic. We'll be going for fees in Euro & cents now for our network. | 22:28:07 |
22 Jan 2024 | ||
Marcel Ruland (Cofinity-X) | https://app.element.io/#/room/#GXFSTRAIN:matrix.org | 08:36:57 |
lauresha | https://app.element.io/#/room/#GXFSTRAIN:matrix.org | 08:37:01 |
Marcel Ruland (Cofinity-X) | * Workshop room link: https://app.element.io/#/room/#GXFSTRAIN:matrix.org | 08:37:11 |