Because it's not what you thing and doesn't solve the problems most companies have.
Firstly jsonld is only a format for serializing semantic metadata, nothing more, so it only specifies how you can attach that metadata, but not what exctly can be attached in what way with what subtle meanings.
Secondly it's one of this very generic tools which "can solve everything" but in practice often
only make things more complicated as long as you don't have enough very complicated (and matrue!) tooling around it.
And that's where the problem lies, the availability and maturity of this tooling is limited and awareness or experience about which tooling is good and mature and which isn't often is missing too.
So it's easy to end up with adding a lot of complexity with very little gain, hence why most avoid it. Through some companies had success with it, but their are often on the size of SAP or similar.
> This expandable graph seems like the purest representation of all data in a company.
Yes, but requires you to have all the data in the right format correctly annotated, correctly maintained and changed and available often non of this is true.
> Imagine hovering over a UI element and seeing who implemented it and when
This would need a proper integration of json-ld in the version manager and development flow, project manager, and probably more. There is a good chance that whatever tooling you use has not integration for any of this points, not even considering that you then still need to bind the data together (query) in a usable performant way which might having a non graph db for caching common queries etc. Each of this points being likely a non trivial sub project, one which most companies wouldn't want to afford for some minor benefit like having such a tooltip in a UI builder.
Now if everyone would always support the semantic web, and would agree on common annotations for all kind of metadata (far beyond the scope of the jsonld spec) and would add accessible apis based on this to their product etc. _then yes it would be grate_.
Yeh I think it's way too complex to shoe-horn in later with minimal benefit.
But new databases are being built at new companies every day. A lot of new companies I see, build out their first MVPs, CRMs, etc. adhoc in Airtable. Then some mockups in Figma. Then they bring in the devs to build a RDBMS.
Now if all these low-code tools worked on manipulating a single graph instead of building a bunch of disparate relational databases...that would be cool. And then you just need a good graph database to build web apps with.
I think a bunch of tools need to be re-invented with this in mind.
> would agree on common annotations for all kind of metadata
Thinking about a project/task manager for example. They all pretty much have similar schemas at this point. There is also a huge industry in connecting tools together. Zapier/IFTTT/Unito/etc. Everything is adhoc though or proprietary. Standardization is slow and boring.
I think the best thing would be if someone made a schema for this that gained wide adoption, and then the transformers from these existing applications fed into this graph. Basically using a graph db instead of relational or key-value.
Firstly jsonld is only a format for serializing semantic metadata, nothing more, so it only specifies how you can attach that metadata, but not what exctly can be attached in what way with what subtle meanings.
Secondly it's one of this very generic tools which "can solve everything" but in practice often only make things more complicated as long as you don't have enough very complicated (and matrue!) tooling around it.
And that's where the problem lies, the availability and maturity of this tooling is limited and awareness or experience about which tooling is good and mature and which isn't often is missing too.
So it's easy to end up with adding a lot of complexity with very little gain, hence why most avoid it. Through some companies had success with it, but their are often on the size of SAP or similar.
> This expandable graph seems like the purest representation of all data in a company.
Yes, but requires you to have all the data in the right format correctly annotated, correctly maintained and changed and available often non of this is true.
> Imagine hovering over a UI element and seeing who implemented it and when
This would need a proper integration of json-ld in the version manager and development flow, project manager, and probably more. There is a good chance that whatever tooling you use has not integration for any of this points, not even considering that you then still need to bind the data together (query) in a usable performant way which might having a non graph db for caching common queries etc. Each of this points being likely a non trivial sub project, one which most companies wouldn't want to afford for some minor benefit like having such a tooltip in a UI builder.
Now if everyone would always support the semantic web, and would agree on common annotations for all kind of metadata (far beyond the scope of the jsonld spec) and would add accessible apis based on this to their product etc. _then yes it would be grate_.