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

ht@inf.ed.ac.uk (Henry S. Thompson) Sat, 21 April 2012 15:12 UTC

Return-Path: <ht@inf.ed.ac.uk>
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 0CDD921F85D7 for <apps-discuss@ietfa.amsl.com>; Sat, 21 Apr 2012 08:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level:
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 6r8sCi05nfMe for <apps-discuss@ietfa.amsl.com>; Sat, 21 Apr 2012 08:12:29 -0700 (PDT)
Received: from treacle.ucs.ed.ac.uk (treacle.ucs.ed.ac.uk [129.215.16.102]) by ietfa.amsl.com (Postfix) with ESMTP id E13B921F858B for <apps-discuss@ietf.org>; Sat, 21 Apr 2012 08:12:28 -0700 (PDT)
Received: from nutty.inf.ed.ac.uk (nutty.inf.ed.ac.uk [129.215.33.33]) by treacle.ucs.ed.ac.uk (8.13.8/8.13.4) with ESMTP id q3LFCB5r003390; Sat, 21 Apr 2012 16:12:15 +0100 (BST)
Received: from calexico.inf.ed.ac.uk (calexico.inf.ed.ac.uk [129.215.24.15]) by nutty.inf.ed.ac.uk (8.13.8/8.13.8) with ESMTP id q3LFCA6S029865; Sat, 21 Apr 2012 16:12:10 +0100
Received: from calexico.inf.ed.ac.uk (localhost [127.0.0.1]) by calexico.inf.ed.ac.uk (8.14.4/8.14.4) with ESMTP id q3LFC9iH024768; Sat, 21 Apr 2012 16:12:09 +0100
Received: (from ht@localhost) by calexico.inf.ed.ac.uk (8.14.4/8.14.4/Submit) id q3LFC8Xh024764; Sat, 21 Apr 2012 16:12:08 +0100
X-Authentication-Warning: calexico.inf.ed.ac.uk: ht set sender to ht@inf.ed.ac.uk using -f
To: Bjoern Hoehrmann <derhoermi@gmx.net>
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> <2ee3p79ijn5orc4i6m85hqfm7ta4vv55mb@hive.bjoern.hoehrmann.de>
From: ht@inf.ed.ac.uk
Date: Sat, 21 Apr 2012 16:12:08 +0100
In-Reply-To: <2ee3p79ijn5orc4i6m85hqfm7ta4vv55mb@hive.bjoern.hoehrmann.de> (Bjoern Hoehrmann's message of "Fri, 20 Apr 2012 21:45:08 +0200")
Message-ID: <f5bty0df7av.fsf@calexico.inf.ed.ac.uk>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Edinburgh-Scanned: at treacle.ucs.ed.ac.uk with MIMEDefang 2.60, Sophie, Sophos Anti-Virus, Clam AntiVirus
X-Scanned-By: MIMEDefang 2.60 on 129.215.16.102
Cc: www-tag@w3.org, Tony Hansen <tony@maillennium.att.com>, 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: Sat, 21 Apr 2012 15:12:33 -0000

Bjoern Hoehrmann writes:

> * 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.
>
> This says that "+json" cannot be used for JSON types where fragment
> identifiers are of any concern since any future specification of the
> application/json type may override such registrations in incompatible
> ways. This seems to be missing the point of why we would have "+json"
> to begin with.

Or, it implies any update to a syntax schema registration such as
application/json has a responsibility to its "deployed base".  Comes
with the territory.

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]