eekim.com: EEK Speaks

Thu, Aug 12, 2004

TPVortex: Intro, Call For Help #

In my manifesto for collaborative tools, I cited BackLinks as an example of a common, yet oft-overlooked conceptual construct in collaborative tools. Those who know me well know that my strategy for implementing some of DougEngelbart's ideas (which I crafted over three years ago) has always been to create simple, concrete tools that could easily be shoehorned into existing applications. The plan was to start with GranularAddressability (PurpleNumbers), then move on to BackLinks. (247)

For a number of reasons, now seems to be the right time for me to start shifting my technical focus to BackLinks. The strategy for doing this is to implement a generic, OpenSource, BackLink database (dubbed "TPVortex" and integrate it into several existing tools: PurpleWiki, blosxom, MovableType, MHonArc. I'm looking for folks who might be interested in participating in this project. (248)

The motivation for such a tool is straightforward: BackLinks provide useful, contextual information. Most Wikis already implement BackLinks. Some of them display BackLinks on the main page, which is the correct behavior. Others (including PurpleWiki) do not. In order to implement this properly, you need a BackLink database. (249)

Once you have a BackLink database, you might as well use it for other applications besides Wikis, such as blogs. We have this integration in PurpleWiki (see WikisAsTopicMaps for the resulting benefits), but again, it would be much nicer to display the BackLinks on the page itself rather than requiring a person to click on a link to see them. In order to implement this properly, the database has to store document metadata, such as title and author, not just the BackLink. For this reason, I think that TPVortex should use an RDF database on the backend. (24A)

Other thoughts: (24B)

Use TrackBack or PingBack as the protocol for updating the database. (24C)
Use IdentityCommons i-names for identification and authentication. (24D)
Implement stubs in multiple languages. (24E)

I welcome help in all forms -- comments, critiques, and especially coding. I've set up a Wiki page at the CollaborationCollaboratory -- Collab:TpVortex -- to serve as the center of design discussions. If you're interested in contributing or commenting, please do it there. Feel free to drop me an email as well. (24F)

/tech/wiki | Posted at 1:17pm

Wiki Linking Using Ontologies #

Last weekend, I posted some notes on MarkupFreeAutoLinkingWiki. The idea is that instead of relying on user syntax for identifying and linking to Wiki pages, the Wiki could do a linguistic scan of the text and link words based on a site-specific ontology. (242)

I posted my notes mainly as a BlueSkyIdea, but it ended up generating a ton of discussion at the CollaborationCollaboratory. That discussion made me realize that this idea may not be all that blue sky after all, and that -- given the proper PurpleWiki:DataBase design -- we're not all that far off from implementing something like this in PurpleWiki. (243)

/tech/wiki | Posted at 12:35pm