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 within 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.
For use within requiredStatement for humans and rights for machines.
Using language and standards based on larger Creative Community’s (DevianArt & others) “noai” and “noimageai” HTML tags, and licenses from RightsStatements.org:
No AI
no image or textual ML/AI at all
No Image AI
no image-based ML/AI, but textual (metadata, ocr, transcript) use ok
Regulated AI
ML/AI Use Permitted - with attribution
ML/AI Use Permitted - with express written consent and attribution
Still Needed / work in progress
Corresponding URIs for using within rights
Implementation variations for a simple use cases (apply per manifest) versus complex uses casses (apply per item/canvas)
Recipe Name
ML/AI Usage Tags Recipe
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 within 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.
These tags were initially proposed during the 2024 IIIF Annual Conference.
Overview of Initial Tags Proposed
For use within
requiredStatementfor humans andrightsfor machines.Using language and standards based on larger Creative Community’s (DevianArt & others) “noai” and “noimageai” HTML tags, and licenses from RightsStatements.org:
Still Needed / work in progress
rights