What approach does UAP Document 301 prescribe for cross-referencing related documents?

What approach does UAP Document 301 prescribe for cross-referencing related documents?

• A. Use duplicate IDs and ignore versions.
• B. Cross-reference manually via file names.
• C. Maintain unique persistent IDs; cross-reference related docs with version-aware links.
• D. Do not cross-reference.

Answer: (C)

The key idea is to keep cross-references stable and precise by using unique persistent IDs for each document and linking related documents with their specific, versioned context. Having a unique persistent ID means the document can be identified unambiguously no matter where it moves or how many revisions occur. Pairing that with version-aware links ensures the reference points to the exact version needed, preserving history, traceability, and integrity across related documents. This approach avoids the problems of duplicating IDs (which creates confusion), ignoring versions (which breaks accuracy), or cross-referencing by file names (which is brittle and easy to mismap).

The key idea is to keep cross-references stable and precise by using unique persistent IDs for each document and linking related documents with their specific, versioned context. Having a unique persistent ID means the document can be identified unambiguously no matter where it moves or how many revisions occur. Pairing that with version-aware links ensures the reference points to the exact version needed, preserving history, traceability, and integrity across related documents. This approach avoids the problems of duplicating IDs (which creates confusion), ignoring versions (which breaks accuracy), or cross-referencing by file names (which is brittle and easy to mismap).