[Playlist] XSPF Start/End time Zeitgeist

[Bjorn Wijers]

Mhhm, maybe I'm not understanding this correctly but what you seem to 
propose looks more like client side stuff than something that would need 
to be proposed in a spec. Wouldn't a 'smart' client parse the whole 
playlist and look for extra extension(s), attributes etc and perhaps 
download extra functionality or warn a user that certain functionality 
isn't available? So the problem of start and end times is the client 
software problem and not of the spec? Should the spec not be more 
concerned with facilitating 'smartness' instead of enforcing 'smartness'?

I mean, I really like the specs for being so tight and clean and this 
feels just not right. I would like to suggest something along these 
lines (from Simuze.nl) and I'm just brainstorming so bear with me:


<extension application="http://www.simuze.nl">
	<cclicense_by>1</cclicense_by>
	<cclicense_commercial>0</cclicense_commercial>
	<cclicense_derative>1</cclicense_derative>
</extension>

or in the case of the start/end time

<extension application="http://www.xspf.org/extensions/name/version">
	<namespace:clip start="10000" end="20000" type="ms">
</extension>

If a XSPF parser has no support for an extension it can find all the 
info at the url which contains the specs for this particular extension 
(and version of the extension). This would create the possibility to 
have a parser 'adapt' new behaviour (ie. the developer could be pinged 
and warned about new possible extensions that users are interested in..)

I have the feeling this might leave more freedom to developers to 
develop interesting extensions while leaving the specs clean and still 
facilitating the software using XSPF..

I'm by no means an expert on this, so feel free to point out any points 
that I'm missing.

grtz
BjornW





Lucas Gonze wrote:
> Nathan Freitas wrote:
>> Kent Bye wrote:
>>> He suggested the extension schema of:
>>> <extension>
>>>   <cl:clip start="10000" end="20000"/>
>>> </extension>
>> That looks prettier than my suggestion. I think I had wed myself to 
>> the <meta> tag, as we are using it for <meta rel="type"></meta> 
>> mime-type stuff.
> 
> It doesn't solve this problem, though:
> 
> Let's say the item in the //playlist/trackList/track/location is two 
> hours long, and you only want the chunk in the time span 1:10-1:11 (the 
> 11th minute of the 2nd hour), and you have a player which doesn't 
> recognize the clip extension.  What will happen then is that you'll get 
> the entire thing from beginning to end, not the clip, and that will do 
> you no good at all.
> 
> Here is a syntax which doesn't have that problem, because the location 
> isn't even seen if the user agent doesn't recognize the clip extension:
> <cl:clip start="1000" end="2000" location="http://example.com/foo.mp3"/>
> 
> 
> _______________________________________________
> Playlist mailing list
> Playlist at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/playlist
>