Re: [apps-discuss] W3C TAG Comment on Draft Media Type Specifications and Registration Procedures
Tony Hansen <tony@maillennium.att.com> Thu, 19 April 2012 13:35 UTC
Return-Path: <tony@maillennium.att.com>
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 6D27421F8636 for <apps-discuss@ietfa.amsl.com>; Thu, 19 Apr 2012 06:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.307
X-Spam-Level:
X-Spam-Status: No, score=-105.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, 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 OQWwa8++B4l6 for <apps-discuss@ietfa.amsl.com>; Thu, 19 Apr 2012 06:35:35 -0700 (PDT)
Received: from nbfkord-smmo03.seg.att.com (nbfkord-smmo03.seg.att.com [209.65.160.84]) by ietfa.amsl.com (Postfix) with ESMTP id 0771821F863B for <apps-discuss@ietf.org>; Thu, 19 Apr 2012 06:35:34 -0700 (PDT)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo03.seg.att.com(mxl_mta-6.11.0-8) over TLS secured channel with ESMTP id 6a4109f4.0.1557671.00-288.4324389.nbfkord-smmo03.seg.att.com (envelope-from <tony@maillennium.att.com>); Thu, 19 Apr 2012 13:35:35 +0000 (UTC)
X-MXL-Hash: 4f9014a70fbf7ae9-f98784ea2d64bfaaeb46fc789694e2bf880197b5
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q3JDZXnY013131 for <apps-discuss@ietf.org>; Thu, 19 Apr 2012 09:35:34 -0400
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q3JDZTY0013105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <apps-discuss@ietf.org>; Thu, 19 Apr 2012 09:35:30 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <apps-discuss@ietf.org>; Thu, 19 Apr 2012 09:35:07 -0400
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q3JDZ7BV010669 for <apps-discuss@ietf.org>; Thu, 19 Apr 2012 09:35:07 -0400
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id q3JDZ2j9010319 for <apps-discuss@ietf.org>; Thu, 19 Apr 2012 09:35:02 -0400
Received: from [130.10.167.85] (vpn-130-10-167-85.vpn.mwst.att.com[130.10.167.85]) by maillennium.att.com (mailgw1) with ESMTP id <20120419133156gw1004oro9e> (Authid: tony); Thu, 19 Apr 2012 13:31:57 +0000
X-Originating-IP: [130.10.167.85]
Message-ID: <4F901485.20800@maillennium.att.com>
Date: Thu, 19 Apr 2012 09:35:01 -0400
From: Tony Hansen <tony@maillennium.att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
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>
In-Reply-To: <4F8D189A.3010304@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-RSA-Action: allow
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@maillennium.att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=1.0 c=1 a=w3AnSTxstZUA:10 a=vnNYxAp2wzwA:10 a=yBMqTHKFRa]
X-AnalysisOut: [4A:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:10 a=ZRNLZ4dFUbCvG8]
X-AnalysisOut: [UMqPvVAA==:17 a=2dTlHvqGvJKXRGe4yj0A:9 a=wPNLvfGTeEIA:10]
X-Mailman-Approved-At: Thu, 19 Apr 2012 07:48:55 -0700
Cc: apps-discuss@ietf.org, "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: Thu, 19 Apr 2012 13:35:36 -0000
On 4/17/2012 3:15 AM, Julian Reschke wrote: > 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. So, I'm revising my draft where I'm actually *registering* a bunch of these structured suffixes. (draft-hansen-media-type-suffix-reg) What I'm thinking is that the fragment considerations section for each should simply point at the base application/whatever specification. That is, if application/SUFFIX has specific fragment identifiers associated with it, then anything with +SUFFIX (e.g., application/TYPE+SUFFIX) should accept the application/SUFFIX fragment identifiers as well as anything specific to the given media type. 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 have similar text for +fastinfoset, +wbxml and +zip. This way, the definition of fragment identifiers for application/json can progress at its own pace, as can any definitions of fragment identifiers for application/fastinfoset, application/vnd.wap.wbxml and application/zip. In addition, I'm thinking draft-hansen-media-type-suffix-reg should have an IANA considerations note to add the Fragment identifier considerations section for +xml, with text similar to the above. (I think the basic paragraph could use a little wordsmithing, but what I have there should get the right idea across.) Tony Hansen
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Murray S. Kucherawy
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Julian Reschke
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Jeni Tennison
- [apps-discuss] W3C TAG Comment on Draft Media Typ… Noah Mendelsohn
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Julian Reschke
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Noah Mendelsohn
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Bjoern Hoehrmann
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Jeni Tennison
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Peter Saint-Andre
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Murray S. Kucherawy
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Peter Saint-Andre
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Bjoern Hoehrmann
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Peter Saint-Andre
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Julian Reschke
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Jeni Tennison
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Jeni Tennison
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Bjoern Hoehrmann
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Tony Hansen
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Julian Reschke
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Henry S. Thompson
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Jeni Tennison
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Bjoern Hoehrmann
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Henry S. Thompson
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Noah Mendelsohn
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Tony Hansen
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Bjoern Hoehrmann
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Henry S. Thompson
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Bjoern Hoehrmann
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Ned Freed
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Henry S. Thompson
- Re: [apps-discuss] W3C TAG Comment on Draft Media… Henry S. Thompson
- Re: [apps-discuss] W3C TAG Comment on Draft Media… David Booth