2. A bit of background info…
• Citysearch editors use video content
eg: Movie reviews
• Copy-pasting embed HTML
• Makes media content hard to index, re-use
and error prone
• We wanted to add a video module to our new
CMS
4. oEmbed
• A open web service specification
– Allows third party content providers (ie:
Citysearch) to
– request media content meta-data (including
iFrame HTML) using the media URL
– from the original content provider (ie:
YouTube)
5. How?
• Original content provider creates the
REST/JSON service adhering to the oEmbed
specification
• Makes the service discoverable by including the
end-points in the <HEAD> of their existing
(X)HTML documents
8. Third party consumers
• Invoke the service by passing the URL and
response type as mandatory parameters
• There can be optional parameters too
– Video width and height for instance
13. Minor bumps on the road
• Most of the video content from YouTube
• YouTube's oEmbed service doesn't support
jsonp callbacks
• Jquery-oembed uses Embed.ly === $$$$
• We wrote a service wrapper for YouTube
• Patched jquery-oembed.js to use our end-
point instead