Hello Simpl Forum community,
I’m excited to be part of this vibrant group working on the future of EU data spaces and the Simpl middleware.
As we know, modularity and adaptability are core principles for Simpl-Open, supporting diverse sectoral data spaces. However, achieving the right balance between flexibility and ease of use remains a challenge.
I’d love to open a discussion on:
- What modular components or features do you find most critical to Simpl-Open’s success in your domain?
- How can we improve adaptability to support both large and small data spaces with different governance and compliance needs?
- Are there specific use cases or scenarios you think Simpl-Open should prioritize in upcoming releases?
- How can the community best collaborate to accelerate these enhancements and share reusable modules?
Looking forward to your insights, experiences, and ideas. Let’s make Simpl-Open a truly adaptable and powerful platform for all!
Good day!
Thank you for reaching out and welcome to our community! Your comments and contributions are always appreciated.
Hi Edward Garry Simpson - your questions are very interesting, and i'm sure the development team and the community can enrich this discussion. as a starting point, seeing the roadmap published recently, is there anything you think we should work on sooner than planned? Simpl-Open Roadmap Update May 2025 | Simpl Programme. Please also note that we will publish soon an updated architecture documentation.
We will also publish soon the guidelines for contributions of the community, this would certainly help to clarify how to submit code contributions or other type of contributions - do you have a specific idea in mind for this?
If you need more background on why is Simpl developed and how, you can refer to previous documentation https://digital-strategy.ec.europa.eu/en/policies/simpl#1712822729753-2…;
Hello Edward Garry Simpson and thank you for opening such a valuable discussion.
I fully agree that modularity and adaptability are essential principles for the long-term success of SIMPL-Open. However, I’d like to emphasize that in the context of SIMPL-Open, there isn’t a single modular component that stands out as the most critical. Rather, it is the modularity of all the building blocks — from identity and access management, governance services, to catalogues and policy enforcement among others — that enables the midleware to support a broad spectrum of data space implementations. Each component must be designed with composability and interoperability in mind to accommodate the diverse requirements of different domains and governance models.
Regarding adaptability to both large and small data spaces: one promising direction is the adoption of configuration-over-customization principles and well-documented APIs that allow data spaces to scale components up or down based on their specific context.
As for the upcoming use cases and features, many of these are already outlined in the SIMPL-Open roadmap as Valentina STAVERIS has point. Once the community contribution guidelines are published, this will be a great opportunity for stakeholders to bring their vision and value to the product.
As a final thought, I’m curious: from your perspective, what kind of value do you think the community can bring to Simpl-Open beyond code (for example, in terms of governance models, interoperability guidelines, or domain-specific knowledge)?
Also, do you think the modular nature of the platform might be at risk if contributions from diverse sources aren’t properly curated or aligned with a shared architectural vision? Do you have any experience with other comunities that can bring value to enrich the one that is being worked on?
Looking forward to your insights and to continuing this conversation with the rest of the community.
Please log in or sign up to comment.