Skip to content

XFSC Catalogue Developers' Community Call Meetings

Jump to bottom
Christoph Lange edited this page Mar 26, 2026 · 28 revisions

2026-03-26

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #45 Neo4j dependency investigation progress
    • New issues (check activity log since last meeting)
      • none
    • Open Pull Requests
    • Closed Pull Requests
    • AOB
      • How to get the committer role?
        • Paul explained the process, unclear who initiates it (ECO or Christoph/Paul)
          • Update: Christoph initiated the process; any committer can do it

2026-03-12

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #45 Neo4j dependency investigation progress
        • Andreas Weiss thinks Neo4j dependency needs to be removed
          • This is not part of the SRS, so MSG will not implement this
    • New issues (check activity log since last meeting)
      • none
    • Open Pull Requests
      • #74 Enhancement CAT-FR-GD-06 - query validation
        • Reject wrong-language queries (SPARQL on Neo4j, openCypher on Fuseki)
      • #75 Bugfix for signature verification + add trust server mock (test infrastructure)
        • bumped uni-resolver-client to new version
          • disable signature checks by default
      • #76 Fix: replace wrong default parameter for schema verification
        • fixed wrong default value in openapi.yml, which caused non-requested schema verifications
      • #77 Enhancement CAT-FR-GD-07 - switchable graph db
        • enable configurable graph database backend selection via graphstore.impl property
      • #78 Enhancement CAT-FR-GD-08 - RDF-star Credential Claims Storage
        • Added new test methods to verify credential claim storage as RDF-star wrapped statements
      • #79 Enhancement CAT-FR-AM-01: non-RDF asset creation
        • Extends the /self-descriptions endpoint to accept non-RDF file uploads alongside existing RDF/JSON-LD Self-Descriptions
      • #80 Enhancement [CAT-FR-GD-09] Enforces protected RDF namespace filtering
        • Implements protected namespace filtering to prevent external actors from injecting internal catalogue metadata into the graph store
      • #82 Enhancement CAT-FR-AC-01 - Access Control
        • added new keycloak roles to enable fine-grained permissions for asset manegement
    • Closed Pull Requests
      • #71 Fix docker compose and enable hot-reloading
        • updated docker and docker-compose file
          • added hot-reload development setup
      • #72 Enhancement CAT-FR-GD-03 - graph database backend
        • added new test methods for Fuseki test infrastructure
      • #73 Enhacement CAT-FR-SF-04 - Disable validation against SHACL schemas on upload
        • Removes forced validation against stored SHACL schemas when uploading assets
          • VerificationService has been refactored with an option to enable/disable automatic SHACL validation via the verifySchema property
    • AOB
      • How to get the committer role?
        • Paul explained the process, unclear who initiates it (ECO or Christoph/Paul)
          • Update: Christoph initiated the process; any committer can do it
      • Relation between exising issues and SRS
        • SRS might be based on existing issues, so new PRs might close these if linked
      • Who is active on the repository?
        • Mostly people who use the XFSC Catalogue in a project-related context
          • Christoph / Paul keep an overview, but are not involved on a technical level
          • Denis answeres technical questions when his capacity allows
          • ECO probably on a "project management level", so not involved on any technical disscussions, but makes sure the SRS are being fulfilled

2026-02-26

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #45 Neo4j dependency investigation in good progress
    • New issues (check activity log since last meeting)
      • none
    • Pull Requests
    • AOB
      • What's the position of the Catalogue in the overall ecosystem?
        • Gaia-X perspective
        • XFSC/FACIS perspective: Gaia-X approach is useful in some context, but out of scope in some other contexts (e.g., the XFSC Catalogue is also used as a contract template repository for the Digital Contracting Service).
        • There is also the Eclipse Dataspace Working Group, of which XFSC is not formally a project, but which works on specifications that are also of interest to the XFSC Catalogue
        • productive usage?
          • Catalogue is part of Simpl-Open, which itself is not yet running in production environments
          • pre-productive usage of XFSC Catalogue (integrated with EDC Connector) in German Culture Dataspace
            • EDC's Federated Catalogue extension only speaks simple DCAT, no validation against extensible schemas
              • we are not aware of it being used widely. E.g., Catena-X follows a different approach for performance reasons
            • Simpl-Open also has an EDC↔XFSC connection (the need for this mainly came from policy bindings): create resource description VC (but without access information)
            • Gaia-X 4 ROMS project had an EDC↔XFSC integration
      • MSG planning that one person also becomes a Committer
      • Kubernetes cluster for testing: MSG will check with Eco in their JF next week

2026-02-12

  • What's the state?
    • New members (here: focus on companies and projects)
      • Melanie Friedrich from T-Systems, working on the SIMPL project
      • Sven Lindner from MSG, Technical PO for FCE
      • Eric Nowak from MSG, Developer for FCE
      • Steven Schwenke, Tech Lead for FCE
    • Open issues (in progress)
      • #45
        • MSG working on technical analysis regarding Neo4j licensing / dependencies
        • Maybe replacing Neo4j with another solution (e.g., Apache AGE) might be a valid approach
      • #57 DSSC Toolbox
        • Christoph and Paul will resume this issue with further colleagues
      • #66 Gaia-X Software Toolkit
        • XFSC Catalogue should be added, examples of how the submission should look like can be found in the comments here
    • New issues (check activity log since last meeting)
      • none
    • Pull Requests
      • Dependabot-generated PRs
        • Who cares for Dependabot PRs?
          • In theory, community work, but up to now, mainly Denis has taken care of them
        • How messy are the remaining open PRs?
          • Not sure, but not all suggestions of Dependabot are necessarily trivial. Some are also not relevant since they don't change anything

2026-01-29

  • What's the state?
    • New members (here: focus on companies and projects)
      • MSG as contractor for FCE
      • Experience with XFSC Catalogue from Gaia-X 4 Future Mobility Projects
      • Today Andreas Kahmann joined the call, but in the future, also more technical colleagues might join
    • Open issues (in progress)
      • none
    • New issues (check activity log since last meeting)
      • none
    • Pull Requests
  • AOB
    • FACIS
      • Paul/Christoph offer support for questions regarding FCE/DCM specification
      • MSG / ECO are still discussing if the work on FCE will happen directly on this repository
      • What is the state regarding the licensing issue with Neo4j?
        • Check with ECO
      • There is a wish for some exchange with the work on the DCM specification (maybe also DCS) to avoid "parallel" implementations
        • Could happen either in this call or ECO should organize some exchange between the contractors

2026-01-15

2025-12-18

2025-12-04

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
      • #45: question "how deeply is Neo4j integrated" clarified internally, now checking with XFSC project lead Lauresha Toska
    • Pull Requests
  • AOB
    • FACIS
      • specifications out for tender:
        • Lot: Federation Architecture Pattern IoT & AI (FACIS.FAP_IoT_AI)
        • Lot: Federation Architecture Pattern Decentralized Catalogue Management (FACIS.FAP_DCM): extending one catalog (XFSC or different) to harvest/crawl metadata from other remote catalogues, includes schema mapping (either simple RDF filtering, or AI-driven translation with a prompt library)
        • Lot: Federated Catalogue Enhancements (FACIS.FCE): already received a handful technical bidders' questions. Further work on the Architecture Document pipeline will be part of this implementation contract.
        • Lot: EasyStack Builder (FACIS.ESB_ICAM)
        • Lot: Digital Contracting Service (DCS): Catalogue will serve as Template Repository, but the corresponding Catalogue requirements are part of FACIS.FCE (see above)
    • Please vote for the XFSC Toolbox to become part of the Deutschland-Stack. Before, register here.

2025-11-20

  • What's the state?
  • AOB
    • FACIS
      • Catalogue enhancement spec is done, will be tendered by eco in a few days. Summary of functional requirements:
        • Asset Management: asset creation, IRI assignment, metadata enrichment
        • Claim Extraction to the Graph Database: extraction from credentials as well as non-credentials, protected namespace
        • Switchable Graph Database Backends: switchable openCypher and SPARQL-star support, linking claims to credentials, query language parameterization
        • Access Control: role-based access control, credentials-based role assertions
        • Lifecycle and Storage: asset lifecycle including versioning and provenance, audit logs, non-RDF schemas, schema versioning, human-readable assets, no forced schema validation
        • Compliance, Trust, and Validation: external trust framework (including Gaia-X), on-demand schema validation
        • Administration User Interface
      • this week and next week: starting specification of the Decentralized Catalogue Management (DCM) Federated Architecture Pattern (FAP)
    • Please vote for the XFSC Toolbox to become part of the Deutschland-Stack. Before, register here.
    • Pipeline for creation of architecture document from GitHub is being restored, PR will follow

2025-11-06

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
      • #56
        • Denis will look into it
      • #45
        • We have direct dependencies to neo4j
        • There are special cases where EPL and GPL 3 can be combined, but we are no licensiing experts
          • Point out the issue to Lauresha, get approval to remove Neo4j (and possibly exchange with RDF Triple store)
    • Pull Requests
  • AOB

2025-10-23

  • What's the state?
  • AOB
    • FACIS
      • Catalogue extension specification: trust framework support will no longer be hard-coded into the Catalogue, but there'll be an external interface to plug arbitrary trust frameworks / compliance services into. The Catalogue will also manage the lifecycle of unverified credentials.

2025-10-09

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #46 (README/CONTRIBUTING compliance, to which PR #54 was related) closed
      • #45 (due diligence) still in discussion
    • New issues (check activity log since last meeting)
    • Pull Requests
      • #54 (README compliance) merged
  • AOB

2025-09-25

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
    • Pull Requests
      • Dependency bumps via bot:
        • #48 (neosemantics: to be addressed in FACIS implementation contract because that's got the graph backend in its scope)
        • #49, #50, #52 (whereas sprint-boot-starter-parent was already bumped to 3.5.5 by #44), #53
  • AOB
    • in FACIS, Fraunhofer FIT will be contracted during October to specify up-to-date requirements for the Catalogue. These will include:
      • improvements that make the Catalogue easier to use according to the requirements for the Digital Contracting Service, whose implementation is now being tendered and whose Template Repository component will be required to use the XFSC Catalogue.
      • general improvements that make the Catalogue easier to be integrated into workflows defined using the XFSC Orchestration Engine
      • Gaia-X Loire release (plus, if applicable, any updates expected for the late-2025 Danube release)
      • but at the same making the trust anchor mechanism rely not exclusively on Gaia-X
      • switchable graph database backend (fixing Neo4j including correct URI support, plus RDF triple store/SPARQL via #47)
      • ensuring a smoother bot-triggered bumping of dependencies (currently, many dependabot-generated pull requests fail)
      • This community is welcome to suggest any further requirements we know from our application scenarios.

2025-09-11

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
    • Pull Requests
      • #47 (RDF triple store backend queryable in SPARQL)
  • AOB
    • Christoph on FACIS: initial intro about new Catalogue specification contract; update in 2 weeks
    • paper was accepted as "short paper" by CoopIS; decision to withdraw. Summary of reviewers' feedback:
      • strong points:
        • topic is of significant importance and corresponds closely to present needs in the field , as it addresses a central challenge in dataspaces, namely the discoverability of and trust in services and data.
        • tackles the important challenge of service discovery in decentralized dataspace environments, which is increasingly relevant given the growing adoption of European data initiatives and federated data architectures
        • fully implemented, tested system with real−world deployment in the German Culture Dataspace, underlining its maturity and facilitating its transition from research to practice. The system has undergone comprehensive testing including functional, performance, and security evaluation against 151 requirements.
        • modular design with clear separation of concerns ( lifecycle management, schema management, verification, and querying) demonstrates solid software engineering practices
        • sound technical design, relying on widely adopted web and data standards, which enhances its robustness and interoperability.
        • integration with established standards like W3C Verifiable Credentials and DCAT shows appropriate use of existing technologies
        • clearly written, logically structured, and supported by appropriate figures that facilitate comprehension
      • weak points:
        • Although the related work section is comprehensive, it remains largely descriptive ; a more systematic comparison, ideally presented in tabular form, would help to highlight more explicitly the distinctive contributions of XFSC in relation to existing catalogue solutions.
        • fails to justify why renowned approaches (e.g., Semantic Web service annotation approaches for service description leveraging mature ontologies such as OWL−S) are inadequate for the stated problem. This conceptual gap undermines the entire premise.
        • Despite extensive claims about performance and scalability ("scales to large numbers of records," "powerful and efficient semantic queries"), the paper does not provide any quantitative data. The authors mention the usage of Gatling for load testing and scalability experiments but present no numerical results, performance metrics, or comparative analyses.
        • The system essentially integrates existing technologies (Neo4j, SHACL validation, Verifiable Credentials) but the contributions (in terms of algorithmic innovations, theoretical advances, or novel methodologies) are difficult to grasp --> identify novel contributions beyond system integration.
        • The paper lacks comparative evaluation against alternative solutions, user studies, or empirical analysis of the system effectiveness in real−world scenarios. Indeed, the evaluation is primarily internal testing rather than scientific assessment.
        • The paper does not discuss the relationship with DLT/Blockchain technologies, despite the strong overlap in requirements ( decentralization, trust, metadata integrity, use of verifiable credentials ) . There is no reflection on potential synergies, differences, or complementarities.
        • The discussion of limitations is adequate, but the analysis could be further strengthened by a deeper reflection on the trade−offs of decentralization, in particular the choice between crawling and push−based approaches, as well as the dependency on outdated EDC versions.
        • While the quality of the English is high, certain sentences are overly long and could be streamlined to improve readability.
        • Figure captions could be expanded to make them more self−explanatory and accessible without requiring detailed reference to the main text.

2025-08-28

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
    • Pull Requests
      • Dependency bumps via bot: #38, #39, #41 old, #43 and #44 new. Denis will check them and will accept some of them.
  • AOB
    • Materna made, for the CO2for-IT forestry dataspace project, a modification that accepts Loire Participant credentials.
    • FACIS: draft of the Digital Contracting Service specification is being finalized. XFSC Catalogue will play a role for the contract template repository plus possibly further components. The specification focuses on functional and non-functional requirements but recommends the XFSC Catalogue as an implementation of part of these requirements.

2025-08-21

  • Meeting cancelled, due to lack of participation (only Paul and Denis were present)
  • We will be returning to our regular schedule, so the next meeting will take place on the 28th of August

2025-08-07

  • Meeting cancelled, due to lack of participation (only Paul and Denis were present)

2025-07-24

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
      • no updates
    • Pull Requests
      • Dependency bumps via bot: #5 merged, while #37, #38, #39, #40, and #41 are new. Denis will check them and will accept some of them.
  • AOB
    • Andreas Weiss (eco): XFSC Catalogue (together with other components such as OCM, PCM, TSA, Orchestration Engine) is being used in FACIS and related projects
      • listing Trusted Cloud offerings
      • aviation PoC and other real-world requirements
      • [distributed] asset management compliant with Gaia-X Trust Framework
      • Loire compatibility is required for this
      • the running projects have the potential and budget to make implementation contracts, but these need to have a clear goal. And, of course, the result of these contracts should be fed back into this community project.
      • demo video:
        • easy deployment in clusters
        • AI-based prompts for Orchestration Engine (from around 4:00)
      • Specification of Digital Contracting Service (Christoph):
        • Catalogue is suitable for realizing Contract Template Repository with mostly minor changes. Spec based on which implementations will be tendered will specify requirements and probably suggest that the XFSC Catalogue might be suitable for meeting them. Open questions:
          • filter-based search on PostgreSQL database: only active SDs (like graph), or all SDs?
          • what identifiers are given to SHACL shapes: UUIDs? – probably rather a hash/digest of the schema (which then changes when a new version is uploaded)
          • what do our build scripts look like? (Maven's pom.xml plus per-module ones, as well as Helm charts)
          • are we ready for monitoring and incident response? (Not implemented, but can be implemented by adapting Spring Boot configuration)
        • Catalogue, with some conceptual modifications (not storing but pointing to credentials, which the holders release upon request through their OCMs), might additionally meet the requirements for Contract Storage & Archiving.
    • Related question: what Gaia-X releases, esp. Tagus, is the Catalogue compatible with?
      • From a formal/legal/administrative perspective: with the 2021 GXFS requirements specification it was implemented against, including the 2021 Gaia-X specifications referenced by the GXFS specification. On top of that, it is also compatible with the 2022 Trust Framework. This state is summarized in the catalogue-specific architecture document.
      • From a practical perspective, …
        • … I (Christoph) think (but would have to verify) that the changes in subsequent releases of Gaia-X, up to and including Tagus, did not seriously affect the Catalogue’s functionality, …
        • … and a few additional bug fixes and feature implementations were made in the catalogue, but (for lack of capacity of all developers) in a way that was needed by projects, but not systematically aiming for full compliance with any Gaia-X specification.
        • Luckily (Denis), proof verification is implemented in a pluggable way.
      • For a complete understanding, we'd need a mapping between Gaia-X specifications ↔ Catalogue Architecture Document ↔ Catalogue source code (e.g., verification module, and default schemas).
      • avoiding redundancy in future:
        • can signature validation be delegated to an external service?
        • can policies be managed by the TSA?

2025-07-10

  • What's the state?
    • New members (here: focus on companies and projects)
      • Ovidiu Avasilcai (T-Systems) – Simpl, adapting EDC
    • Open issues (in progress)
      • Loire: Materna reports on their recent discussion of it
    • New issues (check activity log since last meeting)
      • no updates
    • Pull Requests
      • Dependency bumps via bot: looked into #5, while #33, #37 are still open, and #38 and #39 are new. Denis will check them and will accept some of them.
  • AOB
    • FACIS
      • work on the formal technical requirements specification for the Digital Contract Service has started; this is the priority till end of July, maybe till early August. In this service, the XFSC Catalogue will be used for managing the lifecycle of contract templates and of contracts. There is a broad scope of contracts, including data usage contracts as well as SLAs for cloud services. The catalogue perspective is represented by Christoph Lange and Paul Moosmann (both Fraunhofer FIT).
      • further Catalogue requirements specification will start in August. If, during this work, we come up with a better understanding of, e.g., the Loire compatibility, we (Fraunhofer FIT) will document it here in the repository.
    • Discussion of some features from a Simpl perspective:
      • Usage of sh:closed (should technically not be a problem but "union shapes graph" validation approach might have undesired practical consequences), validation against union shapes graph does not permit multiple alternative shapes (see specification here).
      • Simpl relies on a different authentication than Keycloak, but for the XFSC Catalogue Keycloak is currently required (?) – but the XFSC Catalogue can also be configured to use XFSC AAS instead.
    • next meetings will be out-of-schedule, on July 10 and 24, on August 7 and 21. Back to regular schedule from August 28? To be discussed in August.
      • Everyone is welcome to use GitHub discussion meanwhile.

2025-06-26

  • What's the state?
  • AOB
    • FACIS (FYI the overall formal scope): Fraunhofer FIT will get a small contract to perform the following tasks during July/August/September:
      • write a formal technical requirements specification for evolving the XFSC Catalogue for use in the FACIS project, e.g., together with the XFSC Orchestration Engine and the Digital Contracting Service, which also includes Gaia-X Loire compatibility. Based on this specification, eco will issue a request for proposals to get the actual implementation done by a contractor.
      • some updates to the Trusted Cloud schemas
      • some fixes to the https://github.com/eclipse-xfsc/sd-creation-wizard-frontend
    • next meetings will be out-of-schedule, on July 10 and 24. July 31 is back in the regular schedule. August to be discussed. Everyone is welcome to use GitHub discussion.

2025-06-05

  • What's the state?
    • New members (here: focus on companies and projects)
      • no new members
    • Open issues (in progress)
      • no updates
    • New issues (check activity log since last meeting)
      • Issue #31 created which contains the epic #6 from the GitLab Repository
        • Lucas was on vacation, so didn't start working on it yet
        • Lucas will have a look at issue #14 as "low-hanging fruit", to get a pull request in as argument to grant him the comitter role
    • Pull Requests
      • automatically generated PRs regarding dependencies, will be discussed next time if Denis is present
  • AOB

2025-05-22

  • What's the state?
  • AOB
    • Migration of Repository to GitLab: basically in place, but:
    • recap of Tech-X and hackathon
      • our intended task (Loire release) was not feasible due to short-notice lack of resources
      • there were presentations broadly related to Catalogues and credentials in general
      • confirmation of uncertainty around XFSC Catalogue given the end of old projects
    • Fraunhofer FIT had short meeting with eco re. FACIS project: specification of Catalogue implementation requirements (to then be contracted to implementation partners)
    • Benedikt Arnold demonstrated SPARQL-star queries (PR will follow soon)
    • Question from Lauresha: are any hardware requirements documented? – Not formally/officially, but 128 MiB memory were probably sufficient. The https://github.com/eclipse-xfsc/federated-catalogue/wiki/FC-Performance-Tests were done with Kubernetes defaults

2025-05-08

(short meeting; not much discussed)

2025-04-24

  • What's the state?
    • New members (here: focus on companies and projects)
      • no new members
    • Open issues (in progress)
      • no updates
    • New issues (check activity log since last meeting)
      • no new issues
    • Merge Requests
      • no new merge requests
    • AOB
      • Migration of Repository will take place soon (probably end of next week - 15.05 or 16.05.)
      • No possibility right now to give Lucas Schnebele Developer rights, since certain requirements (such as active work on the repository in the past) need to be fulfilled
      • We will postpone the demo from Benedikt to the next meeting, since this weeks meeting did not have too many participants

2025-04-10

  • What's the state?
    • New members (here: focus on companies and projects)
      • no new members
    • Open issues (in progress)
      • #257
        • Waiting for feedback of Robert Schubert
      • #260
        • Fixed by !347
      • #242
        • Changing the database to a triple store solves this problem
        • Work in progress by Benedikt Arnold in the Datenraum Kultur
        • Do we want a merge request with these changes?
          • Query Language would change from OpenCypher to SPARQL-star
          • Another possibility would be to offer both solutions
        • Benedikt will demonstrate the implementation in a future meeting and show how to set it up
          • Then we can discuss further steps
            • What needs to be changed
            • Do the changes solve the existing issues?
            • Do we need two separate solutions, or is it feasible to completely switch?
    • New issues (check activity log since last meeting)
      • #261
        • Denis can investigate, but it should be fixed by re-installing the catalogue
    • Merge Requests
      • !347
        • approved by Paul Moosmann
  • AOB
    • Gaia-X Hackathon proposal (deadline 2025-04-18)
      • Input from @langec (I'll join today's call around 13:30, didn't manage to talk to @gristow during Hannover Messe):
        • today, please set up a document (e.g., in this repository) for the proposal. Outline:
          • Hack session name: Upgrading the XFSC Federated Catalogue to the Loire release (Ontology, Credentials, Signatures)
          • Summary:
            • What is the XFSC Catalogue? – The Federated Catalogue of XFSC (Eclipse Cross Federation Services Components) is the Gaia-X Federated Catalogue implementation with the most comprehensive support for validating credentials against schemas and querying the graph structure of claims in credentials. It is used, among others, in the Gaia-X 4 Future Mobility lighthouse project and serves as a foundation of Simpl-Open, thus will play a key role the upcoming Common European Data Spaces.
            • What is the problem? – The XFSC Catalogue has so far been compatible with the Gaia-X Tagus release. Its developers' community has assessed and understood what needs to be done to upgrade it to Loire. Loire changes that impact the XFSC Catalogue include renamed concepts and new standards/formats for credentials and signatures.
            • What needs to be done? – Some of these changes require a deep re-engineering of parts of the Catalogue, including the credential verification pipeline, the database schema and the API endpoints. (maybe one more sentence, which is more precise.)
          • Knowledge required for the audience to participate (not each participant will have to understand everything, but the participants as a whole should have this knowledge):
            • familiarity with the Gaia-X Ontology
              • (Take Ontology from Gaia-X registry? When there are questions in the direction of the Gaia-X Lab Yassir Sellami is the new contact person)
            • familiarity with the Verifiable Credentials Data Model v2.0
            • Enterprise-style Java software development
            • Knowledge of JWT
            • … (please add further, more precise technical skills)
            • While part of the team will do the main implementation, further support is needed to provide test cases.
          • Name, picture and short resume of the hack leaders
            • Paul? (Please highlight your XFSC, Gaia-X Ontology, and Future Mobility experience)
            • Lucas?
            • Who else will be present? Gerald?
          • Contact information (won't be published)
            • @moosmannp can you serve as the main contact?
    • @langec on holiday on 2025-04-24 and 2025-05-08; @moosmannp will host meeting
    • Benedikt will create an Eclipse Account and then Paul will talk to Lauresha to grant Benedikt and Lucas Developer Roles in this Repository

2025-03-27

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #257
      • #260
    • New issues (check activity log since last meeting)
    • Merge Requests
  • AOB
    • Loire compatibility as a contribution to Gaia-X Hackathon at Tech-X (13/14 May 2025). Call for Hackathon sessions.
      • Scope: Loire and further issues of Gaia-X significance, including #257
      • Team
        • Lucas Schnebele (Software AG) would be available as a developer and will get on board
        • @schuberr (msg) interested; @langec will clarify availability/capacity
        • @dsukhoroslov in principle available but limited capacity
      • Who will attend Tech-X? @gristow @moosmannp (both not capable of doing the deep development for this task)
      • Proposal
        • We need to design our hackathon task in such a way that interested, technically skilled people can join and will be able to effectively do part of the job. (Requirement: specify knowledge required for the audience to participate)
          • Enterprise Java
          • Latest Gaia-X specs (Loire) and their underlying standards (pointers are here)
        • Most of the work needs to be done on the hackathon days. To be clarified: can we have remote participants like in previous years (Lucas would be remote)
        • We need to explain that the XFSC Catalogue is relevant (or even critical) for multiple Gaia-X projects, which require Loire compliance.
      • @gristow and @langec will talk during Hannover Messe next week

2025-03-13

  • Roadmap of FACIS (Federation Architecture for Composed Infrastructure Services), and the role of the XFSC Catalogue in it – @laureshamemeti, Andreas Weiss (eco Association of the Internet Industry, who also led the GXFS project, from which XFSC emerged) (15 minutes)
    • Slides
    • Cloud-to-edge continuum
    • Workloads; technical resource provisioning
    • Part of IPCEI-CIS / 8ra (pronounced "Ora") initiative
    • Compare mobile roaming. At this point, there is no counterpart for smart/autonomous driving services. This requires SLAs.
    • Digital contracts are JSON-LD, but not Linked Data (no references to external, dynamic resources), but self-contained.
    • Call to the Catalogue community for requirements/scenarios for industrial deployment (i.e., concrete Federated Architecture Patterns (FAPs)). Workshops will be set up and announced. Implementation may be tendered.
    • Consent manager / data exchange without data spaces are part of the concept, with, e.g., healthcare in mind.
    • What are our current issues with the Catalouge
    • For FACIS, the graph database (e.g., Neo4j) is considered important.
    • FACIS will require a certain level of abstraction. E.g., compliance with Gaia-X (cf. eclipse/xfsc/cat&6) is one possibility but not strictly required.
  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #260 discussion request
    • New issues (check activity log since last meeting)
    • Merge Requests
  • AOB
    • In the course of FACIS (see above), the XFSC repositories will be migrated from Eclipse GitLab to GitHub. In any case, we'll remain in the Eclipse Foundation.
    • @gristow suggested Loire compatibility as a contribution to Gaia-X Hackathon at Tech-X (13/14 May 2025). Call for Hackathon sessions to be opened soon.

2025-02-27

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
      • #260: Both the private and public keys should be stored in the XFSC project and generated using the provided command line. In addition, the public key must be placed in the DID document repository so it can be accessed to validate the signed SD when required. Merge Requests
    • Merge Requests
      • !346 to address #253 approved and merged
  • AOB

2025-02-13

  • What's the state?
    • New members (here: focus on companies and projects)
      • Szymon Truszczyński, Valerii Kalashnikov (T-Systems, Simpl – working on the Catalogue there), experienced back-end developers
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
    • Merge Requests
  • AOB
    • Simpl and its [fork of the Catalogue] (https://code.europa.eu/simpl/simpl-open/development/gaia-x-edc/simpl-fc-service/) (developed over the past year)
      • focus: Storage and Validation of Self-Descriptions against custom shapes and ontology
      • current maturity: PoC
      • Keycloak was removed because there's an external gateway to protect the application. Therefore, the user management endpoints are not currently in use.
      • Replaced integration tests with unit tests to speed up pipeline execution.
      • Spring Boot updated to latest version (was not too difficult)
      • Discussion on signatures and compatibility with signer tools
      • Merging back and forth?
        • Simpl fork started around May 2024 with the then latest version of XFSC; no further merges
        • Currently, there are probably (too?) many conflicts.
      • How to contribute to XFSC? See https://eclipse-xfsc.github.io/landingpage/
        • Discussion on management level will help; @langec will approach Eviden (leading the Simpl implementation contract)
        • @langec will discuss with @laureshamemeti whether there is a lower threshold to contribution (as a contributor, you'll have to work on a fork).
    • branching model
      • current code base should support both Gaia-X releases, Tagus and Loire ← note the up-to-date information from today's Gaia-X OSS Community
      • different endpoints (with different names and/or release names/numbers) in the same codebase
      • goals
        • no distraction of development focus
        • can keep old and new credentials in the same catalogue instance
    • core team submitted paper for Extended Semantic Web Conference, "in-use" track. pre-print of paper-under-review accessible on arXiv – final reviews expected end of February

2025-01-30

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • discussed #253
      • DSSC Toolbox #256 – today's audience was not prepared to work on this; @langec will do another round offline with @moosmannp
    • New issues (check activity log since last meeting)
      • The catalogue apparently doesn't contain the current "gx" Shacl shapes from the registry. We should update the SHACL shapes and also look into #203 again
    • Merge Requests
    • !345 to address #258 approved and merged
  • AOB
    • discuss strategy re. approaching Simpl.
      • BTW there's a public Simpl event going on today, which includes a demo of the first Simpl-Open MVP
      • They forked our project. MRs are open, issues are in a separate, closed (?) system, looks like Jira. @langec's initial assessment of the MRs:
      • It's in our interest to get in touch with them; everyone can ask for access to their repo with the justification "we are contributors to the original Eclipse XFSC Federated Catalogue project from which this was forked, and we'd like to get in touch with its developers" (worked for me @langec)
      • Does anyone know the developers (please check who committed there)? – We would prefer them to engage here, otherwise the future of the XFSC Catalogue won't sustain.
        • Valerii Kalashnikov and Szymon Truszczyński are the main committers so far; both work with T-Systems (different units than @dsukhoroslov) – @dsukhoroslov will put @langec in touch with them.
    • core team submitted paper for Extended Semantic Web Conference, "in-use" track. We'll involve the community during the review process for feedback.
      • pre-print of paper-under-review accessible on arXiv
      • We've received the initial reviews (without scores) – just very few requests for clarification to which we could respond right now. No particular help from the community required; first author Benedikt Arnold will take care.

2025-01-16

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #245 #249
        • closed through !343
      • #247
        • closed through !344
      • #253
        • will move forward as suggested by Denis
          • create Tagus branch, main branch will be used for work related to Loire
      • #255
        • Denis will have a look
      • DSSC Toolbox #256
        • it would be greatly apreciated, if everyone takes a look at the two files linked in #256 and adds comments
    • New issues (check activity log since last meeting)
      • #258
        • We should change default config to only expose necessary endpoints. Afterwards we should create a new release
      • The catalogue apparently doesn't contain the current "gx" Shacl shapes from the registry. We should update the SHACL shapes and also look into #203 again
    • Merge Requests
      • !343 and !344 merged
  • AOB
    • discuss strategy re. approaching Simpl.
      • They forked our project. MRs are open, issues are in a separate, closed (?) system, looks like Jira. @langec's initial assessment of the MRs:
      • It's in our interest to get in touch with them; everyone can ask for access to their repo with the justification "we are contributors to the original Eclipse XFSC Federated Catalogue project from which this was forked, and we'd like to get in touch with its developers" (worked for me @langec)
      • Does anyone know the developers (please check who committed there)? – We would prefer them to engage here, otherwise the future of the XFSC Catalogue won't sustain.
      • Please discuss strategy to approach them, e.g., sending them an Issue.
    • core team submitted paper for Extended Semantic Web Conference, "in-use" track. We'll involve the community during the review process for feedback.

2024-12-19

  • What's the state?
    • New members (here: focus on companies and projects)
      • Gradiant
        • Working on SSI in context of a project called Trusted
          • currently in the assessment phase
        • Met me (Paul) at XFSC Workshop, and sent a follow-up mail
          • Mail will be resend
    • Open issues (in progress)
      • #257 Added a comment regarding the necessary changes to the issue
        • Regarding merging of VCs: Denis already tried to implement something a while back, he will open a branch to further work on it (might take a while, though)
        • Regarding having different credential Subject IDs inside a VP
          • Paul will one issue, that should be discussed next time in a (hopefully) larger round
      • DSSC Toolbox #256 → @langec will prepare something for next call
        • Not prepared yet, self-assessment for DSSC Toolbox can be found here
    • New issues (check activity log since last meeting)
    • Merge Requests
  • AOB
    • core team working on paper for Extended Semantic Web Conference, "in-use" track.
      • Nearly done, will be submitted today

2024-12-05

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
    • New issues (check activity log since last meeting)
      • In discussion of #257, we closed the old issue #173
      • via Kai Meinke / Hossein Rafieekhah: working credentials? (offline email thread "Assistance Needed: Error Encountered While Saving Data in the Catalogue")
        • @rafieekhah thanks for sharing your credentials (coming from Pontus-X) – so far, @moosmannp was not able to reproduce the issue you've had but encountered different problems. To have this properly addressed by the XFSC Catalogue community, could you please open an issue here and join our next call? (See below for the date.) Then, we'll be able to discuss it using our regular process (see the structure of these minutes).
        • related request by Kai Meinke:
          1. "Could the XFSC or catalogue team please provide a working example for a Gaia-X service credential you have been able to integrate in the catalogue and that can be verified against the GXDCH?"
            • to be investigated. As per !328, !330, etc., we recall that we did implement compatibility with Gaia-X Tagus – @jxhn do you recall the right MR. Gaia-X Loire is a new open issue (#255)
          2. "To which reference environment for a catalogue should we point there interested parties? Can you give me an official URL that can be shared with external stakeholders?"
            • we'll find out. We, as the XFSC Eclipse project, don't have the resources to deploy a reference instance, but we'll ask in the community who has a deployed instance. @moosmannp will ask 😄
            • via @ahemid: Fraunhofer FIT has an up-to-date instance in the scope of Datenraum Kultur, where the port can be opened on request
    • Merge Requests
      • !342 fixing #250 merged
  • AOB
    • Pipelines are failing, as no workers are available any more (see, e.g., this job not working) – @laureshamemeti will check whether this is the case for all of XFSC, whether we need to check anything with the Eclipse Foundation, whether new funding is needed, …?
    • Gaia-X Hub DE Expo last week – no video recording, but well covered on LinkedIn. Good spirit about "getting things done".
    • @moosmannp demoed Catalogue to Gaia-X Hub ES last week (last XFSC Tech Workshop funded by the GXFS project). General functionality, then also using an XFSC Catalogue instance deployed by smartSense (incl. CES) with Orchestration Engine (formerly known as Workflow Engine)
    • core team working on paper for Extended Semantic Web Conference, "in-use" track. @langec will do a full review soon, might reach out to individual people in the community?
    • next call on 2024-12-19 – @langec will renew series, first call in 2025 likely on 16 January.

2024-11-21

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #246 closed as !341 was merged
      • #248 closed
      • #237 closed
    • New issues (check activity log since last meeting)
      • #251 → &6 Loire release (incl. #252, #253, #254, #255)
      • #250 in progress
      • #249 in progress
    • Merge Requests
  • AOB
    • review of Gaia-X Summit: there were technical sessions, but they were still quite high-level
    • Gaia-X Hub DE Expo next week – @langec to check whether there will be video recording
    • @moosmannp will demo Catalogue to Hub ES next week (GXFS Tech Workshop)
    • DSSC Toolbox #256
    • core team working on paper for Extended Semantic Web Conference, "in-use" track

2024-11-07

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #240 No update right now
      • #237 No update right now
      • #242 Robert will remind Lena to comment on this issue
      • #244 Paul will ask Ahmad to add provided information to the documentation
      • #246 fixed by MR !341
    • New issues (check activity log since last meeting)
      • #248 No update this week, but Oliver is looking into it
    • Merge Requests
      • !340 Merged, solves #239
      • !341 merged
  • AOB
    • LOIRE Release: What does this mean for the catalogue?
      • Add new schema files to catalogue (SHACL Shapes, Ontology Files)
        • They use a new namespace, so we will probably add the new files, instead of updating the existing ones
      • Signature implementation was changed with LOIRE, this needs to be looked into

2024-10-24

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #241 (closed); see #247 – #247 will be considered in the long-term activities
      • #235 (closed): Developer Guide was provided
      • #244 clarification was added
      • #246 can be fixed by merging !341
      • #237, #240, #242: requested feedback
    • New issues (check activity log since last meeting)
    • Merge Requests
      • !340 needs to be reviewed
      • !341 needs to be merged
  • AOB
    • @laureshamemeti provided an update about the XFSC Final Tech Workshop- at the Madrid Innovation Lab, the planned agenda for the 1st day and the proposed content for the 2nd day.
    • A question was raised regarding the insertion of a Verifiable Presentation containing multiple Verifiable Credentials. It was noted that the first and last issuers of these Verifiable Credentials must be the same; otherwise, it will not function properly.

2024-10-10

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #239 is being addressed by !340 but needs further work
      • #241 will be addressed by Keycloak upgrade ( #247)
      • #243: further testing
      • #244: requested clarification
      • #242, #237, #246: requested feedback
      • #240 requires input from project partner
      • #234 fixed by !339 ? (Requested confirmation)
    • New issues (check activity log since last meeting)
    • Merge Requests
      • !340 (see #239 above)
  • AOB
    • Compatibility between Gaia-X (as implemented here, in the XFSC Catalogue) and IDS (International Data Spaces, where Sovereign Data Exchange is implemented using Connectors, of which https://github.com/eclipse-edc/Connector/ is one)?
      • A specific connection between the EDC and the XFSC Catalogue is being worked on, by @kbaydoun et al.
      • On the Data Plane, connectors support multiple cloud storage backends.
    • https://github.com/orgs/eclipse-xfsc was created by "Eclipse Webmaster Team"; needs clarification.

2024-09-26

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • #239: has to do with URL param creation, loop because always the first batch is fetched, @jxhn will check if he has time for this
      • #243:
        • @ozell: created in the last meeting, same problem as we have
        • @jxhn: trust anchor can be set in env vars
        • @schuberr: root cert needs to be an entity like vSSL
      • #244: postponed, need @ahemid to discuss
      • #241: Keycloak update might be sufficient
    • New issues (check activity log since last meeting)
    • Merge Requests
      • –
  • AOB
    • –

2024-09-12

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • recap of #237 (problem solved?)
      • discussed #240
      • #239 → next meeting
    • New issues
      • from last meeting's discussion: #241 (length of identifiers)
      • @ozell continuing the discussion on "Who should sign provider VCs?", arguing with Gaia-X Trust Framework → #243 next time
      • Implement RDF URI rewriting like the Gaia-X Registry: query, rewriting – could this be the answer to #242?
      • Improve documentation of how to deploy using Helm in Wiki – @ahemid created #244
    • Merge Requests
      • Merged !339 (addressing #234)
  • AOB
    • Tech Deep Dive on Thursday, 26 September 2024, from 15:00 to 16:00 CET
      • During this live session, Vincent Kelleher, Software Developer at Gaia-X, will cover:
        • How Gaia-X uses LinkML to describe the ontology.
        • How the LinkML generators work for different output formats (e.g., JSON-LD contexts, SHACL shapes).
        • The system Gaia-X uses to broadcast the generated outputs.
        • The importance of the Open Source community for Gaia-X and other public projects.
        • Join here

2024-08-29

  • What's the state?
    • New members (here: focus on companies and projects)
    • Open issues (in progress)
      • recap of #236 and #232, which were closed meanwhile (problems solved)
      • discussed #234 (no update meanwhile)
    • New issues
    • discussed #237 and #239
    • closed #238
    • #240 from Gaia-X 4 AMS (Future Mobility): setting up Catalogue behind reverse proxy
      • @dsukhoroslov is ready to help, has always used a reverse proxy.
    • Merge Requests
      • No new merge requests
  • AOB
    • Who should sign provider VCs? The provider itself (yes), or the same issuer (no, not supported by the Catalogue)? Could that be the problem causing #237?

2024-08-01

  • What's the state?
    • New members (here: focus on companies and projects)
      • A1 Digital on the way of becoming recognized as a Gaia-X Digital Clearing House (Flex4RES, EuProGigant)
      • Additional Fraunhofer colleagues working on Datenraum Kultur and related projects
      • YUNEX Traffic (formerly part of Siemens Mobility): Gaia-X 4 ROMS
      • Additional colleagues from smartSense working on open source contributions for Gaia-X and Catena-X
      • Posedio (EuProGigant, working on Publishing Connector)
    • Open issues (in progress)
      • mismatch between claims in submitted JSON-LD and Neo4J? – please open an issue
    • New issues
      • #236 – we tried to clarify it
    • Merge Requests
      • No new merge requests
  • AOB
    • explained relation between SHACL shapes and Neo4J graph database: there is none. Just that any claims are validated against the SHACL shapes before being extracted into the graph database.
    • adding a new participant using the Gaia-X Wizard: this gives you a VerifiableCredential. For the XFSC Catalogue to accept that, it's necessary to wrap it into a VerifiablePresentation.

2024-07-04

  • What's the state?
    • Open issues (in progress)
    • New issues
      • #234
      • Make contribution easy
        • document "how to contribute" ( #235)
        • no easy way to contribute to gitlab.eclipse.org when your project is on GitHub instead, like MERLOT – no explicit links, but local "file-copying" workarounds
      • MERLOT: access credentials as first-class citizens in the graph rather than somewhere else via the API (required for certain business processes)
        • versus: should the CES issue compliance for credentials, or rather for claims?
        • not yet specified by Gaia-X Association (e.g., in the Architecture Document – the CES was realized before specification – in both, this should be documented as an issue)
    • Merge Requests
      • No new merge requests
  • AOB

2024-06-20

2024-06-06

  • What's the state?
    • General
    • Open issues (in progress)
      • Given that #218 is done, let's discuss #208
    • New issues
      • commented #232
    • Merge Requests
      • merged since previous meeting: !335, !336, !337, !338
  • AOB
    • question re. #178:
      • former GXDCH had incorrect implementation of JWT2020 (was, for now, retained for compatibility)
      • now, GXDCHs also supports the correct signatures
      • the notaries, compliance service, etc. still signs with the incorrect implementation (which is not accepted by the XFSC Catalogue)
      • MERLOT and ROMS projects will continue with their own fixes (ROMS: disabled verification; MERLOT: not checking compliance credentials)
        • MERLOT will try to publish their patch
      • Gaia-X AISBL won't fix it for now, as they will be switching from JWT2020 "embedded proofs" to "enveloped proofs" signing the payload; thus, in the near future (timeline?!), we'll see one breaking change instead of two (cf. https://gitlab.com/gaia-x/lab/gxdch/-/issues/19)
    • Reviewing Tech-X
      • a few members of the Catalogue community had a successful hackathon track on improving the LinkML-based CI that's used in Gaia-X Service Characteristics to generate schemas (SHACL, OWL, JSON-LD contexts)
    • Eco/Fraunhofer will give a Webinar on the XFSC Catalogue for the Spanish Gaia-X Hub on 2024-06-17, to be followed by a hands-on workshop around October. We hope to recruit new members into the developers' community.

2024-04-25

  • What's the state?
    • Open issues (in progress)
      • #218
        • Question: Do we want to accept multiple VC types in a single VP
        • Yes, Denis will think about how to update the SD handling accordingly
          • This will impact the work on #208
    • New issues
    • Merge Requests
      • !335
        • implements solution for #218
        • might also have an impact on #208
  • AOB
    • Gaia-X Lab working on changing supported signature
      • switch from embedded signature to envelope signature
      • payload will be json web token

2024-04-11

  • What's the state?
    • Open issues (in progress)
      • #218
    • New issues
      • #222
    • Merge Requests
  • AOB
    • Update on Gaia-X Compliance → #222
    • Any ideas for hackathon proposals at Tech-X? Deadline Thursday 18th.
      • related: @langec @moosmannp are working on a proposal for advancing the WG Service Characteristics LinkML CI

2024-03-28

2024-03-14

  • What's the state?
    • Open issues (in progress)
      • #182 Paul will create a Wiki Page for related tools
        • Eclipse might close the Wiki? Think about other solution for documentation
      • #193 / #208
        • Should we accept VC without the VP wrapper
          • yes, we should in some way. Implement switch to disable VP Signature verification?
        • #208 Updating catalogue specification still ongoing
      • #178 implements further signature validation, which works fine on tests done by John Hoffmann and Lena Sauermann
      • #212 Denis will think about how to resolve this issue
    • New issues
    • Merge Requests
      • !329 in progress, related to #201
      • !328 Approved and will be merged after the meeting, closing #178
  • AOB

2024-02-29

  • What's the state?
    • Open issues (in progress)
    • Open issues (raised)
    • New issues
      • Namespace URIs of the schema used by the Catalogue inconsistent with what the Gaia-X Compliance Service accepts ( @gristow) – this is a sub-task of #199
      • #211: Create new release? Currently, the latest is 1.0.1. @schuberr, @dsukhoroslov
    • Merge Requests
      • !325 and related MRs fixed #210 Current Neo4j version leads to error when using docker (issue / MR will follow)
  • AOB
    • GXFS project will end in 2024, and is progressing in the transition from public funding to a self-sustaining community effort.
      • Coordination of the XFSC Catalogue Developers' Community is no longer funded by GXFS but will continue – driven by the community in their own interest. Fraunhofer FIT will continue to run this call, motivated by their involvement in, e.g., Datenraum Kultur (German culture data space) and Gaia-X 4 Future Mobility.
      • @laureshamemeti presented XFSC Roadmap 2024
        1. Q1: advancing toolbox
        2. Q2: finalizing toolbox
        3. Q3/4: community adoption/uptake
    • In 2 weeks: Data Spaces Symposium in Darmstadt; this call will take place nevertheless, moderated by @moosmannp

2024-02-15

  • What's the state?
    • Open issues (in progress)
      • #193
        • Analysis of current code in progress
        • Bigger update next meeting
        • Is there any way to assist on this issue?
          • After initial analysis, Maharshi will set up a meeting with Fabian to discuss potential collaboration
    • Open issues (raised)
    • New issues
      • Current Neo4j version leads to error when using docker (issue / MR will follow)
    • Merge Requests
      • !321 Increase VP character limits
        • Related to #199 since it is necessary regarding compatibility with Gaia-X Lab Wizard
      • !323 Fixed issue when disabling signature check
      • !322 Fixed expired expiration date
  • AOB

2024-02-01

  • What's the state?
    • Open issues (in progress)
      • Update on https://gitlab.eclipse.org/eclipse/xfsc/cat/fc-service/-/issues/178
        • Signature implementation of the catalogue correct according to specifications
        • Signature implementation of compliance service will be changed in next update (around end of Q2)
        • Till then it might be best to disable signature verification from the catalogue side
      • #193
        • Credential Event Service functional requirements survey. Conclusions:

          • The service stays publicly open (no onboarding required) and freely accessible for consumption (pull/GET) and publication (push/POST)

            The rational is that the content of the Credentials is NOT shared on CES. Only the resolvable ID of the Credentials. Should the owner/holder of the credentials wish to even keep the ID of their credentials private, then don’t use the public CES instance and either spawn an instance private to the holder’s ecosystem or use another mechanism for publication.

          • The service should be Available and Partition Tolerant, not necessarily Consistent.

            Check https://en.wikipedia.org/wiki/CAP_theorem

          • The service is going to expose 2 types of endpoints:

            1. We keep today’s endpoints accepting only Gaia-X Compliance credentials

            2. We add a new one accepting resolvable IDs of cryptographically valid Verifiable Credentials

              If there is an abuse, we might:

              1. Add constraints on the type of issuer
              2. Reduce data retention

          • The service is going to accept standard OIDC4VP API. (To be confirmed shortly)

      • The GXFS-FR Catalogue apparently can merge VCs from multiple sources pointing to the same credentialSubject: https://gitlab.com/gaia-x/data-infrastructure-federation-services/deployment-scenario/catalogue/federated-catalogue → we need to understand how that works (-> #208).
        • Lena will open an issue and look into the implementation of the GXFS-FR Catalogue
    • Open issues (raised)
      • #207 Frontend Requirements
        • Feedback will be given as comments
    • New issues
    • Merge Requests
      • !314 / !315 Currently no updates
  • AOB

2024-01-18

2024-01-04

  • What's the state?
  • AOB
    • new TSA with new Signer is ready for QA; QA will be done next week in preparation of 22/23 January Tech Workshop (which will focus on TRAIN)
      • what's that signer compatible with? (cf. #178)
      • draft workshop agenda was discussed during call
    • Tech workshop participant encountered problems with "Example 2: Make a build of fc-service from the Dockerfile" – resolved :slight_smile:
    • Who is (seriously) using queries (openCypher, SPARQL, …), and for what purpose / use case?
      • Let's start a systematic documentation – when more people with project / use case experience are in the call
      • Background: only very few queries have been documented for the whole community
      • Support for semantics in queries is limited, as the ontology is not currently indexed into the graph database (known issue #134 – short summary: the case was understood, but in the 1st implementation phase there were no resources available to get it implemented)

2023-12-21

  • What's the state?
    • Open issues (in progress)
      • !197 other query languages
      • !198 client libraries in other programming languages
    • Open issues (raised)
    • New issues
    • Merge Requests
      • Revisiting !314 and !315, which, for now, were only merged into a feature branch
      • !317 was merged by @dsukhoroslov – procedural questions by @langec
        • (How) can we enforce reviews/approvals before merge?
          • We are generally supportive of having mandatory approvals
          • @dsukhoroslov will ask @laureshamemeti how to have them enabled for this project
        • GitLab strangely pointed out vulnerabilities – they are not necessarily in our code (at least not in !317), but in dependencies. – @dsukhoroslov will create a new issue about that.
  • AOB
    • If you do not have a role in this project/repository, please let @laureshamemeti know (who is the only maintainer).
    • Harbor Registry is in place
      • but giving 404 to many of us, and others are not yet able to access the recent artifacts.
      • current workaround (also discussed in Matrix chat): go to Jobs, check for an .io URL in the log of the deploy:jdk11 job, and use that with Docker.
    • Who is (seriously) using queries (openCypher, SPARQL, …), and for what purpose / use case?
      • Let's start a systematic documentation.
    • Gaia-X WG Service Characteristics now has the new CI to create schemas. Next step is (for the Gaia-X Lab staff) to publish these latest schemas through the registry, replacing the manually created workaround that is currently in place.

2023-12-07

  • What's the state?
    • Open issues (in progress)
      • #178
        • Denis has proposed a solution for another gaiax project. Contact with Christoph 
      • #193
        • It is merged in another branch, requires more review  
      • #199
        • Contact John Hoffmann for further progress and state 
    • Open issues (raised)
      • #201 (connected to #199 ?)
        • We know how to make it but we in the need of  deveoplement resources. 
      • #202
        • This is supported. Futher investigation to find the current issue
      • #203 (connected to #199 ?)
        • We need dev. resource.  
        • Registry should provide some apis for notification  
        • A refresh checker code is needed  
        • It is a big rish to have a non-compatible schema (Solution: a sandbox to check if the new schema is compatible or not, otherwise reject it) 
    • New issues
      • #204
        • Further details are required from Lange and schbert. What needed and what extent for issue 
    • Merge Requests
      • !314 and !315 merged into a new feature branch feat-ces-event-integration. This is connected to #193 and will be used at the upcoming GXFS Tech Workshop
  • AOB
    • Who is (seriously) using openCypher queries, and for what purpose / use case?
      • Make a sheet could be an idea and send by email. Maybe add SPARQL as well  
    • FYI in Gaia-X WG Service Characteristics the implementation of the new CI that creates the new schemas is technically complete, now being tested. Thus, we will soon have the "right" schemas in the Gaia-X Registry rather than temporary workarounds.

2023-11-23

  • What's the state?
    • Open Issues
      • #178
        • in good progress among @hrohmer, @fabianscheidt, @jxhn et al.
        • Unit tests need revision, potential confusion on "what's the right schema"
      • #193
        • code for pulling from CES being tested – not yet in this repo. New developer Dilip (smartSense) was just onboarded and will open MR
        • Part of the next GXFS Tech Workshop (12./13. December in Cologne)
        • need frontend to demonstrate Catalogue/CES interaction – possible solution by using XFSC WFE to be discussed next week, also in preparation of the Tech Workshop
        • Postman as a simple frontend – yes, it's already part of this project
      • #199 – being investigated, also including connected issue #202
    • New Issues
      • #200 – resolved via !313
      • #201
      • #202
      • future work: thinking #199 further towards #203
    • Merge Requests
      • !305
        • Was closed since it will be handled by the work done for #199
  • AOB
    • reminder of 2FA in the Eclipse repositories (how to activate)
    • EDC / XFSC Catalogue Integration
      • Exchange between @ahemid, Jérome and @schuberr
      • Very different approaches based on different business requirements / architecture backgrounds:
        • "EDC / XFSC Catalogue Integration" is not specific enough
        • Need to make clear what exactly is being done
        • Create a Wiki page with an overview of what kind of work is being done in the different projects – @ahemid will create an issue and involve @schuberr
    • @schuberr and team wanted to contribute to https://gitlab.eclipse.org/eclipse/xfsc/self-description-tooling/sd-creation-wizard-api but pipeline is failing right now – might be resolved in the scope of general XFSC/Eclipse works. @moosmannp could you please monitor this progress?

2023-11-09

  • What's the state?
    • Update on EDC Integration (Ahmad)
      • Goal is to get catalogue data instances from EDC
      • PLC AAD did something similiar
      • Merlot implemented this in the opposite direction (take from XFSC catalogue and store in EDC)
      • How helpful is a direct connection? Might it be more helpful to talk to the CES?
      • Send mail to Jerome, Robert and Ahmad for exhcange regarding EDC <-> XFSC Catalogue
    • Open Issues
      • #178
        • Meeting with Sebastian Duda, any updates?
          • swapping dependency and see if it improves the situation
          • setting up environment for testing
          • different schema and different signature
          • isolate signature problem
          • working on changes for validation logic
        • Consideration: Compatibility? Do we want to keep supporting the old signer?
          • More general: Is there a governance process
          • Do we have a release schedule / semantic versioning?
          • We need a proper pipeline to build the catalogue and push to a registry
          • -> Needs to be checked with ECO / Eclipse Foundation
      • #193
        • Denis reached out to Maharshi, any updates?
          • No updates yet
          • Topic relevant for the next GXFS Tech Workshop taking place in Cologne in December
          • Exchagne between Christoph Lange and Maharshi at the Gaia-X Summit
      • #199
        • Take a look at comment of John Hoffmann
          • The library used doesn't seem to be able to handle different ways to express the json-ld context
          • John will open issue
          • Denis will take a look at it since he has an idea for an easy fix (adjust loader parameters)
        • Request by Bonian Riebe to point to the related parts of the implementation
          • issue will be updated
    • Merge Requests
      • !311 Merged
      • !312 Merged
      • !305 Merge or add GX-Schema? (see #199)
        • -> Add GX-Schema

2023-10-26

  • What's the state?
    • Merge Requests
      • !305
        • Doesn't solve compability issues with gaia-x lab (-> new issue #199)
          • Need to add GX schema as default schema to XFSC Catalogue
          • Catalogue should accept credentials with the 'gx' namespace
          • Catalogue should accept signature of the Compliance Service
          • Quick and dirty approach: Allow everything to be uploaded to the catalogue ( !301)
    • Existing issues
      • #193
        • Lauresha will get Maharshi and Denis in contact (Add Khalil regarding potential re-use of EDC / Catalogue integration attempt)
      • #178
        • Preparation: Create an working SD with GXFS Catalogue and Signature of Compliance Service
        • Meeting with Sebastian Duda on the 27th of October
    • New Issues?
      • #197 Feature Request: Further Query Languages?
        • Please comment if this is relevant to you
      • #198 Feature Request: Further Client Libraries?
        • Please comment if this is relevant to you

2023-10-12

  • What's the state?
    • Merge Requests
      • !305
        • Adds missing properties (LEI) from Trust Framework 22.10 to the default schema
        • Doesn't solve compatibility issues with the Gaia-X Lab Wizard regarding the used namespaces or signatures
        • Paul Moosmann will review this MR
    • State of existing issues
      • #193
        • Step 1.1: Check if existing Self Descriptions fit the stated requirements (-> Paul Moosmann)
        • Step 1.2: Maharshi Suchak will try to solve this step, Denis will point him towards the right direction
        • To check with Philip Hertweck: Where to do the booking regarding the credential events in the SD Management / Storage module
      • #178
        • Fabian Scheidt has an implementation idea
        • Try to reach out to Sebastian Duda and connect him with Fabian Scheidt
  • Work Schedule and Priorities
    • What is important for which project?
      • Project Labels have been introduced and can be used to link issues to the related projects

2023-09-28

  • Welcome: purpose and expectations
    • Join the community: matrix chat, make sure you are registered in Eclipse GitLab
    • You will receive the invitation from Eclipse to do the contributor agreement (to ensure proper open source governance)
  • Introduce yourself in 15 seconds: name, company, Gaia-X project(s), technical skills
  • The current state of XFSC Catalog
    • The current repo of the XFSC Catalog
      • Eclipse Projects / xfsc / Federated Catalogue / FC Service · GitLab
      • Architecture Document for design decisions
    • Discussing open merge requests
      • !305
    • Syncing across catalogues with the Credential Exchange Service (CES)
    • More specifically: EDC Extension for XFSC Catalog
      • Who is interested in this?
      • Who is working on such solutions?
      • GitLab
  • The current development and improvement
    • The current Issues on the repo
      • #178
  • Work Schedule and Priorities
  • Based on discussions during this meeting, the priorities and dependencies can be identified.
  • We'll set up per-project labels for all projects in the repo so that we can express "what issue/MR is relevant to what project"
  • The current availability and development support
    • Meetings every 2 weeks
    • Assigning the available tasks and duties based on the availability and development skills.
  • Summary
  • Event announcements
    • GXFS Tech Workshop # 4, 17 October, Reutlingen (3 hours): focusing on #172 (frontend API)
    • Gaia-X Summit, 9-10 November, Alicante
    • GXFS Tech Workshop # 5, 12-13 December, Cologne

Catalogue Documentation

Clone this wiki locally