Over time we have seen an increasing interest in using Jupyter as a part of traditional text-based collaborative workflows (e.g. git, diffing, etc). There seem to be more and more projects that create their own text-based specification for how a notebook is structured. These projects generally do this in a very ad-hoc way that suits their own needs.
I suspect that this will only become more common, especially as excellent projects like jupytext gain traction.
To that extent, I am curious if folks think it would be useful to try and decide on a “recommended” text-based specification for Jupyter Notebooks. This doesn’t have to be an officially-supported spec in, e.g., JupyterLab etc, but it could be a community recommendation as others build tooling in the ecosystem, to try and reduce the forking paths of one-off specifications.
Do folks think it would be a good idea to, say, open up a JEP to begin discussion of this?
Note - I’m not talking about changing the default-supported markdown in Jupyter interfaces, but instead just talking about how one could represent the structure of the notebook (e.g., the content blocks, metadata about the blocks, and if/how to include outputs)