Albin Larsson

> Perhaps the format of a request file would need some extra info apart from the URL, like, setting some headers etc as it is now possible with the predefined...

I don't think that this issue is very far outt, I have had the same issue as you describe when working with IIIF data not available in a SPARQL instance...

Preparation: - `snowman cache` is ready for this as of [04fbebe](https://github.com/glaciers-in-archives/snowman/commit/04fbebe5389a6cff7d2534d300a592c4713e0ce9). ✅ - The cache manager should be renamed to be SPARQL specific. ✅ - The `snowman build` flag `cache`...

A "small" implementation change: Instead of storing all items by the sha256 hash of the URL, they are now stored by the sha256 hash of the hostname and then the...

Support has now landed on the `cached-resources` branch. The `snowman cache resources` commands still needs to be implemented.

More non-obvious changes related to this and #91: `snowman cache clear` synonym to `snowman cache inspect` summarizing the cache from both SPARQL queries and remote resources(#91). Not very obvious but...

Additional non-obvious: `snowman cache` should be an alias for `snowman cache --help`

We have been experimenting with the CLI interface and are leaning towards splitting it into an additional layer of sub commands: `snowman cache inspect sparql [args]` `snowman cache inspect resources...

> Hmm, can you speak more about the additional information and what this might look like? And what safety concerns are you thinking of? By "safety" I do not mean...

I couldn't agree more @thadguidry, and JSON-LD based previews would actually make some of our services compatible simply by pointing to URIs of our various data services(example: https://fornpunkt.se/lamning/bjyWKNz.jsonld). Not to...