FORA is an open transaction protocol. AI agents discover, license, pay for and receive content on terms the rights holder sets. The Exchange signs every offer, the agent signs every request, and both keep evidence anyone can check.
FORA doesn't ask you to fit a template. It breaks your license into the parts every license has, keeps your document as the reference, and signs the result.
Pick a license. Each clause becomes a field of one FORA term, or stays in the license document the term identifies. The RSL 1.0 and IAB CoMP 1.0 tabs show how each standard expresses the same clauses, and where it can't. Both standards were written for crawlers and AI systems, so the photo, music and manufacturing licenses fall outside what they set out to cover.
The most common open license for articles, photos and music: use it for anything, credit the creator.
semantics: ENUMERATED license: id: "CC-BY-4.0" uri: "https://creativecommons.org/licenses/by/4.0/legalcode" uri_digest: "sha256:9d1c…" restrictions: - kind: FUNCTION permitted: ["reproduce", "distribute", "modify", "commercial"] - kind: GEOGRAPHY permitted: ["*"] pricing: model: FREE metering: NONE obligations: - kind: ATTRIBUTION trigger: ON_DISTRIBUTION detail: "Credit the creator, link the license, note any changes"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
all, RSL's widest usage token, means "any automated processing", narrower than copying and sharing by people. Those rights come from the CC BY license that <standard> names.
No token for adaptation. Remixing and building on the work rest on the CC BY license alone.
No <permits type="user">, so any user, commercial or not.
No <permits type="geo">, so worldwide. attribution asks for credit, not money.
<payment type="attribution"> requires "visible credit and a functional link to the original source". Linking the license and noting changes are CC BY duties.
RSL states the disclaimer in the XML: <legal type="disclaimer">as-is no-warranty</legal>.
The RSL specification uses CC BY as its own <standard> example. The credit and the disclaimer are in the XML; the rights to copy and adapt are in the license it names.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/photos/harbor.jpg"> <license> <permits type="usage">all</permits> <payment type="attribution"> <standard>https://creativecommons.org/licenses/by/4.0/</standard> </payment> <legal type="disclaimer">as-is no-warranty</legal> </license> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
A package has no field for permitted functions. The AI system names its intended function in the request, and the license at licenseurl decides.
No field for adaptation. Remixing rests on the CC BY text at licenseurl.
ause 0 (commercial) allows commercial use.
CoMP has no free price type, so free is pricetype 3 (flat) at unitprice 0. No country is listed.
citation 1 says the content owner must be cited, and the image's author field names J. Doe. Linking the license and noting changes are CC BY duties.
No warranty field. The disclaimer is in the CC BY text at licenseurl.
The package names CC BY, requires the credit and allows commercial use. The rights to copy and adapt, and the disclaimer, are in the license text.
{
"id": "harbor-photo",
"seller": "photos.example",
"licenseurl": "https://creativecommons.org/licenses/by/4.0/",
"citation": 1,
"scope": {
"ause": 0,
"pricetype": 3,
"unitprice": 0,
"cur": "USD",
"ctype": [2],
"image": [{ "title": ["Harbor at dawn"], "author": ["J. Doe"] }]
}
} Free for non-commercial use, and anything you make from it carries the same license.
semantics: ENUMERATED license: id: "CC-BY-NC-SA-4.0" uri: "https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode" uri_digest: "sha256:2b7e…" restrictions: - kind: FUNCTION permitted: ["reproduce", "distribute", "modify"] prohibited: ["commercial"] - kind: GEOGRAPHY permitted: ["*"] pricing: model: FREE metering: NONE obligations: - kind: SHARE_ALIKE trigger: ON_DISTRIBUTION scope_license: { id: "CC-BY-NC-SA-4.0" } - kind: ATTRIBUTION trigger: ON_DISTRIBUTION detail: "Credit the creator and link the license"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
all means "any automated processing", narrower than copying and adapting by people. Those rights come from the CC BY-NC-SA license that <standard> names.
<permits type="user">non-commercial</permits> is a user class, defined as "Non-commercial purposes" and applied to "the entity or operational context responsible for the automated use". CC BY-NC-SA tests the purpose of each use.
No share-alike element.
<payment type="attribution">: visible credit and a functional link.
No <permits type="geo">, so worldwide. attribution asks for credit, not money.
RSL defines non-commercial in three words, "Non-commercial purposes". The CC definition is in the license that <standard> names.
The credit and the license URL carry over, and share-alike travels with the URL. Non-commercial shifts meaning: RSL classifies the entity responsible for the use, CC tests the purpose of each use.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/photos/harbor.jpg"> <license> <permits type="usage">all</permits> <permits type="user">non-commercial</permits> <payment type="attribution"> <standard>https://creativecommons.org/licenses/by-nc-sa/4.0/</standard> </payment> </license> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. Copying and adapting rest on the license at licenseurl.
ause 1 (non-commercial) states the kind of use allowed. CoMP gives the value a label and no definition.
No share-alike field.
citation 1 says the content owner must be cited. How to credit, and the link to the license, are in the CC text.
Free is pricetype 3 (flat) at unitprice 0. No country is listed.
The CC definition of non-commercial is at licenseurl.
ause 1 states non-commercial as a kind of use, as CC does. Share-alike exists only in the license text.
{
"id": "harbor-photo-nc",
"seller": "photos.example",
"licenseurl": "https://creativecommons.org/licenses/by-nc-sa/4.0/",
"citation": 1,
"scope": {
"ause": 1,
"pricetype": 3,
"unitprice": 0,
"cur": "USD",
"ctype": [2]
}
} The short permissive software license: do anything, keep the notice.
semantics: ENUMERATED license: id: "MIT" pricing: model: FREE metering: NONE obligations: - kind: NOTICE trigger: ON_DISTRIBUTION detail: "Keep the copyright and permission notice"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
all means "any automated processing", narrower than using, merging, selling and sublicensing. Those rights come from the MIT license that <standard> names.
<payment type="free"> with no <permits type="user">: free, to anyone.
No notice element. RSL's attribution is a credit and a link, not a notice kept in copies.
RSL states the disclaimer in the XML: <legal type="disclaimer">as-is no-warranty no-liability</legal>.
The XML says free, to anyone, as is. The grant itself and the notice duty are in the MIT text that <standard> names.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/code/parser.tar.gz"> <license> <permits type="usage">all</permits> <payment type="free"> <standard>https://opensource.org/license/mit</standard> </payment> <legal type="disclaimer">as-is no-warranty no-liability</legal> </license> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. Using, merging, selling and sublicensing rest on the MIT text at licenseurl.
Free is pricetype 3 (flat) at unitprice 0. A package has no field that limits who may use it.
No notice field. citation is about citing the content owner, not keeping a notice in copies, and this package sets it to 0.
No warranty field. The disclaimer is in the MIT text at licenseurl.
The fields say free, for commercial use. The grant, the notice and the disclaimer are all at licenseurl.
{
"id": "parser-source",
"seller": "code.example",
"licenseurl": "https://opensource.org/license/mit",
"citation": 0,
"scope": {
"ause": 0,
"pricetype": 3,
"unitprice": 0,
"cur": "USD",
"ctype": [0]
}
} Copyleft that also reaches software offered as a network service.
semantics: ENUMERATED license: id: "AGPL-3.0-only" pricing: model: FREE metering: NONE obligations: - kind: SHARE_ALIKE trigger: ON_DISTRIBUTION scope_license: { id: "AGPL-3.0-only" } - kind: NETWORK_COPYLEFT trigger: ON_NETWORK_SERVICE detail: "Offer the source to network users" - kind: NOTICE trigger: ON_DISTRIBUTION
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
all means "any automated processing", narrower than running, studying, modifying and sharing. Those rights come from the AGPL that <standard> names.
No share-alike element.
No element for software offered over a network.
No notice element.
No element for a patent grant or termination.
The XML names the AGPL and marks it free. The copyleft, the network clause and the notices exist only in the license it names.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/code/server.tar.gz"> <license> <permits type="usage">all</permits> <payment type="free"> <standard>https://www.gnu.org/licenses/agpl-3.0.html</standard> </payment> </license> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. Running, studying, modifying and sharing rest on the AGPL at licenseurl.
No share-alike field.
No field for software offered over a network.
No notice field.
No field for a patent grant or termination.
As in RSL, the package names the AGPL and prices it at zero. Every duty the AGPL imposes stays in its text.
{
"id": "server-source",
"seller": "code.example",
"licenseurl": "https://www.gnu.org/licenses/agpl-3.0.html",
"scope": {
"ause": 0,
"pricetype": 3,
"unitprice": 0,
"cur": "USD",
"ctype": [0]
}
} A news site's AI license: AI answers allowed for a fee per crawl, training not allowed.
semantics: ENUMERATED license: uri: "https://news.example/license.xml" uri_digest: "sha256:4c1f…" restrictions: - kind: FUNCTION permitted: ["ai-input", "search"] prohibited: ["ai-train"] pricing: model: PER_UNIT unit: "fetches" rate: "0.05" currency: USD metering: NONE obligations: - kind: ATTRIBUTION trigger: ON_USE detail: "Cite the publication at the original URL"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
<permits type="usage">ai-input search</permits>. FORA registers RSL's six usage tokens unchanged.
<prohibits type="usage">ai-train</prohibits>.
<payment type="crawl"> with <amount>: a payment "every time the content is crawled".
A license has one <payment> with one type, and attribution is a type. A license priced per crawl can't also require credit in the XML.
This is the kind of license RSL was designed for, and three of its four clauses map. The credit is lost because RSL makes attribution a payment type, and the one payment here is the crawl fee.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/articles/"> <license> <permits type="usage">ai-input search</permits> <prohibits type="usage">ai-train</prohibits> <payment type="crawl"> <amount currency="USD">0.05</amount> </payment> </license> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. function, with the same ai-input and search values, is what the AI system declares in its request; the license decides.
No field prohibits a function. The ban on ai-train is in the license at licenseurl.
pricetype 0 (per use) at unitprice 0.05. CoMP doesn't define one use, so a price per fetch and a price per answer read the same.
citation 1 beside a per-use price: CoMP can require credit on paid content.
CoMP keeps the credit RSL loses, because citation is a field of its own. Which functions are allowed or banned stays in the license.
{
"id": "articles-ai",
"seller": "news.example",
"licenseurl": "https://news.example/license.xml",
"citation": 1,
"scope": {
"scope": 1,
"pricetype": 0,
"unitprice": 0.05,
"cur": "USD",
"ctype": [0]
}
} A subscription: one AI company pays a yearly fee and its agents use the archive within a monthly cap.
semantics: ENUMERATED license: uri: "https://news.example/deals/acme-ai-2027.pdf" uri_digest: "sha256:a07e…" scopes: ["subscription:acme-ai-2027"] restrictions: - kind: FUNCTION permitted: ["ai-input", "ai-index"] prohibited: ["ai-train"] quotas: - { metric: "accesses", limit: 100000, window: MONTHLY } pricing: model: FREE license_duration_months: 12 metering: ONLINE
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
No field names a licensee. <custom> sends agents to the licensing page, or a License Server (the server attribute) issues the license to each client. The public file can state the offer, not one subscriber's terms.
subscription is "Recurring payment for access". The file states no <amount>, so the fee stays private.
<permits type="usage">ai-input ai-index</permits> and <prohibits type="usage">ai-train</prohibits>.
No quota element for a monthly cap.
<reporting type="audit"> requires reports under a profile you publish. The 30-day window and the required fields are defined in that profile.
<terms> links the general subscription terms, with no digest to pin them. Terms negotiated with one subscriber stay out of the public file.
The payment type and the uses map, and reporting is required, with its window and fields in a profile. The licensee and the cap aren't in the file.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/archive/"> <license> <permits type="usage">ai-input ai-index</permits> <prohibits type="usage">ai-train</prohibits> <payment type="subscription"> <custom>https://news.example/licensing/ai</custom> </payment> <reporting type="audit" profile="https://news.example/licensing/ai/reporting/v1" endpoint="https://news.example/licensing/ai/reports"/> </license> <terms>https://news.example/licensing/ai/terms</terms> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No package field names the buyer. The AI system's request carries lid, the license ID it holds from the deal.
pricetype 3 (flat) with licensedur 365. The package states no unitprice, so the fee stays private.
No field for permitted or prohibited functions.
max 1 says a limit exists. CoMP defines it as a limit on crawling and sends the AI system to the license for the figure.
reporturl says where to send reports. CoMP lists reporting as out of scope, so it has no field for the window or the report contents.
No field for liability, audit rights or renewal.
max and reporturl show that a cap and a reporting duty exist. Their size, window and contents are in the deal document at licenseurl.
{
"id": "acme-ai-2027-archive",
"seller": "news.example",
"licenseurl": "https://news.example/deals/acme-ai-2027.pdf",
"reporturl": "https://news.example/deals/reports",
"scope": {
"scope": 0,
"ause": 0,
"pricetype": 3,
"licensedur": 365,
"max": 1,
"ctype": [0]
}
} A typical standard stock license: pay once, use the image in many places, up to a print run.
semantics: ENUMERATED license: uri: "https://stock.example/license/standard" uri_digest: "sha256:51a3…" restrictions: - kind: FUNCTION permitted: ["display", "reproduce", "advertising"] prohibited: ["sell"] - kind: GEOGRAPHY permitted: ["*"] quotas: - { metric: "copies", limit: 500000, window: TOTAL } pricing: model: FLAT rate: "29.00" currency: USD metering: NONE
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
RSL's usage tokens cover automated processing, and none means display, print or advertising. <prohibits type="usage">ai-all</prohibits> rules out AI use; other automated processing, such as search, stays permitted.
No token for selling the image as a product.
No quota element for a print run.
<payment type="purchase">, a one-time payment, with <amount>. No <permits type="geo">, so worldwide.
<terms> links the license text, with no digest to pin it.
The price maps, and ai-all keeps AI systems out. The uses, the ban on merchandise and the print run are only in the license that <terms> links.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/photos/7781.jpg"> <!-- No RSL words for display, print or advertising --> <license> <prohibits type="usage">ai-all</prohibits> <payment type="purchase"> <amount currency="USD">29.00</amount> </payment> </license> <terms>https://stock.example/license/standard</terms> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. CoMP's function list, like RSL's usage tokens, covers automated processing.
No field prohibits a use.
max 1 says a limit exists. CoMP defines it as a limit on crawling and sends the AI system to the license for the figure. Here the limit is on printed copies.
pricetype 3 (flat) at unitprice 29, with no licensedur and no country list.
No field for trademark or sensitive-subject rules.
The package carries the price and says a limit exists. What the buyer may do with the photo, and how many copies, are in the license.
{
"id": "stock-7781",
"seller": "stock.example",
"licenseurl": "https://stock.example/license/standard",
"scope": {
"ause": 0,
"pricetype": 3,
"unitprice": 29.0,
"cur": "USD",
"max": 1,
"ctype": [2],
"image": [{ "title": ["Harbor crane at dusk"] }]
}
} A news photo for reporting, never for ads, with a credit line on every use.
semantics: ENUMERATED license: uri: "https://photos.example/license/editorial" uri_digest: "sha256:e8f2…" restrictions: - kind: FUNCTION permitted: ["editorial"] prohibited: ["advertising", "commercial", "sell"] - kind: USER_TYPE permitted: ["news_publisher", "broadcaster"] pricing: model: FLAT rate: "150.00" currency: USD license_duration_months: 12 metering: NONE obligations: - kind: ATTRIBUTION trigger: ON_USE detail: "Photo: J. Doe / Example Agency"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
No usage token for editorial use. <prohibits type="usage">ai-all</prohibits> rules out AI use; other automated processing stays permitted.
No token for advertising or merchandise, and <permits type="user">non-commercial</permits> would shut out the news organizations this license is for.
RSL's user tokens are commercial, non-commercial, education, government and personal. None means a news organization.
<copyright> names Example Agency as the rights holder but imposes no duty to credit. The license's one <payment> is the purchase, so attribution can't be added.
purchase is a one-time payment, and RSL has no element for a term.
The price and the rights holder are in the XML, and ai-all keeps AI systems out. The editorial use, the news-only licensee, the credit line and the one-year term are only in the license that <terms> links.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/photos/summit-0412.jpg"> <!-- No RSL words for editorial use or for news organizations --> <license> <prohibits type="usage">ai-all</prohibits> <payment type="purchase"> <amount currency="USD">150.00</amount> </payment> </license> <copyright type="organization">Example Agency</copyright> <terms>https://photos.example/license/editorial</terms> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions.
No field prohibits a use. ause 1 (non-commercial) is a different restriction from "no advertising or merchandise".
ause takes one value: commercial, non-commercial, educational, government, personal, BYO License or other. None names news organizations, and "other" would say nothing, so the package omits ause.
citation 1, and the image's author field carries the credit "J. Doe / Example Agency".
licensedur 365: the license runs 365 days from delivery.
CoMP states the credit line and the one-year term in fields, where RSL leaves both to the linked license. Editorial use and the news-only licensee stay in the license.
{
"id": "summit-0412",
"seller": "photos.example",
"licenseurl": "https://photos.example/license/editorial",
"citation": 1,
"scope": {
"pricetype": 3,
"unitprice": 150.0,
"cur": "USD",
"licensedur": 365,
"ctype": [2],
"image": [{ "title": ["Summit arrivals"], "author": ["J. Doe / Example Agency"] }]
}
} A track synchronized into one TV program, in two countries, for three years.
semantics: REFERENCE_ONLY license: name: "Sync license, one program" uri: "https://label.example/licenses/sync-tv.pdf" uri_digest: "sha256:bfab…" restrictions: - kind: FUNCTION permitted: ["sync", "broadcast", "stream"] prohibited: ["advertising", "ai-train"] - kind: USER_TYPE permitted: ["broadcaster", "commercial_entity"] - kind: GEOGRAPHY permitted: ["GB", "IE"] quotas: - { metric: "vendor:productions", limit: 1, window: TOTAL } pricing: model: FLAT rate: "450.00" currency: EUR license_duration_months: 36 metering: NONE obligations: - kind: OTHER trigger: ON_DISTRIBUTION detail: "Cue sheet through the broadcaster" - kind: NOTICE trigger: ON_DISTRIBUTION detail: "℗ 2026 Example Records"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
No usage token for sync, broadcast or streaming. RSL's usage tokens cover automated processing.
<prohibits type="usage">ai-all</prohibits> rules out AI training and every other AI use, wider than the clause. No token means advertising.
<permits type="user">commercial</permits> covers the production company. No user token means a broadcaster.
<permits type="geo">GB IE</permits>, in ISO 3166-1 alpha-2 codes, as FORA writes them.
purchase is a one-time payment, and RSL has no element for a term.
No quota element for a count of productions.
No element for a cue sheet.
<copyright> names the rights holder but imposes no duty to show the ℗ line.
No element for these terms. RSL calls the <terms> document "supplemental legal information", not the authority a REFERENCE_ONLY term makes it.
The territory maps, and <copyright> names the label. Sync, the three-year term, the production limit and the cue sheet are only in the document that <terms> links.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/tracks/harbor-lights.wav"> <!-- No RSL words for sync, broadcast or streaming --> <license> <prohibits type="usage">ai-all</prohibits> <permits type="user">commercial</permits> <permits type="geo">GB IE</permits> <payment type="purchase"> <amount currency="EUR">450.00</amount> </payment> </license> <copyright type="organization">Example Records</copyright> <terms>https://label.example/licenses/sync-tv.pdf</terms> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. CoMP's function list, like RSL's usage tokens, covers automated processing.
No field prohibits a use.
ause 0 (commercial) fits the production company. No ause value means a broadcaster.
country 826 and 372, the numeric codes for the United Kingdom and Ireland. The spec types country as integers and describes alpha-2 codes; this package follows the type.
licensedur 1095: three years, counted in days from delivery.
max 1 says a limit exists. CoMP defines it as a limit on crawling and sends the AI system to the license for the figure. Here the limit is on productions.
No field for a cue sheet.
citation 1, with Example Records in the audio's author field. The ℗ line is in the document.
licenseurl links the document. ause 5 (BYO License) would refer the AI system to its terms, but ause holds one value, and this package uses it for commercial.
Territory and term are fields. The uses, the production limit and the cue sheet are in the document at licenseurl.
{
"id": "harbor-lights-sync",
"seller": "label.example",
"licenseurl": "https://label.example/licenses/sync-tv.pdf",
"citation": 1,
"scope": {
"ause": 0,
"pricetype": 3,
"unitprice": 450.0,
"cur": "EUR",
"country": [826, 372],
"licensedur": 1095,
"max": 1,
"ctype": [3],
"audio": [{ "title": ["Harbor Lights"], "author": ["Example Records"] }]
}
} A collecting society's agreement, too long and conditional to enumerate field by field.
semantics: REFERENCE_ONLY license: name: "Blanket sync license MR-7741" uri: "https://society.example/license/MR-7741" uri_digest: "sha256:3b1f…" pricing: model: FLAT rate: "500.00" currency: USD
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
<standard> names the society's license. A client that accepts it gains access to all content whose RSL licenses name the same URL.
RSL has no digest, so the document at the URL can change after the agent agrees to it.
<payment type="purchase"> with <amount>.
The XML restricts no use and leaves that to the society's document. RSL considers "only licensing terms defined in the RSL namespace" and has no rule for a conflict with the document that <standard> names.
RSL built <standard> for shared frameworks like this one: accept it once, and every file naming the URL is covered. RSL can't pin which version of the document the agent accepted.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/catalog/"> <license> <payment type="purchase"> <standard>https://society.example/license/MR-7741</standard> <amount currency="USD">500.00</amount> </payment> </license> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
ause 5 (BYO License): the terms are the ones at licenseurl.
licenseurl has no digest, so the document can change after the agent agrees to it.
pricetype 3 (flat) at unitprice 500.
The package states only the license and the price, and CoMP has no rule for a field that contradicts the license.
ause 5 is CoMP's value for this case. Like RSL, CoMP can't pin the document.
{
"id": "society-mr-7741",
"seller": "society.example",
"licenseurl": "https://society.example/license/MR-7741",
"scope": {
"ause": 5,
"pricetype": 3,
"unitprice": 500.0,
"cur": "USD"
}
} A dataset free to subscribing universities, for training and inference, with share-alike on the models.
semantics: ENUMERATED scopes: ["subscription:institution"] restrictions: - kind: FUNCTION permitted: ["ai-train", "ai-input"] - kind: USER_TYPE permitted: ["academic", "non_profit"] quotas: - { metric: "seats", limit: 10, window: MONTHLY } pricing: model: FREE obligations: - kind: SHARE_ALIKE trigger: ON_DISTRIBUTION scope_license: { id: "CC-BY-NC-SA-4.0" }
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
<payment type="subscription"> with <custom>: your licensing page decides who subscribes.
<permits type="usage">ai-train ai-input</permits>.
<permits type="user">education non-commercial</permits>. education means "Educational use in schools or universities"; non-commercial is the nearest token to a non-profit, and names a purpose, not a kind of organization.
No quota element for seats.
No share-alike element. <standard> would name the dataset's license, not the one for trained models.
The AI uses map token for token, and the user list comes close. The ten-seat limit and the share-alike duty on trained models are only in the license that <terms> links.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/datasets/coastal-survey/"> <license> <permits type="usage">ai-train ai-input</permits> <permits type="user">education non-commercial</permits> <payment type="subscription"> <custom>https://data.example/institutions/join</custom> </payment> </license> <terms>https://data.example/license/institutional</terms> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No package field names the buyer. The AI system's request carries lid, the license ID it holds from its subscription.
No field for permitted functions.
ause takes one value, here 2 (educational), so non-profit use can't be added beside it.
max 1 says a limit exists. CoMP defines it as a limit on crawling and sends the AI system to the license for the figure. Here the limit is on seats.
No share-alike field.
One ause value, educational, stands in for two kinds of user. The seat limit is flagged; the AI uses and the duty on trained models are left to the license.
{
"id": "coastal-survey",
"seller": "data.example",
"licenseurl": "https://data.example/license/institutional",
"scope": {
"scope": 0,
"ause": 2,
"pricetype": 3,
"unitprice": 0,
"max": 1,
"ctype": [0]
}
} A 3D-printable part, licensed for production runs reported after the fact.
semantics: ENUMERATED restrictions: - kind: FUNCTION permitted: ["manufacture"] - kind: GEOGRAPHY permitted: ["*"] quotas: - { metric: "units-manufactured", limit: 1000, window: TOTAL } pricing: model: FLAT rate: "200.00" currency: USD metering: OFFLINE_SELF_REPORTED obligations: - kind: CONTRIBUTION trigger: ON_USE detail: "Suggested royalty: $0.50 per unit above 1,000"
Really Simple Licensing: an XML file the publisher hosts, telling crawlers and other automated clients what they may do with the content and what they owe for it.
No usage token for manufacturing; RSL's usage tokens cover automated processing. <prohibits type="usage">ai-all</prohibits> rules out AI use.
No quota element for a unit count.
<reporting type="audit"> requires "periodic or aggregate compliance reporting" under a profile you publish.
contribution is a payment type, and the license's one <payment> is the purchase. RSL calls a second <license> a distinct term set, so it would not add to the first.
The fee and the reporting duty have an RSL form. Manufacturing, the 1,000-unit cap and the royalty above it are only in the license that <terms> links.
<rsl xmlns="https://rslstandard.org/rsl"> <content url="/parts/bracket-v3.step"> <!-- No RSL word for manufacturing --> <license> <prohibits type="usage">ai-all</prohibits> <payment type="purchase"> <amount currency="USD">200.00</amount> </payment> <reporting type="audit" profile="https://parts.example/reporting/production-runs"/> </license> <terms>https://parts.example/license/manufacture</terms> </content> </rsl>
IAB Tech Lab's Content Monetization Protocols: the content owner answers an AI system's request with a package that describes the content, its price and where the license is. CoMP leaves the license terms to be negotiated beforehand.
No field for permitted functions. CoMP's function list, like RSL's usage tokens, covers automated processing.
max 1 says a limit exists. CoMP defines it as a limit on crawling and sends the AI system to the license for the figure. Here the limit is on units made.
reporturl says where to send reports. What to report, and when, is in the license.
A package has one pricetype and one unitprice. pricetype 4 (tiered) carries only a tier identifier in pricetier, and no field holds a royalty.
The package carries the price, a reporting address and a limit flag. Manufacturing and the royalty are in the license; CoMP describes content offered to AI systems.
{
"id": "bracket-v3",
"seller": "parts.example",
"licenseurl": "https://parts.example/license/manufacture",
"reporturl": "https://parts.example/reports",
"scope": {
"ause": 0,
"pricetype": 3,
"unitprice": 200.0,
"cur": "USD",
"max": 1,
"ctype": [5]
}
} Digests are shortened. The licensing terms specification →
FORA reads the rights signals publishers already use, signs with standard cryptography, and leaves payment to the rails that exist.