[Playlist] xspf pagination

[Lucas Gonze]

I don't know this spec well enough to know whether it can be adapted, 
but it's going after pretty much the same territory:
http://tools.ietf.org/wg/atompub/draft-nottingham-atompub-feed-history-11.txt


Ivo Emanuel Gonçalves wrote:
> On 9/1/07, Chris Anderson <jchris at mfdz.com> wrote:
>> I've been thinking about a standard way to paginate xspf results.
> 
> I believe the standard way is by the order the files are listed, which
> makes sense since its the format all other playlists use.
> 
>> It looks like there's nothing in the spec to suggest what to do when the
>> xspf generator only wants to render say, the first 20 tracks of a 100
>> track playlist.
> 
> Then the application only renders the first 20 tracks in the playlist.
>  It would be a limitation of the application and not of the format.
> 
>> I'm thinking that perhaps using the link attribute,
>> with rel="next" would be the best way to do it within the spec.
> 
> That makes no sense, in my opinion.  It looks like a hack to go around
> a certain program, and thus it is a bad idea.
> 
>> rel="next" is a standard html relation [1]
> 
> Yes.
> 
>> but I'm not sure if it
>> counts as a URI, to be valid in the XSPF spec
> 
> XSPF only allows valid URIs, no matter the case.  It should be read as
> IRIs, but amounts to the same if the application supports Unicode.
> Which should anyway, since the recommended encoding type is UTF-8.
> 
> 
> -Ivo
> 
> _______________________________________________
> Playlist mailing list
> Playlist at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/playlist
> 
>