Clarification on order of content resolving and <location>-tags
Motivation
Currently there is no step-by-step list of actions a renderer should do to locate a playable copy of the referenced track. Such a list would help implementing renderers as well as keeping their behaviour more aligned.
Suggested change
This should be changed and clarified.
Important:
- Such a list should keep in mind
<location>
-,<link>
-,<meta>
-,<extension>
-tags, and "human-readable" elements. - Keep the difference between transport qualities in mind (e.g. prefer local files over remote files).
- Clarify if finding a fetchable but unrenderable resource is a error condition that should stop rendering the current track. (e.g. if a
<location>
-tag links a FLAC but the player does not support FLAC if it should stop or try other<location>
-tags to see if it finds a file in a format it supports.)
Example list
- Try without accessing the network:
- All
<location>
-tags - Ask your neighbour
- All resources found by fuzzy matching
- All
- Retry with accessing the network.
- Fail
Required version updates
This change will not require a version or namespace update.