Showcase

From Media Fragments Working Group Wiki
Revision as of 17:36, 10 April 2012 by Rtroncy (Talk | contribs)

Jump to: navigation, search

Goal

This page aims to reference all existing implementations or applications using the Media Fragments URI specification.

The applications and implementations referenced below will appear shorty in a showcase portal at http://mediafragments.org/

Existing implementations

Developers: Do not hesitate to mail public-media-fragment@w3.org your showcase application to be added in this table

Product Lead developer Comments
Firefox (nightly or Firefox 9+) (demo), see announcement Mozilla / Chris Double Supports the temporal dimension of Media Fragment URI, see also the implementation report
WebKit, see bug closed and test cases Apple / Eric Carlson Supports the temporal dimension of Media Fragment URI
Chrome, see announcement Google Supports the temporal dimension of Media Fragment URI
mediafragment.js (github) Thomas Steiner A javascript library parsing media fragment URIs and that can be used as a polyfill for various browsers, see also the implementation report
NinSuna Media Fragments Player (demo) Wim Van Lancker An HTML5-based video player supporting both the temporal and the spatial dimensions, see also the implementation report
Synote Media Fragment Player (UK parliament demo) Yunjia Li A client-side implementation of the temporal dimension, see also the implementation report
Ligne de Temps platform Vincent Puig et Raphaël Velt A client-side implementation of the temporal and spatial dimensions enabling to create and share media fragments
EuropeanaConnect Media Annotation Prototype (demo and github) Europeana / Austrian Information Institute / Simon Rainer Annotation prototype generating media fragments URI for the spatial dimension only at the moment
NinSuna Media Fragments Server (demo) Davy Van Deursen An implementation of the media fragments processing recipes for the temporal and the track dimensions. Media segments can be requested by using the query parameter and/or through the HTTP range header. It is important to notice that no transcoding is applied to create the media segments. More specifically, all segments are extracted from the original media resource.