From 9cbec37685a9d893fae14b768c54487f6e21d5ac Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michael=20Mur=C3=A9?= Date: Wed, 8 Jan 2025 21:14:30 +0100 Subject: [PATCH] container: no extra keys in the packaging allowed --- pkg/container/SPEC.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/pkg/container/SPEC.md b/pkg/container/SPEC.md index 9f92720..7cd6d5d 100644 --- a/pkg/container/SPEC.md +++ b/pkg/container/SPEC.md @@ -27,7 +27,9 @@ The UCAN spec itself is transport agnostic. This specification describes how to UCAN tokens, regardless of their kind ([Delegation], [Invocation], [Revocation], [Promise]) MUST be first signed and serialized into DAG-CBOR bytes according to their respective specification. As the token's CID is not part of the serialized container, any CID returned by this operation is to be ignored. -All the tokens' bytes MUST be assembled in a [CBOR] array, which is then inserted as the value under the `ctn-v1` string key, in a CBOR map. The ordering of tokens in the array MUST NOT matter. Also, this array SHOULD NOT have duplicate entries. +All the tokens' bytes MUST be assembled in a [CBOR] array. The ordering of tokens in the array MUST NOT matter. This array SHOULD NOT have duplicate entries. + +That array is then inserted as the value under the `ctn-v1` string key, in a CBOR map. There MUST NOT be other keys. For clarity, the CBOR shape is given below: