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
The canonical CC license URLs per creative commons [1] ends in a "/" and not "/legalcode". The vast majority of PubMed Central JATS XML files use the CC canonical URL and do not append "legalcode". A quick search of ~77,500 JATS XML files results in only ~100 that append "legalcode" to the license URL; so probably something like only a tenth of a percent or so of PMC JATS XML appends "legcalcode".
In contrast, the Go and Python commonmeta libraries normalize the canonical CC licenses to have "legalcode" appended. E.g. the NormalizeCCUrl Go function and the Python normlize_cc_url Python function and their associated unit tests.
I was surprised to see Commonmeta diverge from the canonical CC URL documented by Creative Commons for a URL that they control/host and from ~99.9% of PMC JATS XML.
Shouldn't the Commonmeta JSON interop data align with the canonical URL and what PMC (probably) enforces?
Applications are free to append "legalcode" if they want, but it seems counter-interop to diverge from the canonical and what PMC archives.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The canonical CC license URLs per creative commons [1] ends in a "/" and not "/legalcode". The vast majority of PubMed Central JATS XML files use the CC canonical URL and do not append "legalcode". A quick search of ~77,500 JATS XML files results in only ~100 that append "legalcode" to the license URL; so probably something like only a tenth of a percent or so of PMC JATS XML appends "legcalcode".
In contrast, the Go and Python commonmeta libraries normalize the canonical CC licenses to have "legalcode" appended. E.g. the NormalizeCCUrl Go function and the Python normlize_cc_url Python function and their associated unit tests.
I was surprised to see Commonmeta diverge from the canonical CC URL documented by Creative Commons for a URL that they control/host and from ~99.9% of PMC JATS XML.
Shouldn't the Commonmeta JSON interop data align with the canonical URL and what PMC (probably) enforces?
Applications are free to append "legalcode" if they want, but it seems counter-interop to diverge from the canonical and what PMC archives.
[1] See "Canonical URL" on https://creativecommons.org/licenses/by/4.0/
Beta Was this translation helpful? Give feedback.
All reactions