New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use rightsstatements.org for license/rights examples in Image API #1094
Comments
I propose that we change the first example to use just http://rightsstatements.org/page/InC-EDU/1.0/ , and the second to have http://example.org/rights/license1.html & http://rightsstatements.org/page/InC-EDU/1.0/ |
👍 to proposed solution |
Hi, it's great what you've done here! |
As noted on the 12 April 2017 call:
|
Continuing on noting the discussion on 12 April 2017 call: there is reluctance (especially from @zimeon ) on adding the example in the normative part (table at the top of section 5.4). |
I also agree with @anarchivist : For 2.1, I am very fine with the current spec draft, which makes only a suggestion about the use of URIs like the ones of CC and RS.org, not a stronger recommendation. |
👍 for using stating that the URL should be from a machine-readable/dereferencable/from a controlled vocabulary/etc statement. |
Clone of #960 to separate Image API case from Presentation API case. We agreed that we should use examples from rightsstatements.org as these are likely good statements for our community. In Image API 2.1 we have two examples that include
license
(to be renamedrights
in v3 #644):"http://example.org/rights/license1.html"
[ "http://example.org/rights/license1.html", "https://creativecommons.org/licenses/by/4.0/" ]
Tasks:
The text was updated successfully, but these errors were encountered: