Currently, it's rather difficult to use OSEM and embed a schedule into another website. We currently use OSEM for the backend, but still use a different system for our main site. This change allows us to dynamically embed the schedule in our main website as well as allow us a simple way to get data for the use in mobile applications or similar.
This limits the JSONP support to only GETS on json formatted requests. This prevents any XSS even though we don't require a authenticity token.
