]> Creative Commons

timid@creativecommons.org

Web and Internet Transport AI Preferences AI Preferences Artificial intelligence Public Interest This document proposes an update to the AI preferences vocabulary in order to establish protected uses (exclusions). About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the AI Preferences Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .

Introduction This proposal establishes exclusions within the AI preferences to protect public interest activities. These exclusions help balance content holder agency, end user priority, and public interest activities that remain essential for the open web. Creating explicit exclusions from AI preferences for public interest activities will create certainty and, therefore, strengthen their position. It proposes a new "Public Interest Exclusions" section in . This proposal can also be viewed as a .

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Statements of Preference See .

Understanding Preferences See .

Public Interest Exclusions Regardless of the preferences expressed, the following public interest uses are excluded:

• Anyone can use the assets for malicious content detection
  • For example: A website that permits user uploads may use the assets to develop or use tools that detect harmful content according to established terms of use.
• Any end user can use the assets for internationalization and localization, and for accessibility tools to aid individuals with accessibility needs
  • For example: Individuals with accessibility needs may utilize software that uses the assets to access automated captions or generate accessible formats.
• Organizations that preserve expressed preferences can use the assets for public archiving
  • For example: An archive that preserves preferences may use the assets to improve the metadata associated with assets or help with discoverability.
• Cultural heritage institutions and not-for-profit research and/or educational organizations can use the assets for analysis and research
  • For example: A cultural heritage organization may use the assets to provide more useful, reliable, or discoverable access to historical web collections.

Security Considerations See .

IANA Considerations This document has no IANA actions.

References Normative References Open Future Mozilla In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Informative References Digital Medusa Internet Archive n.d.

Acknowledgments The following individuals made significant contributions to this document:

• Diyana Noory
• Sarah Pearson
• Vito Quaglia