Use reference-spec-reader pkg for ReferenceStore

[manzt]

No description provided.

[manzt]

example:
https://6060eed9dc5ef100075be024--vizarr.netlify.app/?source=https://gist.githubusercontent.com/manzt/436fc2966c484205a2c60824f659b412/raw/cdc69f2ce645d953185f10d7552501bfd459dd12/Vanderbilt-Spraggins-Kidney-MxIF.ome.tif.json&channel_axis=0

[oeway]

Hi @manzt This is awesome! Thank you.

For the URL, I have two question regarding this:

• the reference maker allows specifying the URL as null and then we can define a common URL, can we support this? Maybe allow passing something like reference_spec_url in the URL? This will be desired because for URLs generated with S3, it carries a super long signature
• not all the url will end with .json, would be nice to have a way to explicitly tell the viewer to parse an arbitrary URL as a reference spec.

[manzt]

Hey! I have a couple of ideas here. My first thought is to adopt something similar to fsspec and and force reference spec urls to have reference:// protocol signify the URL is for a reference, then we can pass other query parameters for the reference url (like target).

e.g. http://hms-dbmi.github.io/vizarr?source=reference://<reference_url>?target=<target_url>

This avoids needing to expose another top-level API input, and instead we can check for the reference:// and parse the complete referenced (for a default target etc).

[manzt]

Ah, but then the reference url might break. I think avoiding special structure of URLs is desirable (moving away from checking for file extensions (e.g. .json or .zarr) and instead being explicit by prepending an additional protocol: reference://.

I still don't know what the best solution for encoding the default target URL, however. I don't totally love the option of adding reference_spec_url because it feels like that information should be provided with the reference source.