- neither mystrands.com nor ilike.com are listed at the
XSPF applications page yet. anybody got time to
write a fruity summary for me to add an entry?
- ilike.com seems to serve valid XSPF-1, hooray!
(i'm positively surprised as many don't.)
i needed google to find some ilike use of XSPF, though.
has anybody got a contact at ilike who could make them
show XSPF more visibly? maybe even the "valid xspf" button?
- mystrands.com is serving XSPF-1 under the name of XSPF-0,
i.e. version is set to "0" but they serve <extension> elements.
So that's easy to fix. Anybody got a contact at mystrands
to pass this through?
- where can i find that resolver? it reads
"turns into this:
on the page for me. should there be something else?
Sebastian Pipping wrote:
> - mystrands.com is serving XSPF-1 under the name of XSPF-0,
> i.e. version is set to "0" but they serve <extension> elements.
> So that's easy to fix. Anybody got a contact at mystrands
> to pass this through?
PS: Adding line breaks would make their XSPF both human readable
and processable on text-level (e.g. shell scripts), not just
on XML level. My vote for line breaks.
Y'know, it seems to me that the way to get MyStrands to care about
validity and iLike to care about visibility is to create a compelling
business case for playlist sharing from their perspective. They use
XSPF because it's faster than rolling their own, but they don't intend
to exchange playlists with anybody.
Lucas Gonze wrote:
> MyStrands: a music-oriented social site focused on taste-sharing and
> iLike: a music site oriented towards social-networks; for sharing music
> tastes and playlists, and learning about new artists and concerts together.