Rulebook 3.0

[PeterKoen-MSFT]

Pull Request: Rulebook-3.0 — Replace and Modernize Rulebook Content

Overview

• Purpose: This PR replaces the existing rulebook text with a fully revised Rulebook-3.0. The new content modernizes language, fills gaps, and reorganizes material to reflect current best practices for data spaces.
• Scope: Full replacement of the legacy rulebook text across the branch Rulebook-3.0 with updated documentation aligned to international standards, the IDSA Architecture Working Group outputs, and relevant open-source specifications hosted under the Eclipse Foundation.

What Changed

• Content replacement: Core chapters and annexes rewritten to reflect 3.0 principles and architecture decisions.
• Structure: Sections re-organized for clearer separation of concepts (principles, roles, technical components, governance, compliance,...).
• Clarity & guidance: Added practical guidance for implementers and integrators, with clear references to standards and open-source projects.

Key Highlights

• Updated conceptual model: Improved definitions and relationships for data spaces, participants, and data space governance authorities.
• Stronger alignment to standards: Explicit mapping to relevant international standards and bodies (Eg. ISO/IEC 20151-1).
• Architecture-aligned guidance: Text informed by the Architecture Working Group to ensure consistency with reference architectures and patterns.
• Open source specification alignment: Guidance and examples aligned to Eclipse Foundation specification projects (for example, the Eclipse Dataspace Protocol) to support interoperable, real-world implementations.

Standards & Compliance Alignment

• Examples of referenced standards: ISO/IEC families, CEN/CENELEC European Norms, W3C recommendations, and recognized national guidance where applicable.
• Compliance guidance: Clear notes for compliance-related responsibilities for DSGA's and participants.

Architecture Working Group Contributions

• Design inputs: Core architectural principles, component responsibilities, and interfaces documented by the Architecture Working Group are incorporated and will be cross-referenced as text evolves.
• Patterns and anti-patterns: Practical patterns adopted from the working group (on onboarding, identity, and trust) are now described with recommended approaches.

Open Source Specifications & Interoperability

• Eclipse Foundation specification projects: The text references and aligns with key open-source initiatives (e.g., the Eclipse Dataspace Protocol (DSP)) to ground the Rulebook in specifications used by implementers.
• Interoperability focus: Actionable recommendations for data space design, connector behaviour, and governance to maximize interoperability with community projects.

Testing, Review & Validation

• Review expectations: This PR requests review from the members & chairs of the Rulebook Working Group, Architecture Working Group, IDSA technical staff, and editorial maintainers.

How To Review

• Primary reviewers: Rulebook Working Group representatives, Architecture Working Group liaisons, and contributors familiar with the previous rulebook structure.
• Focus areas: Accuracy of definitions, alignment with referenced standards, practical clarity for implementers, and cross-references to IDSA Manifesto.

Changelog & Files

• Changelog: See the top-level SUMMARY.md and individual chapter headers for a per-file summary of content.
• Files affected: This branch is a full replacement of the legacy rulebook content; reviewers should use the branch diff to inspect specific file-level changes.

Acknowledgements

• Contributors: Thanks to the Rulebook Working Group, editorial contributors, and open-source community whose work informed this revision.

Next Steps

• Iterate on feedback and validate validity of described functional requirements.