The Aust Gate

The New York Times had a piece on digital piracy of books and the contrasting views which was picked up by Slashdot. Starting out from the anti-piracy view, it does note that bestsellers are often the most pirated books which backs up Cory Doctorow’s assertion:

“I really feel like my problem isn’t piracy,…It’s obscurity.”

His own position of publishing free digital copies at the same time as the paid for “treeware” version comes out has helped the all important word of mouth get about his books. He has built a passionate community around his work who both download and pay for books. Through his acknowledgement that there will be cheap skates who will only download the free version but encouraging the rest of the community to be involved in discussing  and remixing his work, his latest novel stayed in the NY Times bestseller for seven weeks.

There must, however, be an acknowledgement that the creator has rights to the work. Doctorow uses Creative Commons to protect his original work but to allow users certain rights to do something with the work. The Open Definitions also do this. Through a simple transformation of rights as open shops rather than closed, i.e. changing to saying what you can do, rather than what you cannot, could change publishing and how it reacts to piracy.

So perhaps publishers need to accept that there will always be a certina amount of it going on. However they should not see piracy as open (it’s not and never will be). The challenge, I believe, for publishers is how to digitise and make available works to a community and allow the community to do things with the books and find new markets and models that way.

The transition would be rough and mistakes made but they need to happen. Publishing needs to learn the lessons of iTunes rather than seeing the digital world as Napster.

It would be great to link into publisher versions of books to create citations or from which to construct models in blogs and wikis using community licenses. It would allow for publisher works to be re-used, ideally be open but perhaps operate on micro-payments based on traffic or level of citation, and for the user to have some authentication (or not depending on publisher) of the data as coming from a reliable source.

Just a thought but the time is ripe for change and experimentation.

As part of the Open Milton project, I’ve been thinking about the place of  XML in it. Over Christmas, I wrote a small XSL transform using the Bosak XML Shakespeare files. Rufus took Anthony and Cleopatra and,  using Latex (I gather), created the Open Shakespeare Anthony and Cleopatra pdf.

At one level, this is yet another version of Shakespeare. True.

But think of the possibilities. A user could happily generate their own version of the play (for instance using it in a class) or create their own annotated version for that class and not have to worry too much about losing the text / book as it can be printed and shared widely. Communities of interested parties could be pointed towards a website where they could download the material either in final form or just get the XML to use it.

To some extent this is also about embracing a standard and making it common outside of academia and closed repositories. It would appear to be easier to share texts and make use of them if we know what the coding is going to be rather than have to wait for the download to complete before taking a look.

To that end, I’ve started a contribution (currently in prototype) to create a small parser so that we can start transforming text files into TEI (Text Encoding Initiative) Lite format. Granted it is at an early stage but the initial results show some promise and are encouraging (well for me at least).

As per Open Milton/Shakespeare, I’ve been using Python to do this with the minidom package with regular expressions. The next step will be to split out the script into  reader, parser and writer. I’ve been concentrating on drama but prose and verse have their own vocabularies so the parser will probably need to be split into three, each bit concentrating on a form and calling methods from the writer as appropriate.

I’ve recently been working on a plugin for Wordpress to set up each post as RDF enabled using OAI_ORE and SWORD which I presented to the Oxon SWIG on Tuesday.

The Berlin Declaration of Open Access states the work should be free and also that it should be deposited in a repository. This seems to be about papers and articles but what about the use of blogs, wikis and even perhaps Twitter (might be a little stretch at the moment but I could see it being used)? That suggests a layer of data which could and, where practical, should be being archived in repositories as they are being used as open Laboratory notebooks with links to data.

The plug -in that I’m working on is designed to make blogs readable in RDF for the purposes of repository deposit.

At the moment, I have written a channel which lists all the blog’s posts (using the ?repository=site ) as well as individual post’s in RDF ( using ?repository=post&repository_id= postid). I’ve been using the SIOC exporter as the base model but I’m looking at using skos to get the categories and tags out of the Wordpress (and trying to leverage folksonomy through that). Next will be to look at the comments and trackbacks and using the isReferencedBy to export incoming links.

I’ve put this onto KnowledgeForge as its own project.