Skip to content

Design Decisions

Nick Evans edited this page Jul 14, 2017 · 2 revisions

Design Decisions

JSON vs. XML

For JSON:

  • The CEO of British Orienteering (one of the most data literate sports due to their demographic), said that although there is an XML standard for Orienteering, everyone finds it too difficult to use XML, so they ended up implementing their data feed in JSON, and it has proven popular among the Orienteering community

  • Two major booking systems we're aware of, Legend and MINDBODY, are both currently rewriting their SOAP API into a JSON API to "modernise".

RDF vs. Schema.org

For Schema.org:

  • It has been suggested that a pragmatic solution to recommending a variety of RDF vocabularies to the sector, is to work on a schema.org extension which includes the subset of those vocabularies that we want the sector to adopt. This will make it much easier for the sector to implement.
Clone this wiki locally