Addison Phillips

Closing this issue as obsolete. Open new issues for specific HTML compatibility proposals or related requests.

Is this issue still useful? Let's close if not. Otherwise, it's tagged for `Future`

Reopen if desired for `Future`

@eemeli wrote: > Ah, ok. So do I understand right that you're advocating for us to define a "format to string parts" API, and that if an implementation were to...

this may have been addressed in the F2F proposal for F2P (format to parts). As mentioned in today's telecon (2023-09-18), closing old requirements issues.

Addressed by adoption of ABNF?

Per discussion, I think we previously decided that comment were out of scope. Marking this issue for potential closure.

@eemeli I agree this is now addressed. Keeping open to allow others time to review.

This is probably linked to #408 and to other issues about typing in general. So far we have avoided having types at the syntax/spec level, but our work on function...

We are untyped by consensus. This appears to be out of scope? Reopen if needed.