Rich Inputs

.gitignore

.venv
.ipynb_checkpoints/
.virtual_documents/

README.md

Rich Inputs

References

• Google Doc
• HackMD

cell.schema.yaml

core.schema.yaml

# the workbench doesn't support this draft yet
# $schema: https://json-schema.org/draft/2020-12/schema
$schema: http://json-schema.org/draft-07/schema

# this would be the schema URI that is consumed by other packages
$id: https://jupyter.org/schema/notebook/6.0/notebook-6.0.schema.json

title: the jupyter notebook format 6.0

type: object

required:
  - cells
  - $schema

properties:
  $schema:
    description: the version of the schema to which a document conforms
    type: string
    default: https://jupyter.org/schema/notebook/6.0/notebook-6.0.schema.json
  schemas:
    $ref: "#/definitions/additional-schemas"
  cells:
    description: the jupyter cells this notebook contains
    type: object
    additionalProperties:
      $ref: "#/definitions/cell"

definitions:
  cell:
    description: a jupyter cell
    type: object
    properties:
      source:
        description: a description of the sources
        $ref: "#/definitions/rich-element"
      outputs:
        type: array
        items: "#/definitions/output"
      metadata:
        type: object

  rich-element:
    required:
      - data
    properties:
      data:
        description: |-
          a MIME-type-dependent encoding of the data. text-based formats will usually be encoded
          as lines.

          binary types will usually be a base64-encoded string.

          JSON types will usually be a top-level JSON object.
      metadata:
        description: additional properties of this element
        type: object

  mimebundle:
    # tighten up with mime regex
    # patternProperties:
    additionalProperties:
      oneOf:
        - type: array
          items: string

  cell-map:
    type: object
    additionalProperties:
      - $ref: "#/definitions/cell"

  additional-schemas:
    description: |-
      additional JSON Schema that further constrain a document, following
      the `allOf` semantics of JSON Schema
    type: array
    items:
      oneOf:
        - title: URI
          description: |-
            a URI for a schema. extension would register this with the client
            application
            this _should_ be reachable as a URL, but this is not
            required.
          type: string
          format: uri
        # Maybe don't have to ship this to-start
        - title: Inline
          description: |-
            embedded schema against which this document is validated
          type: object
          # JSON schema drafts would always be available with a schema validator
          # library, so this would resolve and validate
          # $ref: https://json-schema.org/draft/2019-09/schemaotebook/

environment.yml

channels:
- conda-forge
- nodefaults
dependencies:
- ipywidgets
- json-e
- json-lsp
- jsonpatch
- jsonpointer
- jsonschema-with-format-nongpl
- jupyter_server >=2.2.1
- jupyter-lsp-python
- jupyterlab >=3.6,<4
- jupyterlab-git
- jupyterlab-lsp
- jupyterlab-markup
- python >=3.11,<3.12
- rdflib
- tomli
- tomli-w
- wxyz_datagrid
- wxyz_dvcs
- wxyz_html
- wxyz_json_e
- wxyz_json_schema_form
- wxyz_lab
- wxyz_tpl_jinja
- wxyz_yaml
- yaml-lsp

jupyter_config.json

{
  "LabApp": {
    "collaborative": true,
    "expose_app_in_browser": true
  },
  "ServerApp": {
    "tornado_settings": {
      "jpserver_extensions": {
        "jupyter_offlinenotebook": false,
        "nteract_on_jupyter": false
      },
      "page_config_data": {
        "buildAvailable": false,
        "buildCheck": false
      }
    }
  }
}

postBuild

#!/usr/bin/env bash
set -eux
cp ${NB_PYTHON_PREFIX}/bin/jupyter-lab ${NB_PYTHON_PREFIX}/bin/jupyter-notebook
mkdir -p ~/.jupyter/
cp jupyter_config.json ~/.jupyter/

RichInputs.ipynb