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 f07576451a MAS v0.2 final (MAS-WP-0009 finished); residual MAS-WP-0014 
Founder decision after the second implementation: close the two open gaps,
then declare v0.2 final. Section 13: parsers MUST reject over 64 octets
(fixtures p1-050/051); section 8: equivalence is between targets, key format
not normative. Draft markers removed, CHANGELOG dated 2026-10-19,
MAS_VERSION 0.2, mas_conformance vendors the v0.2 addresses.json. Mode
contract v0.1 stays draft: MAS-WP-0014 (independent email side).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 5787@bnt-lap001
Assistant-Session: 5db26b82-138b-40cc-9856-4d5eb0f752fd
2026-10-19 13:35:10 +02:00

1.6 KiB
Raw Blame History

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

This bundle is MAS v0.2, final as of 2026-10-19. It extends v0.1.1 (see CHANGELOG.md). Two independent implementations pass its fixtures unchanged: mas_core (Python) and impl/js (JavaScript).

Contents

  • SPECIFICATION.md — normative protocol/convention text (v0.2)
  • 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
  • conformance/statute-aware.json — v0.2 stand-in, equivalence and destination-transform cases
  • 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.2 semantics

The normative machine grammar is deliberately ASCII-only. SMTPUTF8/Unicode addresses may exist, but Unicode MAS semantics are not part of the canonical 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.