Update docs about the dropped Tagus support#27
Open
noVaSon wants to merge 2 commits intoeclipse-xfsc:mainfrom
Open
Update docs about the dropped Tagus support#27noVaSon wants to merge 2 commits intoeclipse-xfsc:mainfrom
noVaSon wants to merge 2 commits intoeclipse-xfsc:mainfrom
Conversation
…ove-tagus-support Reflect the removed Tagus support
|
8 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the architecture documentation to reflect that the Federated Catalogue no longer supports the earlier Gaia-X trust framework generations (Elbe and Tagus). The documentation now describes the current state — VC 2.0 with JWT signatures only — rather than maintaining parallel descriptions of removed code paths.
What changed
Verification pipeline — Removed all references to Linked Data proof verification (URDNA2015,
JsonWebSignature2020) and the three-path format detection model. The building block view and runtime view now describe a single JWT-based verification path. Flowcharts and sequence diagrams simplified accordingly.ADR 9 — Rewritten from "namespace coexistence" to "removal of Tagus support". Documents the decision to drop VC 1.1 and Tagus-era namespaces, with a clear migration warning that the catalogue rejects these formats with an exception — not a graceful deprecation.
Glossary — Tagus entry updated to reflect it is no longer supported.
Examples — Appendix query examples migrated from VC 1.1 /
gax-trust-framework:to VC 2.0 /gx:2511#.References — VC Data Model footnote updated from v1.1 to v2.0.
📋 Checklist