Changes

Jump to navigation Jump to search
268 bytes removed ,  12:00, 5 March 2019
no edit summary
==Overview==
 XML documents often rely on Document Type Definitions (DTDs). While parsing a document with BaseX, entities can be resolved with respect to that particular DTD.By default, the DTD is only used for entity resolution.
XHTML, for example, defines its doctype via the following line:
 
<pre class="brush:xml">
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
</pre>
Fetching <code>xhtml1-strict.dtd</code> obviously involves network traffic. When dealing with single files, this may seem tolerable, but importing large collections benefits from caching these resources. Depending on the remote server, you will experience significant speed improvements when caching DTDs locally.
== XML Entity and URI Resolvers ==
 BaseX comes with a default URI relies on the Apache-maintained [http://xml.apache.org/commons XML Commons Resolver]. The {{Code|xml-resolver that -1.2.jar}} library is usable out included in the full distributions of BaseX. If the boxresolver is not found in the classpath, and if Java 8 is used, Java’s built-in resolver will be applied (via <code>com.sun.org.apache.xml.internal.resolver.*</code>).
To enable entity resolving you have to provide a valid XML Catalog file, so that the parser knows where to look for mirrored DTDs.
A simple working example for XHTML might look like this:
 
<pre class="brush:xml" start="0">
<?xml version="1.0"?>
<catalog prefer="system" xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
<rewriteSystem systemIdStartString="http://www.w3.org/TR/xhtml1/DTD/" rewritePrefix="file:///path/to/dtds/" />
</catalog>
</pre>
 
This rewrites all systemIds starting with: ''<nowiki>http://www.w3.org/TR/xhtml1/DTD/</nowiki>'' to ''file:///path/to/dtds/''.
===GUI Mode===
 
When running BaseX in GUI mode, simply provide the path to your XML Catalog file in the ''Parsing'' Tab of the Database Creation Dialog.
===Please Note===
 
Entity resolving only works if the [[Parsers#XML Parsers|internal XML parser]] is switched off (which is the default case).
If you use the internal parser, you can manually specify whether you want to parse DTDs and entities or not.
== Using other Resolvers More Information ==There might be some cases when you do not want to use the built-in resolver that Java provides by default(via <code>com.sun.org.apache.xml.internal.resolver.*</code>). BaseX offers support for the Apache-maintained [http://xml.apache.org/commons XML Commons Resolver], available for download [http://xerces.apache.org/mirrors.cgi here]. To use it add '''resolver.jar''' to the classpath when [[Startup|starting BaseX]]:<pre class="brush:bash">java -cp basex.jar:resolver.jar org.basex.BaseXServer</pre>
== More Information ==
*[http://en.wikipedia.org/wiki/Document_Type_Definition Wikipedia on Document Type Definitions]
*[http://xml.apache.org/commons/components/resolver/resolver-article.html Apache XML Commons Article on Entity Resolving]
*[http://java.sun.com/webservices/docs/1.6/jaxb/catalog.html XML Entity and URI Resolvers], Sun
*[http://www.oasis-open.org/committees/download.php/14810/xml-catalogs.pdf XML Catalogs. OASIS Standard, Version 1.1. 07-October-2005.]
Bureaucrats, editor, reviewer, Administrators
12,258

edits

Navigation menu