We’ve been doing more work on the Open Shakespeare project with the result that a new version (v0.4) is ready for release (full details including the Changelog can be found below). For those unfamiliar with the project, Open Shakespeare has two basic aims.

First, to provide a simple but compelling open knowledge exemplar — and to show some of the complexities in producing open knowledge. For example, simply getting a good open set of Shakespeare’s work involves some degree of effort: Project Gutenberg has 4 versions of most of Shakespeare, two of those four versions are copyrighted (and all Gutenberg texts have Gutenberg headers and footers that need to be removed). Next those out-of-copyright texts you can find are not always ‘socially open’, that is easy to access and download (particularly in an automatable manner). Finally, the texts that are available aren’t necessarily technologically open so work has to be done to put them into open, machine processable formats (plain text/xml etc).

The second basic aim of Open Shakespeare is to illustrate real-world knowledge packaging — all the Open Shakespeare material is available in a single (python) bundle that can be automatically downloaded and ‘installed’. Furthermore, every effort is made to make the material as reusable as possible and there’s a full programmatic API together with ancillary tools: our main aim is not to provide another Shakespeare website but to provide the tools and material to allow others to build their own applications and websites. While we have created a simple site using the material we’ve gathered its purpose will be to showcase what can be done and to encourage others to use our work in ways we haven’t even considered.

Release Announcement

A new version of open shakespeare is out. Get it via the code page:

http://www.openshakespeare.org/code/

Changelog

• Annotation of texts (js-based in browser) (ticket:20, ticket:21) (http://www.openshakespeare.org/2007/04/10/annotation-is-working/)
• Switch to unicode for internal string handling (resolves ticket:23: some texts breaking the viewer)
• Add functional tests for the web interface (ticket:11)
• Substantial improvements to speed of concordance (ticket:22) (http://www.openshakespeare.org/2007/01/03/improvements-to-the-concordance/)
• Switch to genshi templates from kid
• Switch to plain WSGI from cherrypy

Outstanding Issues

• Annotation cannot handle long texts because of javascript performance issues

About Open Shakespeare

A full open set of Shakespeare’s works along with anciallary material, a variety of tools and a python API.

For more information see the about page:

http://www.openshakespeare.org/about/

Get involved: http://www.openshakespeare.org/participate/

Mailing list: http://lists.okfn.org/mailman/listinfo/okfn-discuss/

Related posts:

1. v0.3 of Open Shakespeare Released We’ve been doing quite a bit of work on the Open Shakespeare project (which we’ve mentioned before). Given that a brief search on the net turns up many sites about Shakespeare and lots of online copies of shakespeare’s texts you...
2. Annotation is Working! After another push over the last few days I’ve got the web annotation system for Open Shakespeare operational (we’ve been hacking on this on and off since back in December). To see the system in action visit: http://demo.openshakespeare.org/view?name=phoenix_and_the_turtle_gut&format=annotate Quite a...
3. Open Shakespeare v0.2 With a little bit of free time over the last couple of weeks I’ve managed to do some more work on open shakespeare. The new version (v0.2dev) is up and running on the site: http://openshakespeare.org/ (formerly http://demo.openshakespeare.org/). NB: concordance only...