changed 5 years ago  
Linked with GitHub

JEP Draft: Cell ID/Information Bi-weekly Meeting

Next Meeting

August 31, 2020

Time: 9:30 AM Pacific (your timezone)
Where: Zoom Channel
Meeting ID: 837 104 3123
Passcode: 18>jB4(l}3

Attendees

Name affiliation username
Carol Project Jupyter / Noteable @willingc
Matt Project Jupyter / Noteable @mseal

Agenda + Minutes

  • Comments or questions about PR#62 Cell ID Proposal
    • Matt and Carol reviewed comments on the JEP and have responded in the PR.
  • Current plan to send the JEP to Steering Council on Friday for approval which is 7 days after the PR was opened.

August 17th, 2020

Time: 9:30 AM Pacific (your timezone)
Where: Zoom Channel
Meeting ID: 837 104 3123
Passcode: 18>jB4(l}3

Attendees

Name affiliation username
Carol Project Jupyter / Noteable @willingc
Tony Quansight @tonyfast
Nick Project Jupyter / Georgia Tech @bollwyvl
Matt Project Jupyter / Noteable @mseal

Agenda + Minutes

  • Overview of Preliminary Issue
  • Document scope of the JEP
    • Keep it small
    • Keep it focused
    • Larger changes to the nbformat should be a different larger effort
  • Identify Goal of the JEP
  • Discussion of options and approaches

Notes

  • lots of back channel, no proposals

  • constraints

    • notebook enterprise summit feedback
    • smallest change possible, least impact, disruption

  • cells and notebooks

  • quantopian postgresql ? still using

  • cocalc william stein

  • julia, python, r, typescript - language support

    • nbformat (python)
    • julia (??)
    • r (??)
    • typescript (nteract / jlab?)

  • What is identity in JSON schema and JSON-LD?

    • based on URI
    • move toward existing standards

  • UUID

    • know what it is
    • robust semantics?
    • internet doesn't know what it is
    • not a canonical link
    • not a global identifier for all notebooks

  • identify a cell within a notebook consistently

  • nbformat

    • $id ID ref
    • has a meaning beyond structure #/ (URL anchor hanging off the notebook)
    • $id as opposed to just id
    • key being $id (Nick)
    • agreed upon pattern
    • no $schema in notebook

  • why not in metadata

    • folks have already used id in not conformant way
    • breaking user notebooks that exist

  • ok with not in metadata

  • conventions to take

    • $schema
    • type string-format-URI ref
    • JSON-LD
    • type string-format-URI
    • loose interpretations

  • Can we point to one of these formats?

  • Good id constraint: don't need to be escaped; limit characters, max and min lengths

  • URI ref

  • $id perhaps

  • save nicely (will be used in different cases)

  • $id and regex
    Next Actions:

  • investigate if formats above would meet needs

  • patch from Matt for specific change

Next meeting: 2 weeks from now

Select a repo