From 41b77c798b51ba3cf23b893831ff06cd034e2cf4 Mon Sep 17 00:00:00 2001 From: Christian Hommrich Date: Thu, 28 May 2026 12:29:01 +0200 Subject: [PATCH] fix(spec): correct header version to 1.2.1, add v1.2.1 changelog entry The spec header still read "1.2.0-draft" even though v1.2.0 and v1.2.1 are tagged releases. A "-draft" suffix on a released version is misleading for anyone reading the spec linked from the project site. Changes: - Header version 1.2.0-draft to 1.2.1 (the latest tagged release; all method-spec commits since the v1.2.1 tag are editorial chore/docs, so no minor or major bump is warranted) - Header date aligned to the v1.2.1 release date (2026-04-22) - Added the missing v1.2.1 changelog entry (the editorial trail-hash reference fix in 6.3 that the tag shipped) Status remains "Draft": this is a W3C Community Group specification, not a ratified standard, so the maturity label stays accurate. Co-Authored-By: Claude --- spec/did-method-trail-v1.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/spec/did-method-trail-v1.md b/spec/did-method-trail-v1.md index 4b69c03..df45446 100644 --- a/spec/did-method-trail-v1.md +++ b/spec/did-method-trail-v1.md @@ -1,11 +1,11 @@ # did:trail Method Specification -**Version:** 1.2.0-draft +**Version:** 1.2.1 **Status:** Draft **Authors:** Christian Hommrich (TRAIL Protocol Initiative) **Contact:** christian.hommrich@trailprotocol.org **Repository:** https://github.com/trailprotocol/trail-did-method -**Date:** 2026-03-04 +**Date:** 2026-04-22 **License:** CC BY 4.0 --- @@ -2238,6 +2238,14 @@ The `OutputAttestationVC` is protocol-agnostic. It can be issued regardless of h ## 16. Changelog +### v1.2.1 (2026-04-22) + +Editorial patch release. No behavioral change for implementations. + +| # | Change | Sections Affected | +|---|--------|-------------------| +| 1 | **Aligned trail-hash reference in §6.3 with the normative definition in §4.5.2** — §6.3 (Hash and Key Rotation Semantics) still referenced `[0:12]`, a leftover from v1.1.0-draft before the 48-bit to 64-bit change. The normative definition in §4.5.2 already used `[0:16]` (16 hex characters, 64 bits) correctly. This patch removes the stale reference. | §6.3 | + ### v1.2.0 (2026-04-21) This release adds normative support for platform-hosted AI agent deployments (Managed Agents). It addresses the structural gap identified in v1.1.0-draft: the assumption that an agent has a persistent identity and can directly interact with the TRAIL Registry does not hold for agents dynamically provisioned per session by third-party platforms.