rights extensions are actually just registrations

[azaroth42]

In the Presentation API, it says:

The value must be drawn from the set of Creative Commons license URIs, the RightsStatements.org rights statement URIs, or those added via the extension mechanism.

However you don't add a new URI via a context like this. The context would be needed if you alias it to some string, in the way we do with motivations in WADM or behaviors in IIIF, but not when it's the full URI.

I think what we meant was "by registering the URI and the expected client behavior in the Rights registry" ... which doesn't exist, perhaps because no one has tried to do this ... until now.

Propose to make this change for 4.0

(Thanks to @alliomeria for pushing on this!)

[alliomeria]

Thanks for opening this related issue @azaroth42!

[BartChris]

Somewhat related:
The IIIF-Validation for 3.0 does not allow using

https://creativecommons.org/publicdomain/mark/1.0/

in rights, although this has been used in version 2-manifests for license. Is there a reason why the property has been restricted to the license domains on CC?

Error 1 of 1. Message: 'https://creativecommons.org/publicdomain/mark/1.0/' does not match 'http://creativecommons.org/licenses/.*'

Edit: I have to correct myself:
It seems like the https variant is not allowed

https://creativecommons.org/publicdomain/mark/1.0/

but the http variant is.

http://creativecommons.org/publicdomain/mark/1.0/

So the problem is more that the validator https://presentation-validator.iiif.io/ gives a misleading error message.