index.md
HTML wrapper for HTML-only fetchers; content is shown verbatim.
Raw file
Links (extracted)
Clickable list for reviewers; avoids copy/paste line-wrap issues.
# URN:NBN as a carrier for if.trace (if.bus preview one-pager)
**Audience:** preview cohort
**Reality gate:** no URN:NBN adapter is deployed on this host; this is a roadmap integration for `if.api` + `if.bus`.
---
## 1) What URN:NBN is (black/white)
- URN:NBN is a persistent identifier scheme managed by national libraries.
- It assigns stable URNs for publications and digital objects.
- URN:NBN does not, by itself, provide a receipt for your output bytes.
## 2) What if.trace is (black/white)
- `if.trace` binds bytes to hashes with receipts (signatures only when present and verifiable).
- `if.trace` proves integrity of specific output bytes, not correctness or truth.
## 3) Overlap (small)
- Both are used to reference long-lived artifacts.
- URN:NBN names the artifact; `if.trace` attests to the bytes you publish.
## 4) Non-overlap (important)
- URN:NBN does not describe your transformation or receipt chain.
- `if.trace` does not assign national-library identifiers.
## 5) Recommended pattern (carrier model)
1) Use URN:NBN as the persistent identifier.
2) Produce an output pack (report, audit, decision).
3) Bind the output to `if.trace` receipts and link them alongside the URN landing page.
## 6) What not to claim
- Do not claim "URN:NBN = receipt for output bytes".
- Do not claim "if.trace replaces URN:NBN identifiers".
---
## References (one URL per line)
https://urn.nbngw.net/
https://www.dnb.de/EN/Professionell/Standardisierung/URN/urn_node.html
https://infrafabric.io/if/trace/