demoday

April 9, 2014

Since February I have been doing some outreach about StructuredStories and have come to realise that I need to communicate more clearly about the technology. I am therefore providing two related guides – one in the form of a video demonstration of the prototype, and the other in the form of an informal FAQ document.

The video demonstration is quite extensive – about 1 hour – and my goal has been to replicate what an interested layperson would experience if I were demonstrating the prototype to them personally. I provide lots of commentary, including brief introductions to knowledge graphs and to FrameNet, and I apologise in advance for butchering some of these descriptions in attempts at simpler explanations. The video is on YouTube – I recommend that you view it in High Definition mode. The link is here:

A Demonstration of the StructuredStories prototype.

[IMPORTANT!: The link above is a video demo of the *proof-of-concept prototype*, not of the beta product, and it is intended for those interested in the technical background behind Structured Stories. If you want a demo of the beta product then either get in touch or wait until it launches in mid-October, 2014.]

The Frequently Asked Questions document is loosely based on questions that I receive while demonstrating and talking about the technology, and I intended for this document to accompany the demonstration. I suggest that you read this document first, then decide if you want to view the 1 hour demo. The FAQ document is in PDF format and is linked here:

StructuredStories – Frequently Asked Questions

The StructuredStories project is now in a new phase. I have decided to focus my attention on the specification and architectural design of a ‘version 1’ product, and therefore to place less emphasis on the prototype except for experimentation and communication. This will increase the time until I can release a publicly-accessible beta product, but will hopefully result in the creation of an enduring suite of technology. The prototype has largely served its purpose. It works.