Differences
This shows you the differences between two versions of the page.
| dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture [2026/07/13 12:31] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| Dependency Capture is the controlled process of identifying, | Dependency Capture is the controlled process of identifying, | ||
| - | The process may capture dependency content, identities, versions, source locations, integrity values, licensing information, | + | The process may capture dependency content, identities, versions, source locations, integrity values, licensing information, |
| Dependency Capture supports reproducibility, | Dependency Capture supports reproducibility, | ||
| Line 25: | Line 25: | ||
| Dependency Capture does not necessarily copy every external service or capability. The capture scope identifies which Dependencies can be preserved as transferable content and which require another form of representation or substitution. | Dependency Capture does not necessarily copy every external service or capability. The capture scope identifies which Dependencies can be preserved as transferable content and which require another form of representation or substitution. | ||
| - | A complete Dependency Capture should preserve enough information to identify the captured content and relate it to the process or artefact | + | A complete Dependency Capture should preserve enough information to identify the captured content and relate it to the process or artifact |
| ===== Example ===== | ===== Example ===== | ||