-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to assign track links to Spotify/Youtube/... ? #16
Comments
XSPF shows using a I am wondering about how to translate something like this: track.links[:spotify] = 'https://play.spotify.com/track/0tY6yscxkyjm0o0ppVhd5b' But I am not sure what the real URI should be: <link rel="http://something.com/spotify">https://play.spotify.com/track/0tY6yscxkyjm0o0ppVhd5b</link> Maybe a URI relative to the playlist itself: <link rel="#spotify">https://play.spotify.com/track/0tY6yscxkyjm0o0ppVhd5b</link> |
Yes, the documentation is not really obvious on this. |
It might be worth asking on the Mailing List - even if just to point people who know about XSPF to the Stackoverflow question, |
I just had an email reply from one of the specs author (which also did reply to the stackoverflow post), where he says that we could put those links in the location or identifier tags.
So I guess this issue can be closed. Do your gem supports multiple locations for a track ? |
...Which leads me to new problems : Your 'location' attribute doesn't support multiple values (at least this is what is said in the documentation),
I get
Thanks man ! |
It doesn't currently support multiple locations for a track, but I will have a think about how best to do it. Please can you open a separate issue for adding multiple locations? |
multiple locations --> #17 |
Hi, could you add a :link property for tracks ?
it differs from the :location property, as seen on the XSPF specs :
I would use this to define links to audio services (like Spotify, Youtube, Soundcloud), which are not really an audio ressource. + I need to be able to add several links.
Thanks a lot, again.
The text was updated successfully, but these errors were encountered: