Call for Consensus (deadline: 2026-09-15, 00:00UTC)

Dear RecordWeb Community Group,

This is a new Call for Consensus (CfC) of the RecordWeb Community Group with a 14-day discussion period under GOVERNANCE.md §4.1 starts now.

Please review and comment on the issues in CfC#4

Deadline: 2026-09-15, 00:00UTC

How to participate
- Substantive discussion, concerns, and suggested edits belong in comments on the relevant issue. That is where the specification text is developed.
- On **this** issue, react with 👍 if you support closing this CfC with the current or consensus-amended text of all eight issues once the deadline passes.
- If you object to adopting one or more issues, a 👍/👎 reaction alone is not sufficient. Please add a comment on this issue before the deadline that identifies the affected issue or issues and explains the technical rationale. Detailed proposed edits should be made on the respective issue.
- The conformance issues are intentionally presented as one architectural set. Comments that affect profiles, roles, the conformance matrix, ConformanceRecords, or Source Integration should identify consequences for the other issues in that set.
- Silence is not treated as an objection. Active review is particularly welcome from implementers, records and case-management practitioners, connector developers, procurement specialists, security experts, and institutional adopters.

What happens next
After the deadline has passed, the Editor (or a Chair, if no Editor is assigned) will summarise the outcome in the associated CfC tracking issue. If consensus is reached, the proposed text is merged. If consensus cannot be reached, the Chairs will decide and document the reasoning in the relevant issue, in accordance with GOVERNANCE.md §4.1.

Thank you for engaging with this second round.

Best regards,
Nik Jenzer
Co-Chair, RecordWeb Community Group