Vocabulary For Expressing Content Signals

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 4 April 2026.¶

Copyright Notice

Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

This proposal introduces and aims to define a specific set of preferences to address the need for expressing how digital assets can be used by automated systems, particularly in the context of training artificial intelligence (AI) models and generating search results. These preference categories enable clear and explicit communication of preferences regarding the use of digital assets for search indexing and AI training.¶

2. 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 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶

For the purposes of this document, in addition to the definitions in Section 4 of [AIPREF-VOCAB], the following terms are used:¶

• Search Results: hyperlinks and short excerpts returned from contents of the retrieved asset(s)¶

• Retrieval-Augmented Generation (RAG): A technique where external content is retrieved at query time and supplied to a model to condition the generated output (B. Silver)¶

3. Vocabulary Definition

4. Usage Category Labels

Each usage category in Section 3 is mapped to a short textual label. Table 1 specifies this mapping.¶

5. Security Considerations

TODO Security¶

6. IANA Considerations

This document has no IANA actions.¶

7. Addendum

The definition definition for Search (3.1) provided in this document may be replaced with the Search Category definition proposed in [AIPREF-VOCAB] and copied below:¶

Using one or more assets in a search application that directs users to the location from which the assets were retrieved. Search applications can be complex and may serve multiple purposes. Only those parts of applications that direct users to the location of an asset are included in this category of use. This includes the use of titles or excerpts from assets that are used to help users select between multiple candidate options.¶

Preferences for the Search category apply to those parts of applications that provide search capabilities, regardless of what other preferences are stated.¶

Parts of applications that do not direct users to the location of assets, such as summaries, are not covered by this category of use.¶

The use of assets for Search is a proper subset of Automated Processing usage.¶

8. References

Appendix A. Acknowledgments

TODO acknowledge.¶

Authors' Addresses