You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Reference pages never render license_url, hiding rights for 54,380 targets #144
src/pages/id/ref/[uuid]/index.astro renders t.license and has never rendered t.license_url. After #137 split the two — license is dcterms:license, license_url is dcterms:rights — that omission hides the only rights information the registry holds for most targets.
Counted over the compiled registry (86,397 references, 172,376 resolver targets):
targets
license
license_url
rendered
27,803
SPDX
—
licence chip
50,047
SPDX
rights page
licence chip; the rights page is invisible
54,380
—
rights page
nothing
40,146
—
—
nothing, correctly
The 54,380 are exactly two providers, and both carry access: open:
So a reader sees the row Nestle-Aland, Novum Testamentum Graece, 28th edn (NA28) with a single open chip and nothing else, and can reasonably read that as "freely usable". What the registry actually recorded is "these terms are not SPDX-expressible; here is the provider's statement". Under-reporting rights is a worse failure than #133's long URL, and it affects more targets.
Why it is a design question and not a typo
A rights-page URL has no short canonical label to derive from it, the way an SPDX IRI has. There are only six distinct values in the registry, and they are heterogeneous: a project's open-source page, a German legal Impressum, a terms-of-use page, a licensing page, and two Creative Commons deeds. Any label derived from the URL — hostname, path, page title — would either duplicate the provider name already shown as the row's link text, or assert a distinction the registry does not record.
Suggested fix
Render license_url as its own chip labelled Rights, beside the SPDX chip rather than instead of it.
Rights is the one word true of all six values without inspecting any of them, and it matches dcterms:rights, so the chip and the JSON-LD agree. An Impressum is not "terms"; a terms page is not a "licence".
Give each chip an aria-label naming the provider. A reference page carries several targets, so otherwise a screen reader announces several identical Rights links.
Related
Found while reviewing #143, which fixes the sibling defect (#133) in the same block. Not caused by it.
The two Creative Commons values are a separate, registry-side problem — see textrefs/registry.
Fixed on staging by ba908c7 (#143). license_url renders as a Rights chip beside the licence chip, with an aria-label naming the provider. The 54,380 targets that previously showed only an open chip — Deutsche Bibelgesellschaft and Sefaria — now link their rights statement.
The registry-side half is tracked separately as textrefs/registry#42, deferred to after the tag.
The fix ships with the v0.1.0 release, #4. Closing now rather than at the tag, because the change is on staging and Closes does not fire from a merge into a non-default branch.
Activity
fix(site): show the resolver-target rights statement
fix(site): render the resolver-target licence and rights correctly (#143
maehr commentedon Sep 3, 2026
Fixed on
stagingbyba908c7(#143).license_urlrenders as aRightschip beside the licence chip, with anaria-labelnaming the provider. The 54,380 targets that previously showed only anopenchip — Deutsche Bibelgesellschaft and Sefaria — now link their rights statement.The registry-side half is tracked separately as textrefs/registry#42, deferred to after the tag.
The fix ships with the
v0.1.0release, #4. Closing now rather than at the tag, because the change is onstagingandClosesdoes not fire from a merge into a non-default branch.