Skip to content

Commit 4dd279b

Browse files
committed
Clarify "paths" and "path_hash_prefixes"
Clarify "paths" and "path_hash_prefixes" in delegations, because currently, it's not properly defined which of these options can be used to create a valid target file: - BOTH paths and path_hash_prefixes - ONLY ONE of paths and path_hash_prefixes - NONE of paths and path_hash_prefixes With this change, I aim to define clearly that a valid target file will contain ONLY ONE of them or NONE of them. Signed-off-by: Martin Vrachev <[email protected]>
1 parent 2a8d459 commit 4dd279b

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

tuf-spec.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1021,9 +1021,8 @@ format:
10211021
package that are not made by the delegated party or its descendants to be
10221022
ignored.
10231023

1024-
In order to discuss target paths, a role MUST specify only one of the
1025-
<a>"path_hash_prefixes"</a> or <a for="delegation-role">"paths"</a> attributes, each of which we
1026-
discuss next.
1024+
The <a>"path_hash_prefixes"</a> and <a for="delegation-role">"paths"</a>
1025+
attributes are OPTIONAL, if used, exactly one of them should be set.
10271026

10281027
: <dfn>"path_hash_prefixes"</dfn>
10291028
::

0 commit comments

Comments
 (0)