[Feature] Add XÖV validation/mapping module #1

New Issue

2026-07-10T22:08:52+02:00

zemion commented

2026-07-10 22:08:52 +02:00

Moved from add-ideas/govoplan-core#127.

Reason: XÖV validation/mapping work belongs to the XÖV module.

Original issue body:

Imported from a backlog-like text file.

Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
Line: 332
Source kind: product
Section: GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform

Imported item:

Add XÖV validation/mapping module.

Moved from add-ideas/govoplan-core#127. Reason: XÖV validation/mapping work belongs to the XÖV module. Original issue body:  Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `332` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform` Imported item: ```text Add XÖV validation/mapping module. ```

zemion referenced this issue from GovOPlaN/govoplan-core

2026-07-10 22:08:56 +02:00

[Feature] Add XÖV validation/mapping module #127

zemion added the area/module-system codex/needs-human module/xoev

priority

p2

source/backlog-import

labels 2026-07-29 14:15:09 +02:00

zemion commented

2026-08-21 14:20:19 +02:00

“XÖV” is a family, so an exact first schema family and version must be selected before implementation.

Decisions required:

first message standard/journey and pinned schema/rule-set versions;
validation-only versus canonical mapping versus bidirectional transformation;
extension policy, unknown-field preservation, code-list resolution, and version-upgrade behavior;
whether invalid messages are rejected, quarantined for review, or accepted with bounded diagnostics.

Manual inputs required:

authoritative schema/code-list packages with redistribution terms, representative valid/invalid fixtures, expected diagnostics, and a conformance target if one exists.

Once selected, the autonomous slice is a sandboxed parser/validator capability with immutable input/rule/result digests, bounded diagnostics, no network fetch during validation, and module-owned documentation.

“XÖV” is a family, so an exact first schema family and version must be selected before implementation. Decisions required: - first message standard/journey and pinned schema/rule-set versions; - validation-only versus canonical mapping versus bidirectional transformation; - extension policy, unknown-field preservation, code-list resolution, and version-upgrade behavior; - whether invalid messages are rejected, quarantined for review, or accepted with bounded diagnostics. Manual inputs required: - authoritative schema/code-list packages with redistribution terms, representative valid/invalid fixtures, expected diagnostics, and a conformance target if one exists. Once selected, the autonomous slice is a sandboxed parser/validator capability with immutable input/rule/result digests, bounded diagnostics, no network fetch during validation, and module-owned documentation.

zemion added

and removed

labels 2026-08-21 14:20:48 +02:00

Sign in to join this conversation.