Possibility: make images a top-level collection

[govynnus]

Hello,

I've had a thought, but I'm not sure if it's a good one (or one that's already been had): should images be it's own top-level collection?

There would be endpoints /aura/images and /aura/images/(id) (rather than /aura/tracks/(id)/images) which would return "image resource objects". Then the actual file could be retrieved like audio for a track with something like /aura/images/(id)/image-file. Image resource objects for a specific track/album would be obtained through inclusion as is the case now.

Obviously this would mean you'd have to have globally unique IDs for each image which might be a bit more complicated than a simple per-resource index, but I think standardising images to behave more like other parts of the spec could make it simpler overall.

What do you think?

[govynnus]

Just realised you've already thought about this in #3 and suggested nearly exactly what I just did as one of the options :-)
I'll close this and possibly continue my thoughts in #3 once I've considered it a bit more.