22 lines
910 B
Markdown
22 lines
910 B
Markdown
# Marketplace ID prefixes v1
|
|
|
|
Canonical prefixes:
|
|
|
|
| Prefix | Object | Example |
|
|
| --- | --- | --- |
|
|
| `op_` | Operator ID | `op_m2core` |
|
|
| `prop_` | Proposal ID | `prop_01j2abc` |
|
|
| `lst_` | Listing ID | `lst_mm-pdf-report` |
|
|
| `sub_` | Fedlearn submission ID | `sub_01j2candidate` |
|
|
| `clu_` | Fedlearn cluster ID | `clu_01j2cluster` |
|
|
| `core_` | Promoted core learning ID | `core_01j2learning` |
|
|
|
|
Rules:
|
|
|
|
- Operators use `op_<slug>` everywhere. Bare names such as `m2bd` or `sdjs-operator` are display
|
|
names, not marketplace IDs.
|
|
- Proposals use `prop_`, never `prp_`.
|
|
- Listings use `lst_` and control price, visibility, version, and license grants.
|
|
- Solution manifests keep `sol_` for `solution_id`; this is already frozen in schema and is not
|
|
a replacement for `lst_` in Store links or ledger refs.
|
|
- Ledger transaction groups, grants, accounts, and jobs keep S1-owned prefixes outside this file.
|