https://www.kevinmarks.com/memex.html

I got stuck over the weekend, so I totally missed Kevin Marks' memex demo at IndieWebCamp's Create Day, but it is an interesting little UI experiment.

I'll always maintain that Vannevar Bush really harmed the first few generations of web development by not mentioning the word commonplace book in his conceptualization. Marks heals some of this wound by explicitly tying the idea of memex to that of the zettelkasten however. John Borthwick even mentions the idea of "networked commonplace books". [I suspect a little birdie may have nudged this perspective as catnip to grab my attention—a ruse which is highly effective.]

Some of Kevin's conceptualization reminds me a bit of Jerry Michalski's use of The Brain which provides a specific visual branching of ideas based on the links and their positions on the page: the main idea in the center, parent ideas above it, sibling ideas to the right/left and child ideas below it. I don't think it's got the idea of incoming or outgoing links, but having a visual location on the page for incoming links (my own site has incoming ones at the bottom as comments or responses) can be valuable.

I'm also reminded a bit of Kartik Prabhu's experiments with marginalia and webmention on his website which plays around with these ideas as well as their visual placement on the page in different methods.

MIT MediaLab's Fold site (details) was also an interesting sort of UI experiment in this space.

It also seems a bit reminiscent of Kevin Mark's experiments with hovercards in the past as well, which might be an interesting way to do the outgoing links part.

Next up, I'd love to see larger branching visualizations of these sorts of things across multiple sites... Who will show us those "associative trails"?

Another potential framing for what we're all really doing is building digital versions of Indigenous Australian's songlines across the web. Perhaps this may help realize Margo Neale and Lynne Kelly's dream for a "third archive"?

Lima, Manuel. The Book of Trees: Visualizing Branches of Knowledge, 2014. https://papress.com/products/the-book-of-trees-visualizing-branches-of-knowledge.

https://personalknowledgegraphs.com/#/page/Personal%20Knowledge%20Graphs

https://app.thebrain.com/brains/3d80058c-14d8-5361-0b61-a061f89baf87/thoughts/32f9fc36-6963-9ee0-9b44-a89112919e29/attachments/6492d41a-73b2-20d8-b145-3283598c612b

A fantastic example of an extensive mind map from Jerry Michalski using The Brain.

There are lots of interesting links and resources, but on the whole

How many of the nodes actually have specific notes, explicit ideas, annotations, or excerpts within them?

Without these, it's an interesting map and provides some broad context, but removes local specific context of who Jerry is and how he explicitly thinks. One can review the overarching parts to extract what his biases may be based on availability heuristics, but in areas of conflicting ideas which have relatively equal numbers of links within a particular area, one may not be able to discern arguments from each other.

Still a fascinating start and something not commonly seen in the broader literature.

I'll also note that even in a small sample of one video call with Jerry sharing his screen while we talked about a broad sub-topic it's interesting to see his prior contexts as we conversed. I've only ever had similar experiences with Bill Seitz who regularly drops links to his wiki pages in this sort of way or Kevin Marks (usually in text chat contexts and less frequently in video calls/conversations) who drops links to his extensive blogging history which also serves to add his prior thoughts and contextualizations.

https://kumu.io/

Make sense of your messy world. Kumu makes it easy to organize complex data into relationship maps that are beautiful to look at and a pleasure to use.

tagline:

The art of mapping is to create a context in which others can think.

Tool mentioned on [[2022-06-02]] by Jerry Michalski during [[Friends of the Link]] meeting.

https://www.youtube.com/watch?v=F-icwOk8YFk

It's interesting to see the differences between the bookclubs in this visualization of their related notes.

https://www.otherlife.co/pkm/

The PKM space has gotten crazy, but mostly through bad practice, lack of history, and hype. There are a few valid points I see mirrored here, but on the whole this piece is broadly off base due to a lack of proper experience, practice and study. I definitely would recommend he take a paid course to fix the issue, but delve more deeply into recommended historical practices.

This useless knowledge graph is one of the worst parts about Roam Research. It is bad UI and wholly unusable.

I think there's definitely an aesthetic enjoyment factor, but that doesn't mean it's bad -- if anything it might be the opposite?

You could imagine describing a knowledge graph as 'pleasant' -- or even 'beautiful'. You can see them as "pretty pictures" -- or you can see them as (generative?) art.

Beispiel für eine KG-Erweiterung

Verbesserungspotential von EKGs

Zukunft: Zugang für Nicht-Techniker

Einsatz von Projektgraphen Erweiterung um die Fähigkeit, basierend auf seine beschreibenden Texten relevante Themen und Technologien zur Übernahme vorzuschlagen

Projekt „Smart Data Web“ Corporate Knowledge Graph (CKG) - ermöglicht eine einheitliche, konsistente und elegante Verknüpfung interner und externer Informationen, ganz im Sinne einer „Enterprise-Intelligence“-Lösung

Semantische Verknüpfung/Ontologie:

Dabei werden interne Kennzah- len, z. B. zum Projektvolumen und zu Bewertungen einzelner Lieferanten, mit aktuellen, automatisch gesammelten, firmen-, produkt- und standortbezogenen Ereignissen aus<br /> Nachrichten und anderen Textdatenquellen verknüpft

Potential: eine Gesamt- sicht auf entscheidungsrelevantes Wissen erhalten.

Enterprise Knowledge Graphs (EKGs) als eine Verkörperung von LED

The unified approach has the advantage, that the enterprise has more control over the data and quality, and the data querying is significantly faster.

Enterprise Knowledge Graphs are the next stage in the evolution of knowledge management systems.

PDF zur Studie

Bei der Einbettung von Wissensgraphen (KG) werden die Komponenten eines KG, einschließlich Entitäten und Beziehungen, in kontinuierliche Vektorräume eingebettet, um die Bearbeitung zu vereinfachen und gleichzeitig die inhärente Struktur des KG zu erhalten. Sie kann für eine Vielzahl von nachgelagerten Aufgaben wie KG-Vervollständigung und Relationsextraktion von Nutzen sein und hat daher schnell große Aufmerksamkeit erlangt. In diesem Artikel geben wir einen systematischen Überblick über die vorhandenen Techniken, wobei wir nicht nur den aktuellen Stand der Technik, sondern auch die neuesten Trends berücksichtigen. Dabei wird insbesondere auf die Art der bei der Einbettung verwendeten Informationen eingegangen. Zunächst werden Techniken vorgestellt, die die Einbettung nur anhand der in der KG beobachteten Fakten durchführen. Wir beschreiben den allgemeinen Rahmen, das spezifische Modelldesign, typische Trainingsverfahren sowie die Vor- und Nachteile solcher Techniken. Danach werden Techniken diskutiert, die neben Fakten auch zusätzliche Informationen einbeziehen. Wir konzentrieren uns insbesondere auf die Verwendung von Entitätstypen, Beziehungspfaden, textuellen Beschreibungen und logischen Regeln. Abschließend stellen wir kurz vor, wie die KG-Einbettung auf eine Vielzahl von nachgelagerten Aufgaben wie KG-Vervollständigung, Beziehungsextraktion, Beantwortung von Fragen usw. angewendet werden kann und davon profitiert.

Machine Learning and Knowledge Graphs

Titel: A knowledge representation practionary Autor: Michael K. Bergman

comprehensive definition

Maybe the vendor dependency is one of the problems.

pretty great intro to knowledge graphs

This applies to universal KG in particular. Domain specific KGs can have any level of complexity - can they still be called knowledge graphs then?