First described on Sat 24 Nov 2012 by Nils Dagsson Moskopp.

On Mon, Dec 17, 2012 at 4:37 PM, Ian Hickson <ian@hixie.ch> wrote:
>
> You have a Web page with a single "major" <video> or <audio> element
> in it, e.g. the YouTube watch page, and you want to be able to link
> to that page with a fragment identifier that causes the video to
> start playing at a particular time, without any scripts involved.
>
> Also, from within a page, use a hyperlink to cause a media element
> to seek to a specific time, in response to user interaction, without
> any scripts involved.

On Tue, 18 Dec 2012, Nils Dagsson Moskopp wrote:
>
> I want to be able to link to a media element in the context of a
> particular page at a particular time via a URI. Starting playing is
> something that is already handled by the autoplay attribute, being
> able to link to an element at a particular time is the issue at
> hand.
>
> Since one can have multiple media elements on a page – for example,
> in a blog post – I find it important to be able to address a
> specific element, like
> <http://example.org/podcast.html#episode1&t=01:23>. (A solution
> where the fragment addresses the element with parameters would
> preserve most current semantics. Would using the ampersand for
> parameters be web-compatible?)

On Tue, 18 Dec 2012, Nils Dagsson Moskopp wrote:
>
> http://daten.dieweltistgarnichtso.net/src/media-fragments-html-polyfill/

On Wed, 19 Dec 2012, Philip Jägenstedt wrote:
>
> Redefining/extending what the fragment component does for HTML is
> somewhat risky, so it really comes down to what exactly the
> processing should be.
>
> What should a browser do with a URL ending with #foo&t=10 if there
> is an element on the page with id="foo&t=10"? What about #foo&bar if
> there is an element with id="foo"? I would be surprised if treating
> #foo& the same as #foo were Web compatible...

More data at:
   http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0222.html