[Playlist] Project Opus Extension to XSPF

[Jim Garrison]

Matthias Friedrich wrote:
> On Monday, 2006-10-02, David Gratton wrote:
> I think data that's useful for a wider audience (like the number of
> listens, for example) and works without internal IDs from a single
> vendor should be officially added to XSPF using the link/meta mechanism.
> Maybe this way:
> 
> <meta rel="http://xspf.org/ns/0/number-of-listens">value</meta>

I tend to prefer the term "play count" to "number of listens."

And to clarify, I understand "number of listens" as a number that
increments every time the user plays the track.  If I am wrong, and you
actually mean a "repeat count," such that the player should repeat the
track X number of times before moving on to the next track, then
disregard the rest of this message. :)

It's difficult for me to understand what place such a value that a
player automatically updates has in a *sharable* playlist format.  When
I send a friend an XSPF file, do I want them to inherit my current play
count for each track in it?  No.  And therefore, XSPF shouldn't even
attempt to standardize on this particular feature.

If a media player stores its internal library as a XSPF playlist, then
it can use this type of extension in an implementation-specific manner.
 There may even be a small benefit in standardizing it so that multiple
applications can open the same file and retain the play count database,
but I don't think that it is enough of an advantage when one considers
the confusion caused by informally adding a "play count" to a playlist
format primarily meant for sharing.

Jim