[Playlist] question about the XSPF specs

[Lucas Gonze]

Benoît, how can I help you out with this? Would a real time chat or zoom be
helpful?

If so, is anybody else interested in participating?

On Mon, Sep 14, 2020 at 2:22 PM Lucas Gonze <lucas at gonze.com> wrote:

> I agree. It would be a productive project, and probably not too hard.
>
> On Benoit's ideas about how to do what he's thinking about, I wonder if
> other people think that it would be wise to have a track with multiple
> location elements, each pointing to a different streaming service. That
> would function similarly to the sources idea:
>
> "sources": [
> 'https://open.spotify.com/track/3FgDF8tNn6aqB7ycygy7ch',
> 'https://www.youtube.com/watch?v=PA3P1-aSvKQ',
> 'https://www.youtube.com/watch?v=vUes9-tFWm4',
> ]
>
> Then, Benoit brought up the issue of having different metadata for each
> track.location or track.sources[i], like this:
>
> >>
>      "meta"          : [
>        {'wpsstmapi/input_url'=> 'myvalue1'},
>        {'wpsstmapi/xspf_url'=> 'myvalue2'},
>        {'wpsstmapi/importer_slug'=> 'myvalue3'},
>      ],
> In the specs, the keys are urls like http://example.com/rel/1/. Should
> this point to an URL that exists or can I use what I want ?
> <<
>
> The URL does not have to exist. This is legal, even though there is not
> actually any domain at example.org:
>
> <track><meta rel="http://example.org/meta/track/vendornick
> ">Spotify</meta></track>
>
> Over the years I have softened up quite a lot towards namespaces, and
> don't think something like this would be a bad thing:
>
> <track><location ns:vendornick="Spotify">
> https://open.spotify.com/track/3FgDF8tNn6aqB7ycygy7ch</location></track>
>
> On Mon, Sep 14, 2020 at 2:01 PM Martin McEvoy <martin at weborganics.co.uk>
> wrote:
>
>> +1 from me on a JSON version.
>>
>> On Tue, 24 Mar 2020, 17:13 Lucas Gonze, <lucas at gonze.com> wrote:
>>
>>> Benoît, it's excellent to meet you. I am CC'ing the XSPF list at
>>> playlist at xiph.org and copying this answer to the Stack Overflow thread.
>>>
>>> The info element is designed to do what you need:
>>> http://xspf.org/xspf-v1.html#rfc.section.4.1.1.2.14.1.1.1.6
>>>
>>> However, there can only be one info element per track.
>>>
>>> Regarding the many years since the last update of the spec, maybe it's
>>> time to do one. A blessed JSON version would be useful.
>>>
>>> -Lucas
>>>
>>>
>>> On Tue, Mar 24, 2020 at 1:38 AM Benoît Gréant <gordie.lachance at gmail.com>
>>> wrote:
>>>
>>>> Hi guys !
>>>>
>>>> I love your XSPF thing :)
>>>> Have been playing with it since several years, using it as base for my
>>>> website (&API
>>>> <https://www.spiff-radio.org/wordpress-soundsystem-plugin/soundsystem-api/>,
>>>> &WP plugin) spiff-radio.org.
>>>>
>>>> I have a small question.  I want to attach (several) links to a
>>>> playlist track (eg. spotify/youtuble/apple music...); what tag should I use
>>>> for this ?
>>>>
>>>> Well, I posted the complete question on Stackoverflow
>>>> <https://stackoverflow.com/questions/60822682/xspf-xml-playlist-specifications-how-should-i-format-links-to-one-or-several>
>>>> .
>>>>
>>>> Thanks for your help.
>>>>
>>>> Benoît
>>>>
>>> _______________________________________________
>>> Playlist mailing list
>>> Playlist at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/playlist
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/playlist/attachments/20200917/4f070700/attachment.html>