3 ms·
This isn't too different from the current format, except the URI method is pushing the type into the URI, rather than into the name of the key. I do wonder abo
by StavrosK 10y ago
This isn't too different from the current format, except the URI method is pushing the type into the URI, rather than into the name of the key.
I do wonder about what you said, though: Would it be useful to be able to specify two different file paths or URIs for the same item? I'm leaning towards no, because, when clicking on an entry, you want it to start playing, so the choice is made when adding the file, rather than when playing it. The problem with multiple file paths is that both have the same weight, so how do you choose?
I guess you'd choose the same way you choose between the formats already, based on whatever is available/found.
- zeveb 10y ago> This isn't too different from the current format, except the URI method is pushing the type into the URI, rather than into the name of the key. Yup, which I think is good, since URI schemes already exist for many identifiers, and more can be added. > Would it be useful to be able to specify two different file paths or URIs for the same item? I think so. Maybe one is one removable medium and the other is on another. > The problem with multiple file paths is that both have the same weight, so how do you choose? If they have equal weight, does it matter which you choose?
- StavrosK 10y agoYou're right, I have updated the spec to make each item a list. Since the URIs can be anything (including files), this is pretty much equivalent to your proposal.