W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > January 2005

Re: SPARQL Variable Binding Results XML Format

From: Paul Ford <ford@ftrain.com>
Date: Sun, 16 Jan 2005 12:20:23 -0500
Message-ID: <41EAA257.8060509@ftrain.com>
To: public-rdf-dawg-comments@w3.org

> 3) XML Literal Content.
> I see that XML literal content is escaped in output.xml. Yuck :-) Please 
> don't do that.

I too am wondering for the reason behind this -- Sesame's XML 
serialization does it too.

The workaround I've found is to run an XSLT script on the output, where 
I reproduce the XML exactly, except when I run into XML literal content, 
where the rule is:

<xsl:value-of select="." disable-output-escaping="yes"/>

Unfortunately, the current version of libxslt won't allow you to operate 
on the results dynamically. You can't convert ecaped content to a 
variable containing unescaped content, then operate on it using 
exsl:node-set(). However, the escaped content will be converted to 
proper XML in the result tree.

The upshot is that I need to run two XSLT scripts on any serialization 
in order to do much with it. It's not the end of the world, but it would 
be nice to cut out that first step, if possible.

Best wishes,

Paul Ford
Received on Monday, 17 January 2005 02:11:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:05 UTC