This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27335 - updateIETF MIME type registration appendix
Summary: updateIETF MIME type registration appendix
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.1 (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-15 17:24 UTC by Liam R E Quin
Modified: 2015-07-06 09:07 UTC (History)
2 users (show)

See Also:


Attachments

Description Liam R E Quin 2014-11-15 17:24:32 UTC
The MIME Type appendix in XQuery 3.1 needs updating:

http://www.w3.org/TR/xquery-31/#id-mime-type

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

should now read, e.g.:

[[
This media type registration is to allow for deployment of XQuery on the World Wide Web.
]]

The example encoding declaration
   xquery version "1.0" ...
should say, xquery version "3.1" ...

Delete, Currently the version number, if present, must be "1.0"

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

to be, e.g.
[[
The optional XQuery Update Feature allows XQuery expressions to create and update persistent data, potentially including writing to arbitrary locations on the local filesystem as well as to remote URIs. Untrusted queries should not be given write access to data.
]]

(these changes probably also apply to XQueryX)
Comment 1 Jim Melton 2014-12-03 20:18:19 UTC
I have applied the relevant aspects of this comment to XQueryX 3.1, along with change markup to distinguish all modified text in the MIME appendix of that document.
Comment 2 Jonathan Robie 2014-12-09 00:00:00 UTC
Fixed in current internal draft.
Comment 3 Michael Kay 2015-07-06 09:07:43 UTC
Confirmed fixed.