Mailing-List: contact vxquery-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: vxquery-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=DKIM-Signature:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
  b=hNWznH2I0nnbJ7yuieqaf8B/Aug06cDGj0r41DV0H9pDC92IUMjTBgprS6gGaCufa2dGwZ54kVfglNTCP+nkfDKBG4tK0PmD7CxJ17GdpwPdZxA636mKOzOB5GqNdGg4bBFQG4WFuxLgBAhsgYx+FnAmPaJWtHlUHb9VX8KBd00=
  ;
Message-ID: <4FED4A17.6000604@yahoo.com>
Date: Thu, 28 Jun 2012 23:24:23 -0700
From: Vinayak Borkar <vborky@yahoo.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: vxquery-dev@incubator.apache.org
Subject: fn:doc() support
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Guys,

I have checked in support for fn:doc(). The ground work to represent the 
6 different XML node types as bytes (that Till and I spent the last few 
weeks building) is also in to support the fn:doc() function.

Currently, the only thing you can do is to use the doc() function in a 
query to parse in an XML document. Functions that evaluate path steps or 
that serialize XML nodes into text XML have not yet been implemented.

Initial analysis shows that the binary representation of documents 
occupies about 2 to 2.5x the size of the original XML file. Further 
optimization is possible, but the next step will be to focus on getting 
more functionality in place.

Please let me know if you have any thoughts or comments.

Thanks,
Vinayak