You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/file_hierarchy_for_the_verification_of_os_artifacts.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -229,7 +229,7 @@ Each of the following identifiers represents a subdirectory layer in that hierar
229
229
The _os_ identifier is used to uniquely identify an Operating System (OS).
230
230
231
231
The identifier relies on data provided by the ubiquitous [os-release].
232
-
The following keywords are understood and their value format follows that established by [os-release] (i.e. no spaces and no characters outside of `0–9`, `a–z`, `"."`, `"_"` and `"-"` are allowed):
232
+
The following keywords are understood and their value format follows that established by [os-release] (i.e. no spaces and no characters outside of `0–9`, `a–z`, `"."`, `"_"`, and `"-"` are allowed):
233
233
234
234
-`ID`: name of OS (e.g. `arch` or `debian`)
235
235
-`VERSION_ID`: the version of the OS (e.g. `1.0.0` or `24.12`)
@@ -280,7 +280,7 @@ Either two or one _purpose_ directories may exist per _role_:
280
280
- One directory which contains _artifact verifiers_ (e.g. `package`), and a second directory which contains the corresponding _trust anchors_ (e.g. `trust-anchor-package`).
281
281
- Just one directory which contains _artifact verifiers_ (e.g. `package`).
282
282
283
-
The _purpose_ directory name must not contain characters outside of `0–9`, `a–z`, `"."`, `"_"` and `"-"`.
283
+
The _purpose_ directory name must not contain characters outside of `0–9`, `a–z`, `"."`, `"_"`, and `"-"`.
284
284
VOA implementations must not consider invalid directories and should raise a warning if such a directory is encountered.
285
285
286
286
##### Two purpose directories: Verification relying on trust anchors
@@ -339,7 +339,7 @@ Specific examples for **context** are
339
339
340
340
If no specific context is required, the **context** directory `default` must be used.
341
341
342
-
Analogous to the os-release data, **context** strings may only contain `[a-z]`, `[0-9]`, `_`, `.` and `-`.
342
+
Analogous to the os-release data, **context** strings may only contain `[a-z]`, `[0-9]`, `_`, `.`, and `-`.
343
343
344
344
For more in-depth discussion on the use of the _context_ identifier, see the [examples] section.
345
345
@@ -358,7 +358,7 @@ Further specification work is required before implementing further technologies.
358
358
Each technology specifies file suffixes for verifiers.
359
359
Note that these suffixes may overlap.
360
360
361
-
A _technology_ directory name must not contain characters outside of `0–9`, `a–z`, `"."`, `"_"` and `"-"`.
361
+
A _technology_ directory name must not contain characters outside of `0–9`, `a–z`, `"."`, `"_"`, and `"-"`.
362
362
VOA implementations must not consider invalid directories and should raise a warning if such a directory is encountered.
0 commit comments