Reference Material

These are links to prior art, related efforts and resources for consideration in how Newt evolves as a prototype.

Data Modeling

• Syntax for GitHub form schema
• A React component for building Web forms from JSON Schema
• JSON Forms
  • pretty heavy weight in the deployed results (i.e. renders to either React or Angular)
  • Uses JSON rather than YAML or TOML to describe forms which can be construed as less human friendly
• YAQL, a YAML like query language that maps to SQL
• pg_query, a Ruby library to parse SQL and normalize into a data structure
• htmx, a Web Component like markup implementing the wrapping layer between JSON API and HTML structured markup
• Yafowil, yet another form widget library
  • Describe YAFOWIL forms with YAML
• MDN Web Components, could be useful for making specialize input elements, like ORCID, DOI, ArXiv identifier entry
• MDN HTML5 input types
• Generate web forms based on YAML schema with pykwalify
• Flask Open API 3

Web Form generation

• Deform

SQL DB to REST JSON API

• PostgREST, build a REST JSON API directly on top of Postgres. This is what started my think about Newt prototype
• MRS, MySQL REST Service
• sqlite2rest, Automatically RESTful OpenAPI server from SQLite database
• Soul, A SQLite REST and real time server built on NodeJS (wonder if it runs in Deno?)

SQL JSON support

• SQL dialects
  • database guide, documentation for various SQL dialects including Postgres and SQLite
• Postgres
  • Postgres JSON functions and operators
  • Postgres JSON tutorial
• SQLite 3
  • SQLite Overview JSON functions
  • JSON improvements in SQLite 3.38.0
  • SQLite JSON function enhancements (2022)
  • SQLite cli docs, e.g. “Changing output formats” in section 5 covers .mode json

Data transformation and mashups

• Pipes is a spiritual successor to Yahoo! Pipes

Other approaches and background

• Doing More with Less: Orchestrating Serverless Applications without an Orchestrator. with David Liu, Shadi Noghabi, and Sebastian Burckhardt. (to appear) In proceedings of the 20th USENIX Symposium on Networked Systems Design and Implementation (NSDI) 2023. Paper
• path-to-regexp
• URLPattern at MDN
• URLPattern at Chrome Developer site
• Flask Route tutorial
• router.js
• Azure application gateway routing
• React Router
• Nextjs routing
• dJango routing
• HYDRA, Hypermedia-Driven Web API
• HAL, Hypertext Application Language
  • JSON-HAL
• JSON-LD
• Richardson Maturity Model, used to evaluate RESTful-ness in JSON API
• HAR, HTTP Archive Request
• GoJa, Pure Go JavaScript engine
• HTTPie-go, A go implementation of HTTPie, useful to debug API interactions
  • Fork with out stale package references, HTTP-Pie-go
• Lama2, a plain text powered rest client (not to be confused with Meta’s LLM)
• Go’s extended html docs, HTML tokenizer and parser package

Go implementations for unique identifiers

It appears it may be desirable when generating SQL code and web forms to allow for the automatic creation of three object attributes as some sort of minimally viable object, unique object id with created and updated timestamps

{
    "oid": "xxxxxxxxx",
    "created": "timestamp value for object creation",
    "updated": "timestamp, updates on change"
}

This could be implemented directory into the generated SQL or have an Identifier service that sits in front of the DB JSON API.

• UUID, v4 UUID, go storage in Postgres, long for URL
• shortid
• shortuuid, Python shortuuid package
• shortuuid, a Port of the Python package to Go, algorithmically compatible with the Python implementation, currently at v4 and still actively developed (April 2024), see https://pkg.go.dev/github.com/lithammer/shortuuid/v4
• ulid, a logically sortable unique identifier package, ported from the JavaScript package implementing ulid
• Cuid2, a port of Cuid2 JavaScript implementation
• Sonyflake, a uid inspired by Twitter’s snowflake
• Mongo BSON ObjectID, Go implementation from Mongo’s go client library
• xid

Blog posts on identifiers

• Identify Crisis, how modern applications generate unique identifiers
• Unique identifiers in three parts
• What is a ulid and why should you start using it?

Web Components

If Newt shipped with a set of LAM oriented web component that could allow for a more complex data model to be addressed by Newt. E.g. lists of authors are a web component would probably have not just the name fields but also identifiers like ORCID and ISNI attached to them. Something worth exploring.

Internet Archives seems to be investing in the Lit component library heavily.