Okay, so asking the Fediverse is asking for biased opinions, but here it goes: If you were to specify an API format for a service, would you choose to go with schema.org definitions/fields and JSON-LD?
It *really* does depend on the sum of requirements and constraints, both written and unwritten, business domain, environment, etc.
Personally, in one project I got some inspiration from it (and other ontologies) but would not use the schema.org ontology or json-ld just for the hell of it, only if *that* was a specific functional requirement.
@rixx I started using schema.org with HTML markup, I am not sure if JSON+LD is a good idea or not. I know that some larger sites are using it, e.g. the Tele5 mediathek. And a release from 2017 is not that old in 2019.
For a new API you could use it or not. Using it has the advantage of a ready-to-use specification. But on the other hand, when you're designing the API yourself it does not matter if it follows existing specifications.
chaos.social - because anarchy is much more fun with friends.
chaos.social is a small Mastodon instance for and by the Chaos community surrounding the Chaos Computer Club. We provide a small community space - Be excellent to each other, and have a look at what that means around here.
Follow @ordnung for low-traffic instance-related updates.
The primary instance languages are German and English.