The gist of llms is that they use the same interface humans use, text. Llms do not use an alternative llm only channel or api for communication. Llms have no

The gist of llms is that they use the same interface humans use, text. Llms do not use an alternative llm only channel or api for communication. Llms have no problem reading a website, if you implement this dumb standard as a website owner you are duplicating the things an llm can read. And if you implement this as an llm tool dev, you are now reading two different sources of information, you are now tasked with integrating them and resolving differences, and opening yourself up to straight up lying. If a website says one thing to humans and another to llms, which one would you rather display to the user? That's right, the thing humans actually see. If llms benefit from a standarized side channel for transmitting metadata, it needs to: 1-not be the actual data 2- be a bit more explicit about what data is transmitted. This standard proposes syntax but leaves actual keys up to the user? Sections are called Optional, docs, FastHTML? Have some balls pick specific keys and bake them into your proposal, and be specifically useful. Sections like: copyright policy, privacy policy, sourcing policy, crowdsourcing, legal jurisdiction, owner. Might all be useful, although they would not strictly be llm only.