@Edent if you wanted to share what output a prompt got in your case, maybe output, or just blockquote…

if you were publishing generated text where only the last iteration was LLM generated, eg to spellcheck or improve writing, 'assisted', that seems to me an indication of a different kind, that may be more of a meta thing to disclose in an AI statement rather than something made programatically available for all content where that was done.

@Edent

Comic Sans has entered the chat

@Edent I would blockquote it, and have a special class for it with visibly different formatting, perhaps a monospace font as well to emphasize the robot-ness of it.

@Edent “ai” isn’t a valid locale, so I wouldn’t use it for a language attribute.

<output> seems to have specific semantics that don’t fit.

I voted for the Schema option.

<meta name="AI" content="true"> <!-- Or false -->

You could add partial or complete attributes to the spec.

@Edent

@Edent I don't think the organisation behind a model (OpenAI) or the model family (chatgpt) should be named, it should just be more generic: "llm", "ai" or "generated".

@Edent CSS:

#ai, .ai { background-color: black; color: black; }

@Edent I thought of a custom html tag that would prevent copying (lol) like: <ai-generated model="model name" date="date here" prompt="prompt to generate text">text here</ai-generated>

We could implement this now in validating html using the custom HTML elements api

@Edent

lang attribute is for human languages. ai is not a language. Also “ai” is the country code for Anguilla, which could appear in a lang attribute

output is for interactive elements like a calculator.

schema + itemprop: maybe! but I don’t see a clear standard yet. IPTC has metadata for gen AI images, not text

If entire doc is gen AI: JSON-LD for entire doc can indicate author, and even entity type = Person, so in theory something else can go there?

Why do you feel you need this?

@Edent No opinions other than a strong one that it should not be the “lang="ai"” version. “ai” isn't an appropriate ISO 639 language code which is what a lang attribute with this syntax should be.

@Edent I wouldn't have thought to add metadata to identify it separately from my own work.

@Edent

A dedicated <meta> tag or a custom attribute could be used to prevent repurposing existing HTML semantics like lang or output. This avoids ambiguity (e.g., lang="ai" isn’t valid) and doesn’t misrepresent the AI as an "author" (since it’s a tool, not a creator with intent).

@Edent I'd use `<blockquote>` with `<cite>` element or `<q>` for inline citation. For machine readable metadata I'd probably use `Quotation` type from Schema.org with `spokenByCharacter`, although I don't like classifying an LLM output as a creative work

@Edent I'd say using the lang attribute for that is the wrong move, as it has existing uses related to screen-readers. Different languages have different pronunciations for syllables/words that are written the same, and the screen-readers take that into account.
I imagine it might also mess up in-line automated translation tools.
Also itemId is supposed to always be a URL

Guidance for custom attributes is to use data-*, so I'd say like <p data-author="ChatGPT"> is best
https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/data-*

@Edent To me it’d feel most idiomatic to use a <blockquote>! lang=“ai” would make it impossible to say which language the AI has responded in, right? 🤔