Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LinkedDataHub: The Knowledge Graph Notebook

github.com

Post reply on HN
Print view View original

41–46 of 46 posts

Re: LinkedDataHub: The Knowledge Graph Notebook

#41

Post by jitl »

namedgraph wrote: post #29
jitl wrote: post #15

What is the use-case for this software? From the README: > We are building LinkedDataHub primarily for: > researchers who need an RDF-native notebook that can consume and collect Linked Data and SPARQL documents and follows the FAIR principles I would be interested in reading a user story of a few paragraphs about how this works. I don't know anyone working with RDF or SPARQL documents, but I'm curious about these te…

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.

What were the projects you did? I think concrete examples would help me understand the software more.

Re: LinkedDataHub: The Knowledge Graph Notebook

#42

Post by jitl »

namedgraph wrote: post #31
jitl wrote: post #16

Earlier quoted context omitted.

What's good about XSLT? Is its ecosystem substantially better than alternative options like simple string templating a la https://pkg.go.dev/html/template ?

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

Can you describe a task that XSLT makes substantially easier to build/more correct/faster to execute? Saying “yep its good” gives an opinion but after looking at XSLT docs I am not “getting it”. Why do I want this? I transform data all the time with a bash script, is XSLT like bash?

Re: LinkedDataHub: The Knowledge Graph Notebook

#43

Post by namedgraph »

jitl wrote: post #41
namedgraph wrote: post #29

Earlier quoted context omitted.

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.

What were the projects you did? I think concrete examples would help me understand the software more.

https://atomgraph.com/cases/

Re: LinkedDataHub: The Knowledge Graph Notebook

#44

Post by namedgraph »

jitl wrote: post #42
namedgraph wrote: post #31

Earlier quoted context omitted.

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

Can you describe a task that XSLT makes substantially easier to build/more correct/faster to execute? Saying “yep its good” gives an opinion but after looking at XSLT docs I am not “getting it”. Why do I want this? I transform data all the time with a bash script, is XSLT like bash?

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.

Re: LinkedDataHub: The Knowledge Graph Notebook

#46

Post by capevace »

namedgraph wrote: post #35
capevace wrote: post #26

Earlier quoted context omitted.

So I don’t personally have many use cases for RDF-type data, but I plan on implementing RDF data endpoints in a music library app I’m building. I suppose RDF thrives in the academic space, whereas userspace suffers from a chicken and egg type problem. There aren’t many common services available that have public RDF endpoints, so few applications using them get built. Edit: I suppose that’s what LinkedDatHub provides…

It doesn't have many ETL features, but it does support CSV import. What kind of data are you looking to transform?

Basically I’m combining your local music library with data from streaming services so you have unified playlists across them.

So basically I’m having to match a bunch of resources like songs together from different APIs.

Post reply on HN