DP: It would be easier for people if MIME-type is written in the media-types.xml document.
... CB mentioned that is the case for W3C specs for most of the time.
... I am not sure if we can change the situation given that some other W3C specs are in the same situation.

Canonical EXI - 4.3.1 and 4.3.2

DP: Even an example would help.
... I will double-check what's the best way to resolve this, including the possibility to merge the two section.

Re: application/exi media-type

CB: The resource is outside of IANA.
... W3C includes the media-type in its document.
... Some others create standalone document, but we don't.

DP: It's a bit pitty. But we are not the only one.

CB: We have IETF liaison, but I am not sure if how far we can go to improve IANA registration.

use of elements for property names in EXI4CSS

CB: There should be some report from CSS WG. They had face-to-face meeting recently.

DP: Property names are currently string values. TK suggested to use element names.
... You save 1 byte for each value occurrence.
... I tried to be aligned with CSS Object Model.
... It was specified as string values.
... I plan to experiment a bit.
... For smaller use cases, pre-population was giving good performance. For larger files, it was not as good.
... I wonder whether we want to stick to CSSOM, or we can deviate a little bit.
... When I look at CSSOM, it does not explicitly say property names are strings.