We're updating the issue view to help you get more done.Learn more

Improve explanation of ATTESTATION in common.change_control

It is not completely clear how ATTESTATIONS should be handled if they are created for
fine-grained parts of the data in a VERSION. If a new version is created in which some
part (say an ENTRY in a COMPOSITION) was not changed, and had been specifically attested
in the previous version, then the attestation of that part would have to be logically
referred to by the equivalent part in the new version. No statement can be made about
how this is done physically, since implementations could work by creating copies
or by referring to literally the same attestation object in a singleton pattern.

Status

Assignee

JeffJ

Reporter

JeffJ

Change Description

Provide a more detailed description for how ATTESTATION is handled when used for fine-grained parts of the data of a VERSION.

Approved By

PG

Components

Fix versions

Priority

Trivial