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

Julian Reschke <julian.reschke@gmx.de> Fri, 20 April 2012 08:56 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA38721F8568 for <apps-discuss@ietfa.amsl.com>; Fri, 20 Apr 2012 01:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.894
X-Spam-Level:
X-Spam-Status: No, score=-102.894 tagged_above=-999 required=5 tests=[AWL=-0.295, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brpHhETNu2Ui for <apps-discuss@ietfa.amsl.com>; Fri, 20 Apr 2012 01:56:47 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id D187E21F868A for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 01:56:44 -0700 (PDT)
Received: (qmail invoked by alias); 20 Apr 2012 08:50:03 -0000
Received: from p57A6D903.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.217.3] by mail.gmx.net (mp072) with SMTP; 20 Apr 2012 10:50:03 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19QrqtClmRQMjkoIiK1gYuR8iXNJVyIaPhgrEhFpt NPaeq4L1jW+3vI
Message-ID: <4F91233A.1000603@gmx.de>
Date: Fri, 20 Apr 2012 10:50:02 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: Tony Hansen <tony@maillennium.att.com>
References: <4F877CEE.5030107@arcanedomain.com> <01OE8S1I9Z2K00ZUIL@mauve.mrochek.com> <9452079D1A51524AA5749AD23E0039280EF063@exch-mbx901.corp.cloudmark.com> <CA8E55D5-822A-47DC-B5CB-583CC328227B@jenitennison.com> <4F87EBD4.90501@gmx.de> <CFA00AEC-F80B-4517-8101-A5DDA57555ED@jenitennison.com> <01OEABGEZ8RU00ZUIL@mauve.mrochek.com> <098D7D86-2FF3-4287-800F-5FAB6C0212F2@jenitennison.com> <01OEE9DUSD8400ZUIL@mauve.mrochek.com> <4F8D189A.3010304@gmx.de> <4F901485.20800@maillennium.att.com>
In-Reply-To: <4F901485.20800@maillennium.att.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "www-tag@w3.org List" <www-tag@w3.org>, apps-discuss@ietf.org
Subject: Re: [apps-discuss] W3C TAG Comment on Draft Media Type Specifications and Registration Procedures
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2012 08:56:48 -0000

On 2012-04-19 15:35, Tony Hansen 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.
> ...

Maybe, to avoid confusion, point out that at the time of publication, 
there was no fragment identifier syntax for JSON...

Best regards, Julian