mail-address-semantics/mas-v0.1-spec/README.md
tegwick 52140cee9b Register with State Hub; add MAS v0.1 spec bundle, intent and reference-experiment workplan
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 623586@bnt-lap001
Assistant-Session: 10b30928-5b3b-4c11-9934-5ecca07367d8
2026-10-08 00:14:14 +02:00

31 lines
1.3 KiB
Markdown

# 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
- `grammar/mas-v0.1.abnf` — canonical ASCII local-part grammar
- `schema/mas-statute-v0.1.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.