- From: Steven Pemberton <steven.pemberton@cwi.nl>
- Date: Tue, 12 Sep 2023 08:46:59 +0000
- To: David Woolley <forums@david-woolley.me.uk>, www-html@w3.org, rfc@ritman.com
RDFa will give you the functionality you need for this. https://www.w3.org/MarkUp/2009/rdfa-for-html-authors Best wishes, Steven Pemberton On Monday 11 September 2023 18:32:16 (+02:00), David Woolley wrote: > HTML was never maintained through the Internet RFC mechanism. > > W3C no longer maintain the HTML specification, that is under the control > of an industry consortium called WHATWG. The W3C produced > specifications do not allow META as a child of DIV. I'm not clear on > the the WHATWG ones as they don't have a DTD. > > What you are describing is not a tag, but a metadata name (for use in > META elements). > > On 11/09/2023 04:45, rfc@ritman.com wrote: > > There is a great fear among content publishers of being penalized by > > search engines for using AI generated content, so I wish to propose this > > tag if it does not exist so that users can know they are consuming AI > > generated content, and search engines will "know" that it is in fact AI > > generated content, and weigh that in to the algorithm that determines > > the value of any given content versus the given search term. > > > > Is this the correct email thread? If not could you please help point me > > to the correct resource? Thank you very much. I am afraid I do not know > > how to research this properly as I have never even though of submitting > > a new META tag until now. I appreciate you > > > > - Richard Monahan > > > > > > > > > > RFC Proposal: AI-Generated Content Meta Tag > > Abstract > > This RFC proposes the addition of a new meta tag in HTML to indicate > > that content on a webpage has been generated by artificial intelligence > > (AI) systems. The purpose of this meta tag is to provide transparency to > > users and enable web browsers, search engines, and other user agents to > > handle AI-generated content appropriately. > > > > Status of This Memo > > This document is a proposal for an Internet Standard. Distribution of > > this memo is unlimited. > > > > Table of Contents > > Introduction > > > > Motivation > > Scope > > Specification > > > > Definition of the Meta Tag > > Syntax > > Examples of Usage > > Use Cases and Benefits > > Security Considerations > > > > Privacy > > Trustworthiness > > IANA Considerations > > > > Registration of the 'ai-generated' Meta Tag > > References > > > > Relevant standards and documents > > 1. Introduction > > 1.1 Motivation > > AI-generated content is becoming increasingly prevalent on the web, and > > users may benefit from knowing when content has been created by AI > > systems. This meta tag proposal aims to provide a standardized way to > > indicate AI-generated content. > > > > 1.2 Scope > > This RFC defines a new meta tag, "ai-generated," that can be added to > > HTML documents to indicate AI involvement in content generation. > > > > 2. Specification > > 2.1 Definition of the Meta Tag > > The "ai-generated" meta tag is used to indicate that the content within > > the HTML document has been generated, in whole or in part, by artificial > > intelligence systems. > > > > 2.2 Syntax > > The "ai-generated" meta tag can be added to the <head> section of an > > HTML document as follows: > > > > html > > Copy code > > <meta name="ai-generated" content="true"> > > 2.3 Examples of Usage > > Example 1: Entire Page Generated by AI > > html > > Copy code > > <!DOCTYPE html> > > <html> > > <head> > > <meta name="ai-generated" content="true"> > > <title>AI-Generated Page</title> > > </head> > > <body> > > <!-- AI-generated content here --> > > </body> > > </html> > > Example 2: AI-Generated Section > > html > > Copy code > > <!DOCTYPE html> > > <html> > > <head> > > <title>Web Page</title> > > </head> > > <body> > > <div> > > <p>This section is AI-generated.</p> > > </div> > > <div> > > <meta name="ai-generated" content="true"> > > <!-- Additional content --> > > </div> > > </body> > > </html> > > 2.4 Use Cases and Benefits > > Improved transparency for users. > > Enhanced search engine optimization (SEO) by allowing search engines to > > understand AI-generated content. > > 3. Security Considerations > > 3.1 Privacy > > Implementers should consider privacy implications when using the > > "ai-generated" meta tag, especially when AI-generated content may > > involve personal data. > > > > 3.2 Trustworthiness > > The use of this meta tag should not imply that the content is > > trustworthy or free from potential biases introduced by AI systems. > > Users should exercise caution and critical thinking when encountering > > AI-generated content. > > > > 4. IANA Considerations > > This section describes the registration of the "ai-generated" meta tag > > with the Internet Assigned Numbers Authority (IANA). The details of this > > registration are specified in [IANA registry link]. > > > > 5. References > > RFC 1866 - Hypertext Markup Language - 2.0 > > > > URL: RFC 2070 > > This RFC addresses internationalization issues in HTML and may > > indirectly relate to META tags used for language or character encoding. > > RFC 2731 - Encoding Dublin Core Metadata in HTML > > > > URL: RFC 2731 > > While not a generic META tag specification, this RFC discusses encoding > > Dublin Core metadata within HTML documents, which involves the use of > > META elements. > > RFC 2854 - The 'text/html' Media Type > > > > URL: RFC 2854 > > This RFC discusses the 'text/html' media type used for HTML documents. > > It doesn't cover META tags directly, but it's relevant to the broader > > context of HTML content. > > > > > > > >
Received on Tuesday, 12 September 2023 08:47:29 UTC