Continuing Workflow Evolution

We summarize how we have come to our current understanding of scripts in the sharing context of federated wiki.

# Background

There are many wiki sites that share content under the creative commons license.

The client allows the owner of a site to edit json encoded pages on one site and retrieve json pages from any other site.

A site can also serve arbitrary assets into the federation. A page can include an Assets plugin configured to read and write files from a particular assets directory.

A page can also include a Frame plugin which will run arbitrary html from somewhere in the internet, quite possibly from an assets directory in some wiki site.

# Workflow

The Frame plugin has grown with message handlers that expose features of the client that lets the sandboxed html script interact with the federated wiki client in interesting ways.

I will show you a pandemic project that has grown out of workflow automation written as small html scripts stored in Assets and run in Frames.

- http://trails.ward.asia.wiki.org/ - http://seattle.fed.wiki/ - http://thompson.fed.wiki/

Today I will give you a guided tour of these three sites with special attention to the software engineering properties that wiki brings to javascript.

.