-
Notifications
You must be signed in to change notification settings - Fork 33
0514 ml usage tags #516
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
base: master
Are you sure you want to change the base?
0514 ml usage tags #516
Changes from 3 commits
aa5c1a0
647f7e1
6241c45
e0adaf2
d166158
77074aa
507c140
b1fcc6a
19ebd3a
5c93302
6ddfc4e
eff85e4
a5bb159
5b34696
191ec32
4253edc
ae28788
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| --- | ||
| title: IIIF ML/AI Usage Tags Recipe | ||
| id: | ||
| layout: recipe | ||
| tags: [rights, requiredStatement] | ||
| summary: "Ethical ML/AI Use Tags for IIIF Manifests" | ||
| viewers: | ||
| - Mirador | ||
| - UV | ||
| topic: | ||
| - text | ||
| - presentation | ||
| property: rights, requiredStatement | ||
| --- | ||
|
|
||
| ## Use Case | ||
|
|
||
| Similar to the initiatives crafted by other content communities in efforts to limit the scraping of images and text using “noai” and “noimageai” meta HTML tags, users of the IIIF APIs may consider implementing a set of tags their IIIF manifests to help better regulate ML/AI content scraping and non-consented or attributed use of IIIF powered content in ML/AI applications. | ||
|
|
||
| ## Implementation Notes | ||
|
|
||
| Use of these standardized ML/AI Usage tags in IIIF Manifests will always need to be paired with sophisticated, up-to-date DevOps and data security practices within the context of a repository environment. | ||
|
|
||
| Recommendation to use a single applicable tag, based on the particular concerns associated with an asset's use in ML/AI applications. | ||
|
|
||
| #### For humans, within [`requiredStatement`](https://iiif.io/api/presentation/3.0/#requiredstatement) | ||
|
|
||
| ```JSON | ||
| { | ||
| "requiredStatement": { | ||
| "label": { "en": [ "No AI" ] }, | ||
| "value": { "en": [ "Material related to this IIIF Manifest should not be used for AI or ML training datasets." ] } | ||
| } | ||
| } | ||
| ``` | ||
| ```JSON | ||
| { | ||
| "requiredStatement": { | ||
| "label": { "en": [ "No Image AI" ] }, | ||
| "value": { "en": [ "Image-based material related to this IIIF Manifest should not be used for AI or ML training datasets." ] } | ||
| } | ||
| } | ||
| ``` | ||
| ```JSON | ||
| { | ||
| "requiredStatement": { | ||
| "label": { "en": [ "Regulated ML/AI Use Permitted - Attribution Required" ] }, | ||
| "value": { "en": [ "Material related to this IIIF Manifest may be used for AI or ML training datasets, as long as Standard Attribution of source content is maintained for the ML/AI dataset. Original URL of source IIIF manifest must be maintained and referenced." ] } | ||
| } | ||
| } | ||
| ``` | ||
| ```JSON | ||
| { | ||
| "requiredStatement": { | ||
| "label": { "en": [ "Regulated ML/AI Use Permitted - Consent Required" ] }, | ||
| "value": { "en": [ "Material related to this IIIF Manifest may be used for AI or ML training datasets, if Prior Written Consent is obtained from the source holding institution. Standard Attribution of source content must be maintained for the ML/AI dataset. Original URL of source IIIF manifest must be maintained and referenced." ] } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| #### For machines, within [`rights`](https://iiif.io/api/presentation/3.0/#rights) | ||
|
|
||
| * URIs to be pursued for machineable interactions, pending further discussions within the IIIF and wider repository communities during Summer 2024 and onwards. | ||
|
|
||
| #### Additional Considerations | ||
|
|
||
| * Simple use cases (apply per manifest) versus complex uses casses (apply per item/canvas) | ||
|
|
||
| * IIIF is an API based framework, geared to machine mediated interactions but: **IIIF resources are for humans** | ||
|
|
||
| * As we, professionally and personally, decide to use or integrate ML/AI tools into our repositories, we need to keep in mind our curatorial legacies and the complex nature of our own content. | ||
|
|
||
| * ML/AI technology will continue to shift over time and require diligent application and monitoring, for the rest of our professional lives. | ||
|
|
||
| ## Restrictions | ||
|
|
||
| No known restrictions. | ||
|
|
||
| ## Example | ||
|
|
||
| {% include manifest_links.html manifest="manifest.json" %} | ||
|
|
||
| {% include jsonviewer.html src="manifest.json" config='data-line="30-39"' %} | ||
|
|
||
| ## Related Recipes | ||
|
|
||
| * [Rights][0008] for demonstrating use of `rights` and `requiredStatement` | ||
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
| @@ -0,0 +1,78 @@ | ||||
| { | ||||
| "@context": "http://iiif.io/api/presentation/3/context.json", | ||||
| "id": "{{ id.url }}", | ||||
| "type": "Manifest", | ||||
| "label": { | ||||
| "en": [ | ||||
| "Picture of Göttingen taken during the 2019 IIIF Conference" | ||||
| ] | ||||
| }, | ||||
| "summary": { | ||||
| "en": [ | ||||
| "<p>Picture taken by the <a href=\"https://github.com/glenrobson\">IIIF Technical Coordinator</a></p>" | ||||
| ] | ||||
| }, | ||||
| "rights": "http://creativecommons.org/licenses/by-sa/3.0/", | ||||
| "requiredStatement": [ | ||||
|
||||
| * URIs to be pursued for machineable interactions, pending further discussions within the IIIF and wider repository communities during Summer 2024 and onwards. |
(FWIW, also have a brief note about the actionability in general)
This is a bit out of scope for this particular recipe, but It might be worth having a larger discussion about requiredStatement only permitting a single object. I can see the use case for multiple objects/statements (regardless of these potential tags), such as repositories that often have both standardized and local rights statements, where it would helpful to users to see the text for the standardized statement in full alongside the more local statements. Or where multiple language labels and paired value statements could be useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The topics can only be one of the following
I think I would go for
noteat the moment.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, just changed to
note, thanks Glen.