That's a good idea actually! Although I guess there is a part of me that thinks that having just a simple image tag without any fancy stuff is still best for a primary image (so that apps that want to implement it don't need to start messing with this new format and can just load that simple url.
I guess the question then would be if you'd do something like: "If there is a image_gallery tag on the item, use that instead of the image tag" and have the image tag be just image1 and the image_gallery refer to image1,image2,image3 etc. Also, I wonder if this could tie into an IPFS (decentralized internet protocol) system as well Cheers, Thibault On Wed, 26 Aug 2020 at 09:35, Cj Malone < me-osm-tagg...@keepawayfromfire.co.uk> wrote: > As mentioned semi colon has issues with URLs. It may also be worth > noting that a OSM value can only have 254 chars in it, a limit that > would get hit quickly with a few URLs. > > I've thought about this before, I think we need 1 URL to point to > multiple images. But it can't just be a non standard HTML gallery, it > also needs to be programmatically fetchable so downstream OSM consumers > can use the images directly. > > HTTP already has the capability for this with the Accept header. > > - If a given URL is loaded in a browser (Accept: text/html) it can show > a HTML page with multiple images in. > > - If it's requested by a client like OsmAnd (eg Accept: > application/gallery+json) it could return a JSON blob with details > about the images, there licences, alt text, etc to be embedded in the > app. > > But we'd need server support. > > Cj > > > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
