This document proposes a machine-readable Hypertext Transfer Protocol (HTTP) response header field, AI-Disclosure , to disclose the presence and degree of Artificial Intelligence (AI) generated or AI-assisted content in web responses. The header is designed for compatibility with HTTP structured field syntax and provides metadata for user agents, bots, and archiving systems. It supports layered disclosure strategies alongside human-readable and structured metadata formats.| www.ietf.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page] | www.rfc-editor.org
This specification defines common infrastructure that other specifications can use to interact with browser permissions. These permissions represent a user's choice to allow or deny access to "powerful features" of the platform. For developers, the specification standardizes an API to query the permission state of a powerful feature, and be notified if a permission to use a powerful feature changes state.| www.w3.org
This document describes the technical specification for a file format to exchange design tokens between different tools.| second-editors-draft.tr.designtokens.org
Unicode Technical Standard #35| www.unicode.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Info page] | www.rfc-editor.org
[RFC Home] [TEXT|PDF|HTML] [Tracker] [IPR] [Errata] [Info page] | www.rfc-editor.org