Alistair Miles
Alistair Miles
:+1: from me too, thanks @rabernat.
Hi @jakirkham, is this the kind of thing you were thinking of? cc @carreau
Thanks @agstephens for your comment, it's great to know this is potentially useful. As John and Matthias have said this will be easier to develop as an extension to the...
> Also to your subpoint on listable stores, yeah the idea was to capture the full listing under one JSON object. So it tries to capture the use case that...
Hi @shoyer, can you explain this one a little more? Not fully getting it.
Thanks @shoyer. So trying to make this concrete, correct me if any of the following is wrong. You have an array of air temperature estimates `e`. The shape of this...
Ok, thanks. So the requirement for versioning, do you think that lives at the storage layer? I.e., does it make sense to think of this in terms of store classes...
One simple way to implement this that immediately comes to mind would be to extend the DirectoryStore class and use git to provide versioning. Could even use GitPython to provide...
Hi Stephan, One quick question. Currently the metadata in the v3.0 spec is *not* just a flat set of name/value pairs, where values are simple types like string or number....
Just to generalise a bit, I think there are two possible sets of requirements here: (1) If/how to support storage implementations which have some "native" mechanism for storing metadata (e.g.,...