W3C home > Mailing lists > Public > www-tag@w3.org > April 2012

Re: [apps-discuss] W3C TAG Comment on Draft Media Type Specifications and Registration Procedures

From: Jeni Tennison <jeni@jenitennison.com>
Date: Fri, 20 Apr 2012 11:30:54 +0100
Cc: Ned Freed <ned.freed@mrochek.com>, apps-discuss@ietf.org, "www-tag@w3.org List" <www-tag@w3.org>
Message-Id: <02811F06-0325-4A0D-AE0D-3B5AF07EAE97@jenitennison.com>
To: Tony Hansen <tony@maillennium.att.com>
Hi Tony,

On 20 Apr 2012, at 08:24, Ned Freed wrote:
>> So I've added these Fragment identifier considerations sections to the
>> suffixes that have an underlying media type registration.
>> 
>>     Media types using "+json" MUST accept any fragment identifiers
>>     defined for "application/json". Specific media types may
>>     identify additional fragment identifier considerations.
> 
> I like the overall idea but, per the above, MUST is too strong. SHOULD
> is appropriate here, and I'd capitalize the may in the second sentence.

I agree with Ned about softening the wording. The other thing that you could specifically draw out is that fragment identifiers that are classed as errors in the media type related to the suffix may be classified as OK within a specific media type.

The other (word-smithing) comment I'd make is that it's not enough for the specific media type to 'accept' fragment identifiers: they should be processed in the same way as well.

So I'd suggest something like:

    Media types using "+json" SHOULD process any fragment identifiers
    defined for "application/json" in the same way as defined for that
    media type. Specific media types MAY identify additional fragment 
    identifier considerations and MAY define processing for fragment 
    identifiers that are classed as errors for "application/json".

Cheers,

Jeni
-- 
Jeni Tennison
http://www.jenitennison.com
Received on Friday, 20 April 2012 10:32:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:44 UTC