NeurodataWithoutBorders / lindi

Linked Data Interface (LINDI) - cloud-friendly access to NWB data
BSD 3-Clause "New" or "Revised" License
2 stars 1 forks source link

Discuss library name #7

Closed oruebel closed 5 months ago

oruebel commented 5 months ago

The README currently defines the name as Linked Neurodata Interface (LINDI). I'm wondering how specific the library actually will be to neurodata. It seems this library may be much more broad in nature, in that it only cares about the data format (HDF5, Zarr, etc.) but it may not really care about the actual schema. Dealing with the schema and application-specific functions, seem like they will likely remain with the domain libraries, e.g,. PyNWB, HDMF etc.. With that in mind (and keeping with the current acronym), I'm wondering whether it should be just Linked Data Interface (LINDI).

rly commented 5 months ago

I like Linked Data Interface, but I worry that it will be overly broad and connected to JSON-LD. We are really interfacing between chunked array storage. How about Linked N-Dimensional Array Interface (LINDI)?

rly commented 5 months ago

Some other options that didn't quite make the cut:

magland commented 5 months ago

Or zarrbie :)

magland commented 5 months ago

Or we could call it LINDI and have it stand for multiple things, depending on the context.

magland commented 5 months ago

Distributed Archives for Neurophysiology Data Integration = DANDI Linked Neurophysiology Data Interface = LINDI

and then when it's not neurophysiology

Linked Data Interface

oruebel commented 5 months ago

So far, my personal favorites are:

rly commented 5 months ago

All right, let's go with Linked Data Interface (LINDI). It's growing on me.