Notebook vs notebook vs notebook vs notebook.

[Carreau]

Closing the browser will not shut down the notebook computational kernel. The notebook can be reopened and it will be still running. To close a notebook and shut-down the kernel use the menu File -> Close and Halt. A this point the notebook is closed, Jupyter Notebook is still running and can open new notebooks.

Emphasis mine. This is something we have difficulties with also in main IPyhon docs. Notebook mean too many things. At some point you need to stop using notebook and differentiate by using, document, server, file , application or user will be lost.

As I told on the ML, some part of this are definitively welcomed in our docs. We are still restructuring the repos, and what goes where but. Though the high level direction should go in there I think. jupyter.org website woudl also need some high level descriptive text.

[tritemio]

Do you have any "official" suggestion for the names.

I would use "Jupyter Notebook App" (capitalized), the "notebook" (lower case) for the document and the "kernel" for the computational engine. The 3 need to be explained at least once at the beginning.

[tritemio]

I did the modification (b7c65b57a2144554c4c287365b247a5b26133249 and previous 2 commits). Now I always use these names (with the style):

• Jupyter Notebook App
• notebook document
• Notebook Dashboard
• kernel or kernel (i.e. the computational engine)

At one point I say that the Jupyter Notebook App is a server.

[tritemio]

Now these names are links pointing to a mini glossary.

[Carreau]

We disagree among ourself on the naming. I roughly use something that what you describe above.