XSPF Wish List

From XiphWiki

(Difference between revisions)
Jump to: navigation, search
 
(4 intermediate revisions not shown)
Line 1: Line 1:
This page is a place to file requests for features for [[XSPF]].  Any kind of feature can be entered here, please don't be bashful.
This page is a place to file requests for features for [[XSPF]].  Any kind of feature can be entered here, please don't be bashful.
-
* Request: track start and end attributes. In many media players, a parameter, such as 'range' can be used for video files, to specify the start and stop positions of the content for the track.  An example of specifying this in the URI for the content:
+
* Request: track start and end attributes. Some media servers permit range headers in the http request, to specify the start and stop positions of the content for the track.   
-
 
+
-
<track><location>http://<myserverurl>/video.mpg?range=0-1145600</location></track>
+
-
 
+
-
 
+
-
where 0 is a long long integer denoting the ''start'' byte offset of the content and 1145600 is a long long integer denoting the ''end'' byte offset of the content.  For large video files the specification of ''start'' and ''end'' positions within the content for the track would relieve us from splitting or recoding videos just because we want to play a part of the content for the track.
+
See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35
See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35
-
Rather than specifying this as a parameter in the example URI above, include tags to denote the byte offset within the file for the track, and require long long integers.   
+
For large video files the specification of ''start'' and ''end'' positions within the content for the track would relieve us from splitting or recoding videos just because we want to play a part of the content for the track.  Please include tags to denote the byte offset within the file for the track, and require long long integers.   
* Request: MIME type of linked media
* Request: MIME type of linked media
Line 21: Line 16:
** This idea taken further brings a related one: separate sublist blocks each with own base.
** This idea taken further brings a related one: separate sublist blocks each with own base.
*** Possibly nestable?
*** Possibly nestable?
 +
*** Sublist blocks could share more information than just baseurl: It would allow album-like collections that share, e.g., creator, album, image.
 +
* Request: Semantics for next playlist.  This would enable a player to follow the playlist to another playlist URI in order to form linked playlists.
 +
** I realize this is available in some extensions, but thought it may be relevant enough to add to the core specification
 +
 +
[[Category:XSPF]]

Latest revision as of 18:54, 21 January 2008

This page is a place to file requests for features for XSPF. Any kind of feature can be entered here, please don't be bashful.

  • Request: track start and end attributes. Some media servers permit range headers in the http request, to specify the start and stop positions of the content for the track.

See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35

For large video files the specification of start and end positions within the content for the track would relieve us from splitting or recoding videos just because we want to play a part of the content for the track. Please include tags to denote the byte offset within the file for the track, and require long long integers.

  • Request: MIME type of linked media
    • This would be parallel to the RSS enclosure 'type' attribute. It is for user-agents to use in guessing whether they would want to traverse some link.
    • Proposal: a new extension element defined as the result of a HEAD on the link.
  • Request: Semantics for M3U-like '#CURTRACK'
  • Request: Track creation & last modified dates
  • Request: playlist relativization: separate the base from the file locations relativized from the base. This apparently should be optional, because some (but i suppose not many) playlists might be desired to have entries with no common path entries. This will allow UI's to provide rebasing of playlists -- imagine a media set accessible locally, via FS, and remotely, via, say, HTTP.
    • This idea taken further brings a related one: separate sublist blocks each with own base.
      • Possibly nestable?
      • Sublist blocks could share more information than just baseurl: It would allow album-like collections that share, e.g., creator, album, image.
  • Request: Semantics for next playlist. This would enable a player to follow the playlist to another playlist URI in order to form linked playlists.
    • I realize this is available in some extensions, but thought it may be relevant enough to add to the core specification
Personal tools


Main Page

Xiph.Org Projects

Audio—

Video—

Text—

Container—

Streaming—