Test Information Space: Warewiki

Description

Warewiki

Posted by cadsmith on May 9, 2009

Tools evolve and drive inventors to new efforts. The wiki is probably no exception. It can be used to comment software and track bugs. Static content pages can be translated to wiki format using automated keyword hyperlinking and tagging. It seems to be the case that, by adding a few simple additional field types, they can be made more active. For example, a selector entry might be switched between values to use different other pages. So we enter the world of wiki-based computing. Documentation applications handle system descriptions, designs, metadata and statistics. It is not impossible for them to add operation and debugging. Each page is a memory snapshot or state of a set of values which can include hyperlinks and tags. A series of these can be used to drive activity just as a set of source code modules can be an instance of an algorithm, or machine components can be an engine. These modules are versioned and there can be a selector field parameter to string the correct choices together. This gives some flexibility in either pre-specifying order of execution, or allowing a test-driven approach to exercise combinations until a result is obtained. Automated editing or refactoring is more complex; this can be content-driven or result-driven. It may be possible for the wiki to edit itself to adapt to some external context or usage. A processing medium would have the ability to execute from wiki description or code to binary. This implies a ware descriptor language . Applications might be imagined for emulation, virtualization or hypervisors. This allows digital experiments to compare implementations prior to production. A wiki can also then become an operational component of a system. Pieces may be upgraded to other media or machines. Consider the ...

Original URL

http://cadsmith.wordpress.com/

http://cadsmith.wordpress.com/