Bimlas,

Even if a note has a name, in fact it will never be completely clear 
> because its context determines what effect its content achieves. For 
> example, if a note is titled "String," it says virtually nothing, because 
> it could be related to programming as well as music. The context is mostly 
> given by the text of the link pointing to it. If we just list the note 
> names, it won’t be so clear why they’re included in a given context. 
> Instead, you can use the text of the links to tell you how they relate to 
> that topic. For example, if we only use their titles in an introduction to 
> programming


This context sensitivity is why the links in relationships are best 
independent from just the title, On the second use of "string" you 
"discover" the need for a logical disambiguation that arose from one of the 
contexts in which you found a connection with string. At this point you may 
split and link to a different string "musical string" and rename the other 
"text string", or you may maintain the abstract "string" with subtiddlers 
for alternative definitions, this is uncovering or discovering information 
and relationships in the data set you are collecting. Except perhaps as a 
definition of the word "string", I may be unlikely to use this as a title 
without disambiguating from the start. 

For example, If I created a tiddler "string" to provide the definition of 
the word, I would realize there is now a set of relationships between word 
use and their definitions. So I would more likely disambiguate by a 
namespace $:/glossary/string providing a new context that of definition. 
his is all a matter of a "process of discovery", thus the underlying system 
must be capable of adaption.

For the system to be remain adaptive we must;

   - Avoid Dependencies on compound keys
   - Maintain maximum renamability (Relink or Serial Numbers)
   - Maximise the readability of titles independently of how we organise 
   tiddlers. 

If we deal with the context correctly we can use Captions to 
"re-ambiguate", so it appears as "string" but its link or tooltip is to a 
different "string".

This is an interesting discussion and two particular thoughts have arisen 
in my mind

   - If we can analyse this enough and empower users to handle any 
   relationships that appear, what a great feature it would be.
   - Perhaps we could scan a Tiddlywiki and extract all relationships found 
   and formalise these with a new tiddler for each, representing the 
   relationship(s) even identify different contexts, needs for disambiguation 
   and re-ambiguation etc...
   - Could we design "ambiguous tiddlers" that internally disambiguate? eg 
   String has the children "musical string" and "text string"
      - "musical string" could store the context in which it is valid eg 
      tiddler has music keyword.
   - Discovery of ambiguity and abstractions and the reverse are important, 
   let us capture and support them. 
   - and many others

Regards
Tony


Regards
Tony

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/b5c1f6ad-579e-4dfb-b16e-5c2bf9807062%40googlegroups.com.

Reply via email to