The Moro Database: A client-side documentation interface

[pathall]

So when you say “interface”, you mean CLDF right?

Creating a web page with audio tags

To expand on what I said above: I’d hope that CLDF can become the “interface” between linguistic data and tools/apps/visualizations, to allow for what programmers mean when they say code against the interface not the implementation.

In other words, it would be nice if the Moro interface were rewritten to accept CLDF data as an input.

But who defines that interface? I think we should expect a process of refinement, maybe something like the web standards process. I for one, for instance, am not convinced that a model based on tabular/CSV data (as opposed to more hierarchical JSON data) is the right starting point for documentary data. That’s because it ends up requiring fields with delimited content. (This kind of thing: esi-n\tšebi\txeci-n\tšebi\tzow-n-ƛax\tsis\tɣˤana-xediw.) A field containing delimiters requires a parser, and now we’re coding data to the implementation again, right?