@reiver I wish I was a bit more knowledgeable about these things, and I'm working on that, but I would like to say jsonld is very confusing to entry level folks. Though I assume it will become more and more familiar. Personally I'm all about yamlld because it's yaml, and linkml.
I agree that JSON-LD is very confusing for entry level people.
And I think that is a bad thing for the Fediverse.
...
At first, JSON-LD seems like regular JSON with some weird extra stuff added, but — if you tried to use it like regular JSON you would have problems.
The paths to data can be different in JSON-LD documents for the exact same information.
For example in one document it might be:
data.publicKeyBase64
In another it might be:
data["toot:publicKeyBase64"]
In yet another it might be:
data[0]["http;//joinmastodon·org/ns#publicKeyBase64"][0]["＠value"]
...
You need to use what it calls "expanded JSON-LD" for it to work more like JSON.
Which isn't obvious.
And extra coding work, that adds complexity.
But even then, the paths are complicated in a way that makes the developer-ux worse.
@reiver I follow and agree.
The tools involved are out there and getting better, but, yeah, learning curve for these different forms (compact, expanded, etc.)
I'm developing a modeling tool that I hope works from standard to schema to instance data. If the modeling is right and allows for interop, it should be smoother for all. LinkML is the best answer I have for now.