Quote:
Originally Posted by sexobon
Since the preview of the quote continues to be fine in the Cellar software, I'd guess the issue is at the Vimeo end; but, who knows.
|
I may have guessed right!
I asked Google "Why does the VIMEO URL link display a video?" Among the results I found was
Vimeo supports oEmbed, which allows you to turn a Vimeo URL into an embed link. I followed a link therein to
oEmbed is an open standard for embedding videos and/or images into a website. A link in that page led me to the explanation:
Quote:
oEmbed is a format for allowing an embedded representation of a URL on third party sites. The simple API allows a website to display embedded content (such as photos or videos) when a user posts a link to that resource, without having to parse the resource directly. …
… 1. Quick Example
A consumer (e.g. WordPress) makes the following HTTP request:
HTML Code:
http://www.flickr.com/services/oembed/?format=json&url=http%3A//www.flickr.com/photos/bees/2341623661/
The provider (e.g. Flickr) then responds with an oEmbed response:
HTML Code:
{
"version": "1.0",
"type": "photo",
"width": 240,
"height": 160,
"title": "ZB8T0193",
"url": "http://farm4.static.flickr.com/3123/2341623661_7c99f48bbf_m.jpg",
"author_name": "Bees",
"author_url": "http://www.flickr.com/photos/bees/",
"provider_name": "Flickr",
"provider_url": "http://www.flickr.com/"
}
This allows the consumer to turn a URL to a Flickr photo page into structured data to allow embedding of that photo in the consumer's website.
|
In our case, the Cellar is the
consumer and VIMEO is the
provider. It seems that the provider can choose to convert the VIMEO URL into an oEmbed HTTP request at the provider's site. The sharing properties of your video does say that it contains a text code. The provider (VIMEO) then gives an oEmbed response and controls whether or not posting a URL results in a video appearing.
That's my story and I'm sticking to it (until someone proves me wrong).
