Registration of media type application/ttaf+xml

[Paul Libbrecht]

Indeed these 4-letter codes are now unused. But please note that Apple  
was registering them before which was a guarantee for uniqueness  
whereas, now, he only conflict-free zone would be the media-type. For  
this reason, I think, te media type registration is usefully enriched  
with clipboard names: it allows fully independent implementors to use  
the same names.

The 4-letter code is, thus, just an extra information which is  
centrally displayed so that conflicts can be avoided even if not in  
use. An update of the RFC can be useful but does not sound in any way  
urgent.

Paul



Le 27 août 2010 à 03:14, Philippe Le Hegaret <plh at w3.org> a écrit :

> On Thu, 2010-08-26 at 17:44 -0700, David Singer wrote:
>> I would leave the Mac file type code blank, myself.  Or make it a  
>> text document (which it is).  We no longer register these, afaik,  
>> so...
>
> Hi David,
>
> as far as I know, RFC 4288 indicates:
> [[
> 4.11.  Additional Information
>
>   Various sorts of optional information SHOULD be included in the
>   specification of a media type if it is available:
> [...]
>   o  File name extension(s) commonly used on one or more platforms to
>      indicate that some file contains a given media type.
>
>   o  Mac OS File Type code(s) (4 octets) used to label files  
> containing
>      a given media type.
> ]]
> http://www.ietf.org/rfc/rfc4288.txt
>
> So, I don't mind one way or another, but it seems to me RFC 4288 needs
> to be updated if we're going to drop the usage.
>
> Philippe
>
>