[Bug 15317] absence of functions for reading binary data in XPath 3.0 Working Draft

https://www.w3.org/Bugs/Public/show_bug.cgi?id=15317

Mike Sokolov <sokolov@falutin.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sokolov@falutin.net

--- Comment #2 from Mike Sokolov <sokolov@falutin.net> 2012-01-03 15:31:23 UTC ---
More use cases: 

1) Test for the existence of a binary document.  This is useful when processing
documents with references to image files.  When they're not present (this often
happens due to variances between copyright for print and for online
distribution), the requirement may be to process the XML differently, eg by
stripping all references to the images, including captions, etc.  Currently
trying to do this with doc-available fails - I forget why, but perhaps that can
be patched up as an implementation issue. 

2) Read in and write out a binary document unchanged, in an efficient manner
(eg without the need to transcode to some text encoding).  This would really be
useful if it were also practical to process entire directories or archives (zip
files, etc) in the context of xslt/xquery.  At the moment we do directory
processing externally, in Java, so this use case is mostly theoretical at the
moment, for us. But it still could be useful to, say, pass every file in a
folder through xslt, transforming uris on the way, and for the xml, also
transforming the content.

I think if this were to go forward, it'd be best to add a binary type to the
XDM if there isn't one already.  Then it would be possible to call out to
extension functions to perform binary processing as well.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Tuesday, 3 January 2012 15:31:25 UTC