[media-types] [IANA #1450656] Re: Re: Review request for updated registration of text/css

Hi Alexey,

We have an updated W3C request from Chris Lilley. Is this OK?

thanks,
Amanda

=====

Hi Alexey, Amanda,

The two requested changes have been made (N/A instead of none, binary 
instead of the text from the original registration) and the defining 
document at https://www.w3.org/TR/css has been updated today to include 
these changes (in section 5. The text/css media type):

https://www.w3.org/TR/css/#media-type

I append a text copy of the updated registration for your convenience.

In terms of the wish for a link to the different modules, that is 
already there. In the defining specification, section 2.1. Cascading 
Style Sheets (CSS) — The Official Definition lists all the modules which 
form the CSS specification and for each, there is a brief summary and a 
link to the actual module:

https://www.w3.org/TR/css/#css-official

In addition, the in-development modules are also listed:

2.2. Reliable Candidate Recommendations
https://www.w3.org/TR/css/#reliable-cr

2.3. Fairly Stable Modules with limited implementation experience
https://www.w3.org/TR/css/#fairly-stable

2.4. Modules with Rough Interoperability
https://www.w3.org/TR/css/#rough-interop

also, section 8. Indices has an index of terms, of selectors, of 
at-rules, of properties and of values.

https://www.w3.org/TR/css/#indices

Here is the updated registration text:

This updated registration obsoletes RFC 2318 
<https://datatracker.ietf.org/doc/html/rfc2318>.

Type name: text

Subtype name: css

Required parameters: N/A

Optional parameters: charset (but see below)

Encoding considerations:

   binary

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.




On 2026-05-01 17:56, Alexey Melnikov via RT wrote:
> Hi Amanda/Chris,
>
> On 29/04/2026 19:43, Amanda Baber via RT wrote:
>> Hi Alexey,
>>
>> Can you review this one? We have confirmation from the W3C liaison that this can be processed.
> Ok, some nits below, but otherwise this looks fine. (I wish there was a
> link to find where different CSS modules are defined. Can this be
> added?). Copied the original request to reduce the number of quoting
> levels in my reply:
>
>> Type name: text
>>
>> Subtype name: css
>>
>> Required parameters: none
> Nit: Please use "N/A" instead of "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.
> This field must contain 1 of 4 choices: 7bit, 8bit, binary or framed. I
> think this should be "binary" if lines longer that 1000 octets are
> allowed. Otherwise it is "8bit".
>> 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.
>> 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 [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
>>>
> Best Regards,
>
> Alexey
>
-- 
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 to [email protected]