Hi, I must admit, i am not able to see the advantage of storing information about a person or object in a link instead of in a field. In fields you can store
name: Joe familiy: Doe father: Alfred Doe mother: Beatrix Doe spouse: Foo Bar course-about-hacking: attended The last one might be solved differently by storing a list of attendants in a tiddler "course about hacking" of course. Now you could write macros to style links based on that information. And you would have all the information in the one place where it makes sense istead of scattered over many tiddlers and many links. – But let’s assume it makes sense in some contexts. Question: how would HTML handle the additional relation information? Could it be presented to users in a useful and accessible way? And a short reminder: HTML anchors (a) already can have *type* and *rel* attributes – both are not supported by the link widget at the moment, but there are indeed some kinds of relations already covered to be aware of. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a One last provocation: How about [[ Joe (stepson) | Joe Doe ]] ? Goodnight ;–) Thomas -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5ae51ee5-d80e-44a3-99c7-f686ffbb2617n%40googlegroups.com.
