[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

PLEASE do not cross-post xml-dev to XQuery comments list

• To: 'XML Developers List' <xml-dev@l...>
• Subject: PLEASE do not cross-post xml-dev to XQuery comments list
• From: Jonathan Robie <jonathan.robie@d...>
• Date: Thu, 16 Dec 2004 11:10:12 -0500
• In-reply-to: <41C1AECE.20402@m...>
• References: <E1Cevry-0007LI-00@u...> <41C1AECE.20402@m...>
• User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

PLEASE do not cross-post xml-dev to XQuery comments list. The latter 
operates at a much lower traffic level and a much higher signal-to-noise 
ratio than is customeray for xml-dev.

This comment is certainly appropriate - but not as a cross-post!

Jonathan

--- Begin Message ---

• To: Michael Kay <mike@s...>
• Subject: [XQuery] Re: draft-rsalz-qname-urn
• From: Elliotte Harold <elharo@m...>
• Date: Thu, 16 Dec 2004 10:50:38 -0500
• Cc: "'Rich Salz'" <rsalz@d...>, xml-dev@l..., public-qt-comments@w...
• Delivered-to: mailing list xml-dev@l...
• In-reply-to: <E1Cevry-0007LI-00@u...>
• List-help: <mailto:xml-dev-help@l...>
• List-post: <mailto:xml-dev@l...>
• List-subscribe: <mailto:xml-dev-subscribe@l...>
• List-unsubscribe: <mailto:xml-dev-unsubscribe@l...>
• Mailing-list: contact xml-dev-help@l...; run by ezmlm
• References: <E1Cevry-0007LI-00@u...>
• User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20040910

Michael Kay wrote:

> The XQuery specification, incidentally, defines a mapping of error QNames to
> error URIs. It's different from this one, of course.

The error URIs in the XQuery spec look like this:

http://www.w3.org/2004/10/xqt-errors#XPST0017

Something similar has been tried before in XML digital signatures and 
RDF. For reasons elucidated in the draft proposal, this format is not 
suitable for all QNames and does not work as a generic mechanism for 
encoding Qnames as URIs.

The XQuery format also seem to suffer from the disease that everything 
must be an http URI even when, as in this case, the URI is not actually 
resolvable. (http://www.w3.org/2004/10/xqt-errors is a real page but the 
fragment ID doesn't point to anything.)

I agree with most of your concerns about the details of the proposed 
qname URN scheme (IRIs vs. URIs, percent encoding, etc.) but at a 
fundamental level I think the proposed scheme is better than what XQuery 
is proposing. I would suggest that XQuery adopt the new qname URN scheme 
rather than using http URIs to identify error codes. In fact, I'll cc 
this to the XQuery working group to register it as a formal comment.

-- 
Elliotte Rusty Harold  elharo@m...
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://www.oasis-open.org/mlmanage/index.php>

--- End Message ---

• References:
  • RE: draft-rsalz-qname-urn
    • From: "Michael Kay" <mike@s...>
  • [XQuery] Re: draft-rsalz-qname-urn
    • From: Elliotte Harold <elharo@m...>

• Prev by Date: RE: A Systematic Approach to using Simple XML Vocabularies to Implement Large (Complex) Systems
• Next by Date: RE: A Systematic Approach to using Simple XML Vocabularies to Implement Large (Complex) Systems
• Previous by thread: [XQuery] Re: draft-rsalz-qname-urn
• Next by thread: Re: [XQuery] Re: draft-rsalz-qname-urn
• Index(es):
  • Date
  • Thread