Proposal: Allow relative image URIs in chapter JSON

[Mtillmann]

I believe this could make chapter definitions a lot more portable in certain situations. The image URIs should be relative to the location of the chapters.json file.

Examples:

// chapters.json located at https://example.com/assets/podcasts/episode-1234/chapters.json
{
  "chapters" : [
    {
      "startTime" : 0,
      "img" : "some-image.jpg"
      //resolves to https://example.com/assets/podcasts/episode-1234/some-image.jpg
    },
    {
      "startTime" : 60,
      "img" : "./some-image.jpg"
      //also resolves to https://example.com/assets/podcasts/episode-1234/some-image.jpg
    },
    {
      "startTime" : 120,
      "img" : "media/another-image.jpg"
      //resolves to https://example.com/assets/podcasts/episode-1234/assets/media/another-image.jpg
    },
    {
      "startTime" : 300,
      "img" : "https://example.com/another-folder/media/absolute-image.jpg"
      //resolves to https://example.com/another-folder/media/absolute-image.jpg
    }
  ]
}

[theDanielJLewis]

I support this.

(But it's not a chapters file! It's a file that can hold all kinds of episode meta data, including but not limited to chapters.)