You would not want to hard code the |high quality or |low quality version to the article / wiki syntax. The idea is that you just put something like [[Stream:my_movie]] or [[File:my_movie.ogg]] (in your example) and then based on the client bandwidth, client supported codecs, local language, and client player preference and the available streams on the server the javascript player choses the appropriate set of video, audio, and text streams to playback.

Its not quite the same problem as existing File namespace transformations system. Same temporal meaning files are not _only_ files programmability transcoded from a single my_video.ogg source. Its different from the thumbnails or flattened SVGs derivatives. Aside from the issue of associating dubbed audio tracks, Users will never upload their original HD footage because of bandwidth constraints and for maximum quality on the low-end version we want to create the low bandwidth derivatives from the original footage so the derivatives will not really be a "temporary file" that can easily be regenerated.

We can certainly overload the File namespace as you suggest to enable such associations but the minimal hierarchy of a Stream namespace to associate specific identical temporal meaning files seems cleaner/worthwhile to me. It will mean that a single File: page will be associated with many actual "files" that may have different licenses etc.

The stream namespace also contains interfaces for associated layers of timed text putting all those associations into the File namespace may complicate things but we can go that way if its the consensus.

peace, --michael

Platonides wrote:

Michael Dale wrote:

...

If we want to support multiple quality settings for a single "stream" this will require a bit more infrastructure. Specifically I propose we add another namespace for temporal media called Stream: and have it directly map to ROE xml something like: http://tinyurl.com/72x57r more info on ROE http://wiki.xiph.org/index.php/ROE

File:my_movie_low_quality.ogg and File:my_movie_high_quality.ogg would soft redirect to Stream:my_movie and all the meta info would be stored there. The Stream namespace also allows us to group other media tracks that share a temporal meaning such as multiple language audio dubbing and multilingual transcripts/ subtitles. The javascript player can then dynamically select audio language and or subtitles based on the user language.

No need. Users would use [[File:my_movie.ogg|high]] or [[File:my_movie.ogg|low]] The actual ROE file would be at upload/thumb/f/fa/my_movie.ogg/my_movie-ROE.ogg (or Special:MvExportStream as metavidwiki does) as other types do. Same for the other temporary files.

---

Commons-l mailing list Commons-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/commons-l