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 j89Jvbct026342; Fri, 9 Sep 2005 12:57:37 -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 j89JvbZc026341; Fri, 9 Sep 2005 12:57:37 -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 j89JvZad026328 for ; Fri, 9 Sep 2005 12:57:36 -0700 (PDT) (envelope-from duerst@it.aoyama.ac.jp) Received: from scmse2.scbb.aoyama.ac.jp (scmse2 [133.2.253.17]) by scmailgw1.scop.aoyama.ac.jp (secret/secret) with SMTP id j89JvJu04517; Sat, 10 Sep 2005 04:57:19 +0900 (JST) Received: from nodnsquery(133.2.210.1) by scmse2.scbb.aoyama.ac.jp via csmap id 9d28a752_216b_11da_9bc9_0030482532aa_14668; Sat, 10 Sep 2005 04:55:04 +0900 (JST) Received: from EBOSHIIWA.it.aoyama.ac.jp (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.13.1/8.13.1) with ESMTP id j89JxuZ9019655; Sat, 10 Sep 2005 05:01:08 +0900 Message-Id: <6.0.0.20.2.20050910031859.04c45150@localhost> X-Sender: duerst@localhost X-Mailer: QUALCOMM Windows Eudora Version 6J Date: Sat, 10 Sep 2005 03:25:06 +0900 To: Chris Lilley , "'Liam Quin'" From: Martin Duerst Subject: Re: W3C Last Call and Media Type request for comments: XSLT 2.0 Cc: public-qt-comments@w3.org, ietf-types@iana.org, ietf-xml-mime@imc.org In-Reply-To: <1164639983.20050908222926@w3.org> References: <20050908180657.GO20337@w3.org> <20050908184853.GS20337@w3.org> <1164639983.20050908222926@w3.org> 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: List-ID: List-Unsubscribe: At 05:29 05/09/09, Chris Lilley wrote: >this has come up before as W3C uses the new process. The requirement to >make the registration template an appendix in the spec means that people >tend to forget that the appendix also has the be read as an independent >document by the people here. Just a small point: There is no requirement that the template be an *appendix*. For many specs, making the template an appendix will work out fine, but it could as well be a section or subsection if that works better for the spec in question. >The appendix has to make sense as a standalone registrations, so rather >than saying "this document" say "the document at (url) called (title)". Yes, indeed. It will be self-referencing :-). Regards, Martin. 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 j890kAVw089974; Thu, 8 Sep 2005 17:46:10 -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 j890kABQ089973; Thu, 8 Sep 2005 17:46:10 -0700 (PDT) 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 j890k9P0089964 for ; Thu, 8 Sep 2005 17:46:10 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id 312504EEEC; Thu, 8 Sep 2005 20:46:09 -0400 (EDT) Date: Thu, 8 Sep 2005 20:46:09 -0400 From: "'Liam Quin'" To: Chris Lilley Cc: Scott Hollenbeck , ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XSLT 2.0 Message-ID: <20050909004609.GU20337@w3.org> References: <20050908180657.GO20337@w3.org> <20050908184853.GS20337@w3.org> <1164639983.20050908222926@w3.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1164639983.20050908222926@w3.org> X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.9i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thu, Sep 08, 2005 at 10:29:26PM +0200, Chris Lilley wrote: > On Thursday, September 8, 2005, 8:48:53 PM, 'Liam wrote: > > LQ> On Thu, Sep 08, 2005 at 02:12:43PM -0400, Scott Hollenbeck wrote: > >> Thanks, but my point is that you need to put this info in the template > >> itself. > LQ> OK, noted. > > LQ> Note that the information is also elsewhere in the published > LQ> specification -- it's at the beginning of the document -- since > LQ> this Internet Type information is being published as part > LQ> of a larger document. > > LQ> Liam > > Liam, > > this has come up before as W3C uses the new process. The requirement to > make the registration template an appendix in the spec means that people > tend to forget that the appendix also has the be read as an independent > document by the people here. > > The appendix has to make sense as a standalone registrations, so rather > than saying "this document" say "the document at (url) called (title)". Thanks (Chris and Scott and Paul) -- We will publish another round of draft documents very soon, but the set after that will reflect these and any other comments, and yes, will have the URI in it :-) Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ 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 j88KdxBf065855; Thu, 8 Sep 2005 13:39:59 -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 j88Kdx8A065854; Thu, 8 Sep 2005 13:39:59 -0700 (PDT) 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 j88Kdvow065841 for ; Thu, 8 Sep 2005 13:39:58 -0700 (PDT) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 08 Sep 2005 20:39:51 -0000 Received: from dsl-084-056-228-090.arcor-ip.net (EHLO hive) [84.56.228.90] by mail.gmx.net (mp014) with SMTP; 08 Sep 2005 22:39:51 +0200 X-Authenticated: #723575 From: Bjoern Hoehrmann To: "'Liam Quin'" Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XSLT 2.0 Date: Thu, 08 Sep 2005 22:40:19 +0200 Message-ID: References: <20050908180657.GO20337@w3.org> <20050908184853.GS20337@w3.org> In-Reply-To: <20050908184853.GS20337@w3.org> X-Mailer: Forte Agent 3.0/32.763 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: * 'Liam Quin' wrote: >Note that the information is also elsewhere in the published >specification -- it's at the beginning of the document -- since >this Internet Type information is being published as part >of a larger document. My understanding is that IANA will maintain a copy of the template, see e.g. . -- 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 j88KTaO1064776; Thu, 8 Sep 2005 13:29:36 -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 j88KTa5g064775; Thu, 8 Sep 2005 13:29:36 -0700 (PDT) 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 j88KTZbr064768 for ; Thu, 8 Sep 2005 13:29:35 -0700 (PDT) (envelope-from chris@w3.org) Received: from localhost (localhost [127.0.0.1]) by homer.w3.org (Postfix) with ESMTP id 108C74EEDF; Thu, 8 Sep 2005 16:29:32 -0400 (EDT) Date: Thu, 8 Sep 2005 22:29:26 +0200 From: Chris Lilley Reply-To: Chris Lilley X-Priority: 3 (Normal) Message-ID: <1164639983.20050908222926@w3.org> To: "'Liam Quin'" Cc: Scott Hollenbeck , ietf-types@iana.org, , Subject: Re: W3C Last Call and Media Type request for comments: XSLT 2.0 In-Reply-To: <20050908184853.GS20337@w3.org> References: <20050908180657.GO20337@w3.org> <20050908184853.GS20337@w3.org> 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, September 8, 2005, 8:48:53 PM, 'Liam wrote: LQ> On Thu, Sep 08, 2005 at 02:12:43PM -0400, Scott Hollenbeck wrote: >> Thanks, but my point is that you need to put this info in the template >> itself. LQ> OK, noted. LQ> Note that the information is also elsewhere in the published LQ> specification -- it's at the beginning of the document -- since LQ> this Internet Type information is being published as part LQ> of a larger document. LQ> Liam Liam, this has come up before as W3C uses the new process. The requirement to make the registration template an appendix in the spec means that people tend to forget that the appendix also has the be read as an independent document by the people here. The appendix has to make sense as a standalone registrations, so rather than saying "this document" say "the document at (url) called (title)". -- Chris Lilley mailto:chris@w3.org Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG 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 j88ImsWe054155; Thu, 8 Sep 2005 11:48:54 -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 j88Ims6G054154; Thu, 8 Sep 2005 11:48:54 -0700 (PDT) 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 j88Imrkc054144 for ; Thu, 8 Sep 2005 11:48:54 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id 7B6A44EEDF; Thu, 8 Sep 2005 14:48:53 -0400 (EDT) Date: Thu, 8 Sep 2005 14:48:53 -0400 From: "'Liam Quin'" To: Scott Hollenbeck Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XSLT 2.0 Message-ID: <20050908184853.GS20337@w3.org> References: <20050908180657.GO20337@w3.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.9i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thu, Sep 08, 2005 at 02:12:43PM -0400, Scott Hollenbeck wrote: > Thanks, but my point is that you need to put this info in the template > itself. OK, noted. Note that the information is also elsewhere in the published specification -- it's at the beginning of the document -- since this Internet Type information is being published as part of a larger document. Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ 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 j88ID1VZ049976; Thu, 8 Sep 2005 11:13:01 -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 j88ID14h049975; Thu, 8 Sep 2005 11:13:01 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from mail.verisignlabs.com (cliffie.verisignlabs.com [65.201.175.9]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j88ID07d049968 for ; Thu, 8 Sep 2005 11:13:01 -0700 (PDT) (envelope-from sah@428cobrajet.net) Received: from dul1shollenbl1 ([::ffff:216.168.239.87]) (AUTH: LOGIN shollenb, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Thu, 08 Sep 2005 14:13:00 -0400 id 00368564.43207F2C.00001518 From: "Scott Hollenbeck" To: "'Liam Quin'" Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: RE: W3C Last Call and Media Type request for comments: XSLT 2.0 Date: Thu, 8 Sep 2005 14:12:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050908180657.GO20337@w3.org> Thread-Index: AcW0oBy/yAWpo+iTT7W4OUup4Qw1OQAAKW6A X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > -----Original Message----- > From: 'Liam Quin' [mailto:liam@w3.org] > Sent: Thursday, September 08, 2005 2:07 PM > To: Scott Hollenbeck > Cc: ietf-types@iana.org; ietf-xml-mime@imc.org; > public-qt-comments@w3.org > Subject: Re: W3C Last Call and Media Type request for > comments: XSLT 2.0 > > On Thu, Sep 08, 2005 at 12:54:46PM -0400, Scott Hollenbeck wrote: > > The "Published specification" section of the template > should include a > > pointer (a URL is OK) to the published specification that > describes the > > media type. > > The specification is a draft, but my fault for omitting the link!! > > The text is at: http://www.w3.org/TR/2005/WD-xslt20-20050404/ > > The latest public version of the XSLT 2 specification > is always at http://www.w3.org/TR/xslt20/ > (the links get you the same result right now, of course) Thanks, but my point is that you need to put this info in the template itself. -Scott- 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 j88I6xQa049411; Thu, 8 Sep 2005 11:06:59 -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 j88I6xAr049410; Thu, 8 Sep 2005 11:06:59 -0700 (PDT) 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 j88I6wmX049403 for ; Thu, 8 Sep 2005 11:06:58 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id 0A2DA4EEDF; Thu, 8 Sep 2005 14:06:57 -0400 (EDT) Date: Thu, 8 Sep 2005 14:06:57 -0400 From: "'Liam Quin'" To: Scott Hollenbeck Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: Re: W3C Last Call and Media Type request for comments: XSLT 2.0 Message-ID: <20050908180657.GO20337@w3.org> References: <20050908164936.GN20337@w3.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.9i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: On Thu, Sep 08, 2005 at 12:54:46PM -0400, Scott Hollenbeck wrote: > The "Published specification" section of the template should include a > pointer (a URL is OK) to the published specification that describes the > media type. The specification is a draft, but my fault for omitting the link!! The text is at: http://www.w3.org/TR/2005/WD-xslt20-20050404/ The latest public version of the XSLT 2 specification is always at http://www.w3.org/TR/xslt20/ (the links get you the same result right now, of course) Liam -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/ 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 j88Gt4ja041008; Thu, 8 Sep 2005 09:55:04 -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 j88Gt4ef041007; Thu, 8 Sep 2005 09:55:04 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from mail.verisignlabs.com (cliffie.verisignlabs.com [65.201.175.9]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j88Gt3Yc040999 for ; Thu, 8 Sep 2005 09:55:03 -0700 (PDT) (envelope-from sah@428cobrajet.net) Received: from dul1shollenbl1 ([::ffff:216.168.239.87]) (AUTH: LOGIN shollenb, SSL: TLSv1/SSLv3,128bits,RC4-MD5) by mail.verisignlabs.com with esmtp; Thu, 08 Sep 2005 12:55:02 -0400 id 003682A1.43206CE6.00000288 From: "Scott Hollenbeck" To: "'Liam Quin'" , ietf-types@iana.org Cc: ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: RE: W3C Last Call and Media Type request for comments: XSLT 2.0 Date: Thu, 8 Sep 2005 12:54:46 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20050908164936.GN20337@w3.org> Thread-Index: AcW0lVigqnlQuQ1tSGOD0uN8+LBeKwAAFnmg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Liam, The "Published specification" section of the template should include a pointer (a URL is OK) to the published specification that describes the media type. -Scott- > -----Original Message----- > From: Liam Quin [mailto:liam@w3.org] > Sent: Thursday, September 08, 2005 12:50 PM > To: ietf-types@iana.org > Cc: ietf-xml-mime@imc.org; public-qt-comments@w3.org > Subject: W3C Last Call and Media Type request for comments: XSLT 2.0 > > [ > Notes: > > We slipped up in not sending this along with the Last Call > announcement; please caaept our apologies. > > We are using bugzilla to track comments on this document; > comments on the MIME-related part of the document may be made > on the ietf-types mailing list or in Bugzilla. See the > "Status of this Document" section for further information. > > We are following > > http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-05.txt > here, and the text is written to be part of a larger document. > > Finally, as for XQuery, we'll probably expand the Security > Considerations after gaining more implementation experience. > > ] > > > Registration of MIME Media Type application/xslt+xml > ---------------------------------------------------- > > MIME media type name: application > MIME subtype name: xslt+xml > Required parameters: None. > Optional parameters: charset > This parameter has identical semantics to the charset parameter > of the application/xml media type as specified in [RFC3023]. > > Encoding considerations: > By virtue of XSLT content being XML, it has the same > considerations > when sent as "application/xslt+xml" as does XML. See RFC 3023, > section 3.2. > > Security considerations: > Several XSLT instructions may cause arbitrary URIs to be > dereferenced. In this case, the security issues of [RFC3986], > section 7, should be considered. > > In addition, because of the extensibility features for XSLT, it is > possible that "application/xslt+xml" may describe content that has > security implications beyond those described here. However, if the > processor follows only the normative semantics of this > specification, > this content will be ignored. Only in the case where the processor > recognizes and processes the additional content, or where further > processing of that content is dispatched to other > processors, would > security issues potentially arise. And in that case, they > would fall > outside the domain of this registration document. > > Interoperability considerations: > > This specification describes processing semantics that dictate > behavior that must be followed when dealing with, among > other things, > unrecognized elements. > > Because XSLT is extensible, conformant "application/xslt+xml" > processors can expect that content received is well-formed XML, > but it cannot be guaranteed that the content is valid XSLT or that > the processor will recognize all of the elements and attributes in > the document. > > Published specification: > > This media type registration is for XSLT stylesheet modules as > described by this specification. It is also appropriate > to use this > media type with earlier and later versions of the XSLT language. > > Applications which use this media type: > > Existing XSLT 1.0 stylesheets are most often described using the > unregistered media type "text/xsl". > > There is no experimental, vendor specific, or personal tree > predecessor to "application/xslt+xml", reflecting the fact that > no applications currently recognize it. This new type is being > registered in order to allow for the expected deployment of XSLT > 2.0 on the World Wide Web, as a first class XML application. > > Additional information: > > Magic number(s): > > There is no single initial octet sequence that is > always present > in XSLT documents. > > File extension(s): > > XSLT documents are most often identified with the extensions > ".xsl" or ".xslt". > > Macintosh File Type Code(s): > > TEXT > > Person & email address to contact for further information: > > Norman Walsh, . > > Intended usage: > > COMMON > > Author/Change controller: > > The XSLT specification is a work product of the World Wide Web > Consortium's XSL Working Group. The W3C has change control over > these specifications. > > B.2 Fragment Identifiers > > For documents labeled as "application/xslt+xml", the > fragment identifier > notation is exactly that for "application/xml", as > specified in RFC 3023. > > -- > Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ > http://www.holoweb.net/~liam/ > 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 j88Gnc4q040459; Thu, 8 Sep 2005 09:49:39 -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 j88Gncoe040458; Thu, 8 Sep 2005 09:49:38 -0700 (PDT) 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 j88GncKH040445 for ; Thu, 8 Sep 2005 09:49:38 -0700 (PDT) (envelope-from liam@w3.org) Received: by homer.w3.org (Postfix, from userid 16040) id 6EC4A4EF7D; Thu, 8 Sep 2005 12:49:37 -0400 (EDT) Date: Thu, 8 Sep 2005 12:49:37 -0400 From: Liam Quin To: ietf-types@iana.org Cc: ietf-xml-mime@imc.org, public-qt-comments@w3.org Subject: W3C Last Call and Media Type request for comments: XSLT 2.0 Message-ID: <20050908164936.GN20337@w3.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Feet: bare, comfortable. happy and free! User-Agent: Mutt/1.5.9i Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: [ Notes: We slipped up in not sending this along with the Last Call announcement; please caaept our apologies. We are using bugzilla to track comments on this document; comments on the MIME-related part of the document may be made on the ietf-types mailing list or in Bugzilla. See the "Status of this Document" section for further information. We are following http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-05.txt here, and the text is written to be part of a larger document. Finally, as for XQuery, we'll probably expand the Security Considerations after gaining more implementation experience. ] Registration of MIME Media Type application/xslt+xml ---------------------------------------------------- MIME media type name: application MIME subtype name: xslt+xml Required parameters: None. Optional parameters: charset This parameter has identical semantics to the charset parameter of the application/xml media type as specified in [RFC3023]. Encoding considerations: By virtue of XSLT content being XML, it has the same considerations when sent as "application/xslt+xml" as does XML. See RFC 3023, section 3.2. Security considerations: Several XSLT instructions may cause arbitrary URIs to be dereferenced. In this case, the security issues of [RFC3986], section 7, should be considered. In addition, because of the extensibility features for XSLT, it is possible that "application/xslt+xml" may describe content that has security implications beyond those described here. However, if the processor follows only the normative semantics of this specification, this content will be ignored. Only in the case where the processor recognizes and processes the additional content, or where further processing of that content is dispatched to other processors, would security issues potentially arise. And in that case, they would fall outside the domain of this registration document. Interoperability considerations: This specification describes processing semantics that dictate behavior that must be followed when dealing with, among other things, unrecognized elements. Because XSLT is extensible, conformant "application/xslt+xml" processors can expect that content received is well-formed XML, but it cannot be guaranteed that the content is valid XSLT or that the processor will recognize all of the elements and attributes in the document. Published specification: This media type registration is for XSLT stylesheet modules as described by this specification. It is also appropriate to use this media type with earlier and later versions of the XSLT language. Applications which use this media type: Existing XSLT 1.0 stylesheets are most often described using the unregistered media type "text/xsl". There is no experimental, vendor specific, or personal tree predecessor to "application/xslt+xml", reflecting the fact that no applications currently recognize it. This new type is being registered in order to allow for the expected deployment of XSLT 2.0 on the World Wide Web, as a first class XML application. Additional information: Magic number(s): There is no single initial octet sequence that is always present in XSLT documents. File extension(s): XSLT documents are most often identified with the extensions ".xsl" or ".xslt". Macintosh File Type Code(s): TEXT Person & email address to contact for further information: Norman Walsh, . Intended usage: COMMON Author/Change controller: The XSLT specification is a work product of the World Wide Web Consortium's XSL Working Group. The W3C has change control over these specifications. B.2 Fragment Identifiers For documents labeled as "application/xslt+xml", the fragment identifier notation is exactly that for "application/xml", as specified in RFC 3023. -- Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/ http://www.holoweb.net/~liam/