Its honestly fantastic to see web pages that are using XSLT, is this the most advanced app out there using it these days?
LinkedDataHub: The Knowledge Graph Notebook
11–20 of 46 posts
Re: LinkedDataHub: The Knowledge Graph Notebook
#12LinkedDataHub, a "RDF-native notebook", is not to be confused with LinkedIn DataHub, which is a metadata store/crawler/ui for your data systems: https://datahubproject.io/.
Re: LinkedDataHub: The Knowledge Graph Notebook
#13In my ears, knowledge graph sounds a bit grandiloquent. I do not have a definition, but I know that when talking about knowledge as it is embodied in people, it's quite a subtle thing, hard to formalize and to be honest, something relatively rare. Why can we just call these things fact databases? Add. Knowledge evokes a lot of other associations as well, for example that what we are able to know changes over time. Th…
> Why can we just call these things fact databases? Companies that want to reinvent/repackage and sell boring RDBMS tech
Its not rdbms though. It's RDF, triple store, graph-like data models.
Re: LinkedDataHub: The Knowledge Graph Notebook
#14Earlier quoted context omitted.
> Why can we just call these things fact databases? Companies that want to reinvent/repackage and sell boring RDBMS tech
Its not rdbms though. It's RDF, triple store, graph-like data models.
Those are easy to implement on top of RDBMS. Query performance is a different thing, which can only be evaluated on a case-by-case basis, but you can go a long way with good indexes.
A few companies need real time analytics on really big graphs. Most don't and shouldn't waste their time with fancy Google-scale databases.
Re: LinkedDataHub: The Knowledge Graph Notebook
#15What 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 technologies. Graphs are cool, and SPARQL has a certain appeal. Who is using these things already day-to-day?
> developers who are looking for a declarative full stack framework for Knowledge Graph application development, with out-of-the-box UI and API
I work on an application (https://notion.so) that would be better with more Knowledge Graph, but I don't need a framework. I'm curious what application developers approach the knowledge graph space looking for a "full stack framework". I presume most commercial developers would prefer to use their existing application tooling. Maybe academic researchers writing software for their lab?
>What makes LinkedDataHub unique is its completely data-driven architecture: applications and documents are defined as data, managed using a single generic HTTP API and presented using declarative technologies. The default application structure and user interface are provided, but they can be completely overridden and customized. Unless a custom server-side processing is required, no imperative code such as Java or JavaScript needs to be involved at all.
This kind of flexibility is intrinsically appealing to programmers, but the resulting user experience leaves a lot to be desired. Usually it's better to build a good product first, and then to extract the framework bits once they've proved productive. Otherwise you may end up with a framework that can do anything, but in a way nobody wants.
Re: LinkedDataHub: The Knowledge Graph Notebook
#16Its honestly fantastic to see web pages that are using XSLT, is this the most advanced app out there using it these days?
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?
Re: LinkedDataHub: The Knowledge Graph Notebook
#17In my ears, knowledge graph sounds a bit grandiloquent. I do not have a definition, but I know that when talking about knowledge as it is embodied in people, it's quite a subtle thing, hard to formalize and to be honest, something relatively rare. Why can we just call these things fact databases? Add. Knowledge evokes a lot of other associations as well, for example that what we are able to know changes over time. Th…
> Why can we just call these things fact databases? Companies that want to reinvent/repackage and sell boring RDBMS tech
A Knowledge Graph is the data in the database, not the tech.
You can absolutely implement this in a RDBMS. There are some advantages to a proper graph database though.
But SPARQL is a dead-end - I don't think anyone is really using that in practice outside a dew public demonstration apps. To a large extent this is true of RDF too: triples are useful, RDF gets in the way.
Re: LinkedDataHub: The Knowledge Graph Notebook
#18Its honestly fantastic to see web pages that are using XSLT, is this the most advanced app out there using it these days?
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 ?
> What's good about XSLT?
Nothing. It was a bad choice in its heyday (I worked on some projects way back then).
> Is its ecosystem substantially better than alternative options
No.
Re: LinkedDataHub: The Knowledge Graph Notebook
#19My first intuition of a knowledge graph would be an IDE. If that's not right, how am I wrong? If it is a typical use, what IDE(like) examples are there? Org-mode is a tree instead of a general graph, but general graphs can be traversed as (sets of) trees. Is the tree discipline somehow important to understanding code?
Re: LinkedDataHub: The Knowledge Graph Notebook
#20Graphs are great for querying drawing a query can really help explaining what you really want. But for results visualization as soon as you reach the hundredish nodes it becomes unbearable. There are tricks used by crime analyzis software for example where results are grouped in different nodes that can make it easier, but that's only good for when you don't have too many node types.