Today, notebook cell have the following URI format
vscode-notebook-cell://<notebook-authority>/<notebook-path>, cell <handle>?<payload>
This makes then
- render in the UI like
some/path/someNotebook.foo, cell 12
- makes a cell a different resource - by the rules of URI
The downsides are
- The cell handle appears in the UI and that's something users can not really relate to
- A cell is inside the notebook, not a different resource, using fragments is the better fit
- Grouping is often (but not always) bogous (see screen shot below)

The plan is to use a URI format for notebook cells that do not make them appear as separate things but make them appears as the notebook itself
Today, notebook cell have the following URI format
vscode-notebook-cell://<notebook-authority>/<notebook-path>, cell <handle>?<payload>This makes then
some/path/someNotebook.foo, cell 12The downsides are
The plan is to use a URI format for notebook cells that do not make them appear as separate things but make them appears as the notebook itself