M
To: users@jena.apache.org; aj...@apache.org
Subject: Re: Why RDF/XML? Was: loading many small rdf/xml files
I don't see any practical usage of managing RDF data via its XML serialization
through XML tools.
In my town, a huge project tried to store graph data in a XML database. And
query
I know that. We are using keys extensively (mostly to lookup blank nodes).
Still, XSLT processing model is based on XML trees, and not RDF graphs.
It also depends on the output format you want to produce. In our case it is
XHTML which renders the resources and properties (and not triples), so it
c
On 11 October 2017 at 19:30, Martynas Jusevičius
wrote:
> TriX is not particularly well-suited for XSLT processing as it's a raw list
> of statements. A nested resource/property structure like in RDF/XML is a
> more natural fit for the parent/child traversal that XSLT does best.
>
In XSLT you're
TriX is not particularly well-suited for XSLT processing as it's a raw list
of statements. A nested resource/property structure like in RDF/XML is a
more natural fit for the parent/child traversal that XSLT does best.
On Wed, Oct 11, 2017 at 11:24 AM, Conal Tuohy wrote:
> On 11 October 2017 at 1
On 11 October 2017 at 18:53, Martynas Jusevičius
wrote:
> I wouldn't be so categorical :) We generate all the UI layouts straight
> from RDF/XML using XSLT 2.0:
> https://github.com/AtomGraph/Web-Client/blob/master/src/
> main/webapp/static/com/atomgraph/client/xsl/bootstrap/2.3.2/layout.xsl
>
>
I wouldn't be so categorical :) We generate all the UI layouts straight
from RDF/XML using XSLT 2.0:
https://github.com/AtomGraph/Web-Client/blob/master/src/main/webapp/static/com/atomgraph/client/xsl/bootstrap/2.3.2/layout.xsl
The prerequisite is that RDF/XML structure is predictable like Jena's
I don't see any practical usage of managing RDF data via its XML
serialization through XML tools.
In my town, a huge project tried to store graph data in a XML
database. And querying all that with XQuery.
It was probably the most expensive failure I have seen in my career.
(performances were awful)
Simply because it is both XML and RDF.
There is an enormous installed base of expertise and tooling for XML. It's often worth taking advantage of, even if it
is technically unperformant on a case-by-case basis. If you have to process RDF and you already know a great deal about
XML and use langu
