The RBTP Knowledge Base is evolving weekly as part of our pilot programs with RBA members. We’d love your input — submit feedback or help shape the protocol in real time by joining a pilot.
RBTP Extension
The RBTP extension adds terms to UNTP credentials for data that UNTP doesn't already cover. Wherever UNTP has a standard field, RBTP credentials use it instead, so any UNTP tool can read them.
This page lists every term in the extension, what it holds and which credentials carry it. It describes the extension as used in production on 13 November 2026, and is updated with each release that changes the extension.
Where it's published
- The extension file is a JSON-LD context: rbtp-untp-extension.jsonld. It's the authoritative list of terms and their data types.
- It extends UNTP 0.7.0. See the UNTP 0.7.0 specification.
- Term identifiers use the base
https://www.responsiblebusiness.org/vocab/. They don't yet resolve to a definition, so this page is the readable reference. - The RBA Conformity Vocabulary defines the schemes and criteria being assessed. It doesn't define these credential fields.
Which credentials use it
| Credential | Extension terms |
|---|---|
| RMAP Summary conformity credential | Yes |
| RMAP Full conformity credential | Yes |
| Digital Facility Record (DFR) | Yes |
| VAP conformity credential | None: standard UNTP fields only |
| Facility Standard conformity credential | None: finding counts are in the standard UNTP field assessedPerformance (see below) |
Using the extension
-
Add the extension file to the credential's
@context, after the W3C and UNTP contexts:"@context": [
"https://www.w3.org/ns/credentials/v2",
"https://vocabulary.uncefact.org/untp/0.7.0/context/",
"https://documents.credentials.responsiblebusiness.org/rbtp-untp-extension.jsonld"
] -
Use a standard UNTP field wherever one exists. Use an extension term only for the data in the tables below.
-
Validate the credential against the UNTP 0.7.0 schema for its type. RBTP doesn't publish a JSON Schema of its own yet. The extension terms sit in UNTP objects that accept additional properties.
Reading a credential: terms starting rbtp: are RBTP's own. So are mineral, material, countryOfOrigin, assuranceLevel and sourceCredential in a DFR. Every other field is standard UNTP or W3C. A term is left out when the source has no value for it.
RMAP credentials
The RMAP Summary is public. The RMAP Full is encrypted and adds due diligence detail.
| Term | What it holds | Summary | Full |
|---|---|---|---|
rbtp:rmapId | The RMAP assessment ID | Yes | Yes |
rbtp:assessmentStage | The assessment type | Yes | Yes |
rbtp:assessmentFrequency | The assessment cycle, e.g. "3 years" | Yes | Yes |
rbtp:assessmentPeriod | Assessment start and end dates | Yes | Yes |
rbtp:assessmentScopePeriod | Scope period start and end dates | Yes | Yes |
rbtp:reportIssueDate | The report's issue date | Yes | Yes |
rbtp:address | The facility's postal address | Yes | Yes |
rbtp:remediation | Corrective action plans and their dates | Closure date, with the plan's label (e.g. "CAP1"); plans with no closure date are left out | Name, start and closure date |
rbtp:findingsSummary | Finding counts by finding type | Yes | Yes |
rbtp:assessmentLevelNotes | Assessor notes on the whole assessment | Yes | Yes |
rbtp:metalStatus | Marks the entry giving a metal's RMAP status | Yes | Yes |
rbtp:oecdStep | Marks an OECD step result | Yes | Yes |
rbtp:notApplicable | Marks a criterion the assessment found not applicable, in place of a finding | Yes | Yes |
rbtp:remediationRecommendation | The assessor's suggested improvement for a criterion | Yes | Yes |
rbtp:relatedParty | The assessment firm | No | Yes |
rbtp:assessmentStatus | Where the assessment stands in RMI's workflow | No | Yes |
rbtp:hasDueDiligenceData | Marks a Full credential as carrying due diligence detail | No | Yes |
Digital Facility Record (DFR)
These terms appear in a DFR's country of origin claims.
| Term | What it holds |
|---|---|
mineral, material | The mineral or material a country of origin claim is about |
countryOfOrigin | The countries of origin claimed for it |
assuranceLevel | Who stands behind a country of origin claim: First-party when the facility declares it, Third-party when an RMAP credential backs it |
sourceCredential | The RMAP credential a third-party country of origin claim relies on: its ID, name, issuer and the date it's valid from |
Facility Standard credentials
Facility Standard credentials use no extension terms. Finding counts, including Priority findings, are in the standard UNTP field assessedPerformance, with one count per finding type, for the overall result and for each section. See the UNTP 0.7.0 Conformity Credential specification.
Defined but not used
| Term | Notes |
|---|---|
rbtp:reviewByDate | Defined in the extension file but not written by current credentials. RMAP credentials don't carry a review-by date. |