Examples
Worked examples
- Is an instance
A UK institutional repository exposing RIOXX-formatted metadata over OAI-PMH for Jisc Publications Router consumption.
- Is an instance
RIOXX metadata feeding a UKRI funder-compliance dashboard.
Counter-examples
Looks similar, but isn't
- Not an instance
Plain oai_dc Dublin Core is not RIOXX.
- Not an instance
JATS XML is not RIOXX — JATS describes full-text article structure, RIOXX describes repository-record metadata.
- Not an instance
A repository record with a funder name only in free-text notes, rather than in the structured rioxxterms:funder/rioxxterms:grant fields, does not meet RIOXX's compliance-reporting purpose even if technically valid XML.
Editorial commentary
RIOXX was developed by Jisc and the UK Research and Innovation funder community to address the gap in standard repository metadata around funder identification, grant references, embargo dates, and licences — fields essential to demonstrating compliance with funder OA policies. RIOXX records are intended to be exposed over OAI-PMH alongside oai_dc. RIOXX v3.0 (2022) aligns with the OpenAIRE Guidelines and adds richer relationship modelling.
The compliance fields RIOXX adds to Dublin Core
Where plain Dublin Core has no structured way to record funding or licensing detail, RIOXX layers on dedicated elements including rioxxterms:funder (with a Crossref Funder ID or RCUK/UKRI funder code), rioxxterms:grant (the specific award reference), rioxxterms:licenseref (a machine-readable licence URI, e.g. a Creative Commons licence), rioxxterms:apc (whether an article processing charge was paid), and embargo-related date fields distinguishing deposit date from public-availability date. These are exactly the fields a funder-compliance checker (such as Jisc’s Publications Router) needs to automatically verify OA-policy adherence at scale, rather than requiring manual checking of each deposit.
Version history
RIOXX 1.0 launched in 2014 in response to early RCUK/HEFCE open-access mandate requirements; RIOXX 2.0 refined the schema (with input drawing on CASRAI’s own metadata dictionary work at the time); RIOXX 3.0 (2022) realigned the profile with the OpenAIRE Guidelines for broader European interoperability and expanded relationship modelling between records.
What this is not
RIOXX is not JATS XML — it describes repository metadata records, not full-text article structure — and it is not a replacement for plain Dublin Core, which most RIOXX-compliant repositories continue to expose alongside it for harvesters that don’t understand the RIOXX extensions.
References
- Jisc, ‘RIOXX v3.0 Application Profile’ (rioxx.net).
- Walk P., ‘RIOXX 2.0 and CASRAI’ (Jisc Scholarly Communications blog).
Also known as
Research Outputs Information Exchange
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="RIOXX"
vocab-term-identifier="https://casrai.org/dictionary/term/rioxx" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/rioxx",
"name": "RIOXX",
"identifier": "https://casrai.org/dictionary/term/rioxx",
"description": "Research Outputs Information Exchange XML (RIOXX): a UK-originated application profile for institutional-repository metadata, layered on Dublin Core, designed to capture funder, project, and licence information for OA-compliance reporting, currently maintained at v3.0.",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/research-info-systems#set",
"url": "https://casrai.org/dictionary/term/rioxx",
"alternateName": [
"Research Outputs Information Exchange"
],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"author": {
"@id": "https://casrai.org/#editorial-team"
},
"datePublished": "2026-05-21T02:17:04",
"dateModified": "2026-09-05T14:23:13",
"inLanguage": "en-GB",
"isAccessibleForFree": true
}
