RSL Integration
Map RSL (Robots Specification Layer) 1.0 usage tokens to PEAC control purposes. The mapping translates RSL content-use signals into the canonical purpose vocabulary used by PEAC consent and licensing records, so policy-aware evidence travels across systems.
Package: @peac/mappings-rsl (source-only)
Source-only. @peac/mappings-rsl is not published to npm. Build it from the repository at packages/mappings/rsl. There is no npm install path; this page documents the reference mapping.
What It Does
RSL expresses content-use permissions as usage tokens. The mapping parses those tokens and converts them to and from PEAC control purposes, so an RSL-stated policy can be recorded as verifiable PEAC evidence.
1. Parse RSL tokens
parseRslTokenString reads an RSL token string; isValidRslToken and getKnownRslTokens validate against the known vocabulary.
2. Map to control purposes
rslTokenToControlPurposes converts RSL usage tokens to PEAC control purposes; controlPurposeToRslToken maps the other direction.
3. Record consent evidence
The mapped purposes feed PEAC consent and licensing records, which verify offline with the issuer's public key.
Key functions
| Function | What it does |
|---|---|
parseRslTokenString | Parse an RSL usage token string |
rslTokenToControlPurposes | Map a single RSL token to PEAC control purposes |
rslUsageTokensToControlPurposes | Map a set of usage tokens to control purposes |
controlPurposeToRslToken | Map a PEAC control purpose back to an RSL token |
Semantic Boundary
PEAC records content-use policy signals as evidence. It does not host or enforce licensing terms, operate a rights registry, or settle royalties. An RSL-derived record proves which usage purposes were stated, not that they were honored.