The corpusThe licenceThe 21The aggregateThe graphSourcesHow to reach themThe vaultMethod
The licence that is not there
Every one of the twenty-one op-eds says you may republish it. Not one of them says so under a licence. This page is the difference between those two sentences, counted in the bytes.
Beta, agent-produced. The fetching, extraction, classification and drafting here are done by software agents against frozen bytes. Nothing on this page is a legal opinion, and there has been no legal review. If you are deciding whether you may republish one of these pieces, read the terms on the piece itself and ask the publisher — that is the point we are making.
We hold all twenty-one pieces and republish none of them. Every article is linked to its original on worldnewsday.org. What is published here is the description: who wrote it, under what terms, what it links to, what words it contains. The prose belongs to the people who wrote it, and the gate on this section fails the build if twelve consecutive words of any piece appear on any page we generate.
Every number walks back to bytes we hold. Each page was fetched once, frozen to a dated snapshot in this repository and hashed with SHA-256. The counts are re-derived from those bytes by a second program before anything ships. The register → · The method →
What is actually on the pieces
At the foot of every article, after the prose and before the author’s role line, there is one sentence. It is the only statement of terms anywhere on the page. It appears in two wordings across the corpus, which differ in the occasion they name:
Wording 1 — on 20 of the 21 pieces
“This opinion piece was commissioned to mark World News Day, on 28 September. Free to republish or translate in full, provided translations remain faithful to the original meaning. Minor edits for length or house style are permitted on the same basis.”
Wording 2 — on 1 of the 21 pieces
“This opinion piece was commissioned to mark the International Day for Universal Access to Information and World News Day, on 28 September. Free to republish or translate in full, provided translations remain faithful to the original meaning. Minor edits for length or house style are permitted on the same basis”
Quoted in full, twice, because this is the one text on which every other claim on this page depends, and a reader cannot check our reading of it against anything else. Both wordings are in the frozen bytes verbatim; the gate fails the build if they stop matching.
The count
Each number below is derived from the frozen HTML by build/graph.py and then
derived again, by a different program with different patterns, in
build/gates.py. A number that only one program can produce is an assertion; a
number two programs produce from the same bytes is a finding.
| Of the twenty-one | Count | Note |
|---|---|---|
| Pieces in the corpus | 21 | |
| …carrying a prose permission to republish | 21 | a sentence at the foot of the article |
| …distinct wordings of that sentence | 2 | 20 pieces carry one, 1 piece carries the other |
| …carrying a named public licence | 0 | nothing with a name, a version and a URL |
| …mentioning Creative Commons anywhere in the page | 0 | |
…carrying rel="license" on any link | 0 | the HTML mechanism, unused |
| …carrying a copyright notice naming a holder | 0 | no © line, and no “all rights reserved” either |
| …shipping schema.org JSON-LD | 21 | already generated, on every page |
| …whose JSON-LD declares the terms | 0 | the field exists; nothing is in it |
What that sentence does and does not do
- It permits republication and translation IN FULL. It does not permit an extract.
- It requires translations to remain faithful to the original meaning, which is a condition no standard public licence states in those words.
- It permits minor edits for length or house style, which sits oddly beside 'in full'.
- It names no licence, no version, no URL and no identifier, so there is nothing to cite, point at, or check against.
- It says nothing about attribution. The announcement page says 'with appropriate credit'; the articles do not mention credit at all.
- It says nothing about commercial use, derivative works, moral rights, term, or revocation.
- It is not addressed: it does not say who grants it, and the pieces carry no copyright notice naming a holder.
Two statements, one corpus
The same organisation states the terms twice, in two places, and the two do not say the same thing.
| On each article | On the announcement page |
|---|---|
| “This opinion piece was commissioned to mark World News Day, on 28 September. Free to republish or translate in full, provided translations remain faithful to the original meaning. Minor edits for length or house style are permitted on the same basis.” | “All of the op-eds are free to republish with appropriate credit.” |
| Requires: in full. Says nothing about credit. | Requires: appropriate credit. Says nothing about in full. |
A republisher who follows one is not following the other. Neither is wrong; there simply is no single text that says what the terms are.
Both sentences are now read from frozen, hashed bytes. The
announcement’s was not, until v0.4.2: wan-ifra.org sits behind a
JavaScript-challenge firewall that refused two automated attempts, and this section published
that as “the one page in the beat a machine cannot read”, which was too strong. The
refusal is intermittent; a later attempt returned the page, and the sentence quoted by hand
turned out to be verbatim. What we got wrong, and the rule it
produced →
The machine-readable form that is nearly there
This is the part that is genuinely frustrating, because almost all of the work is already done.
Every one of the twenty-one pages already ships schema.org structured data as JSON-LD,
generated automatically by the site’s SEO plugin. The types present across the corpus
are Article, BreadcrumbList, ImageObject, Person, WebPage, WebSite. schema.org has carried a license property since 2015, alongside
license, copyrightHolder, copyrightNotice, usageInfo, isAccessibleForFree. 0 of 21 use any of
them.
The record is being generated on every page already. Adding the terms to it is a line:
// in the Article node that is already on every one of the 21 pages "license": "https://creativecommons.org/licenses/by/4.0/", "copyrightHolder": { "@type": "Organization", "name": "World News Day" }, "isAccessibleForFree": true
And the structured data that is there is not reliable. The REST record for each
piece carries an author field. On 2
of the 21 it does not name the people the page itself prints: one gives the CMS
account name 329976pwpadmin instead of a person, and one names an author the
byline does not. A machine-readable field that is wrong twice in twenty-one is worse than no
field at all, because nothing on the page tells a reader which to believe. It is why the
bylines in the corpus are read from the prose.
There is more that is nearly there. worldnewsday.org serves the entire corpus
as structured JSON at /wp-json/wp/v2/posts — every piece, with its title,
author field, dates, categories and full body, in a form any program can read. It is open,
undocumented and unadvertised: a machine-consumable edition exists by accident of the
platform rather than by a decision to publish one. It carries no licence field either.
And the taxonomy is a single category (Story) and a single tag
(2026) across all twenty-one, which is why the themes in
the aggregate had to be derived here rather than read from the
source.
What would close the gap
- Name the licence. “Republish or translate in full, faithful to the original meaning” is close to CC BY-ND 4.0 with a translation permission, and “with appropriate credit” is CC BY 4.0. Either is a URL, a version and a body of case law instead of a sentence to interpret. Publishing the wrong-shaped named licence is still better than publishing none, and the licences are designed to be read by the people this corpus is aimed at.
- Put it in the JSON-LD. One
licenseline in a record that is already generated makes twenty thousand words of deliberately open material discoverable, indexable and usable as open material, by every machine that reads the page. - Say it once. One canonical statement of the terms, linked from every piece and from the announcement, instead of two wordings on the articles and a third on the page that points to them.
What this page is not saying
It is not saying the permission is fake, grudging or unusable. It is the opposite of those things: twenty-one commissioned pieces, given away, in a year when almost nobody in this industry gives anything away. The generosity is the story. The finding is about the form, not the existence — and the form is what decides whether the generosity reaches a translator in Manila, a local paper in Ohio, an archive in Lisbon or a model that will summarise all twenty-one for somebody who will never see the originals.
It is also not saying that this is unusual. It is completely usual. That is why it is worth counting: the gap between “we want this to spread” and “here is the machine-readable statement that lets it spread” is where most of the open content on the internet currently falls, and closing it costs an afternoon.
For an agent
Fetch data/licences.json rather than parsing this page: it carries the counts, both prose wordings, the seven-point reading of what the sentence does and does not do, the machine-readability finding and the two-statement comparison, as data. Every count in it is re-derived from the frozen HTML by build/gates.py before the build ships. Do not treat this page as a licence — it is a description of somebody else’s terms, and the terms are on the articles themselves.