Work with TransClusion seems to have progressed to the point that it may be worth taking the risk of posting this to attract some constructive criticisms. Hence, this collection of some point-form Findings, Conclusions and Recommendations.

Feel free to jump in!

Some Findings(Observations)...

initial Conclusion(s)...

Context modifies meaning.

Using One Wiki Engine to control content in another, may be preferable

Recent experience in creating MicroContent blocks that exist in many different (OddMuse) wikis as evolved into a methodology in which TiddlyWiki is used to control access to OddMuse content.

A couple of examples in which this appears to dramatically more productive, include…


Next steps

rough notes being accumulated for this page...

 <include "http://www.communitywiki.org/odd/HansWobbe?action=browse;id=MicroContentPlansOfHwo;raw=1">

…from… Hwo:MicroContentPlansOfHwo

MicroContentPlansOfHwo … a TransClusion from the …\odd\… WikiHive to … [Wc:MicroContent Cw:MicroContent]
  • Extend by use of TiddlySpace, (Some preliminary documentation… http://docs.tiddlyspace.com)
  • The CommunityWiki page “MicroContent” is likely to become TooBigToEdit (at least efficiently). Hence, this block is edited n a remote location and “assembled” at CW by means of an <include…
    • TransClusion(s) among OddMuse wikis is very effective.
    • During the second half of 2007, several new WikiHive(s) were created, including a personal “localhost” wiki that can be used to create MicroContent page components.
      • Perhaps these component blocks can be described as PanWikiMicroContent or PanWikiPages, since the component blocks will typically appear in several different wikis simultaneously.
      • The use of these components is not a panacea, however, since sharing such a block in diverse environments does require additional tracking and care to ensure that they still fit appropriately into different contexts. Only truly “common” MicroContent blocks are likely to endure.
        • That being said, there are some obvious benefits, such as…
  • Enhance some understandings of these tagging concepts by trying to answer Lion’s question regarding the OddMuse Calendar + Tag capabilities.
    • Then introduce the TiddlyWiki complexities of the “tagging:” & “tags:” displays for each tiddler as well as the TagglyTagging concepts.


((byDate)-bySubject) PageName (.byTag)...

This convention adds both a prefix and a suffix to the standard pageName in order to…

  1. Take advantage of the oddmuse calendar support by simply adding a prefix to the name of the Date, in order to include it in a displayed Calendar. Another -bySuject term can be added in order to allow subsequent searches to find pages by title substrings.
  2. Incorporate .byTag1.byTag2 terms directly into the page name.


  • ByDate allows for automatic inclusion within the oddmuse Calendar displays within the BySubject prefix.
    • the ByDate.BySubject terms can be the first of three page name components in wikis that recognize prettyLinks that include both the “ “ and “.” characters.
      • BySubject could incorporate the use of LocalNames and the DynamicSubstitution Procedures that can be included within a TiddlyWiki document.
  • ByTag types include the ‘dimensions’ of Tag.Space, Tag.Time, Tag.Entity, …
    • Tag.Entity may be Author, Audience(Site, Community, …, Person, …)
      • Consider incorporating the extended [[E]]ntity definitions, as WikiSyllables.
        • At the least, these should be appended and consider for future use in more sophisticated situations.
    • Tag.Time may be a ‘relative’ time period such as … Hour Day Week Fortnight Month Quarter Year Decade Century Millenium …
    • Tag.Space may be geographic
    • Tag.LnGn is a LocalName GlobalName tupple

  • ByTag.ByType…
    • …[[C]](ategory)
    • …[[P]](rocedure)
    • …[[N]](ote)
    • …[](pace = latitude & longitude for map references)
    • …[[T]](ime)


  • Replace the local page controls with the use of the ones in the central TW Control.Tiddler for this Topic.

Discussion(s) ...

http://wagn.org/wagn/Wagn.org creates “cards” instead of “pages”. Allows TransClusion by attaching cards to other cards through a very simple page naming scheme:

“Sam_Rose” could be the main “card” (page)

“Sam_Rose+current_work” would make “current_work”, but also automatically transclude it into “Sam_Rose”

Also, there is a “WQL” being developed to query Wagn http://wagn.org/wagn/WQL

I am talking with some of them now about ideas around InterWiki and NearLinks, at least between Wagn installs.

This comes very, very, very close to what I had in mind for doing this type of things with OddMuse. Thought you might at least fidn it interesting, HansWobbe.

PS. HansWobbe:

The dynamic capabilities of javascript that make TiddlyWiki and ideal Client-side engine allow this wiki to import the source of an OddMuse page and render it very effectively within a TiddlyWiki wrapper. This has PROFOUND benefits in creating “pages” that offer the best of both worlds!

That is quite interesting. Do you have examples of this working? Also, where do you detail how you integrate with OutLook? (if at all)?

Re: OutLook? integration…

MicroContent needs to anticipate migrating among diverse MicroContext?(s).

  • Recent releases of TheBrain? are increasingly integrated with OutLook?. Not only do these feature good GUI interfaces, but they both support RTF, making it relatively easy to “publish” documentation for both electronic and print media. While I am not a fan of MicroSoft?’s OutLook? and Exchange server technologies (I consider them “bloatware”), they are almost universally used in the “enterprise” class organizations that I work with. Furthermore (at least so far) OutLook? seems to dominate in synching its standard Objects between mobile and desktop systems. As a result I find myself letting my content objects “migrate” among these environments, as well as between TiddlyWiki (and its emerging server-side TiddlySpace? evolution) and about a dozen OddMuse sites (which are used to host Content for specific groups).
  • The fact that my MicroContent is increasingly mobile and generally appears in many different environments, is one of the reasons that I find myself defining a “lowest common denominator” for wiki source, that can coexist, migrate and sync in many different “MicroContexts?”.


  • Sorry for the delay in responding, but I’ve had to focus on a few other matters and will likely have to continue to do so until the end of the month.
  • Thanks for the “Wagn” reference.

Hans, no problem. Consider us in the WikiNow, and I am sure you’ll engage when you can :)

Define external redirect: EricShulman TiddlySpace TiddlyTools MicroContexts AjAx TheBrain MilliContent GreaseMonkey NestedSlidersPlugin EnDimensionalArray MicroContext OnlyOnce PicoContent MicroKernel WikiEngines MicroSoft WikiWord OutLook WikiEngine TagGridArray