Bug 25269 mentions needing a way to embed Commons videos into WordPress blogs; once whitelisted, the embedding information can be exposed to WordPress via oEmbed (bug 25854) -- however currently we don't have stable embedding code.
Embedding in arbitrary sites is currently done using an experimental setup built around the mwEmbed player, which isn't actually fully set up natively on Commons etc. The result is that the embedding HTML code includes unstable URLs referring to a prototype site with a bunch of mwEmbed-specific paths in it.
I think we'll want to have a stable URL on the wiki for the referenced object for the embedding; then we can expose _that_ and let the wiki worry about whether it needs to pull in OggHandler, mwEmbed, or whatever is appropriate *at view time* based on presently-deployed tech and file formats.
My notes on this from bug 25269:
The embedding HTML currently exposed via the MwEmbed JS stuff seems pretty
weird:
<object
data="http://prototype.wikimedia.org/mwe-gadget/mwEmbed/remotes/../mwEmbedFrame.php?apiTitleKey=Nice_People_MEDIUM.ogv&apiProvider=commons&skin=kskin&durationHint=86&width=640&height=360"
width="640" height="382" style="overflow:hidden" ></object>
We probably want to have stable embedding URLs that'll use whatever the current
appropriate technology is -- since the references will be used in blog posts
etc on other sites, they'll need to be stable and functional over a period of
many years. That means avoiding test hostnames and hardcoded extension paths.
The above even isn't even referencing the core servers, so I'm assuming this is
a whole bunch of custom JS stuff that isn't accessible within MediaWiki itself,
such as to generate the embedding code direct from MediaWiki... what's the
story on this currently?
Might want to see something more like this:
<object
data="http://commons.wikimedia.org/wiki/Special:EmbedMedia/Nice_People_MEDIUM.ogv?durationHint=86&width=640&height=360"
width="640" height="382" style="overflow:hidden" ></object>
The embedding URL should stay the same whether we're currently using
OggHandler, mwEmbed, or some unrelated video format handler to display the
file.
Version: unspecified
Severity: enhancement