Post 9gBi063wpLAZVAUmi8 by mrtoto@chaos.social
 (DIR) More posts by mrtoto@chaos.social
 (DIR) Post #9gAnzZERIQqsFIZcqe by rixx@chaos.social
       2019-02-24T22:07:59Z
       
       0 likes, 0 repeats
       
       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?
       
 (DIR) Post #9gAoIUYAvWcBEBpRxo by rixx@chaos.social
       2019-02-24T22:11:25Z
       
       0 likes, 0 repeats
       
       As the last schema.org release was in 2017, I'm a bit afraid on beating a dead horse by going with them …
       
 (DIR) Post #9gB6Zekm2jZuyE3XZw by 61@en.osm.town
       2019-02-25T01:36:12Z
       
       0 likes, 0 repeats
       
       @rixxIt *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.
       
 (DIR) Post #9gBi063wpLAZVAUmi8 by mrtoto@chaos.social
       2019-02-25T08:35:34Z
       
       0 likes, 0 repeats
       
       @rixx For API formats I would use https://jsonapi.org nowadays. Simple, not overengineered, solves a lot of common problems.
       
 (DIR) Post #9gBtHrcQMoM5PfIQIS by allo@chaos.social
       2019-02-25T10:42:02Z
       
       0 likes, 0 repeats
       
       @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.
       
 (DIR) Post #9gBtOm7PDPRoNh5D0a by allo@chaos.social
       2019-02-25T10:43:17Z
       
       0 likes, 0 repeats
       
       @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.