Subject: [httpapi] REST media types split (was Re: Updated agenda)
From: Henry Andrews <[email-masked]>
To: "[email-masked]" <[email-masked]>, "Salz, Rich" <rsalz=[email-masked]>
Date: Wed, 23 Oct 2024 17:45:52 +0000 (UTC)
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>

I should note that I still have ambitions of taking on the OpenAPI media types draft, it's just been stuck behind getting the OpenAPI patch releases out, which have helped clarify some of the media type needs.
I'm curious as to what splitting still needs to be done- the only thing I've noticed in the OpenAPI-centric document is that it still credits the JSON Schema folks for their input (I assume that credit should move over to the JSON Schema media type draft (unless they were more active discussing the OpenAPI media type than I'm guessing in which case of course keep the credits!).  Otherwise the current JSON Schema vs OpenAPI draft document split looks good.
thanks,-henry
    On Wednesday, October 23, 2024 at 09:24:34 AM PDT, Salz, Rich <rsalz=[email-masked]> wrote:  

In datatracker, github repo, and here:
 
# HTTPAPI at IETF 121

 
- Wednesday, Session II, 13:00-14:30 UTC
 
- Liffey MR 3

 
## Chair

 
- Note well reminders
 
- Note taker(s)
 
- Document update
 
-- api-catalog submitted
 
-- deprecation-header in RFC queue

 
## Documents

 
- Patch-byterange

 
- Idempotency-key-header

 
- Privacy (exposing API keys via HTTP)

 
- HTTPbis signature work

 
- Ratelimit-headers

 
- Digests-fields problem types

 
- REST media types
 
-- Volunteers to help split this?

 
- Expired documents
 
-- authentication link
 
-- link-hint

 
## Any other business

 
  
 -- 
httpapi mailing list -- [email-masked]
To unsubscribe send an email to [email-masked]