Re: [media-types] Macintosh file type code

["Chris Lilley" <[e-mail]>]

On 2016-12-09 01:40:41, Martin J. Dürst <[e-mail]> wrote:
> 2) Is there value in adding the Apple UTI (which is at least documented, and in current use) to the registration templates?
>
> My reason for asking is draft-ietf-justfont-toplevel
> https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/
>
> which will define a new top-level Media Type for fonts. I am very tempted to just remove the "Macintosh file type code" from the registration template, and could go either way on replacing it with an "Apple Uniform Type Identifier" field - opinions welcome.

Do the individual subtypes that this draft is registering have UTIs, or
should they have them? If yes, then having this field is definitely
valuable.
Chris Lilley: 
Yes, they do, and I have added them to the current document yesterday.


> Raising on this list since it affects all other registration templates as well.

I'd propose you also ask for advice on
https://github.com/svgeesus/ietf-justfont/issues/24 and
https://github.com/svgeesus/ietf-justfont/issues/23
here on this list, because I think that's where the chance of getting
some valuable input is highest.

Chris Lilley:

Good idea, thanks Martin. The one about case insensitivity is settled, but I will send a separate message about the spaces in parameters. However, the current document now disallows spaces.


--
Chris Lilley
@svgeesus
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media