Skip to content

docs(arc42): federated catalogue — content verification and decoupling sweep#45

Open
noVaSon wants to merge 3 commits into
eclipse-xfsc:mainfrom
federated-catalogue-enhancements-2026:2026-fce-content-verification-sweep
Open

docs(arc42): federated catalogue — content verification and decoupling sweep#45
noVaSon wants to merge 3 commits into
eclipse-xfsc:mainfrom
federated-catalogue-enhancements-2026:2026-fce-content-verification-sweep

Conversation

@noVaSon
Copy link
Copy Markdown
Contributor

@noVaSon noVaSon commented May 29, 2026

🚀 Summary

Sweep across the arc42 architecture document for the federated catalogue to make it more durable as a reference for new contributors and maintainers. Three passes were applied in order: (1) decouple the prose from implementation detail — SQL DDL, Liquibase changeset names, HTTP status codes in prose, federated-catalogue.*=value property pins, /latest/ Gaia-X links — replaced with conceptual descriptions that point at the OpenAPI spec, the wiki Installation & Configuration Guide, and the Liquibase changelog as the actual sources of truth; (2) a linear-readability pass that added chapter leads, fixed a handful of broken <<…>> cross-references and an anchor typo, repaired a garbled section opener in chapter 6, documented the gap in ADR numbering (10 → 15), and extended the glossary with SRS, EVC/EVP, Audit Shadow, Provenance Credential, and RDF-star entries; (3) follow-up work on out-of-order definitions in chapter 5 (forward pointers to GraphStore, the trust-framework-bundle / base-class concept, and RdfClaim) and a carve-out of the Keycloak operator cookbook from chapter 7 into the wiki Administration Guide, leaving a four-point architectural framing behind.

Side effects: Gaia-X external links pinned per Loire sub-document (Architecture 25.05, ICAM 24.07, Compliance 25.10, Data Exchange 25.07, Ontology 25.11) so a future Gaia-X release does not silently reinterpret statements authored against Loire; appendix example-query links repaired and verified against the source repository; example credential timestamps replaced with illustrative placeholders; the Loire / Danube / `danubetech` library naming collision is now disambiguated in chapter 4.

✅ What's Changed

  • Documentation updated
  • Feature implemented / Bug fixed
  • Tests added or updated
  • Code formatted and linted

🧪 How to Test

  1. Build the architecture document locally (or via the `buildDocs` workflow in `eclipse-xfsc/docs`) and confirm it builds cleanly without AsciiDoctor warnings.
  2. Skim the rendered HTML / PDF top-to-bottom as a first-time reader; each chapter should now open with a short orienting paragraph and the chapter-5 forward references should resolve to a downstream section.
  3. Spot-check every external link in chapter 3 (Gaia-X document set), chapter 7 (wiki Administration Guide, wiki Configuration Guide), and chapter 13 (example-query files under `eclipse-xfsc/federated-catalogue/examples/queries/`) — all should resolve to a live target.
  4. Search the chapters for `HTTP 4`, `federated-catalogue.`, `admin_config`, `assets_aud`, `/latest/`, `Liquibase changeset \``, and `Jena 5.5`; results should be limited to the documented historical or operator-facing exceptions (e.g. config-name table in the wiki Configuration Guide).
  5. Verify cross-references with `grep -nE '<<[a-z_]+'` and confirm every anchor exists.
  6. Open the Keycloak section of chapter 7 and confirm it reads as architectural framing only; the step-by-step Keycloak procedures should now live in the wiki FC Administration Guide.

🔍 Related Issues

Closes #
Related to #

📸 Screenshots (if applicable)

📋 Checklist

  • I've tested my code locally
  • I've added tests if needed
  • I've updated documentation if necessary
  • My changes follow the project's coding style

noVaSon added 3 commits May 29, 2026 14:35
…ementation detail

Sweep the official architecture documentation under docs/federated-catalogue/
to make it durable against implementation churn:

- terminology: title and lead use XFSC; GXFS retained only as dated
  historical provenance; new glossary entry for GXFS vs XFSC; Loire
  vs Danube + danubetech library naming collision clarified in Ch.4
- references: Gaia-X links pinned per Loire sub-document (Architecture
  25.05, ICAM 24.07, Compliance 25.10, Data Exchange 25.07, Ontology
  25.11), no /latest/; cross-repo example links absolute and verified
  against origin/main; example credential timestamps replaced with
  illustrative placeholders
- decoupling: SQL DDL tables, Liquibase changeset IDs, sequence names,
  HTTP status codes, property-name=value pins, and inline OpenAPI paths
  in prose replaced with conceptual descriptions; Ch.7 references the
  wiki Installation & Configuration Guide as the canonical config source
- ADR hygiene (Ch.9): SRS story IDs, internal PR numbers, `admin_config`
  column references, and property-name pins removed in favour of concept
  statements; ADR-4 enrichment rewritten free of column-level detail
Final readability pass over the federated-catalogue architecture docs:

- add or strengthen chapter leads (Ch.2, 3, 4, 5, 8, 9, 10)
- fix broken/non-standard internal xrefs and an anchor typo
- repair a garbled section opener in Ch.6
- explain the ADR numbering gap (10 → 15) in Ch.9
- mark Ch.1 historical assumptions as provenance, not current spec
- extend the glossary with SRS, EVC/EVP, Audit Shadow, Provenance
  Credential, and RDF-star
- add a glossary pointer and inline glosses in Ch.4 for forward terms
- Ch.5: add forward pointers for RoutingGraphStore/GraphStore,
  baseClass + trust-framework bundle, and RdfClaim
- Ch.7: replace the Keycloak admin-UI cookbook (realm directories,
  iframe headers, console URL override) with a 4-point architectural
  framing and a link to the wiki Admin Guide
- wiki: extend FC-Administration-Guide with the carved-out Keycloak
  realm + iframe-header + Admin Console URL procedures
@sonarqubecloud
Copy link
Copy Markdown

@noVaSon noVaSon requested a review from Sw3eks May 29, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant