From 95cae6d26ae628c0fbe19860e148d03b45b624b5 Mon Sep 17 00:00:00 2001 From: tegwick Date: Sun, 18 Oct 2026 17:46:06 +0200 Subject: [PATCH] MAS-WP-0005-T01: SCP-2 decided (lower-case resource types); SCP-6 direction noted Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 252470@bnt-lap001 Assistant-Session: ad628c8f-4be2-4979-94c9-76c7ed6f8241 --- docs/spec-change-proposals.md | 3 +++ workplans/MAS-WP-0005-spec-errata-v0-1-1.md | 8 +++++++- 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/spec-change-proposals.md b/docs/spec-change-proposals.md index 228210a..df4917f 100644 --- a/docs/spec-change-proposals.md +++ b/docs/spec-change-proposals.md @@ -42,6 +42,9 @@ does not parse. A new conformance fixture should record the equivalence. registers lower-case type names. The address parses but can never match a declared type, even under `ascii-insensitive`. +**Decision (founder, 2026-10-18): option (a).** Resource types are +lower-case in the grammar. + **Options:** - **(a) recommended:** restrict `resource-type` in the grammar to lower-case ALPHA, DIGIT and `-`. `Ticket=PR42` then parses as an opaque target, which diff --git a/workplans/MAS-WP-0005-spec-errata-v0-1-1.md b/workplans/MAS-WP-0005-spec-errata-v0-1-1.md index ab11fb4..8b3614d 100644 --- a/workplans/MAS-WP-0005-spec-errata-v0-1-1.md +++ b/workplans/MAS-WP-0005-spec-errata-v0-1-1.md @@ -26,7 +26,7 @@ copies, the fixtures and the implementation together. ```task id: MAS-WP-0005-T01 -status: todo +status: progress priority: high state_hub_task_id: "10c0433a-9b25-5b62-987f-2be7e9d49df2" ``` @@ -34,6 +34,12 @@ state_hub_task_id: "10c0433a-9b25-5b62-987f-2be7e9d49df2" Walk through SCP-1 to SCP-7, settle the open options (SCP-2 (a) or (b), SCP-6 split rules), and record which proposals are accepted. +- 2026-10-18: SCP-2 decided as option (a): resource types are lower-case + in the grammar. SCP-6 is under discussion. Founder direction: `=` stays + canonical and `--` is accepted as a replacement only for endpoints that + refuse `=`. A transform profile per recipient/destination may be needed + when something we send out must match that destination's requirements. + ## v0.1.1 errata ```task