namedgraph

I use it in ETL whenever I have an XML source, then I use XSLT to lift it to RDF (either RDF/XML or TriX). I use it for the UI where I'm transforming RDF/XML to HTML. I'm also using for the interactive parts instead of Javascript (or React or Svelte etc.), but that's the interactive XSLT extension that goes beyond the standard.

XML to XML, XML to RDF, JSON to XML and XML to JSON, XML to text -- XSLT can be used for all kinds of transformations. 3.0 also supports streaming transforms, which is very useful for large input files.

XSLT is a declarative DSL made specifically for the XML data model. It does limited things such as navigating the XML tree but does them really well. It lifts the abstraction level so you can focus on the transformation. You can transform XML with bash or a general purpose language like Java, but it will never be so concise or effective.

No complaints about the Saxon processors here (we're using Saxon-HE server-side and Saxon-JS client-side). The XSLT standards are excellent, as is the quality of Saxon implementations.

That's just bullshit. Stop spreading FUD.

We participated in a huge RfP for a pharma company which planned RDF KG infrastructure for the next couple of years with 500 billion triple capabilities.

Biomedical, finance, defence, automotive -- all of those industries are using RDF/SPARQL. Just because your problems are not big or complex enough doesn't mean this tech is not used. It takes a certain organization size for Knowledge Graphs to make sense and pay off, that's why most industry users are Fortune 500-level companies.

It doesn't have many ETL features, but it does support CSV import.

What kind of data are you looking to transform?

The endpoint served by our partners went down.

Can you ping me at [email protected]? Would be appreciated.

Absolutely. XSLT is a data transformation technology, not a template language.

You do realize this is an open-source project? And you are comparing with a product by Neo4J who got $300M VC investment?

The enterprise Knowledge Graphs (yes, it's the same SemWeb tech stack in principle) in Fortune 500 sized companies have in-house platforms that present the graph to the end-users, with entity browsers, analytics, dashboards, structured content etc. LinkedDataHub is an attempt to bootstrap an open-source, standards-driven version of that.

LinkedDataHub was extracted from the common code from a number of Linked Data projects that we have done in different domains.

It can be used as a framework but it's a standalone application as well, because it provides the default built-in ontologies as well UI for Linked Data and SPARQL consumption.

Disclaimer: I'm the main developer.

It's special in the way that it is a standard. Pretty much the only standard NoSQL query language still.