[media-types] [IANA #1450656] Re: Re: Review request for updated registration of text/css
"Amanda Baber via RT" <[email protected]> Wed, 29 Apr 2026 18:43:49 +0000
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Hi Alexey, Can you review this one? We have confirmation from the W3C liaison that this can be processed. thanks, Amanda On Wed Apr 22 07:45:46 2026, amanda.baber wrote: > Hi Chris and IETF-designated media type experts, > > Sorry, IANA isn't subscribed to the [email protected] list, so we > don't have a ticket for/haven't seen this. In order to make this > update, we need approval from one of the IESG-designated experts > (Alexey Melnikov, Darrel Miller, Murray Kucherawy). We usually assign > the request to a specific expert when we forward the request to the > list. > > Alexey or Murray (asking you in case you ran into something like this > as an AD), can one of you pick up this request? Because this media > type was registered by RFC 2318, but has a blank change controller > field, we also need confirmation that this media type can be modified > without an RFC. The template's "published specification" field does > refer to a W3C spec. > > W3C has asked us to confirm media type submissions with one of their > liaisons, so I'll send that message to them separately. > > thanks, > Amanda > > On Tue Apr 21 19:48:35 2026, [email protected] wrote: > > Amanda, > > > > All the review comments on the updated registration request for > > text/css > > have been addressed to the satisfaction of those commenting. > > > > What is the next step for updated registration? > > > > On 2026-03-26 18:50, Chris Lilley wrote: > > > > > > The new template (with public.css added): > > > > > > Type name: text > > > > > > Subtype name: css > > > > > > Required parameters: none > > > > > > Optional parameters: charset (but see below) > > > > > > Encoding considerations: > > > > > > For use with transports that are not 8-bit clean, quoted- > > > printable encoding is recommended since the majority of > > > characters will be CSS syntax and thus correspond to the > > > US-ASCII-compatible subrange of UTF-8. > > > > > > Security considerations: > > > > > > CSS is a modular specification and thus, the individual > > > Security Considerations section of each CSS module in use > > > should be consulted. > > > > > > Interoperability considerations: > > > > > > CSS has proven to be widely interoperable across computer > > > platforms, across Web browsers of different makes, and for import > > > and export in multiple authoring tools. > > > > > > Published specification: > > > > > > https://www.w3.org/TR/css > > > > > > Applications that use this media type: > > > > > > CSS is device-, platform- and vendor-neutral and is supported by > > > a wide range of Web user agents and authoring tools for > > > formatting HTML documents. > > > > > > Fragment identifier considerations: > > > > > > N/A > > > > > > Additional information: > > > > > > Deprecated alias names for this type: N/A > > > Magic number(s): N/A > > > File extension(s): .css > > > macOS Uniform Type Identifier(s): public.css > > > Windows clipboard name(s): N/A > > > > > > Person & email address to contact for further information: > > > > > > The W3C CSS Working Group<[email protected]> > > > > > > Intended usage: > > > > > > COMMON > > > > > > Restrictions on usage: > > > > > > N/A > > > > > > Author: The W3C CSS Working Group > > > > > > Change controller: W3C > > > > > > Fallback encoding: > > > > > > For Web compatibility, to determine the character encoding, > > > user agents follow the CSS Syntax Level 3 specification, > > > "To determine the fallback encoding of a stylesheet" > > > https://www.w3.org/TR/css-syntax-3/#determine-the-fallback-encoding > > > > > > Stylesheet authors should author their stylesheets in UTF-8, and > > > ensure that either an HTTP header (or equivalent method) declares > > > the encoding of the stylesheet to be UTF-8, or that the referring > > > document declares its encoding to be UTF-8. > > > > > > -- > > > Chris Lilley > > > @[email protected] > > > W3C Distinguished Expert, Color, Graphics & Fonts > > > W3C Technical Programming Team, Core Web Design > > > > > > _______________________________________________ > > > media-types mailing list [email protected] > > > To unsubscribe send an email [email protected] > > _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]