Implementations
Every known implementation, on identical terms, in alphabetical order. The reference implementation is marked and receives no other distinction.
Every known implementation of AKP is listed here on identical terms, whether it is commercial, independent, complete or partial. The reference implementation is marked as such and receives no other distinction.
The order is alphabetical by name and is applied mechanically when this page is built. No implementation can be advantaged by its position, and the ordering is not a ranking, an endorsement or an assessment of quality.
| Implementation | Maintainer | Language | Capability | Licence | Targets specification | Conformance |
|---|---|---|---|---|---|---|
| akp-core Reference implementation The reference implementation. It exists to discover the information model, so it is expected to lead the specification rather than follow it. | Stemmar | Rust | Reader, writer, validator | Open source; licence to be confirmed | 1.0-rc (candidate) | No conformance claim is made. SPEC-0001 §11 now defines what conformance means for a reader, a producer and an artifact, but the suite that would test a claim does not exist yet — so no claim is made, including by the reference implementation. |
What the conformance column means§
At present it means nothing, and it says so. There is no conformance test suite yet and no published definition of what an AKP conformance claim asserts — see conformance claims. Until they exist, no entry on this page carries a conformance claim, including the reference implementation.
When the suite exists, this column will record which profile an implementation passes and against which specification version, and the evidence will be reproducible by anyone who downloads the suite.
Adding an implementation§
Send the change controller the following, or open a pull request against the site repository:
- The name of the implementation and the language it is written in.
- Who maintains it.
- Whether it reads, writes, or validates AKP artifacts, and which parts it does not implement.
- Its licence.
- Which specification version it targets.
There is no review of quality, no fee, no approval step and no requirement to be related to this project in any way. An implementation is listed because it exists. The only entries that will be refused are ones that cannot be shown to exist.
Partial implementations are welcome and should say what they do not do. A reader that handles manifests and knowledge objects but ignores embeddings entirely is a legitimate implementation of a format whose embeddings are explicitly optional, and describing it accurately is more useful than describing it generously.
Why this list matters§
The specification's own test of success is that somebody implements it from the published document alone, without contacting anyone, and interoperates. Until this page has an entry that was written by someone outside this project, that test has not been passed and the format's interoperability claim is unproven.
A page listing one implementation is an honest statement of where the format currently stands.