ACDP Registries
This directory tracks the well-known identifiers used in ACDP. Each registry is a Markdown table; entries are added via PR.
| Registry | File | Authority RFC |
|---|---|---|
| Anchor schemes | anchor-schemes.md | RFC-ACDP-0016 §9 |
| Authentication methods | auth-methods.md | RFC-ACDP-0007, RFC-ACDP-0008 |
| Context types | context-types.md | RFC-ACDP-0002 §5 |
| DataRef types | data-ref-types.md | RFC-ACDP-0002 §6 |
| Error codes | error-codes.md | RFC-ACDP-0007 |
| Implementation profiles | profiles.md | RFC-ACDP-0001 §9.1 |
| Lifecycle event types | lifecycle-event-types.md | RFC-ACDP-0013 §4, §7.3 |
| Locator schemes | locator-schemes.md | RFC-ACDP-0002 |
| Media types | media-types.md | RFC-ACDP-0001 |
| Signature algorithms | signature-algorithms.md | RFC-ACDP-0001 §5.10 |
Status values
| Status | Meaning |
|---|---|
Proposed | Suggested in an open RFC or PR. Not yet merged. |
Provisional | Merged but not yet shipped in two interoperating implementations. |
Stable | Two interoperating implementations confirmed. Backwards-compatible additions only. |
Deprecated | Retained for archaeology. New implementations MUST NOT depend on it. |
Naming conventions
- Context type identifiers are lowercase for standard types — snake_case historically, with hyphens permitted since 0.3.0 (
key-revocation, matching the custom-type<type>grammar^[a-z][a-z0-9_-]*$); namespaced custom types use<namespace>:<type>(e.g.science:experiment-replication). - Lifecycle event types are lowercase snake_case matching
^[a-z][a-z0-9_]*$. - Error codes use lowercase snake_case.
- Locator scheme identifiers use dotted-namespace form (e.g.
kafka.offset). - Anchor scheme identifiers use dotted-namespace form (e.g.
macp.commitment). - Experimental identifiers SHOULD use a vendor-prefixed reverse-domain name (e.g.
com.example.feature).