'''Some information about oEmbed and MediaMosa.
'''
 Official oEmbed site:[[BR]]
 http://www.oembed.com/

 MediaMosa oEmbed:[[BR]]
 /services/oembed [GET]

 Parameters:
 - format: The required response format. Value (when supplied) must be
 either "xml" or "json". Optional, default: json.
 - maxheight: The maximum height of the embedded resource. Optional.
 - maxwidth: The maximum width of the embedded resource. Optional.
 - mediafile_id. Mediafile_id or still_id is required.
 - provider_name: Name of the provider. Optional.
 - provider_url: URL of the provider. Optional.
 - still_id. Mediafile_id or still_id is required.

 oEmbed it typically client side feature. Because the consumers see only
 the front-end when they do an oEmbed request. And MediaMosa doesn't have
 information, that which video or image is on the clients pages.
 Eg.
{{{
 http://www.youtube.com/oembed?url=http%3A//youtube.com/watch%3Fv%3DM3r2XDceM6A&format=json
}}}

 MediaMosa oEmbed REST call is a helper function for the clients. If the
 client support a few information, then MediaMosa generate a correct oEmbed
 response.
 MediaMosa oEmbed support video or photo oEmbed response.

 Examples:

 If the client wants a video response in xml format, then:
 /services/oembed [GET]
 - format=xml
 - mediafile_id: mediafile id of the video
 - provider_name: name of the client, eg. MediaMosa. It will be visible in
 the response.
 - provider_url: url of the provider, eg. http://mediamosa.org/ It will be
 visible in the response.

 If the client wants an image repsonse in json format, then:
 /services/oembed [GET]
 - format=json  (this is the default)
 - provider_name
 - provider_url
 - still_id: still id of the still image