Standards
Bakau uses existing standards and invents none, apart from its own record format. This page says what it reads and writes today, which versions, when each was last checked, and what is only an aim.
Built today
Where each is produced now. The audit runs on a client's machine and writes files. The registry is frozen, and its signal endpoints are code with tests, not served on bakau.org while the registry is off.
| Standard | Version | Last verified | In audit output | In the frozen registry |
|---|---|---|---|---|
| ISCC | ISO 24138:2024, via iscc-core | — | Writes Content, Data and Instance codes for every image, in report.json and report.csv; also shown by the public preview. | Stored with each claim. |
| EXIF, IPTC, XMP, PLUS | As embedded in files | — | Reads creator, credit, copyright and usage-terms fields, quoted as found; also shown by the public preview. | — |
| OpenTimestamps | Calendar protocol | — | Writes anchor.json, the filing of the report's Merkle root
(--anchor). The sample report's filing. |
Anchors claim batches. /anchor/{batch}.json Tested, not served on bakau.org |
| TDMRep | W3C CG final, 2024-02-02 | 2026-07-15 | Writes signals/tdmrep.json from the client's stated terms
(--signals). |
/.well-known/tdmrep.json, tdm-reservation header Tested, not served on bakau.org |
| IETF AI preferences, vocabulary | draft-ietf-aipref-vocab-08 (2026-09-14) | 2026-09-15 | Writes Content-usage lines for the client's robots.txt
in signals/robots.txt (--signals). |
Content-Usage header, Content-usage rules in /robots.txt Tested, not served on bakau.org |
| IETF AI preferences, attachment | draft-ietf-aipref-attach-05 (2026-08-19) | 2026-09-15 | ||
| RSL | 1.0 | 2026-07-15 | Writes signals/rsl.xml (--signals). |
/rsl.xml, /work/{work-id}/rsl.xml Tested, not served on bakau.org |
| Record API | v1 (Bakau's own) | — | — | A JSON record per registered work. /api/v1/works/{work-id} Tested, not served on bakau.org |
Signal drafts from an audit are the client's own statements: every image is reserved, and a permission the client states is signalled only for images whose metadata names the client as the one rights holder (DECISIONS #096).
The AI-preference drafts are still changing; they are checked again before the registry's signals are served. Where a format can say less than the terms, the signal says less: a fee for training is published as "not permitted as offered", with a link to the terms, never as "allowed".
Direction
Aims, not features. None of these is built.
- Writing TDM·AI declarations. Liccium's TDM·AI binds rights reservations to ISCC codes. Bakau already computes the same codes, so declarations could be written from a catalogue's records.
- C2PA. Reading manifests where files carry them, as one more piece of evidence, and writing them from creative-app extensions. Manifests can be stripped, so they add to digital fingerprints rather than replace them.
- An attribution layer for RSL licence servers. RSL licenses content at the publisher level. Per-image matching could say whose images a licence covers, so the people who made them can be paid.