Re: Request for comments regarding draft-mccobb-xplusv-media-type-01

Bjoern Hoehrmann <derhoermi@gmx.net> Sat, 26 March 2005 23:06 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 j2QN6eXS079259; Sat, 26 Mar 2005 15:06:40 -0800 (PST) (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 j2QN6egu079258; Sat, 26 Mar 2005 15:06:40 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f
Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by above.proper.com (8.12.11/8.12.9) with SMTP id j2QN6cdj079239 for <ietf-xml-mime@imc.org>; Sat, 26 Mar 2005 15:06:39 -0800 (PST) (envelope-from derhoermi@gmx.net)
Received: (qmail invoked by alias); 26 Mar 2005 23:06:31 -0000
Received: from dsl-084-056-234-233.arcor-ip.net (EHLO localhost) [84.56.234.233] by mail.gmx.net (mp016) with SMTP; 27 Mar 2005 00:06:31 +0100
X-Authenticated: #723575
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Gerald McCobb <mccobb@us.ibm.com>
Cc: ietf-types@iana.org, ietf-xml-mime@imc.org
Subject: Re: Request for comments regarding draft-mccobb-xplusv-media-type-01
Date: Sun, 27 Mar 2005 00:06:48 +0100
Message-ID: <424ce891.128044187@smtp.bjoern.hoehrmann.de>
References: <OFD22126B4.25173883-ON85256FCF.005885B7-85256FCF.00599F76@us.ibm.com>
In-Reply-To: <OFD22126B4.25173883-ON85256FCF.005885B7-85256FCF.00599F76@us.ibm.com>
X-Mailer: Forte Agent 1.92/32.572
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
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>

* Gerald McCobb wrote:
>2.1 application/xhtml+voice+xml Usage
>
>   The application/xhtml+voice+xml media type is intended to be a media
>   descriptor for XHTML+Voice documents.
>
>   This media type registration is not intended for email usage.

The draft does not really explain why there is a need for such a
type in the first place; why don't you use application/xhtml+xml?

>      Optional parameters:
>   version:  refers to the XHTML+Voice language version in the document.
>             Acceptable values are 1.0, 1.1, and 1.2 (default).

What are the processing requirements for this parameter?

>   charset:  has the same meaning as the text/html media type.  See
>   section 2 of [RFC 2854].

A word seems to be missing here. It is not really clear why the draft
refers to RFC 2854 rather than RFC 3023 or RFC 3236. 

>      Security considerations:
> 
>   XHTML+Voice is an extension of XHTML and has the same security issues
>   as XHTML.  These include interpreting anchors and forms in HTML
>   documents, and scripting languages and other dynamic interactive
>   capabilities.  See section 7 of [RFC 2854].

So the extensions to XHTML have no security considerations?

>         File extension(s): html, htm, mxml, xvml

I don't think .html and .htm should be listed here, they are already in
common use for application/xhtml+xml and text/html.

>4. Fragment Identifiers
>
>   See section 3 of [RFC 2854].

It is unclear what this means, RFC 2854 and RFC 3236 have inconsistent
rules for fragment identifiers and XHTML+Voice adds new ID attributes
so that the fragment identifier namespaces are different.

>6. Security Considerations
>
>   Security considerations for this media type are discussed in the MIME
>   type registration that appears in section 4.

Section 4 has no security considerations...

>7. References

The draft should be clear about which of these references are
informative and which normative.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/