Initial implementation of the DateKeys Protocol v0.8.1
Reference implementation in Go, built from the implementation plan
(milestones M0 to M5): datekey, profile, provider, codec, agewrap,
extension, capsule, accesskey, the datekeys CLI, official vectors and
fixtures, the mutation corpus, fuzz targets, interop and live tests,
CI workflows, traceability and policy documents.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 weeks ago
|
|
|
# Trademarks
|
|
|
|
|
|
|
|
|
|
"DateKeys" is a reserved name of the DateKeys project. The Apache-2.0 license
|
|
|
|
|
of the code and the CC-BY-4.0 license of the specification do not grant any
|
|
|
|
|
right to use it as a product, service or organisation name (Apache-2.0 §6).
|
|
|
|
|
|
|
|
|
|
Allowed without asking:
|
|
|
|
|
|
|
|
|
|
- Stating compatibility in plain words, for example "implements the DateKey
|
|
|
|
|
protocol", "reads and writes DateKeyCap (.dkc) files" or "compatible with
|
|
|
|
|
DateKeys v0.8.2", as long as it is true for the version named.
|
Initial implementation of the DateKeys Protocol v0.8.1
Reference implementation in Go, built from the implementation plan
(milestones M0 to M5): datekey, profile, provider, codec, agewrap,
extension, capsule, accesskey, the datekeys CLI, official vectors and
fixtures, the mutation corpus, fuzz targets, interop and live tests,
CI workflows, traceability and policy documents.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 weeks ago
|
|
|
- Referring to this project, its specification or its file formats by name in
|
|
|
|
|
documentation, articles and talks.
|
|
|
|
|
|
|
|
|
|
Not allowed without written permission:
|
|
|
|
|
|
|
|
|
|
- Naming a product, service, package, domain or organisation "DateKeys" or a
|
|
|
|
|
confusingly similar name.
|
|
|
|
|
- Suggesting endorsement by, or affiliation with, the DateKeys project.
|
|
|
|
|
- Calling a modified or incompatible implementation "DateKeys".
|