felixhayashi

As for the rdf import/export, I also thought about it and it should be possible, I mean rdf subject and object resources will be tiddlers and the predicate a relation....

I just tested vue. I like it but it seams, it cannot even properly import the rdf it created itself (when using save as rdf). Anyhow, see my comment here:...

Things that probably are needed for an RDF import mechanism: * **A deserializer**. * What is a deserializer? → http://tiddlywiki.com/dev/#Deserializer * Example of a deserializer → https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins/tiddlywiki/evernote/modules/enex-deserializer.js * **Persisting edges**....

Hi @rcrath > If I am reading How TiddlyMap stores Edges correctly, The various formatting options for the edge (dotted/solid, 1/2/3px width, curved/bezier/straight, outward arrow/inward arrow/bidirectional/nodirection) would be referenced by...

> I believe there would be much more utility in making the nodes/edges more web-friendly, giving them all URLs and potentially allowing them to act as live Linked Data. not...

Hi @micahscopes many thanks for laying out your thoughts in detail. The idea to offer ways to add metadata/weights/parameters to edges that goes beyond mere linking- and styling-data is a...

Hi @micahscopes, > The timeline will of course be defined by the descent of visible graph edges. I still need to answer the question of "descending from where?"... in the...

Hi Danielo, I think this is not intuitive and other people will want to use sizes to symbolize other stuff (For example I plan in a private project to display...

@danielo515 yes, I also thought about a field that defines how big the node should be too but it is something I really want to spend some time thinking on....

yes exactly it is too tricky in my eyes ;) I will instead focus on core functions at the moment. Let us discuss this again once the basics all work...