Re: [media-types] registering vnd.qt.*qml types

Tony Hansen <tony@att.com> Wed, 30 January 2013 14:18 UTC

Return-Path: <tony@att.com>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18BDC21F8B18 for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 06:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.485
X-Spam-Level:
X-Spam-Status: No, score=-107.485 tagged_above=-999 required=5 tests=[AWL=-1.114, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfjVCxo3xniR for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 06:18:13 -0800 (PST)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4324121F8B34 for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 06:18:13 -0800 (PST)
Received: from unknown [144.160.20.145] (EHLO mlpd192.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 3ab29015.0.4122489.00-117.11428092.nbfkord-smmo05.seg.att.com (envelope-from <tony@att.com>); Wed, 30 Jan 2013 14:18:13 +0000 (UTC)
X-MXL-Hash: 51092ba5148d7137-5be790060b386b2da086aa7fa0191980c9a47df3
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 r0UEIBbp007372 for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 09:18:11 -0500
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 r0UEI80r007363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 09:18:09 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 09:17:57 -0500
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 r0UEHvsh029852 for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 09:17:57 -0500
Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id r0UEHtZB029803 for <media-types@ietfa.amsl.com>; Wed, 30 Jan 2013 09:17:55 -0500
Received: from [135.70.101.29] (vpn-135-70-101-29.vpn.swst.att.com[135.70.101.29]) by maillennium.att.com (mailgw1) with ESMTP id <20130130141702gw1006327je> (Authid: tony); Wed, 30 Jan 2013 14:17:03 +0000
X-Originating-IP: [135.70.101.29]
Message-ID: <51092B90.1010907@att.com>
Date: Wed, 30 Jan 2013 09:17:52 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Mohamed Fawzi <Fawzi.Mohamed@digia.com>
References: <D932B8DA-88F9-447A-A0A1-AA1D1BB7D3A8@digia.com> <5107DB33.6090301@gmx.de> <1A6074EA-AFB4-44FD-AE8A-1D64B0412F49@digia.com> <5107E29D.5060506@gmx.de> <FE4E752A-2897-4C0B-B038-87893D2CA5A7@digia.com>
In-Reply-To: <FE4E752A-2897-4C0B-B038-87893D2CA5A7@digia.com>
Content-Type: multipart/alternative; boundary="------------080500000506010603030905"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.20.145]
X-AnalysisOut: [v=2.0 cv=PtskmXw3 c=1 sm=0 a=ZRNLZ4dFUbCvG8UMqPvVAA==:17 a]
X-AnalysisOut: [=BsVaBHLMQX4A:10 a=qvxnG7FKX0EA:10 a=LCnI5vdN5E8A:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=-c5Na2Jp]
X-AnalysisOut: [FxsA:10 a=48vgC7mUAAAA:8 a=lRxpQPx1AAAA:8 a=C7lIxwUCmBEkX3]
X-AnalysisOut: [NHU_AA:9 a=pILNOxqGKmIA:10 a=_RhRFcbxBZMA:10 a=X7LoOsmnAAA]
X-AnalysisOut: [A:8 a=EniF0PnvQoXgJzFplJIA:9 a=_W_S_7VecoQA:10 a=op-nnfl6c]
X-AnalysisOut: [b0A:10 a=6TfDa4B52uubmKWk:21]
Cc: Julian Reschke <julian.reschke@gmx.de>, "media-types@ietfa.amsl.com" <media-types@ietfa.amsl.com>
Subject: Re: [media-types] registering vnd.qt.*qml types
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 14:18:20 -0000

On 1/30/2013 8:11 AM, Mohamed Fawzi wrote:
> On 29 Jan 2013, at 15:54, Julian Reschke <julian.reschke@gmx.de> wrote:
>> On 2013-01-29 15:43, Mohamed Fawzi wrote:
>>> On 29 Jan 2013, at 15:22, Julian Reschke <julian.reschke@gmx.de
>>> Hi Julian thanks for the comment,
>>>
>>>> Regarding the "+qml" suffix -- you should consult
>>>> <http://tools.ietf.org/html/draft-ietf-appsawg-media-type-regs-14>.
>>>> You will likely realize that the use of the "+" notation isn't
>>>> justified in this case.
>>> Qml is actually a language with a well defined grammar
>>> http://qt.gitorious.org/qt/qtdeclarative/blobs/stable/src/qml/qml/parser/qqmljs.g
>>> that is basically an extended javascript syntax.
>>>
>>> All those documents share that syntax (and parser).
>>> So I thought it was ok to use +qml for them.
>>>
>>>  From the document it seems that is allowed, you mean that it should not
>>> be done because
>>> 1) qml definition is not performed by a standard body, or similar
>>> 2) one should register also the base type without the qml syntax
>> If you want to use the suffix, you'll have to register the base type first (I believe).
> looking at the just released documents by Björn Höhrmann it looks to me,
> that the main problem is not that, but rather that I should formalise the +qml
> suffix, probably with an RFC, to use it.

draft-ietf-appsawg-media-type-regs was just published as RFC 6838; see 
it for how to register +qml.

See RFC 6839 (also just published) for example registrations. Work with 
Ned Freed if you choose to go this route -- he's the designated expert 
reviewer for suffix registrations.

Registering a suffix does not *require* an RFC: it can be attached to 
the media type registration form and done together.

     Tony Hansen