<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><figure class="quote"><figcaption><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite>The Complexity of XPath Query Evaluation</cite>
(<time>2011-07-09 16:57:20 +09:00</time>)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="https://infoscience.epfl.ch/record/166890/files/65-pods2003.pdf">https://infoscience.epfl.ch/record/166890/files/65-pods2003.pdf</anchor-external></figcaption><blockquote><p>In this paper, we study the precise complexity of XPath</p><p>1.0 query processing. Even though heavily used by its incorporation</p><p>into a variety of XML-related standards, the</p><p>precise cost of evaluating an XPath query is not yet wellunderstood.</p><p>The first polynomial-time algorithm for XPath</p><p>processing (with respect to combined complexity) was proposed</p><p>only recently, and even to this day all major XPath</p><p>engines take time exponential in the size of the input queries.</p><p>From the standpoint of theory, the precise complexity of</p><p>XPath query evaluation is open, and it is thus unknown</p><p>whether the query evaluation problem can be parallelized.</p><p>In this work, we show that both the data complexity and</p><p>the query complexity of XPath 1.0 fall into lower (highly parallelizable)</p><p>complexity classes, but that the combined complexity</p><p>is PTIME-hard. Subsequently, we study the sources</p><p>of this hardness and identify a large and practically important</p><p>fragment of XPath 1.0 for which the combined complexity</p><p>is LOGCFL-complete and, therefore, in the highly</p><p>parallelizable complexity class NC2.</p></blockquote></figure></body></html>