I ought to say some things about json-ld, because I think a lot of people aren't familiar with the details of it.
- You can play with json-ld live here: https://json-ld.org/playground/
- JSON-LD lets you have extensions but map them to local "compacted" shorthands, while still allowing to expand out into unambiguous form.
- JSON-LD does allow converting to a RDF graph, but it's not required. (It is interesting, though.)
- Unlike most specs, JSON-LD has a complete implementation guide https://www.w3.org/TR/json-ld-api/ Some people have been complaining on here that it's non-normative, but of course it's not normative. For example, the algorithms here are imperative, and it's legal to rewrite to a functional style without breaking the spec.
- The JSON-LD test suite is *fantastic* and if you do an implementation, will really catch a lot of things
@cwebber Wow, full URIs sounds a bit hypocritical, considering they want plain JSON.
I feel like the JSON-LD disconnect is specific to the distributed nature of AP.
In the JSON-LD world, producers simply tack context onto their existing data. Old-school consumers can rely on the same old JSON struct. And yet, data is now linked.
But in AP, we're all peers, and consuming data from producers we don't know. So JSON-LD processing is a hard requirement, and the "It's just JSON" no longer holds.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!