]> Creative Commons

timid@creativecommons.org

Web and Internet Transport AI Preferences AI Preferences Artificial Intelligence This document defines how parameters can be added to AI Preferences. 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 document defines how parameters can be added to AI Preferences .

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.

Parameters As noted in :

• The format relies on the Dictionary type defined in .

The AI Preferences can be extended with parameters. The parameter syntax is defined in ():

• Parameters are an ordered map of key-value pairs that are associated with an Item (Section 3.3) [...]. The keys are unique within the scope of the Parameters they occur within, and the values are bare items (i.e., they themselves cannot be parameterized; see Section 3.3).

URI-refernces If the value of a parameter contains a URI-reference () and its value is not a valid URI-reference, the parameter MUST be ignored. If its value is a relative reference (), it MUST be resolved () before being used.

Examples Generic example: Assuming a content holder wants to highlight the presense of a tip jar: Example of categories from converted to parameters:

Security Considerations See .

IANA Considerations This document has no IANA actions.

References Normative References This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields. This document obsoletes RFC 8941. A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK] 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 Microsoft Corporation Microsoft Corporation Microsoft Corporation Microsoft Corporation

Acknowledgments The following individuals made significant contributions to this document:

• Sara Lovell