Yakov Shafranovich | 3 Apr 08:13 2005

Type 'text/csv', draft-04

I posted a new version (-04) correcting the ABNF grammar in response to 
IESG comments, adding a few clarifications and adding a new optional 
"header" parameter to indicate the absence or presence of a header line. 
Copies of the draft can be found below and the draft should post to the 
IETF ID repository sometime Monday:

http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime-csv-04.html
http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime-csv-04.txt

HTML and text diff of changes:

http://www.shaftek.org/publications/drafts/mime-csv/rfcdiff-03-to-04.html
http://www.shaftek.org/publications/drafts/mime-csv/diff-03-to-04.txt

Yakov

Yakov Shafranovich | 3 Apr 08:18 2005

Re: Media Type "text/csv": new draft (-02) and Last Call

I added this language to the -04 draft. Regarding the issue of the 
header, I added an optional "header" parameter to the MIME type that can 
be used to indicate the presence or absence of the header line.

Yakov

clyde.ingram <at> edl.uk.eds.com wrote:
> Yakov,
> 
> That draft wording sounds excellent.
> 
> Now, if you were to ALSO mandate the presence of the header record, that 
> would mitigate my concern that computer applications should be able to 
> exchange CSV files without worrying about same field order (simply 
> because the header conveys the field names, rather than needing an 
> out-of-band, bilateral agreement).  And, of course, presence of a header 
> record lets a computer application determine immediately whether the 
> supplied fields are likely to be what it expects.   All good aids for 
> careful validation.
> 
> Thank-you,
> Clyde
> 
> -----Original Message-----
> From: Yakov Shafranovich [mailto:research <at> solidmatrix.com]
> Sent: Wednesday, March 30, 2005 8:08 PM
> To: clyde.ingram <at> edl.uk.eds.com
> Cc: GK-lists <at> ninebynine.org; ietf-types <at> alvestrand.no
> Subject: Re: Media Type "text/csv": new draft (-02) and Last Call
> 
(Continue reading)

Max Froumentin | 4 Apr 14:02 2005
Picon

please review draft-froumentin-voice-mediatypes-00

draft-froumentin-voice-mediatypes-00 contains the registration of 
the 6 media types of the W3C Speech Interface Framework
(including the following specifications: SSML, SRGS, CCXML, PLS and VoiceXML)

Draft available at
http://www.ietf.org/internet-drafts/draft-froumentin-voice-mediatypes-00.txt
and copied below.

Max Froumentin, W3C

Network Working Group                                      M. Froumentin
Internet-Draft                                                       W3C
Expires: September 2, 2005                                    March 2005

            The W3C Speech Interface Framework Media Types:
  application/voicexml+xml,  application/ssml+xml,  application/srgs,
  application/srgs+xml, application/ccxml+xml and application/pls+xml
                  draft-froumentin-voice-mediatypes-00

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 3 of RFC 3667.  By submitting this Internet-Draft, each
   author represents that any applicable patent or other IPR claims of
   which he or she is aware have been or will be disclosed, and any of
   which he or she become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
(Continue reading)

Yakov Shafranovich | 5 Apr 05:14 2005

Re: Type 'text/csv', draft-04

One missed problem, we are upto -05:

http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime-csv-05.html 

http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime-csv-05.txt 

HTML and text diff of changes:

http://www.shaftek.org/publications/drafts/mime-csv/rfcdiff-04-to-05.html
http://www.shaftek.org/publications/drafts/mime-csv/diff-04-to-05.txt

Yakov

Yakov Shafranovich wrote:
> I posted a new version (-04) correcting the ABNF grammar in response to 
> IESG comments, adding a few clarifications and adding a new optional 
> "header" parameter to indicate the absence or presence of a header line. 
> Copies of the draft can be found below and the draft should post to the 
> IETF ID repository sometime Monday:
> 
> http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime-csv-04.html 
> 
> http://www.shaftek.org/publications/drafts/mime-csv/draft-shafranovich-mime-csv-04.txt 
> 
> 
> HTML and text diff of changes:
> 
> http://www.shaftek.org/publications/drafts/mime-csv/rfcdiff-03-to-04.html
> http://www.shaftek.org/publications/drafts/mime-csv/diff-03-to-04.txt
> 
(Continue reading)

Gerald McCobb | 5 Apr 15:03 2005
Picon

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


In response to your previous comments (thanks) I submitted draft-mccobb-xplusv-media-type-02.txt to internet-drafts <at> ietf.org.  Please review and thanks in advance:


Network Working Group                                          G. McCobb
Internet-Draft                                           IBM Corporation
Expires: Oct. 1, 2005                                      April 1, 2005


                XHTML+Voice - application/xhtml+voice+xml
                    draft-mccobb-xplusv-media-type-02


Status of this Memo

   By submitting this Internet-Draft, I certify that any applicable
   patent or other IPR claims of which I am aware have been disclosed,
   and any of which I become aware will be disclosed, in accordance
   with RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six
   months and may be updated, replaced, or obsoleted by other documents
   at any time.  It is inappropriate to use Internet-Drafts as
   reference material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved

Abstract

   This document describes the registration of the MIME sub-type
   application/xhtml+voice+xml.  This sub-type is intended for use as a
   media descriptor for XHTML+Voice multimodal language documents.  The
   XHTML+Voice 1.2 language specification is maintained by the VoiceXML
   Forum at <http://www.voicexml.org/specs/multimodal/x+v/12/>.

1.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in BCP 14, RFC 2119
   [RFC2119].



McCobb                   Expires Oct. 1, 2005                   [Page 1]

Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005


2. Introduction

   XHTML+Voice is a member of the XHTML family of document types, as
   specified by XHTML Modularization [XHTMLMOD].  XHTML+Voice extends
   XHTML 1.1 [XHTML11] with a modularized subset of VoiceXML 2.0
   [VXML20], XML Events [XMLEVNTS], and a few extensions to both XHTML
   and VoiceXML 2.0.  XHTML 1.1, VoiceXML 2.0 and XML Events are W3C
   Recommendations.

   The language integration defined by XHTML+Voice supports all modules
   defined by XHTML Modularization, and adds voice interaction to XHTML
   elements to enable multimodal applications.  The defined document
   type for XHTML+Voice is XHTML Host language document type conformant.

   XHTML+Voice 1.2 [XPLUSV12] is maintained by the VoiceXML Forum, at
   URI location <http://www.voicexml.org/specs/multimodal/x+v/12/>.

2.1 application/xhtml+voice+xml Usage

   The application/xhtml+voice+xml media type is intended to be a media
   descriptor for XHTML+Voice multimodal documents. Multimodal browsers
   have special processing requirements for XHTML+Voice documents, such
   as running a voice browser component, and support for the DOM Level
   2 Event Model [DOM2EV] and XML Events [XMLEVNTS].

   This media type registration is not intended for email usage.

3. IANA Registration

      To: ietf-types <at> iana.org
      Subject: Registration of Standard MIME media type
               application/xhtml+voice+xml

      MIME media type name: application

      MIME subtype name: xhtml+voice+xml

      Required parameters: none

      Optional parameters:

        charset:  has the same semantics as the charset parameter of the
                  "application/xml" media type specified in [RFC3023].

      Encoding considerations: 7bit.  See section 4 of [RFC3236].

      Security considerations:
 
   XHTML+Voice is an extension of XHTML and has the same security issues


McCobb                   Expires Oct. 1, 2005                   [Page 2]

Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005

   as XHTML.  These include interpreting anchors and forms in XHTML
   documents, and scripting languages and other dynamic interactive
   capabilities.  See section 7 of [RFC3236].

   In addition, the scripting language can be accessed by both the XHTML
   and the VoiceXML 2.0 markup embedded in the XHTML+Voice document.
   See section 1.3.1.5 of [XPLUSV12].

      Interoperability considerations :

   Because XHTML+Voice is built upon W3C standard recommendations, it is
   designed to be interoperable across a wide range of platforms and
   client devices.  Because the extensions to XHTML are identified by
   their namespaces, all browsers that have namespace support can run an
   XHTML+Voice document as an XHTML document without voice interaction.
     
     Published specification:

         The latest published version of XHTML+Voice is [XPLUSV12].

      Applications which use this media type:

         XHTML+Voice documents are intended to be deployed on the World
         Wide Web and rendered by multimodal browsers that support the
         visual and voice modes of interaction.  Because XHTML+Voice is
         an application of XML, authors can expect XHTML+Voice user
         agents to be conformant XML 1.0 [XML] processors.  See section
         2 of [RFC3236].

      Additional information:

         Magic number(s):  There is no single string that is always
             present.
         File extension(s): mxml, xhvml, xvml, xvm
         Macintosh File Type Code(s): TEXT

      Person & email address to contact for further information:

         Gerald M. McCobb
         mccobb <at> us.ibm.com

      Intended usage: COMMON

      Author/Change controller: Gerald McCobb

      Further information:

4. Fragment Identifiers

   See section 3 of [RFC3236].  Following [RFC3236], fragment


McCobb                   Expires Oct. 1, 2005                   [Page 3]

Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005

   identifiers for XHTML+Voice documents designate the element with the
   corresponding ID attribute value (see [XML] section 3.3.1).

   While XHTML+Voice adds new ID attributes with fragment identifier
   namespaces that are not in the same namespace as XHTML, the fragment
   identifiers are processed in the same namespace as the ID attribute's
   namespace.

5. Recognizing XHTML+Voice files

   Because XHTML+Voice is XML, an XHTML+Voice document [optionally]
   starts with an XML declaration which begins with "<?xml" and has a
   DOCTYPE declaration "<!DOCTYPE html".  XHTML+Voice 1.2 has the
   following DOCTYPE declaration:
 
   <!DOCTYPE html PUBLIC "-//VoiceXML Forum//DTD XHTML+Voice 1.2//EN"
"http://www.voicexml.org/specs/multimodal/x+v/12/dtd/xhtml+voice12.dtd">
   
   Because XHTML+Voice is in the XHTML family of languages, the root
   element of an XHTML+Voice document is 'html' and '<html' can be found
   near the top of the document.  

6. Security Considerations

   Security considerations for this media type are discussed in the MIME
   type registration that appears in section 3.

7. Normative References

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2396]  Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
              Resource Identifiers (URI): Generic Syntax", RFC 2396,
              August 1998.

   [RFC3023]  Murata, M., St. Laurent, S., and D. Kohn, "XML Media
              Types", RFC 3023, January 2001.

   [RFC3236]  Baker, M., Stark, P., "The 'application/xhtml+xml' Media
              Type", RFC 3236, January 2002.

   [XML]      "Extensible Markup Language (XML) 1.0", W3C
              Recommendation.  Available at <http://www.w3.org/TR/REC-
              xml> (or <http://www.w3.org/TR/2000/REC-xml-20001006>).

   [XHTMLMOD] "Modularization of XHTML," 10 April, 2001, Murray Altheim,
              Frank Boumphrey, Sam Dooley, et al, W3C Recommendation,
              http://www.w3.org/TR/xhtml-modularization/



McCobb                   Expires Oct. 1, 2005                   [Page 4]

Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005


   [XHTML11]  "XHTML 1.1 - Module-based XHTML," 31 May 2001, Murray
              Altheim, Shane McCarron, W3C Recommendation,
              http://www.w3.org/TR/xhtml11/.

   [DOM2EV]   "Document Object Model Level 2 Events Specification,"
              Tom Pixley, 2000.  W3C Recommendation,
              http://www.w3.org/TR/DOM-Level-2-Events/.

   [XMLEVNTS] "XML Events - An events syntax for XML", Steven
              Pemberton, T. V. Raman, and Shane McCarron, 2002.  W3C
              Recommendation, http://www.w3.org/TR/xml-events/.
   [XPLUSV12] "XHTML+Voice Profile 1.2," 16 March 2004, J. Axelsson,
              et al, http://www.voicexml.org/specs/multimodal/x+v/12/

   [VXML20]   "Voice Extensible Markup Language (VoiceXML)," 16 March
              2004, Scott McGlashan et al, W3C Recommendation,
              http://www.w3.org/TR/voicexml20/.

8. Authors' Address

   Gerald M. McCobb
   IBM Corporation
   8051 Congress Avenue, Office 2019
   Boca Raton, Florida 33487
   USA

   Phone: +1-561-862-2109
   Fax:   +1-561-862-3922
   EMail: mccobb <at> us.ibm.com


9. Full Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.

   This document and the information contained herein are provided on
   an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
   REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
   INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
   IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
   THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

   Intellectual Property

   The IETF takes no position regarding the validity or scope of any



McCobb                   Expires Oct. 1, 2005                   [Page 5]

Internet-Draft   XHTML+Voice - application/xhtml+voice+xml April 1, 2005



   Intellectual Property Rights or other rights that might be claimed
   to pertain to the implementation or use of the technology described
   in this document or the extent to which any license under such
   rights might or might not be available; nor does it represent that
   it has made any independent effort to identify any such rights.  
   Information on the procedures with respect to rights in RFC
   documents can be found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use
   of such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository
   at http://www.ietf.org/ipr.  

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at ietf-
   ipr <at> ietf.org.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.

























Mccobb                   Expires May 15, 2005                   [Page 6]

Regards,
Gerald McCobb
IBM
8051 Congress Avenue
Boca Raton, FL 33487
Tel. # 561-862-2109 T/L 975-2109



Bjoern Hoehrmann <derhoermi <at> gmx.net>

03/26/2005 06:06 PM

       
        To:        Gerald McCobb/Boca Raton/IBM <at> IBMUS
        cc:        ietf-types <at> iana.org, ietf-xml-mime <at> imc.org
        Subject:        Re: Request for comments regarding draft-mccobb-xplusv-media-type-01



* 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 <at> 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/

Allison Mankin | 6 Apr 14:48 2005

Transport Area requests Media Type review for audio/BV16 and audio/BV32


The Transport Area requests a Media Type review for the proposed
new types audio/BV16 and audio/BV32, intended for the IETF tree,
for Proposed Standard, specified in 
http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-04.txt.

We know of the following needed change:

The reference RFC for maxptime is RFC 3267, not 2327.

Please provide any comments before 21 April 2005.

Thanks,

Allison

Mark Nottingham | 7 Apr 05:41 2005
X-Face
Picon

For review: application/atom+xml

One of the deliverables of the ATOMPUB WG is an xml-based format for 
Web syndication. Please review the proposed "application/atom+xml" 
media type therein; the registration template can be found below, and 
the complete draft is:
   http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-07.txt

Regards,

---8<----
    An Atom Document, when serialized as XML 1.0, can be identified with
    the following media type:

    MIME media type name: application
    MIME subtype name: atom+xml
    Mandatory 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: Identical to those of "application/xml" as
       described in [RFC3023], section 3.2.
    Security considerations: As defined in this specification.
       [[anchor59: update upon publication]]
       In addition, as this media type uses the "+xml" convention, it
       shares the same security considerations as described in [RFC3023],
       section 10.
    Interoperability considerations: There are no known interoperability
       issues.
    Published specification: This specification.  [[anchor60: update upon
       publication]]
    Applications that use this media type: No known applications
       currently use this media type.

    Additional information:

    Magic number(s): As specified for "application/xml" in [RFC3023],
       section 3.2.
    File extension: .atom
    Fragment identifiers: As specified for "application/xml" in
       [RFC3023], section 5.
    Base URI: As specified in [RFC3023], section 6.
    Macintosh File Type code: TEXT
    Person and email address to contact for further information: Mark
       Nottingham <mnot <at> pobox.com>
    Intended usage: COMMON
    Author/Change controller: This specification's author(s).
       [[anchor61: update upon publication]]
--->8---

--
Mark Nottingham     http://www.mnot.net/

Scott Hollenbeck | 7 Apr 13:45 2005
Picon

RE: For review: application/atom+xml

Mark,

One thing I didn't catch earlier (sorry): the change controller for types in
the standards tree MUST be the IESG.  It would be more appropriate to say
it's the IETF community as described in RFC 2048 and the documents that will
soon obsolete 2048, but the IESG is the standards process gatekeeper so
that's what we've been using.  We've also accepted text where people have
said something like "The <foo> working group as designated by the IESG".

-Scott-

> -----Original Message-----
> From: Mark Nottingham [mailto:mnot <at> mnot.net] 
> Sent: Wednesday, April 06, 2005 11:41 PM
> To: ietf-types <at> alvestrand.no
> Subject: For review: application/atom+xml
> 
> 
> One of the deliverables of the ATOMPUB WG is an xml-based format for 
> Web syndication. Please review the proposed "application/atom+xml" 
> media type therein; the registration template can be found below, and 
> the complete draft is:
>    
> http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-07.txt
> 
> Regards,
> 
> ---8<----
>     An Atom Document, when serialized as XML 1.0, can be 
> identified with
>     the following media type:
> 
>     MIME media type name: application
>     MIME subtype name: atom+xml
>     Mandatory 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: Identical to those of 
> "application/xml" as
>        described in [RFC3023], section 3.2.
>     Security considerations: As defined in this specification.
>        [[anchor59: update upon publication]]
>        In addition, as this media type uses the "+xml" convention, it
>        shares the same security considerations as described 
> in [RFC3023],
>        section 10.
>     Interoperability considerations: There are no known 
> interoperability
>        issues.
>     Published specification: This specification.  [[anchor60: 
> update upon
>        publication]]
>     Applications that use this media type: No known applications
>        currently use this media type.
> 
>     Additional information:
> 
>     Magic number(s): As specified for "application/xml" in [RFC3023],
>        section 3.2.
>     File extension: .atom
>     Fragment identifiers: As specified for "application/xml" in
>        [RFC3023], section 5.
>     Base URI: As specified in [RFC3023], section 6.
>     Macintosh File Type code: TEXT
>     Person and email address to contact for further information: Mark
>        Nottingham <mnot <at> pobox.com>
>     Intended usage: COMMON
>     Author/Change controller: This specification's author(s).
>        [[anchor61: update upon publication]]
> --->8---
> 
> 
> --
> Mark Nottingham     http://www.mnot.net/
> 
> 

Mark Baker | 7 Apr 21:21 2005
Picon

Re: For review: application/atom+xml

Mark,

I think you might want to mention somewhere - probably under Interop
considerations - that application/atom+xml is already in use today with
"Atom 0.3", which is incompatible (AIUI) with the new atompub syntax
draft.

Cheers,

Mark.

On Wed, Apr 06, 2005 at 08:41:08PM -0700, Mark Nottingham wrote:
>    Interoperability considerations: There are no known interoperability
>       issues.
[snip]

--

-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

Liam Quin | 7 Apr 22:01 2005
Picon

W3C Last Call and Media Type request for comments: XQuery and XQueryX

[
 Notes:
 (1) - I'm trying to follow a new procedure here.  Becasue not
 everything is in place, the documents I refer to probably don't
 have perfect wording.  The documentation on the process was released
 after the documents were frozen for Last Call, but we can make
 any needed changes for the next round of publication.  I see
 that we failed to define the correct syntax for parameters, and would
 welcome comments on any other areas wheer we need to improve.

 (2) The following text will be inserted in the next published versions
 of the documents:
    This registration is for community review and will be (or has
    been) submitted to the IESG for review, approval, and
    registration with IANA.

 (3) We are using Bugzilla to track comments on these documents;
 comments on these MIME-related pats of the documents may be made
 on the ietf-types mailing list or in Bugzilla.  See the individual
 documents and their respective "Status of this Document" sections for
 further information.

 - Liam
]

In accordance with the draft Media Type Specifications and
Registration Procedures [1], and on behalf of the W3C XML Query
Working Group [2], I hereby give notice that W3C has published
two specifications at the stage "Last Call Working Draft" which
each incorporate definitions of a standards-tree MIME media type,
as allowed for in section 3.1 of [1], and request comments on
these definitions.

The types and subtypes are
    application/xquery
	defined in "XQuery 1.0: An XML Query Language" [3]
	optional parameter: charset
    application/xquery+xml
	defined in "XML Syntax for XQuery 1.0 (XQueryX)" [4]
	optional parameter: charset

**** Registration for application/xquery also at [3]

I The application/xquery Media Type (Non-Normative)
---------------------------------------------------

This Appendix specifies the media type for XQuery Version 1.0. XQuery is
a language for querying over collections of data from XML data sources,
as specified in the main body of this document.

I.1 Introduction
----------------

This document, together with its normative references, defines the
language XQuery Version 1.0. This Appendix provides information about
the application/xquery media type, which is intended to be used for
transmitting queries written in the XQuery language.

This document was prepared by members of the W3C XML Query Working
Group. Please send comments to public-qt-comments [at] w3.org, a public
mailing list with archives at
http://lists.w3.org/Archives/Public/public-qt-comments.

I.2 Registration of MIME Media Type application/xquery
------------------------------------------------------

MIME media type name: application

MIME subtype name: xquery

Required parameters: none

Optional parameters: charset

The syntax of XQuery is expressed in Unicode but may be written with any
Unicode-compatible character encoding, including UTF-8 or UTF-16, or
transported as US-ASCII or Latin-1 with Unicode characters outside the
range of the given encoding represented using an XML-style &#xddd;
syntax.

I.2.1 Interoperability Considerations

None known.

I.2.2 Applications Using this Media Type

The public XQuery Web page lists more than two dozen implementations of
the XQuery language, both proprietary and open source.

This new media type is being registered to allow for deployment of
XQuery on the World Wide Web.

I.2.3 File Extensions

The most common file extensions in use for XQuery are .xq and .xquery.

The appropriate Macintosh file type code is TEXT.

I.2.4 Intended Usage

The intended usage of this media type is for interchange of XQuery
expressions.

I.2.5 Author/Change Controller

XQuery was produced by, and is maintained by, the World Wide Web
Consortium's XML Query Working Group. The W3C has change control over
this specification.

I.3 Encoding Considerations

For use with transports that are not 8-bit clean, quoted-printable
encoding is recommended since the XQuery syntax itself uses the
US-ASCII-compatible subset of Unicode.

An XQuery document may contain an encoding declaration as part of its
version declaration:
    xquery version "1.0" encoding "utf-8";

If an XQuery document contains an encoding declaration, it overrides the
default encoding specified by the MIME charset parameter.

I.4 Recognizing XQuery Files

An XQuery file may have the string xquery version "V.V" near the
beginning of the document, where "V.V" is a version number. Currently
the version number, if present, must be "1.0".

I.5 Charset Default Rules

XQuery documents use the Unicode character set and, by default, the
UTF-8 encoding.

I.6 Security Considerations

Queries written in XQuery may cause arbitrary URIs to be dereferenced.
Therefore, the security issues of [Uniform Resource Locators (URL)]
Section 6 should be considered. In addition, the contents of file: URIs
can in some cases be accessed, processed and returned as results.

Furthermore, because the XQuery language permits extensions, it is
possible that application/xquery may describe content that has security
implications beyond those described here.

The XML Query Working group is working on a facility to allow XQuery
expressions to be used to create and update persistent data. Untrusted
queries should not be given write access to data.

**** Registration for application/xquery+xml also at [4]

C The application/xquery+xml Media Type (Non-Normative)
-------------------------------------------------------

This Appendix specifies the media type for XQueryX Version 1.0. XQueryX
is the XML syntax of a language, XQuery, for querying over data from XML
data sources, as specified in [XQuery 1.0: An XML Query Language].

C.1 Introduction
----------------

This document, together with its normative references, defines the XML
syntax for the XML Query language XQuery Version 1.0. This Appendix
specifies the application/xquery+xml media type, which is intended to be
used for transmitting queries expressed in the XQueryX syntax.

This document was prepared by members of the W3C XML Query Working
Group. Please send comments to public-qt-comments [at] w3.org, a public
mailing list with archives at
http://lists.w3.org/Archives/Public/public-qt-comments.
C.2 Registration of MIME Media Type application/xquery+xml

MIME media type name: application

MIME subtype name: xquery+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].

C.2.1 Encoding Considerations

The considerations as specified in RFC 3023 [XMLMIME] also hold for
'application/xquery+xml'.

C.2.2 Fragment Identifiers

For documents labeled as 'application/xquery+xml', fragment identifiers
are handled as specified in RFC 3023 [XMLMIME].

C.2.3 Restrictions on usage

The intended usage of this media type is for interchange of XQueryX
expressions.

C.2.4 Security Considerations

Queries written in XQueryX may cause arbitrary URIs to be dereferenced.
Therefore, the security issues of [Uniform Resource Locators (URL)]
Section 6 should be considered. In addition, the contents of file: URIs
can in some cases be accessed, processed and returned as results.

Furthermore, because the XQuery language (and thus the XQueryX language)
permits extensions, it is possible that application/xquery+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 arise.

The XML Query Working group is working on a facility to allow XQuery
(and thus XQueryX) expressions to be used to create and update
persistent data. Untrusted queries should not be given write access to
data.

C.2.5 Interoperability Considerations

See Section 5 ConformanceXQ.

C.2.6 Applications That Use This Media Type

The public XQuery Web page lists more than two dozen implementations of
the XQuery language, both proprietary and open source. Some of these are
known to support XQueryX.

This new media type is being registered to allow for deployment of
XQueryX on the World Wide Web.

There is no experimental, vendor specific, or personal tree predecessor
to "application/xquery+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 XQueryX 1.0 on the World Wide Web,
as a first class XML application.

C.2.7 Additional Information

C.2.7.1 Recognizing XQuery Files ("Magic Numbers")

Although no byte sequences can be counted on to consistently identify
XQueryX, XQueryX documents will have the sequence
"http://www.w3.org/yyyy/mm/XQueryX" to identify the XQueryX namespace
(where "yyyy" is exactly four decimal digits and "mm" is exactly two
decimal digits). This sequence will normally be found in a namespace
attribute of the first element in the document.

C.2.7.2 File Extensions

The most common file extension in use for XQueryX is .xqx.

C.2.7.3 Macintosh File Type Code(s)

The appropriate Macintosh file type code is TEXT.

C.2.8 Person and Email Address to Contact For Further Information

Jim Melton, Oracle Corp., jim.melton [at] oracle.com

C.2.9 Intended Usage

COMMON

C.2.10 Author/Change Controller

XQuery was produced by, and is maintained by, the World Wide Web
Consortium's XML Query Working Group. The W3C has change control over
this specification.

[1] http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-02.txt
[2] http://www.w3.org/XML/Query
[3] http://www.w3.org/TR/2005/WD-xquery-20050404/#id-mime-type
[4] http://www.w3.org/TR/2005/WD-xqueryx-20050404/#xqueryx-id-mime-type

--

-- 
Liam Quin, W3C XML Activity Lead, http://www.w3.org/People/Quin/
http://www.holoweb.net/~liam/


Gmane