HTTPAPI at IETF 122

Chair

Documents with Content Updates

"New JSON Schema"

A major rationale: is hard to make tooling for JSON Schema, Avro is also better suited for data-binding.
You can think of this as a refactoring of JSON Schema; some features removed, more data types (that can have attributes). They also have serialization rules to/from JSON string.
Restrictions on $defs/$ref for reusable types.
Documents, etc., at https://github.com/clemensv/json-cs/tree/main/jsc (also posted to list)
Andy Newton as individual: I like this, hope it moves forward
AN as ART Ad: Need to be careful about the name "Json Schema"; might be question of venue. Please also send to art@ietf.org
Clemens: Not wedded to the name, but do want to leverage the existing JSON schema drafts for mindshare.
Darrel as individual: agree JSON Schema is hard to do code-generation and it seems to be stuck right now.
Andy: I think the confusion about JSON is reason enough to look at this.
Chairs and ADs to determine a proposed way forward.
Darrel talked about politics of personal views of various JSON authors, IETF relationship, etc.

Documents ready to move to WGLC ?

Expired documents

If anyone wants to work on either one, contact the Chairs

Any other business