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

Tony Hansen <tony@maillennium.att.com> Fri, 20 April 2012 17:45 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 2991021F8688 for <apps-discuss@ietfa.amsl.com>; Fri, 20 Apr 2012 10:45:29 -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 ALCjCP7br0Hn for <apps-discuss@ietfa.amsl.com>; Fri, 20 Apr 2012 10:45:28 -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 46B3521F8692 for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 10:45:28 -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 7b0a19f4.0.2117693.00-445.5874227.nbfkord-smmo03.seg.att.com (envelope-from <tony@maillennium.att.com>); Fri, 20 Apr 2012 17:45:28 +0000 (UTC)
X-MXL-Hash: 4f91a0b87243dc3c-b3b7909fdef5ef377734059613da25f44655b309
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 q3KHjQod015290 for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 13:45:27 -0400
Received: from sflint01.pst.cso.att.com (sflint01.pst.cso.att.com [144.154.234.228]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q3KHjNOG014999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 13:45:24 -0400
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint01.pst.cso.att.com (RSA Interceptor) for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 13:44:51 -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 q3KHip1x001036 for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 13:44:51 -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 q3KHigdH000628 for <apps-discuss@ietf.org>; Fri, 20 Apr 2012 13:44:43 -0400
Received: from [135.70.234.24] (vpn-135-70-234-24.vpn.east.att.com[135.70.234.24]) by maillennium.att.com (mailgw1) with ESMTP id <20120420174135gw1004ors4e> (Authid: tony); Fri, 20 Apr 2012 17:41:36 +0000
X-Originating-IP: [135.70.234.24]
Message-ID: <4F91A089.6070308@maillennium.att.com>
Date: Fri, 20 Apr 2012 13:44:41 -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> <4F901485.20800@maillennium.att.com> <01OEITCHB07U00ZGHB@mauve.mrochek.com> <02811F06-0325-4A0D-AE0D-3B5AF07EAE97@jenitennison.com>
In-Reply-To: <02811F06-0325-4A0D-AE0D-3B5AF07EAE97@jenitennison.com>
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=WDaDfJvHXAEA:10 a=vnNYxAp2wzwA:10 a=CRkRB2Q0ku]
X-AnalysisOut: [cA:10 a=ofMgfj31e3cA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-IA:1]
X-AnalysisOut: [0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a=sQJM4-vXpLQEO6AIWr4A:9 a]
X-AnalysisOut: [=wPNLvfGTeEIA:10]
X-Mailman-Approved-At: Sat, 21 Apr 2012 09:51:03 -0700
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 17:45:29 -0000

On 4/20/2012 6:30 AM, Jeni Tennison and others wrote:
 > ...

Thanks for all the comments.

This is what I've come up with that seems to satisfy the concerns I've 
heard expressed so far:

Media types using "+json" SHOULD process any fragment identifiers 
defined for "application/json" in the same way as defined for that media 
type. (At publication of this document, there is no fragment 
identification syntax defined for "application/json".) Specific media 
types using "+json" MAY identify additional fragment identifier 
considerations, MAY define processing for fragment identifiers that are 
classed as errors for "application/json" and MAY designate fragment 
identifiers defined for "application/json" that SHOULD NOT be used.

Same text for +fastinfoset, +wbxml and +zip. The note I added for +xml 
is similar:

Media types using "+xml" SHOULD process any fragment identifiers defined 
for "application/xml" in the same way as defined for that media type. 
(At publication of this document, the fragment identification syntax 
considerations for "application/xml" are defined in <xref 
target='RFC3023'/>.) Specific media types using "+xml" MAY identify 
additional fragment identifier considerations, MAY define processing for 
fragment identifiers that are classed as errors for "application/xml" 
and MAY designate fragment identifiers defined for "application/xml" 
that SHOULD NOT be used.



	Tony Hansen