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

Julian Reschke <julian.reschke@gmx.de> Tue, 17 April 2012 07:15 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 244FF11E80A5 for <apps-discuss@ietfa.amsl.com>; Tue, 17 Apr 2012 00:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.94
X-Spam-Level:
X-Spam-Status: No, score=-102.94 tagged_above=-999 required=5 tests=[AWL=-0.341, 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 I0EoT4nnLZ+9 for <apps-discuss@ietfa.amsl.com>; Tue, 17 Apr 2012 00:15:43 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id D1D0921F84D3 for <apps-discuss@ietf.org>; Tue, 17 Apr 2012 00:15:42 -0700 (PDT)
Received: (qmail invoked by alias); 17 Apr 2012 07:15:41 -0000
Received: from p57A6FAF7.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.250.247] by mail.gmx.net (mp040) with SMTP; 17 Apr 2012 09:15:41 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+CjBsw4NqCCBJw8qiacz54CwqFRHYF4lK5Qd8yU3 zHo8a8/+EUkF0k
Message-ID: <4F8D189A.3010304@gmx.de>
Date: Tue, 17 Apr 2012 09:15:38 +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: Ned Freed <ned.freed@mrochek.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>
In-Reply-To: <01OEE9DUSD8400ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: apps-discuss@ietf.org, Jeni Tennison <jeni@jenitennison.com>, tony+mtsuffix@maillennium.att.com, Noah Mendelsohn <nrm@arcanedomain.com>, john+ietf@jck.com, "www-tag@w3.org List" <www-tag@w3.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: Tue, 17 Apr 2012 07:15:44 -0000

On 2012-04-17 02:53, Ned Freed wrote:
> ...
> I note that this raises the issue of what to do about fragment identifiers in
> the initial suffix registry document. Fragment identifiers don't really make
> sense for most of the suffixes defined there. The exceptions I see are +xml and
> +json. +json seems simple enough - refer to draft-ietf-appsawg-json-pointer-01.
> ...

I think that would be premature.

The question has come up several times, and I don't think we are near 
any kind of even rough consensus about whether the spec should try to 
define a fragment identifier syntax for "+json" (or even application/json).

> +xml is a bigger issue. This is a document to populate the registry; it is not
> the place to define how fragment identifiers for XML work. But RFC 3023 section
> 5 seems a bit dated. And waiting for a revision for RFC 3023 when there isn't
> even an I-D doesn't sound like a good idea. So dated or not, I guess a
> reference to RFC 3023 is as good as it gets for now.

Indeed.

Best regards, Julian