aceability. Subsection 4.2.1 requires that the 
components of an AIP be suitably bound and identified for long-term management, but 
places no restrictions on how AIPs are identified with files. Thus, in the general case, an AIP 
may be distributed over many files, or a single file may contain more than one AIP. 
Therefore identifiers and filenames may not necessarily correspond to each other. 
Documentation must represent these relationships. 
4.2.5 The repository shall have access to necessary tools and r