How to Cite XFIDs
Citation formats for referencing XframeworkID identifiers in academic papers, investment memos, regulatory filings, and term sheets.
Inline Citation
When referencing a specific document in running text:
Bibliography / References
For a full bibliographic entry:
Dataset Citation
When citing the XframeworkID registry as a data source:
BibTeX
@misc{xfid:XFI5ICTDJ4,
author = {Iberdrola, S.A.},
title = {Green Bond Framework},
year = {2024},
note = {XframeworkID: XF-I5ICTDJ-4},
url = {https://xframework.id/XFI5ICTDJ4}
}
@dataset{xframeworkid:registry,
author = {Howard, Ian},
title = {XframeworkID (XFID) Registry — Labelled-Bond
Disclosure Document Dataset},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.21297903},
url = {https://xframework.id/data}
} Why Cite XFIDs
Permanence
XFIDs are content-based identifiers. They don't change when issuers move or remove documents. A citation using an XFID will resolve years after the original URL breaks.
Reproducibility
Two researchers citing the same framework with an XFID are provably referencing the same document. The identifier is computed from the content itself.
Version Tracking
If a document is revised, the new version gets a different XFID. Your citation locks to the exact version you analysed, even if the issuer updates it later.
Persistence & Continuity Policy
What happens to your citation if this registry goes away? Three commitments, in decreasing dependence on us:
1. Operator-independent archive
The full XFID→metadata→hash mapping is deposited as versioned snapshots on Zenodo (CERN infrastructure), independently of this registry: doi:10.5281/zenodo.21297903. If xframework.id disappears, every XFID remains resolvable against the archived dataset.
2. Published algorithm
The identifier algorithm (SHA-256 of canonical content, Base36, Luhn check digit) is public and stays public. Anyone holding any copy of a cited document can recompute its XFID and verify a match — no registry required.
3. Better than a dead DOI
A tombstoned DOI loses the content behind it. An XFID's content hash survives in the archive and still verifies any surviving copy, wherever it is. The citation degrades to “verifiable fingerprint” — never to nothing.
Tooling: document pages carry Zotero-readable citation metadata, and the resolver
supports content negotiation —
curl -H "Accept: application/x-bibtex" https://xframework.id/{XFID}
returns BibTeX (CSL-JSON via application/vnd.citationstyles.csl+json).
Third-party recognition: xfid is a registered
identifiers.org prefix, giving XFIDs standing
alongside DOIs and other MIRIAM-registered schemes in tools that resolve compact
identifiers (their redirect still points here, so this is about recognition, not
an independent copy).
Identifier Formats
| Prefix | Entity | Example | Resolves at |
|---|---|---|---|
XF | Document | XF-I5ICTDJ-4 | xframework.id/XFI5ICTDJ4 |
XP | Person (analyst) | XP3VN7Q7TV | xframework.id/XP3VN7Q7TV |
XO | Organization | XO7KN83X7F | xframework.id/XO7KN83X7F |
The display format (with dashes: XF-I5ICTDJ-4) and the compact format (without: XFI5ICTDJ4) both resolve to the same page.
Documents are also resolvable as a compact identifier via
identifiers.org —
xfid:XFI5ICTDJ4 resolves through their registry to the same page,
alongside DOIs, ISBNs and other MIRIAM-registered identifier schemes.
Access the Data
Researchers can access the full XframeworkID dataset for academic use.