mail-address-semantics/mas-v0.1-spec/CHANGELOG.md
tegwick f5848a75b7 MAS-WP-0005-T02: SCP-5 and SCP-7 spec text; v0.1.1 errata complete
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 252470@bnt-lap001
Assistant-Session: ad628c8f-4be2-4979-94c9-76c7ed6f8241
2026-10-18 18:18:59 +02:00

36 lines
1.6 KiB
Markdown

# MAS specification changelog
- **SCP-1, quoted equivalence.** A quoted local-part whose content is a
valid canonical MAS local-part (no quoted-pairs) is equivalent to the
unquoted form. Receivers treat them identically; generators emit the
unquoted form; canonical parsers still reject the quoted form (§4).
Fixture p1-040 note updated.
## v0.1.1 (errata)
Errata from the reference experiment and the live provider test
(mail-address-semantics MAS-WP-0002/0003). Proposals and evidence:
`docs/spec-change-proposals.md` in the implementation repository.
- **SCP-2, resource types are lower-case.** `resource-type` is now
lower-case words of `a-z`/`0-9` joined by single `-` or `_` (§6.1,
grammar, statute schema `resource_types` key pattern). `Ticket=PR42`,
`my--type=X` and `type-=X` are no longer canonical. New fixtures: p1-042
to p1-045.
- **SCP-3, type intake.** Address registry entries may carry
`intake_for: TYPE` (statute schema). This explicitly makes a function
address the intake for a declared resource type (§7). An opaque target
equal to a type name has no intake semantics without it.
- **SCP-5, intake auto-reply bounds.** New §14 item 10: auto-replies to
intake or interaction addresses SHOULD require an authenticated sender,
MUST be volume-bounded, and MUST NOT go to automated mail.
- **SCP-7, case-robust identifiers (recommendation).** §6.2: generators
SHOULD use identifiers whose meaning does not depend on case, and
receivers SHOULD match them case-insensitively. The statute field
`resource_id_case` is deferred to v0.2.
## v0.1
Initial draft.