LinkedDataHub: The Knowledge Graph Notebook
1–10 of 46 posts
Re: LinkedDataHub: The Knowledge Graph Notebook
#2The list of dependencies is amazingly long for a product which seems to be a harder to use TiddlyWiki, or Neo4j UI for the graph viz part. It's crazy the SemWeb community still haven't give up given how much effort have been poured into it for so few results.
Re: LinkedDataHub: The Knowledge Graph Notebook
#3The list of dependencies is amazingly long for a product which seems to be a harder to use TiddlyWiki, or Neo4j UI for the graph viz part. It's crazy the SemWeb community still haven't give up given how much effort have been poured into it for so few results.
This package was designed to solve more problems than it creates
https://github.com/paulhoule/gastrodon
Overall I think of graph visualization as a problem, in particularly there are some people who just don't see that hairballs are incomprehensible
Re: LinkedDataHub: The Knowledge Graph Notebook
#4The list of dependencies is amazingly long for a product which seems to be a harder to use TiddlyWiki, or Neo4j UI for the graph viz part. It's crazy the SemWeb community still haven't give up given how much effort have been poured into it for so few results.
I access SPARQL endpoints from inside programs written (usually) in Common Lisp, Python, and Clojure.
LinkedDataHub looks cool enough for non-tech users, but I prefer working inside a repl/Slime/etc. interactive programming environment.
Also, Google, Facebook, most banks, etc., etc., use Knowledge Graphs - pretty solid technology.
Re: LinkedDataHub: The Knowledge Graph Notebook
#5In 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. That a time has a certain underlying grid, into which certain factual stories appear and later disappear.
Re: LinkedDataHub: The Knowledge Graph Notebook
#6In 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
Re: LinkedDataHub: The Knowledge Graph Notebook
#7Mh... I'm an org-roam (org-mode/Emacs) user, witch have a similar feature and... I find such visualization honestly sugar-eye and useless.
Network analysis of notes links is fascinating, but must be actionable in some way, just having a UI means nothing. Also most noting tools miserably fails to really offer "easy atomic notes that can be combined (transcluded) and splitted as the user wish", some try structured ways (SPARQL/fixed formats alike) others try to offer some loose feature set to make anything possible but a real solution is still decades of development away IMO.
So far the best, witch means least worse, way I found to really analyze my notes is using org-mode drawers with relevant templates help for consistency to be queried via org-ql, witch means essentially key-value structured tagging of notes so I can see them in a timeline, I can see all notes about a URL, an author, a subject, a topic, ... unfortunately is a manual tedious process and at runtime is not that fast nor flexible.
Long story shorts vast approaches like Wikidata, classic libraries cataloguing techniques & tools, modern/old notes and relevant tools all work to a certain extent and fails thereafter.
Re: LinkedDataHub: The Knowledge Graph Notebook
#8The list of dependencies is amazingly long for a product which seems to be a harder to use TiddlyWiki, or Neo4j UI for the graph viz part. It's crazy the SemWeb community still haven't give up given how much effort have been poured into it for so few results.
This package was designed to solve more problems than it creates https://github.com/paulhoule/gastrodon Overall I think of graph visualization as a problem, in particularly there are some people who just don't see that hairballs are incomprehensible https://cambridge-intelligence.com/how-to-fix-hairballs/
Large graphs (just about anything larger than a karate club social network [1]) can't usually be visualized in a useful manner. There are exceptions, but in real world applications they are more useful as pretty art than helping with understanding.
Statistical summary plots are more useful.
Maybe one day someone will figure something out, but much like scatter plots fall over when you plot vast amounts of raw data, so do plotting graphs.
Re: LinkedDataHub: The Knowledge Graph Notebook
#9In 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?
Because (in theory) they are much much more than that.
In practice the semantic web/data space has a problem of building complicated standard on top of complicated standard (as well as having a Java implementation monoculture, which doesn't help that). That also makes it hard to formalize all the non-trivial statements that are part of our knowledge.
And yes, there are subtle aspects to knowledge, that is usually not capturable easily in manually formalized knowledge graphs, but that's where pairing knowledge graphs with ML-based methods (e.g. vector search) can really shine.
Re: LinkedDataHub: The Knowledge Graph Notebook
#10Earlier quoted context omitted.
This package was designed to solve more problems than it creates https://github.com/paulhoule/gastrodon Overall I think of graph visualization as a problem, in particularly there are some people who just don't see that hairballs are incomprehensible https://cambridge-intelligence.com/how-to-fix-hairballs/
Large graphs (just about anything larger than a karate club social network [1]) can't usually be visualized in a useful manner. There are exceptions, but in real world applications they are more useful as pretty art than helping with understanding. Statistical summary plots are more useful. Maybe one day someone will figure something out, but much like scatter plots fall over when you plot vast amounts of raw data, s…
My answer to it is that graphs need to be manually curated. For example, a UML diagram for all the database tables on the system I am working on now would have to be printed out on a wall to make any sense, but if I picked out the tables involved in a new user registration that would be useful.
I went to an exhibit of this guy's works
https://en.wikipedia.org/wiki/Mark_Lombardi
and saw a series of drafts he'd made where he had drawn many different versions of a conspiracy social network and gradually went from a hairball to something that looked meaningful.
In terms of turning this into a tool there's the interesting problem that there is a graph that comes in from the outside world (and could be regenerated) and also data that represents the curation of the graph (Do I show this? What color is this line? What position does this node get displayed at?) You've got to be able to edit one independently of the other and deal with things sometimes getting out of sync to have a tool that advances over the state of the art.