Re: [media-types] Starting work (Fwd: WG Action: Formed Media Type Maintenance (mediaman))

On Fri, Aug 27, 2021 at 09:45:47AM +0200, Harald Alvestrand wrote:
> Hello fellow typers!
> 
> As you can see from the below, the IESG has approved the formation of a
> working group for media maintenance, and I have agreed to be chair of the WG
> (flying solo for now).
> 
> The WG is chartered to use this mailing list for its work.
> 
> Using an existing mailing list has advantages and disadvantages, so lets get
> started on an administrative item:
> Should we ask for a new mailing list, or should we keep this one?
> 
> I'll use the responses as a means of gauging whether people a) notice the
> mail and b) want to participate in the work too :-)
> 
> Welcome to MEDIAMAN!
> 
> Harald
> 
> 
> 
> -------- Forwarded Message --------
> Subject: 	WG Action: Formed Media Type Maintenance (mediaman)
> Resent-Date: 	Thu, 26 Aug 2021 13:51:54 -0700 (PDT)
> Resent-From: 	alias-bounces@ietf.org
> Resent-To: 	harald@alvestrand.no
> Date: 	Thu, 26 Aug 2021 13:51:53 -0700
> From: 	The IESG <iesg-secretary@ietf.org>
> To: 	IETF-Announce <ietf-announce@ietf.org>
> CC: 	The IESG <iesg@ietf.org>rg>, media-types@ietf.org,
> mediaman-chairs@ietf.org
> 
...
> Input Document(s):
> * draft-muthusamy-dispatch-haptics
> 
> * draft-w3cdidwg-media-types-with-multiple-suffixes

i think there's some intersection between the goals of multiple
suffixes and the goals of profiles, à la
<https://datatracker.ietf.org/doc/draft-svensson-profiled-representations/>.

> Proposed milestones (target dates TBD):
> * Publish any specific criteria or guidance for handling registration of
> future top-level media types, either as an RFC or a wiki page.
> 
> * draft-muthusamy-dispatch-haptics (or equivalent) to the IESG for approval
> (Proposed Standard)
> 
> * A draft about handling multiple suffixes to the IESG for approval (BCP)
> 
> * Publish a reviewer’s checklist about Security Considerations in media type
> applications, either as an RFC or a wiki page.

As an occasional media type registration author, I feel like the
recipe for drafting a security section is to start by digging through
recent ones for a similar language. These similarities can be used to
bin languages (XML, JSON and RDF; XQuery snd SPARQL, XML Schema with
ShEx and SHACL, WASM, Java, and JS). The registration process always
get a bit chaotic 'cause someone shows up and says "what about X"
around the same time you're saying "I will add anything people want if
that allows me to finish this project." This produces a cycle of less
concise text, few vested readers, lower priority, and back to less
polished text.

We could apply a bit of DRY; drafting a doc with a few security
checklists for data, query, schema, graphics, and executable
languages. I'd be game to help with that. (I started somewhere; it's
on my disk somewhere...)

> * Deliver recommendations about the media types registry format.
> 
> * Deliver any recommendations about future registration and queue
> management.
> 
> 
> 

> _______________________________________________
> media-types mailing list
> media-types@ietf.org
> https://www.ietf.org/mailman/listinfo/media-types