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
It seems that the idea of using CC license URIs to refer to them is gaining ground as a (good) idea. See for instance the rights statements of IIIF Presentation API 3.0.
My concern is that because canonical URIs are not very explicit on the website and the RDF versions are not very obvious to find (which is normal), users might start to refer to licenses with some non-canonical URIs such as the https version, or the version ending in /deed, which seems like a bad idea...
I think canonical URIs of the various licenses should appear explicitly on the website, with an indication like "URI to use to refer to this license: XXX". One possible source of inspiration is https://rightsstatements.org/page/1.0/?language=en which makes the canonical URIs very explicit.
It seems that the idea of using CC license URIs to refer to them is gaining ground as a (good) idea. See for instance the rights statements of IIIF Presentation API 3.0.
My concern is that because canonical URIs are not very explicit on the website and the RDF versions are not very obvious to find (which is normal), users might start to refer to licenses with some non-canonical URIs such as the
https
version, or the version ending in/deed
, which seems like a bad idea...I think canonical URIs of the various licenses should appear explicitly on the website, with an indication like "URI to use to refer to this license: XXX". One possible source of inspiration is https://rightsstatements.org/page/1.0/?language=en which makes the canonical URIs very explicit.
see IIIF/api#1874
The text was updated successfully, but these errors were encountered: