Earlier quoted context omitted.
I don't fully understand XSLT, but I've been building something which I believe solves a similar problem (albeit JSON-LD and Javascript). The general XML ecosystem of solutions have always looked really complex to me. You need to understand a lot more types/elements than I think is reasonable for people to author with but they are from before my time. I took a look at XForms 2 and it had its own way of defining funct…
Oh I can't say I like XML and XSLT for the syntax or (lack of) terseness. I appreciate how it handles templating via selectors, logical operations, and runs as a first party templating engine in the DOM without depending on the JS runtime. I once built a full RSS reader in XSLT. I had to proxy requests to avoid CORs, but it was all based on an XSLT template for OPMLs that would fetch each feed, parse them, chuck the…
JSON-LD explained for personal websites
51–60 of 94 posts
Re: JSON-LD explained for personal websites
#52Re: JSON-LD explained for personal websites
#53> It can aid web crawlers in understanding the semantic structure of your site, qualifying you for richer link previews, and even potentially improving your search ranking. This is fighting the last war, to stretch a metaphor. As far as I and my WWW site are concerned, Google has nowadays switched to giving people lengthy LLM-generated versions of my stuff, with errors, above pointing people to my actual stuff. 'Brea…
Re: JSON-LD explained for personal websites
#54Re: JSON-LD explained for personal websites
#55For seo purpose, the kind of JSON-LD a search engine will support is very specific and limited. You are far better consulting the targetted search engine's documentation (Google[1], Bing[2]) and following that. Anything else is a waste of time.
Outside of search engines, again, without a specific purpose, JSON-LD is mostly useless. If you have a specific need that requires JSON-LD, go ahead and include the data you know will be useful. Including anything else is like shouting into the void.
IndieWeb[3] does use structured data but considers JSON-LD a DRY violation and uses Microformats[4] instead.
1: https://developers.google.com/search/docs/appearance/structu...
2: https://www.bing.com/webmasters/help/marking-up-your-site-wi...
Re: JSON-LD explained for personal websites
#56Earlier quoted context omitted.
If you want a world where the data you present like this matters, seed it. Even if google doesn't use it, the collective internet applying this kind of metadata makes the web fertile for non-LLM-scraping competitors to provide an alternative option. Rolling over to google only ensures that they remain dominant, with a high bar for competitors, and driving them to use the same technologies.
Interestingly, there is llms.txt (like robots.txt) which is a new emerging standard to aid AI in crawling and gathering data from your website.
Re: JSON-LD explained for personal websites
#57> It can aid web crawlers in understanding the semantic structure of your site, qualifying you for richer link previews, and even potentially improving your search ranking. This is fighting the last war, to stretch a metaphor. As far as I and my WWW site are concerned, Google has nowadays switched to giving people lengthy LLM-generated versions of my stuff, with errors, above pointing people to my actual stuff. 'Brea…
If you want a world where the data you present like this matters, seed it. Even if google doesn't use it, the collective internet applying this kind of metadata makes the web fertile for non-LLM-scraping competitors to provide an alternative option. Rolling over to google only ensures that they remain dominant, with a high bar for competitors, and driving them to use the same technologies.
"The Semantic Web" and all related ideas were always a failure. The metadata quickly got out of date, was never correct in the first place, was only ever implemented on a teeny minority of sites, and always suffered from bad actors where the metadata didn't match the content.
Heck, even before LLMs I'd argue that Google won because they were the best at organizing vast amounts of unstructured data. With LLMs it's even more pointless to have the author generate this metadata - better to have an LLM generate it based on what visitors can actually see when they visit the site.
Re: JSON-LD explained for personal websites
#58Re: JSON-LD explained for personal websites
#59Reinventing XML but worse.
Re: JSON-LD explained for personal websites
#60A bit disappointing that (IIUC) for the common parsers you have to say everything twice, in HTML and in the accompanying JSON-LD form even though RDFa exists for the exact purpose of letting you point at the values already present in your markup. (Admittedly RDFa is perhaps too flexible for its own good when you just want to mark up some stuff, but if you’re writing a full parser anyway dealing with a bit of excessiv…
Granted, all of this is not for SEO purposes, but part of the ActivityPub ecosystem, which also uses JSON-LD for data encoding.