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 j2U2ebNa006934; Tue, 29 Mar 2005 18:40:37 -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 j2U2ebiC006933; Tue, 29 Mar 2005 18:40:37 -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 j2U2eZ9c006926 for ; Tue, 29 Mar 2005 18:40:36 -0800 (PST) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 30 Mar 2005 02:40:29 -0000 Received: from dsl-084-056-224-030.arcor-ip.net (EHLO localhost) [84.56.224.30] by mail.gmx.net (mp013) with SMTP; 30 Mar 2005 04:40:29 +0200 X-Authenticated: #723575 From: Bjoern Hoehrmann To: ietf-xml-mime@imc.org Subject: FYI: XML Schema: Component Designators Date: Wed, 30 Mar 2005 04:40:48 +0200 Message-ID: <424f1059.37521234@smtp.bjoern.hoehrmann.de> 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: List-ID: List-Unsubscribe: Hi, http://www.w3.org/TR/2005/WD-xmlschema-ref-20050329/ is in Last Call, [...] [Definition: A canonical schema component designator is an absolute schema component designator that is a URI that has been normalized according to the rules given in the update to RFC2396 and where the relative schema component designator consists of an xmlns XPointer pointer part (if required) followed by a canonicalized xscd XPointer pointer part.] [Definition: A canonicalized xscd XPointer pointer part is an xscd XPointer pointer part where the pointer data is a canonical schema component path.] [...] As XML Schema schemas are represented "preferably of MIME type application/xml or text/xml" this might be relevant to the RFC 3023 revision. regards. -- 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/ 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 ; 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 To: Gerald McCobb 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: In-Reply-To: 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: List-ID: List-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/ 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 j2PDUb9Q014918; Fri, 25 Mar 2005 05:30:37 -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 j2PDUblE014917; Fri, 25 Mar 2005 05:30:37 -0800 (PST) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from homer.w3.org (homer.w3.org [128.30.52.30]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j2PDUbHp014904 for ; Fri, 25 Mar 2005 05:30:37 -0800 (PST) (envelope-from chris@w3.org) Received: from localhost (localhost [127.0.0.1]) by homer.w3.org (Postfix) with ESMTP id F27344F0D2; Fri, 25 Mar 2005 08:30:34 -0500 (EST) Date: Fri, 25 Mar 2005 14:30:35 +0100 From: Chris Lilley Reply-To: Chris Lilley Organization: W3C X-Priority: 3 (Normal) Message-ID: <1093207012.20050325143035@w3.org> To: Bjoern Hoehrmann Cc: ietf-xml-mime@imc.org Subject: Re: Protocol Action: 'The Standard Hexdump Format' to Proposed Standard In-Reply-To: <42480798.29434890@smtp.bjoern.hoehrmann.de> References: <42480798.29434890@smtp.bjoern.hoehrmann.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thursday, March 24, 2005, 7:39:13 PM, Bjoern wrote: BH> * The IESG wrote: >>The IESG has approved the following document: >> >>- 'The Standard Hexdump Format ' >> as a Proposed Standard BH> Hmm, BH> [...] BH> Required parameters: charset BH> This parameter must exist and must be set to "UTF-8". No other BH> character sets are allowed for transporting SHF data. The character BH> set designator MUST be uppercase. BH> [...] BH> http://www.ietf.org/internet-drafts/draft-strombergson-shf-06.txt BH> So we now have BH> * no charset parameter (e.g., application/vnd.pwg-xhtml-print+xml) BH> * optional charset parameter (e.g., application/xhtml+xml) BH> * required charset parameter (e.g., application/shf+xml) Yes, given that this is not a text/* type, if the format allows only a single encoding, I can't see what purpose the charset parameter serves. Except, perhaps, to force failure if the content is erroneously sent as UTF-16. -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead 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 j2OId1Ym002838; Thu, 24 Mar 2005 10:39:01 -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 j2OId1Ch002837; Thu, 24 Mar 2005 10:39:01 -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 j2OIcx2R002828 for ; Thu, 24 Mar 2005 10:39:00 -0800 (PST) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 24 Mar 2005 18:38:53 -0000 Received: from dsl-084-056-231-203.arcor-ip.net (EHLO localhost) [84.56.231.203] by mail.gmx.net (mp005) with SMTP; 24 Mar 2005 19:38:53 +0100 X-Authenticated: #723575 From: Bjoern Hoehrmann To: ietf-xml-mime@imc.org Subject: Re: Protocol Action: 'The Standard Hexdump Format' to Proposed Standard Date: Thu, 24 Mar 2005 19:39:13 +0100 Message-ID: <42480798.29434890@smtp.bjoern.hoehrmann.de> References: In-Reply-To: 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: List-ID: List-Unsubscribe: * The IESG wrote: >The IESG has approved the following document: > >- 'The Standard Hexdump Format ' > as a Proposed Standard Hmm, [...] Required parameters: charset This parameter must exist and must be set to "UTF-8". No other character sets are allowed for transporting SHF data. The character set designator MUST be uppercase. [...] http://www.ietf.org/internet-drafts/draft-strombergson-shf-06.txt So we now have * no charset parameter (e.g., application/vnd.pwg-xhtml-print+xml) * optional charset parameter (e.g., application/xhtml+xml) * required charset parameter (e.g., application/shf+xml) ... -- 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/