One more thing... it would be totally awesome to be able to create embedded map views parametrically. Today, the widget code only allows embedding views that have already been created. This makes it prohibitive to create individual views for lots of individual tiddlers. However, it seems that templating embedded maps would only require for the widget to also specify edge and node filters. On Monday, October 15, 2018 at 11:32:27 PM UTC-7, LorenzGL wrote: > > Semantic annotation of data is an extremely powerful tool for structuring > knowledge and making it machine readable: domain knowledge is captured by > defining a class hierarchy and describing the properties that relate > individuals class members. For example, in order to model family relations > I can define a class "Person" whose individual members are pairwise linked > to eachother by the properties "has_parent" and "has_child". This then > allows me to query an individual's ancestry, e.g. "has_sibling" or > "has_grandparents" — without having to assert each of these derived > relationships individually. > > > Specialized ontology modeling software (e.g. protégé) exist for building > these semantic models. Yet, while extremely powerful these software > packages are not good at creating attractive user facing knowledge bases. > Interestingly, the ontology concept matches very well onto the "smallest > semantic units possible"-paradigm of TiddlyWiki. In TiddlyWiki, a family > knowledge base can be simply created by storing each persons information in > a tiddler and adding fields for properties has_child and has_parent. Now, > an individual's ancestry can be displayed using templates with appropriate > filters (recursive search along has_parent property). And, since > TiddlyWiki's elegant way of displaying information and media we can easily > add additional information like images, personal details, etc. On top of > this, TiddlyMap makes it trivial to display the family tree graphically > (see "Using the Map Raster" example on TiddlyMap.org). > > > Unfortunately, linking tiddlers by entering tiddler names into properties > fields is tedious and error prone (due to missing auto-completion). > TiddlyMap greatly simplifies this data entry process by allowing to connect > existing tiddlers by simply dragging edges (which are linked to tiddler > fields) between them — thus ruling out broken links due to spelling errors. > However, especially in complex models with many properties it is easy to > forget to some properties since each edges have to be manually created. In > order to improve this I would like to propose a different data entry mode > in TiddlyMap: "dangling edges" could be created for each tiddler that is > added to a map (based on a template/filter) so that all fields can be > easily filled by connecting the respective edges to other tiddlers. In > other words, instead of adding both tiddlers and edges manually, adding a > tiddler should also add "edges" for connecting additional tiddlers. > Ideally, a mechanism for defining rules for which edge type can connect to > which node type (including directionality) could be defined. > > > This behavior would dramatically improve the data input speed, minimize > errors, and enable an incredibly powerful semantic TiddlyWiki. >
-- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/340bfe24-b454-41f8-b131-b27e9a3c0d64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
