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
license and license_url both expand to dcterms:license, giving a target two licence IRIs #129
license and license_url both expand to an IRI-valued dcterms:license. A resolver target that carries both fields publishes two different licence IRIs on one node.
public/contexts/v1.jsonld maps both terms to {"@id": "dcterms:license", "@type": "@id"}. scripts/compile.ts rewrites license to https://spdx.org/licenses/{id}. Both values are now IRIs, so a consumer cannot tell them apart.
The real registry has 50,047 published resolver targets that carry both fields. Example output for one node:
Specification §9 treats license_url as the fallback for non-SPDX terms, used when license is absent. The data and the context disagree with that rule. A consumer that reads dcterms:license gets two conflicting answers and no way to rank them.
Suggested fix
Give license_url its own predicate, or stop emitting both fields on one target.
Found during review of #127. Not caused by that PR.
Fixed on staging by c360c02 (#137). license_url publishes as dcterms:rights; license keeps dcterms:license. standard/schema/context.test.ts now fails whenever any two context terms share a predicate, so the class of bug is guarded, not just this instance.
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(standard): publish license_url as dcterms:rights, not dcterms:lic…
fix(standard): publish license_url as dcterms:rights, not dcterms:lic…
maehr commentedon Sep 2, 2026
Fixed on
stagingbyc360c02(#137).license_urlpublishes asdcterms:rights;licensekeepsdcterms:license.standard/schema/context.test.tsnow fails whenever any two context terms share a predicate, so the class of bug is guarded, not just this instance.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.fix(site): show the resolver-target rights statement
fix(site): render the resolver-target licence and rights correctly (#143