Re: Registration of media type application/xhtml-voice+xml

Martin Duerst <duerst@it.aoyama.ac.jp> Thu, 14 July 2005 06:51 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j6E6pG4x073071; Wed, 13 Jul 2005 23:51:16 -0700 (PDT) (envelope-from owner-ietf-xml-mime@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j6E6pGHG073070; Wed, 13 Jul 2005 23:51:16 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from scmailgw1.scop.aoyama.ac.jp (scmailgw1.scop.aoyama.ac.jp [133.2.251.194]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j6E6obpl072780 for <ietf-xml-mime@imc.org>; Wed, 13 Jul 2005 23:51:15 -0700 (PDT) (envelope-from duerst@it.aoyama.ac.jp)
Received: from scmse2.scbb.aoyama.ac.jp ([133.2.253.17]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id j6E6oVC08616; Thu, 14 Jul 2005 15:50:31 +0900 (JST)
Received: from nodnsquery(133.2.206.133) by scmse2.scbb.aoyama.ac.jp via csmap id 39b68724_f435_11d9_9592_0030482532aa_12528; Thu, 14 Jul 2005 16:02:22 +0900 (JST)
Received: from Spooler by it.aoyama.ac.jp (Mercury/32 v3.32) ID MO0083C4; 14 Jul 05 15:56:09 +0900
Received: from spooler by it.aoyama.ac.jp (Mercury/32 v3.32); 14 Jul 05 15:55:47 +0900
Received: from EBOSHIIWA.it.aoyama.ac.jp (133.2.227.17) by it.aoyama.ac.jp (Mercury/32 v3.32) with ESMTP ID MG0083C2; 14 Jul 05 15:55:40 +0900
Message-Id: <6.0.0.20.2.20050714153404.08e76ec0@itmail.it.aoyama.ac.jp>
X-Sender: duerst@itmail.it.aoyama.ac.jp
X-Mailer: QUALCOMM Windows Eudora Version 6J
Date: Thu, 14 Jul 2005 15:49:12 +0900
To: Gerald McCobb <mccobb@us.ibm.com>, iana@iana.org, ietf-types@iana.org
From: Martin Duerst <duerst@it.aoyama.ac.jp>
Subject: Re: Registration of media type application/xhtml-voice+xml
Cc: "ietf-xml-mime@imc.org" <ietf-xml-mime@imc.org>
In-Reply-To: <OFE9D62E0C.63121448-ON8525703D.0057CB6D-8525703D.005AE95B@ us.ibm.com>
References: <20050712220929.GWHV23513.lakermmtao04.cox.net@A31P> <OFE9D62E0C.63121448-ON8525703D.0057CB6D-8525703D.005AE95B@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-xml-mime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-xml-mime/mail-archive/>
List-ID: <ietf-xml-mime.imc.org>
List-Unsubscribe: <mailto:ietf-xml-mime-request@imc.org?body=unsubscribe>

At 01:33 05/07/14, Gerald McCobb wrote:

>I asked the IESG to postpone the publication of the 
>application/xhtml-voice+xml media type as an informational RFC.  The 
>registration is not correct.  It should be application/xhtml+voice+xml. 
>The application/xhtml+voice+xml media type was the original submission.
>
>There is an issue with the original submission:
>
>One of the reviewers pointed out that "a certain class of error could be 
>avoided by renaming this application/xhtml-plus-voice+xml... I don't know 
>of any other "+xml" [see RFC3023] media types that have a "+" in the 
>name... a poorly-constructed regexp looking for +xml along the lines of 
>/\+(.*)$/  would miss this one."

I agree with that reviewer that the type should not contain
'+' characters except before 'xml'. All other subtypes have used '-'
as a separator. The '+' separator was specifically introduced to
express the fact that the '+xml' part is something more than
a simple subtype.

Although there is probably nothing in RFC 3023 explicitly
disallowing the use of '+' for "arbitrary use", I think that
the whole rationale for '+xml' in Appendix A of RFC 3023
(in particular http://www.ietf.org/rfc/rfc3023.txt, A.12)
seem to indicate that it shouldn't be done.



>I believe this argument is not strong enough to prevent approval of the 
>application/xhtml+voice+xml media type:

>2. The argument for having "+" in the subtype is unconvincing, given that 
>the simplest method to determine if something is XML is also the safest, 
>that is, if the last four characters are "+xml" or "/xml" then the 
>document is XML, otherwise it is not. If that has to be done with regexps, 
>instead of just examining the last four bytes, that would be /[/+]xml$/. 
>If type and subtype were split already it would be /\+?xml$/ for the subtype.

I think the regexp example is only the tip of the iceberg. Not using
the plus will allow better future extensibility.


Regards,    Martin.