Re: [ietf-types] Registration of media type application/vcard+xml

[Chris Lilley <[e-mail]>]

On Thursday, April 7, 2011, 10:27:07 PM, Simon wrote:

SP> On 2011-04-07 16:12, Bjoern Hoehrmann wrote:
>>>   Optional parameters:  none

>> If you do not specify an optional 'charset' parameter, it is ambiguous
>> what the encoding of `application/vcard+xml;charset=...` is; if you only
>> read the registration you are likely to ignore the parameter, while, if
>> you read RFC 3023 you expect the 'charset' parameter to specify the en-
>> coding, which has interoperability and security implications.

SP> I will update this to read:

SP>    Optional parameters: charset as defined for application/xml in
SP>       [RFC3023]; per [RFC3023], use of the charset parameter with the
SP>       value "utf-8" is "STRONGLY RECOMMENDED"

That verbatim quote from RFC3023 will probably suffice to deal with Bjoern's criticism, but as I just pointed out in another message to this thread his criticism is outdated and unwarranted, and raises security issues (as he himself points out).



-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups