XQuery updates are still in the planning stage. Using a combination of DataDirect XQuery and JDBC offers a simple solution to working with both XML and relational data, and providing updates to relational data. See http://www.datadirect.com/developer/xquery/xquery_updates/index.ssp for more information.

DataDirect XQuery is the first embeddable component for XQuery that implements the XQuery API for Java (XQJ). It supports all major relational databases on any Java platform. DataDirect XQuery allows you to query XML, relational databases, or a combination of the two, integrating the results for XML-based data exchange, XML-driven Web sites, and other applications that require or leverage the power of XML.

Information about DataDirect XQuery can be found at http://www.datadirect.com/products/xquery/index.ssp. JDBC Drivers | ODBC Drivers | ADO.NET Data Providers | XQuery | XML Converters | XML IDE | Mainframe Integration

If you want to query and integrate both XML and relational data, DataDirect XQuery provides substantial benefits in performance over a free implementation such as Saxon: DataDirect XQuery provides support for all major databases on any platform. In contrast, Saxon only has minimal support for data stored in relational databases.

Configuring DataDirect XQuery for your environment is straightforward. Once installed, you configure a source configuration file to specify the connection information for XML and relational data sources that are used by XQuery queries. To make this configuration easy, DataDirect XQuery ships with an example source configuration file for each database that the product supports, so you can start with one of these example files and modify the values as needed.

DataDirect XQuery is ideal for any company that needs to access and integrate data stored in XML and relational sources. Unlike other XQuery products, DataDirect XQuery provides the following benefits: DataDirect XQuery provides good performance when querying relational databases because it allows the XQuery query to be executed as efficiently as possible (decomposing the query into SQL statements) and moving out of the database just the minimum amount of data.

DataDirect XQuery supports the W3C Candidate Recommendation 3 November 2005 of the XQuery specification located at: http://www.w3.org/TR/2005/WD-xquery-20050404.

Java applications use the XQuery for Java API (XQJ) to execute XQuery, which is analogous to using the JDBC API to execute SQL statements. The following sample Java code illustrates the basic steps that an application would perform to execute an XQuery expression using DataDirect XQuery. ... // import the XQJ classes import com.ddtek.xquery.*; import com.ddtek.xquery.xqj.mediator.DDXQDataSource; // establish a connection to a data source DDXQDataSource ds = new DDXQDataSource(); ds.

Yes. DataDirect XQuery does not require its own server infrastructure, which makes it easy to embed into other commercial applications.

XML text files/streams. These files/streams can be accessed using fn:doc( ), which supports the http:, ftp:, and file: URI schemes and Stylus Studio XML Deployment Adapter URI schemes. Here is an example of a Stylus Studio XML Deployment Adapter URI scheme in which the name of the Adapter is Base64, the properties set for the conversion are newline and encoding, and the file to convert is base_to_xml.

Yes. DataDirect XQuery™ 3.0 supports updates to relational database tables from inside an XQuery by providing three built-in functions. These functions are: ddtek:sql-insert, ddtek:sql-update, ddtek:sql-delete.

We've compiled a list of frequently asked questions concerning licensing and extending an evaluation license, pricing, packages, oXygen XML Editor, DataDirect JDBC, and developer versions of DataDirect XQuery™ 3.0. If you have a question that is not addressed here, please refer to the DataDirect XQuery™ 3.0 Customer Service page for more information.

Individual entities in the databases are surveyed on an annual basis. Databases are surveyed on a schedule throughout the year. Survey results from all the databases are being entered on an ongoing basis. New data is moved on-line weekly. As new information regarding a facility or individual is obtained between scheduled surveys, this information is updated and the information date specified with that entry's listing is updated accordingly.

A recent world-wide survey of software developers found that the top four reasons for using XQuery were that it simplifies data access and transformation, has a more concise and easier-to-read syntax, can aggregate and manipulate data from different sources, and for its flexibility in working with relational and non-relational data sources. Other reasons that came up frequently included greater performance, flexibility, and the need for standards based approach to XML data integration.

The current, standardized version of SPARQL deals only with retrieving selected data from RDF graphs. There is no equivalent of the SQL INSERT, UPDATE, or DELETE statements. Most RDF-based applications handle new, changing, and stale data directly via the APIs provided by specific RDF storage systems. Alternatively, RDF data can exist virtually (i.e. created on-demand in response to a SPARQL query).

DataDirect XQuery™ 3.0 is ideal for any company that needs to access and integrate data stored in XML and relational sources. Unlike other XQuery products, DataDirect XQuery™ 3.0 provides the following benefits: DataDirect XQuery™ 3.0 provides good performance when querying relational databases because it allows the XQuery query to be executed as efficiently as possible (decomposing the query into SQL statements) and moving out of the database just the minimum amount of data.

Java applications use the XQuery for Java API (XQJ) to execute XQuery, which is analogous to using the JDBC API to execute SQL statements. The following sample Java code illustrates the basic steps that an application would perform to execute an XQuery expression using DataDirect XQuery™ 3.0. ... // import the XQJ classes import com.ddtek.xquery.*; import com.ddtek.xquery.xqj.mediator.DDXQDataSource; // establish a connection to a data source DDXQDataSource ds = new DDXQDataSource(); ds.

Technically, yes. The Saxon.NET project at SourceForge is an ongoing effort to convert the existing Java-based code of the open-source Saxon processor to the .NET platform. However there many problems with this approach: Simply re-compiling Java files into .NET Assemblies is no substitute for an XQuery processor and API built from the ground up in C# and is a far cry from the level of engineering effort that went into optomizing and testing MSXML 4.0. Saxon is primarily an XSLT 1.0/2.

The benefits of Java are well-known. It lets you write applications that work on any operating system, and the J2EE platform provides robust support for XML, security, web services, and database connectivity. Embedding XQuery in Java applications can significantly reduce the amount of Java code that is needed, because XQuery often is easier to use and more efficient than Java for processing XML or querying relational data to create XML.

Web Services depend heavily on XML for both its definition language, Web Services Description Language (WSDL), and its messaging protocol, Simple Object Access Protocol (SOAP). XQuery provides a language that can interact with XML data and other types of data as long as they can be represented as XML. For example, XQuery can be used to access the content of messages or to construct new messages to be passed to a Web service. In addition, you often need data to process Web Services results.

We are continually updating the data in ChemFinder, but we generally try to 'save up' the changes to minimize downtime. On average, the public server gets updated in some fashion about once a week. Of course, not all data is changed during an update. Most often, additional sites are indexed during an update.

SPARQL is a query language developed for the RDF data model; queries themselves look and act like RDF. I.e., the queries are independent of the physical representation of the RDF data (the structure of the databases, their representation in an RDF/XML file, etc). If query was done via, for example, XQuery, the application would have to know how that particular RDF data exactly represented as RDF/XML (and RDF/XML is only one of the possible serialization of the RDF data).

The client and server software need Java 1.4.2 (or higher). The servlets require the Java Servlet library which is available from Java.com in the Java Enterprise Edition (J2EE), or via downloading a servlet engine such as Apache Tomcat.