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

Liam Quin <liam@w3.org> Thu, 07 April 2005 21:14 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 j37LE0IT017376; Thu, 7 Apr 2005 14:14:00 -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 j37LE0bV017375; Thu, 7 Apr 2005 14:14:00 -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 j37LDxlf017368 for <ietf-xml-mime@imc.org>; Thu, 7 Apr 2005 14:13:59 -0700 (PDT) (envelope-from liam@w3.org)
Received: by homer.w3.org (Postfix, from userid 16040) id 640E14F363; Thu, 7 Apr 2005 17:13:58 -0400 (EDT)
Date: Thu, 07 Apr 2005 17:13:58 -0400
From: Liam Quin <liam@w3.org>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
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: XQuery and XQueryX
Message-ID: <20050407211358.GA1005@w3.org>
References: <20050407200151.GN1785@w3.org> <425b93d4.13001640@smtp.bjoern.hoehrmann.de> <20050407204611.GS1785@w3.org> <425e9d44.15417140@smtp.bjoern.hoehrmann.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <425e9d44.15417140@smtp.bjoern.hoehrmann.de>
X-Feet: bare, comfortable. happy and free!
User-Agent: Mutt/1.5.6+20040907i
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, Apr 07, 2005 at 11:06:49PM +0200, Bjoern Hoehrmann wrote:
> * Liam Quin wrote:
> >It lets people put XQuery documents on public Web servers that may
> >not be configured correctly.  But it's not clear that this is the
> >right approach.
> 
> What kind of misconfiguration did you have in mind here? Configured to
> use an incorrect charset parameter? That's then easily addressed by not
> having a charset parameter.

That might in fact be the best approach for us.  I'll take it up
internally, thanks!

> >We expect to add to it later.  Right now the specifications are new
> >enough (in terms of Process) that security implications have not
> >all been explored.  I'd welcome help in this area.  What sort of
> >additional text did you expect in this section?
> 
> http://www.ietf.org/internet-drafts/draft-freed-media-type-reg-03.txt
> section 6 covers this
Note that date on that document is April 1st -- we'll be able to take 
it into account for the next publication, which I hope will be for
Candidate Recommendation.

On whether it should be normative within XQuery, I'll take it
up internally.

> it seems inconsistent with other W3C Technical Reports.
This process of registering MIME types is new, so we're
treading new ground here.

Thanks again for your help.

Liam

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