coulomb/mail-address-semantics
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
mail-address-semantics/mas-v0.2-spec/README.md
tegwick a12e1c4370 MAS-WP-0005-T07: v0.2 draft bundle; mas_core accepts v0.1 and v0.2 statutes 
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 22:19:34 +02:00

1.4 KiB
Raw Blame History

Mail Address Semantics (MAS) v0.2 (draft) — Specification Bundle

This bundle is the draft of MAS v0.2. It extends v0.1.1 (see CHANGELOG.md).

Contents

  • SPECIFICATION.md — normative protocol/convention text (v0.2 draft)
  • CHANGELOG.md — errata applied since v0.1
  • grammar/mas-v0.2.abnf — canonical ASCII local-part grammar (unchanged from v0.1.1)
  • schema/mas-statute-v0.2.schema.json — statute discovery document schema
  • examples/mas-statute.example.json — example statute
  • CONFORMANCE.md — parser/generator/statute conformance rules
  • conformance/addresses.json — positive and negative address fixtures
  • reference/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.