3 ms·
There are a number of opportunities to solve for carbon.txt, security.txt, content licenses, indication of [AI] provenance, and do better than robots.txt; hopef
by westurner 3y ago
There are a number of opportunities to solve for carbon.txt, security.txt, content licenses, indication of [AI] provenance, and do better than robots.txt; hopefully with JSON-LD Linked Data.
> https://news.ycombinator.com/item?id=35888037 https://news.ycombinator.com/item?id=35888037 : security.txt, carbon.txt, SPDX SBOM, OSV, JSON-LD, blockcerts
"Google will label fake images created with its A.I" (re: IPTC, Schema org JSON-LD" (2023) https://news.ycombinator.com/item?id=35896000 https://news.ycombinator.com/item?id=35896000
From "Tell HN: We should start to add “ai.txt” as we do for “robots.txt”" (2023) https://news.ycombinator.com/item?id=35888037 https://news.ycombinator.com/item?id=35888037 :
> How many parsers should be necessary for https://schema.org/CreativeWork https://schema.org/CreativeWork https://schema.org/license https://schema.org/license metadata for resources with (Linked Data) URIs?