W3C home > Mailing lists > Public > public-rax@w3.org > July 2016

Re: RDF / XML Interoperability

From: Martynas Jusevičius <martynas@graphity.org>
Date: Fri, 8 Jul 2016 19:56:02 +0200
Message-ID: <CAE35VmzWfQHjrDXEhbT-fwWXX9joc4DmpC5Oe6LC5vcBPe7pCA@mail.gmail.com>
To: "Lange-Bever, Christoph" <Christoph.Lange-Bever@iais.fraunhofer.de>
Cc: "public-rax@w3.org" <public-rax@w3.org>
Hey all,

we have quite extensive XSLT stylesheets transforming RDF/XML to XHTML:
https://github.com/AtomGraph/Web-Client/tree/master/src/main/webapp/static/org/graphity/client/xsl/bootstrap/2.3.2

We are not using any Java extension functions. We use however a
canonical "flat" RDF/XML layout, in which <rdf:Description>s are not
nested (default output by Jena writer). By limiting RDF/XML to such
layout, and using the key() function to lookup descriptions etc., the
transformation becomes quite manageable.

Martynas
atomgraph.com

On Fri, Jul 8, 2016 at 1:59 PM, Lange-Bever, Christoph
<Christoph.Lange-Bever@iais.fraunhofer.de> wrote:
> Hi Quentin,
>
> the following statement is important; quoting your email as forwarded by Christian:
>
> Dirschl, Christian <Christian.Dirschl@wolterskluwer.com> on 07 July 2016 10:52:
>> As such, transformation between RDF and XML using XSLTs is not optimal and XSLTs need to be tailored  to different flavor of RDF/XML (which is costly). One solution that we have used is to transform the RDF input (in any supported syntax) to be converted into a XML canonical form prior to applying XSLTs.
>
> Indeed many manually-crafted XSLTs suffer from this, …
>
>> The approach is supplemented by a library of Java functions  that can be called from XSLTs to process the graph.
>
> … and such libraries are the solution.  With https://github.com/EIS-Bonn/krextor I have another one (technically it's a collection of XSLT templates and functions that provides an abstraction layer), which you may be interested in looking at.
>
>> However, we have seen issues with the performance of transformation as well as increase in complexity. In other words, it is  difficult to maintain as requirements for transformation change.
>
> However, Krextor is clearly not optimised for performance, but rather for expressiveness and flexibility.
>
> Cheers,
>
> Christoph
>
> --
> Dr. Christoph Lange, Fraunhofer IAIS / Universität Bonn
> At Fraunhofer IAIS: +49 2241 14-2428 (redirects to mobile); room B3-212
> At the University: +49 228 73-4531; Römerstraße 164, Room A209
> Further contacts (Skype etc.):  http://langec.wordpress.com/about
>
> → Please note: I will be on parental leave from 29 July to 28 October.
>   Colleagues will stand in for me by project.
Received on Friday, 8 July 2016 17:56:33 UTC

This archive was generated by hypermail 2.3.1 : Friday, 8 July 2016 17:56:33 UTC