Grammar, statute schema key pattern, parser (is_resource_type, also used by statute lint), reference parser, spec 6.1 and a new CHANGELOG. Fixtures p1-042..045; prop-case-001 Ticket=PR42 is now invalid. 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
1.4 KiB
1.4 KiB
Mail Address Semantics (MAS) v0.1 — Specification Bundle
This bundle turns the MAS v0.1 concept into an implementable draft.
Contents
SPECIFICATION.md— normative protocol/convention text (revision v0.1.1)CHANGELOG.md— errata applied since v0.1grammar/mas-v0.1.abnf— canonical ASCII local-part grammarschema/mas-statute-v0.1.schema.json— statute discovery document schemaexamples/mas-statute.example.json— example statuteCONFORMANCE.md— parser/generator/statute conformance rulesconformance/addresses.json— positive and negative address fixturesreference/mas_parser.py— small non-normative reference parser
Profiles
- P1 / Naming + Resource: naming hints,
=resource binding,+facet - P2 / Interaction: optional
!interaction preference - P3 / Economic: reserved only;
$and^have no v0.1 semantics
The normative machine grammar is deliberately ASCII-only. SMTPUTF8/Unicode addresses may exist, but Unicode MAS semantics are not part of the canonical v0.1 grammar.
Discovery status
/.well-known/mas is specified here as the intended discovery location.
RFC 8615 requires new well-known URI suffixes to be registered for general
Internet use. Until such registration exists, this path should be considered
a draft/controlled-deployment convention rather than an IANA-registered
Internet-wide well-known URI.