W3C home > Mailing lists > Public > www-xml-query-comments@w3.org > March 2001

Re: XQuery as an interface for terminology/vocabulary servers

From: Jonathan Robie <Jonathan.Robie@SoftwareAG-USA.com>
Date: Wed, 28 Mar 2001 12:08:03 -0500
Message-Id: <>
To: Mike Hogarth <mike@hogarth.org>
Cc: www-xml-query-comments@w3.org, w3c-xml-query-wg@w3.org
Dear Mike,

This is a response to the following message, which you posted to the XML 
Query Working Group's comments list:


The XML Query Working Group has approved the following response:

  >  Would you consider changing the syntax slightly
  >  such that it allow for "source" rather than "document"?>
  >  This might allow it to be a more general-use
  >  language. I find it to be very close to what is
  >  necessary for vocabulary "servers", except the
  >  assumption that it is operating on a document
  >  --- rather than something more abstract such
  >  as a tree+nodes structure.
  >  Anyhow, here is an example of what could be done:
  >  <xquery-result-set>
  >  FOR $a IN distinct(source("diseases")//cardiac)
  >      <concept>
  >              <display-name>$a/text()</display-name>
  >      </concept>
  >  <xquery-result-set>

Clearly, XQuery needs to be able to allow queries across repositories of 
documents. XQuery actually operates on an instance of the XML Query Data 
Model, which is basically an ordered forest. In general, a query that is 
executed against a repository does not currently use the document() 
function to identify the collection.

Logically, we might choose either to (1) let the document() function be 
defined such that it works on a collection of documents as well as a single 
document, or (2) come up with a second function for this purpose
We appreciate your feedback on the XML Query specifications. Please let us 
know if this response is satisfactory. If not, please respond to this 
message, explaining your concerns.

Jonathan Robie
On behalf of the XML Query Working Group
Received on Wednesday, 28 March 2001 12:06:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:12 UTC