@openvtc/trust-tasks 0.16.0 → 0.16.1
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 +38 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,44 @@ 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.16.1 — 2026-08-27
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Other
|
|
18
|
+
|
|
19
|
+
- Say what identifierScope is, and that it is not a scope taxonomy (#317)
|
|
20
|
+
|
|
21
|
+
Carries the framework text of trustoverip/dtgwg-trust-tasks-spec#6 into
|
|
22
|
+
this repository's copy of SPEC.md, and aligns the meta-schema
|
|
23
|
+
description with it.
|
|
24
|
+
|
|
25
|
+
Addresses trustoverip/dtgwg-trust-tasks-spec#5: the framework's
|
|
26
|
+
identifierScope and the DTG credentials specification's proposed
|
|
27
|
+
declared correlation scope (trustoverip/dtgwg-cred-spec#22) read as two
|
|
28
|
+
vocabularies for one axis, with `community` and `linked` unmappable
|
|
29
|
+
here. They are not competing, and neither document said so.
|
|
30
|
+
|
|
31
|
+
identifierScope is a machine-readable restatement of §10.5 item 1,
|
|
32
|
+
which is binary: relationship-scoped, or reused across relationships
|
|
33
|
+
and justified. It is not a taxonomy of correlation width. It is
|
|
34
|
+
declared by a specification about a party role, not by a holder about
|
|
35
|
+
an identifier it controls, so the two are assertions about different
|
|
36
|
+
subjects and neither overrides the other. An identifier recognisable
|
|
37
|
+
within a bounded set is, for item 1's purposes, cross-relationship, so
|
|
38
|
+
it is declared `public` and carries the justification obligation in
|
|
39
|
+
full.
|
|
40
|
+
|
|
41
|
+
The meta-schema change is to the `description` string only. The enum
|
|
42
|
+
stays at three values, so all 56 existing declarations remain valid,
|
|
43
|
+
and spec.meta.schema.json is excluded from both binding generators by
|
|
44
|
+
name — scripts/build-ts-bindings.mjs via NOT_PAYLOAD_SCHEMAS, and
|
|
45
|
+
trust-tasks-codegen, which walks payload.schema.json only. No generated
|
|
46
|
+
binding, crate, or package is affected, and no version bump is needed.
|
|
47
|
+
|
|
48
|
+
npm run validate: 349 specs, no errors. Registry build clean.
|
|
49
|
+
|
|
50
|
+
Signed-off-by: Glenn Gore <glenn.gore@gmail.com>
|
|
51
|
+
|
|
14
52
|
## 0.16.0 — 2026-08-27
|
|
15
53
|
|
|
16
54
|
|