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

Liam Quin <liam@w3.org> Thu, 19 May 2005 14:39 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 j4JEd4wt086399; Thu, 19 May 2005 07:39: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 j4JEd42r086398; Thu, 19 May 2005 07:39:04 -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 j4JEd2v0086387 for <ietf-xml-mime@imc.org>; Thu, 19 May 2005 07:39:02 -0700 (PDT) (envelope-from liam@w3.org)
Received: by homer.w3.org (Postfix, from userid 16040) id 680AC4F5EB; Thu, 19 May 2005 10:38:59 -0400 (EDT)
Date: Thu, 19 May 2005 10:38:59 -0400
From: Liam Quin <liam@w3.org>
To: MURATA Makoto <murata@hokkaido.email.ne.jp>
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, 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: XQuery and XQueryX
Message-ID: <20050519143859.GA27635@w3.org>
References: <425e9d44.15417140@smtp.bjoern.hoehrmann.de> <20050517180227.GA10669@w3.org> <20050519101540.67F4.MURATA@hokkaido.email.ne.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <20050519101540.67F4.MURATA@hokkaido.email.ne.jp>
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: <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>

On Thu, May 19, 2005 at 10:18:18AM +0900, MURATA Makoto wrote:
>  
> > (1) to remove the optional encoding parameter, as you suggested
> 
> I think that this is a wrong decision.  Please reintroduce the charset
> parameter.  If present, it overrides the encoding declaration or BOM. If
> it is absent, the encoding declaration or BOM is used.

Please note that this is for application/xquery -- a non-XML format.
For application/xqueryx+xml I'll send separate mail.

One reason for dropping the encoding parameter (after discussions
with Mark Baker and others) is that in practice it's unlikely to be
used... e.g. from a Web browser passing off to a local query processor
or from a saved file).  Since the format is "application", proxies
cannot transcode the file, so the encoding declaration in the file
is authoritative.

Interchange of a database query language over the Web in its own
Internet Type is likely for machine execution or to interchange
files, not for reading by humans, as then text/plain might be
more appropriate... but this is conjecture on my part right now.

Do you have an environment in which the encoding parameter is
useful or important?   We don't have a significant use case for
it, and our understanding was that the W3C TAG had considered
the encoding parameter to be a bad idea too.

Thanks!

Liam

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