@openvtc/trust-tasks 0.28.24 → 0.28.25
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +23 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,29 @@ The package versions over **its own API** — what a consumer compiles against
|
|
|
11
11
|
not over `SPEC.md`. Below 1.0 a breaking change bumps the leading non-zero
|
|
12
12
|
component.
|
|
13
13
|
|
|
14
|
+
## 0.28.25 — 2026-11-09
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Documentation
|
|
18
|
+
|
|
19
|
+
- **vta/dids**: Did:webs is eligible with the key-role designation extension (#1070)
|
|
20
|
+
|
|
21
|
+
* docs(vta/dids): did:webs is eligible with the key-role designation extension
|
|
22
|
+
|
|
23
|
+
The did:webs method profile declared the method ineligible as published
|
|
24
|
+
(criteria 4 and 6: no controller-chosen relationships, no room for
|
|
25
|
+
keyRoles or revoked) and recommended an extension A: role keys anchored in
|
|
26
|
+
the KEL, rendered into their roles' relationships with keyRoles and
|
|
27
|
+
revoked, key-state keys in no relationship. affinidi-did-webs 0.9.1
|
|
28
|
+
implements it as a key-role designation (an anchored ACDC), proposed to
|
|
29
|
+
the did:webs specification.
|
|
30
|
+
|
|
31
|
+
The profile now states the status as eligible with that extension and
|
|
32
|
+
ineligible without it, and renders §4 as built: the record's schema and
|
|
33
|
+
attributes, one standing record, accumulated revocations, the document's
|
|
34
|
+
members, the fail-closed checks. It states the interop caveat: a resolver
|
|
35
|
+
without the extension refuses the published did.json.
|
|
36
|
+
|
|
14
37
|
## 0.28.24 — 2026-11-09
|
|
15
38
|
|
|
16
39
|
|