Resolving References in a Journal
I've talked before about having both organized (structured) topics and classified streams of topics. Ah yes, now we will be supporting multiple streams of unorganized (but classified) topics--we're calling them journals. But there has been something missing.
A Wiki Topic needs a namespace to resolve its WikiNames. No problem in most Wikis, all names are global. And no problem for organized topics in the AgileWiki, as a topic inherits (and modifies) the namespaces of its parents. But what about journals? Must each journal entry depend mostly on its parent (the journal) or itself for the namespace for resolving WikiNames? Perhaps we'll have many journals, each with its own namespace?
There's a better answer. We actually do know a great deal about a properly tagged journal entry. Consider the topics with TagMatches--they are kindof like the parent topics in a structure. OK, then let the journal entries inherit their namespaces based on their tags from the topics with matching TagMatches.
Lets consider a journal entry which deals with several different realms of knowledge. It then has tags which identify those realms, and there should be [structured] topics in those realms with TagMatches referencing those same tags. Bingo--the journal entry can resolve all its WikiNames using the namespaces of those topics.
Previously, we addressed TagMatches as a means of accessing a selection of unorganized topics. Then we named streams of unorganized topics: journals. Now we're using the inverse relationship defined by a TagMatch to provide namespaces for those unorganized topics (i.e. journal entries).
0 Comments:
Post a Comment
<< Home