Dan Allan

This could also work for nodes. If I ask for a node that happens to be an HDF5 file as HDF5, we can just spool the HDF5 file. It might...

I have cherry-picked the backend changes from #350 into #355. Everything is standard code-flow now, I am reasonably confident that we can support front-end authentication with no additional backward-compatible changes...

Collecting links to user agreements: * https://als.lbl.gov/wp-content/uploads/2016/07/nonpropuseragreement_sample-2019.pdf (see Page 6 in particular) * https://next-gen.materialsproject.org/about/terms * https://www.esrf.fr/datapolicy

We should consider whether this should be added as a top-level key _beside_ `metadata`, `specs`, and `references` or as a name with special significance _within_ `references`. (I think we should...

See comments on the rationale for removing `references`: https://github.com/bluesky/tiled/issues/432#issue-1657348968 Likewise, I think license should just live within `metadata`, marked up using some existing standard like JSON-LD.

Agreed with @dylanmcreynolds. It looks nice. I look forward to playing with it for a bit. Your suggestion on Slack > I'm not sure if building it in like this...

I'm going to close this as stale. I am still interested in understanding use cases for GraphQL in Tiled.

Reports have reached us that the h5web one has a notion of extension "backends", and adding a Tiled one may be fairly straightforward. (I have not personally investigated, just noting...

Our current implementation makes a half-hearted attempt at multi-process support but it's flawed in a couple ways. I think it would be better to explicitly make the file-based cache single-process...

I think we should change the internal cache layout from many-small-separate-files to a single SQLite database file, referencing some external files only for large data (MB-scale image chunks, not KB-scale...