PEP 740: clarify that provenance is nullable (#3906)
Signed-off-by: William Woodruff <william@yossarian.net>
This commit is contained in:
parent
5ab4c64d7e
commit
7fbacdcd9d
|
@ -235,9 +235,9 @@ The following changes are made to the
|
||||||
* When an uploaded file has one or more attestations, the index **MAY**
|
* When an uploaded file has one or more attestations, the index **MAY**
|
||||||
include a ``provenance`` key in the ``file`` dictionary for that file.
|
include a ``provenance`` key in the ``file`` dictionary for that file.
|
||||||
|
|
||||||
The value of the ``provenance`` key **SHALL** be a JSON string, which
|
The value of the ``provenance`` key **SHALL** be either a JSON string
|
||||||
**SHALL** be the SHA-256 digest of the associated ``.provenance`` file,
|
or ``null``. If ``provenance`` is not ``null``, it **SHALL** be the SHA-256
|
||||||
as in the Simple Index.
|
digest of the associated ``.provenance`` file, as in the Simple Index.
|
||||||
|
|
||||||
See :ref:`appendix-3` for an explanation of the technical decision to
|
See :ref:`appendix-3` for an explanation of the technical decision to
|
||||||
embed the SHA-256 digest in the JSON API, rather than the full
|
embed the SHA-256 digest in the JSON API, rather than the full
|
||||||
|
|
Loading…
Reference in New Issue