Interesting developments in automatic storyline visualisations. The experimental Mythology Engine was…
“a [BBC] prototype exploring new ways of telling stories on the web. It began as an experiment to bring storylines from Doctor Who to the web. Rather than create a basic page for each episode and character in Doctor Who, the Engine allow[ed] the storyline to be described using an ontology. This storyline can then be presented either in a linear way, mapped to the traditional TV structure of episodes and series, or [extracted] to let you examine a single story arc within a complex narrative, for example. This is particularly interesting when considering the time-travelling escapades of the Doctor. His stories can be viewed at in linear time, or as they are presented in an episode, for example. […] The team demonstrated this as a proof-of-concept by modelling some EastEnders stories and loading them into the Engine with a different visual treatment. There are many remaining challenges: how do you present cliff-hangers or uncompleted storylines without giving away the ending before broadcast, for example? Our colleague, Paul Rissen, investigated this in a follow up project called StoryBox [“which was essentially the next iteration of the Mythology Engine”, says Rissen].
Although someone must be pretty dumb not to be able to follow the plot of Doctor Who — and isn’t one of the pleasures of Doctor Who working out all those extra little fan-bits of who-what-where backstory, afterwards? But as a generative comic-strip software, it sounds interesting.
Another such early automatic story visualisation engine is StoryVisualizer from France.