Bill’s slides are here, and mine are embedded below.

Thanks to Paul for the invite, and to the audience for braving an intermittently (very) wet Manchester evening to spend a few hours discussing Linked Data, the Semantic Web, and related topics; it was fun.

Related articles by Zemanta

• Google Acquires Metaweb To Make Search Smarter (techcrunch.com)
• Tim Berners-Lee Doesnt Seem to Think Linked Data Requires RDF (ironick.typepad.com)
• CubicWeb – The Semantic Web is a Construction Game!: OSCON 2010, The O’Reilly Open Source Convention – O’Reilly Conferences, July 19 – 23, 2010, Portland, OR (oscon.com)
• 15 sessions on marketing and the semantic web (chiefmartec.com)

This podcast was recorded on Friday 16 July, 2010.

I spoke with John Sheridan of the Government’s Office of Public Sector Information (OPSI) back in July of 2009, when this programme was just taking shape. More recently, Talis‘ Richard Wallis recorded a podcast with Richard as data.gov.uk formally launched earlier this year, and his colleague Zach Beauvais followed up with a videocast to explore some uses for the data.

During our conversation, we referred to the following resources;

• ASBOrometer
• Tim Berners-Lee (and my podcast with him)
• Combined Online INformation System (COINS)
• Creative Commons
• Crown Copyright
• data.gov.uk Applications Gallery
• Government Open Data Licence
• The Guardian‘s COINS interface
• IDeA
• JSON
• Linked Data
• Local Government Association (LGA)
• Local Data Panel
• Francis Maude
• mySociety
• National Archives
• Office of National Statistics
• Open Data Commons
• The Open Knowledge Foundation‘s COINS interface
• Ordnance Survey
• OS Open Data
• Public Data Principles (Draft)
• REST
• Rufus Pollock
• Nigel Shadbolt (and my podcast with him)
• SOCITM
• SPARQL
• Jeni Tennison’s recent data.gov.uk blog post
• Tom Steinberg (and my podcast with him)
• Transparency Board
• Treasury
• Where Does My Money Go?

Related articles by Zemanta

• Tim Berners-Lee on Data.gov.uk, open linked data and open standards (radar.oreilly.com)
• Data.gov.uk troupe gets shirty about standards (go.theregister.com)
• Gov 2.0 Down Under: Australia and open government (radar.oreilly.com)
• Some Clarity on Transparency (blogs.talis.com)
• UK Gov’t Spending Details Now Online (news.slashdot.org)
• Maude calls for public choice on open data (go.theregister.com)
• The Government has unlocked the open data safe – now we must open it (blogs.telegraph.co.uk)
• Unlocking innovation | data.gov.uk (data.gov.uk)

Furthermore, ‘Open Access‘ and ‘Repository’ typically go hand in hand. If you support Open Access you need a repository, and if you question the role of repositories you’re in the pocket of evil publishers who want to lock up everything ever written and lease reading rights back to the employers of those who wrote the stuff in the first place.

Nonsense.

Open Access is an important component of today’s scholarly ecosystem. It’s not the only answer, and it’s not perfect, but it does have a significant part to play. Institutions have a role in preserving, disseminating and exploiting the work of their employees, but these are very different tasks that may benefit from different solutions. In too many cases, the repository is by default seen as a preservation mechanism and a dissemination vehicle, and as such it may fail to cost-effectively achieve either aim.

There are some large, well known, and research-intensive institutions where it might be possible to make a compelling argument for projecting a strong institutional image around a single ‘home’ for all of that research output. Never mind, for a moment, that so much research today is the result of inter-institutional collaboration, or that the eminent researcher might wish to take ‘their’ research publications with them as they move from Oxford to Harvard to York during their glittering career.

Alongside those institutions sit a plethora of others where research of equal quality is also being conducted; there just, maybe, isn’t quite as much of it. Bombarded by ‘advice’ and funding, and desperate to keep up with the Russell Group, ever-more institutions blindly join the repository cult and wonder why their new toys do not fill to overflowing with the jewels of scholarly erudition.

As research becomes increasingly data-rich, the whole cycle looks set to repeat. The recently released Panton Principles for Open Data in Science are to be welcomed, but I’ll bet the institutional response will all too often be the commissioning of a ‘data repository’ to sit alongside the ‘publication repository’ they already don’t use.

All of which is a rather long-winded way of introducing the fact that Eduserv’s Andy Powell has asked me to facilitate a breakout afternoon on ‘Policy Issues’ at the Repositories in the Cloud event Eduserv and JISC are holding in London on Tuesday.

“This free event, organised jointly by Eduserv and the JISC, will bring together software developers, repository managers, service providers, funding and advisory bodies to discuss the potential policy and technical issues associated with cloud computing and the delivery of repository services in UK HEIs.”

In a post on 11 February, Andy invited participants to share some of their views ahead of the meeting, and on 19 February he wrote about some of his own thoughts.

Like Andy, I struggled somewhat to nail down a coherent set of thoughts about the issue of pushing today’s repositories into the Cloud. On one level, I wonder whether the vast majority of institutions with small (and relatively low traffic) repositories would see much of a tangible efficiency gain or cost saving by moving off an in-house computer to rent an equivalent Virtual Machine from Amazon, Rackspace, or any of their competitors. If we’re talking about IT systems within a typical university, there are others (email, calendaring, pools of compute resource for research jobs, etc) that appear more immediately compelling for the shift Cloud-ward. Which is not to say that there isn’t a clear opportunity for someone trusted to step into this space and offer a SaaS repository to which institutions might affordably subscribe. Eduserv? Mimas? Edina? The British Library? The National Archives? Duraspace? Any could, and if we’re not ready for something more then at least one probably should.

However, a bolder reconsideration of what repositories are and what they’re for might very well lead to something interesting, sustainable, and perfectly suited for benefitting from Cloud Computing’s strengths.

Why does a paper have to be ‘deposited’ in a repository? Why does a single paper with three authors from three institutions have to be deposited in three separate institutional repositories? Why does that same paper have to be deposited – separately – in the subject repository favoured by scholars in the relevant discipline? Why does the institution’s very reasonable desire to protect, preserve, promote and disseminate its excellence mean that it has to run systems in perpetuity that preserve and permit access? Why do we address the fundamentally different (perhaps even contradictory) problems of access and preservation in the same system? Why can’t the individual researcher easily assemble a view across their publication history, regardless of the institution within which they happened to reside as they wrote each paper? Why don’t the assemblages of papers reflect personal, professional and disciplinary relationships, alongside (or instead of) the contractual accident of employee-employer relationships? Why isn’t the wealth of metadata implicit to any publication (authors, subjects, dates, citations, and more) available and actionable, both inside the repository and far beyond it across the Web? Why isn’t there a tight and active association between the paper and the data from which its findings were derived (something for which Internet Archaeology was demonstrating utility a very long time ago)?

Scholarly papers principally comprise text, augmented by the occasional static image. They’re not big, and they don’t tend to change very fast. In many ways, they represent a fairly easy problem set with which to work. As more and more data becomes key to research in a growing number of subject areas, the problems are set to become far larger and far more difficult. For individual universities to even consider replicating the process by which they all ended up with their repositories of text surely seems madness in this data-rich environment. Even with levels of uptake as low as those seen in too many text repositories, the issues of data management, curation, access and dissemination are too great to be sensibly solved in the institutional machine room. Services like InfoChimps and Amazon’s own Public Data Sets offering show some of the ways that we might begin to work with data at scale. Might we, for example, come to recognise as Amazon has that it’s actually cheaper and quicker to entrust large data sets to FedEx rather than transmit them over the Internet?

‘The answer’ might be some central service for the community, funded by JISC like the Arts & Humanities Data Service (AHDS) of old. Or it might be something different, something nimbler, more responsive, more flexible to individual, institutional, and disciplinary requirements, and something more scalable to new disciplines; institutional support for and use of existing Cloud infrastructures extending far beyond UK Higher Education, aligned with a clear understanding of the separation between preservation and access.

I certainly don’t have all the answers, but I do believe that simply asking whether or not we should move existing repositories to the Cloud is to miss the point. Rather, we should ask what role the Cloud might play in addressing the business requirements to which the institutional repository was our initial – faltering – response. The answer might very well be ‘None,’ but I doubt it.

I look forward to Tuesday’s discussion. I’m not going there to push my personal view that individual institutions frequently shouldn’t be building, running or populating their own repositories at all. I’m going there to facilitate the discussion those in the room want to have, and to learn from their experiences and their perspectives.

Related articles by Zemanta

• Does a Citation Advantage Exist for Mandated Open Access Articles? (scholarlykitchen.sspnet.org)
• Scholarly content and the cliff edge: the place of subject ‘repositories’ (hangingtogether.org)
• Scholarly Communications must be Scalable (downes.ca)
• Beyond Open Access: Open Publishing (opendotdotdot.blogspot.com)
• 57 college presidents declare support for public access to publicly funded research in the US (scienceblog.com)
• Mandelson says academics are ‘set in aspic’ (guardian.co.uk)

And then things went quiet.

Fast forward to 2010, and Siri is back. The back-end technology is faster, more robust, and fuelled by loads more data. Robert Scoble has been amongst those dropping not-so-subtle hints on Twitter for days, and other big names in and around the Valley have also been targeted in a carefully orchestrated programme of pre-briefings and beta invites. That all ends today, as the iPhone app is now out of beta and available this morning from Apple‘s App Store. Versions for Android devices and the Blackberry are coming along close behind, and the company has big plans for building upon what they already have.

I got my hands on the app earlier this month, and put it through as many of its paces as I could from 3,000 miles outside the US market for which the current app and data are optimised.

I’ve written up the results of my play (and my conversation with Siri’s other two co-founders) for ZDNet, and look forward to trying it for real on my next trip to the States.

Related articles by Zemanta

• DARPA’s CALO project, the militaristic Clippy, set to invade iPhones this year (engadget.com)
• The drive and culture behind Siri (vator.tv)
• DARPA Builds Smarter Version of Microsoft’s Clippy (tech.slashdot.org)

Like the BBC, the UK Government and others, they’re interested in the opportunities created by adoption of Linked Data, and will be issuing a call to fund some projects in the space early next year.

As part of the process, I was asked to prepare a short report and some recommendations for activity across the sector.

A draft of that report is now available, and both JISC staff and myself would welcome any comments that you might have before we finalise the document. I should stress – several times – that this document is a draft, and that its recommendations have not been endorsed by JISC.

Earlier this week Flip and I got together on Skype to reprise some of the conversation as a podcast, which is now available.

Production of this podcast was supported by Talis.

My arrangement with Talis concludes with the release of this podcast, so if you want to keep listening to my content you will need to subscribe directly to my feed, either on this site or in iTunes. Talis podcasts continue without me, and you can find their various channels aggregated here.

Related articles by Zemanta

• Is Infochimps’ Aggregated Data a Boon to Researchers or a Privacy Nightmare? (gigaom.com)
• Dear Twitter: Really? Seriously? [Infochimps] (siliconangle.net)
• Infochimps: Share and Sell Your Raw Data (readwriteweb.com)
• DEMO: Infochimps lets users share and sell data (venturebeat.com)
• Infochimps Wants Folks to Monkey Around With Its Data (gigaom.com)
• Twitter Data Dump: InfoChimp Puts 1B Connections Up For Sale (readwriteweb.com)

For various reasons, I was unable to make it to Virginia for the event, but a scan through the presentations from Leigh, Tom Heath (another former colleague), Jordan Hatcher (with whom I worked on earlier iterations of the Open Data Commons license), and Creative Commons‘ Kaitlin Thaney, it looks like they did a great job covering the bases on this critically important aspect of the evolving Data Web.

If we are to encourage the sorts of break-out use of data that Tim Berners-Lee and Tim O’Reilly were discussing at last week’s Web 2.0 Summit, we need to move past the current laissez-faire approaches adopted by too many and ensure that there are licensing regimes in place to enable, facilitate and encourage widespread re-use.

As Leigh’s work demonstrates, we have a long way to go. Only around a third of the current Linked Data projects are explicitly licensing their content, and several of those may be mis-licensing by applying copyright-based licenses such as those from Creative Commons to data not covered by copyright legislation.

With the current state of data licensing, and the reliance of CC0 and Open Data Commons’ Public Domain Dedication and License upon the public domain as a means of overcoming territorial differences, will we find enterprise use of Linked Data increasingly relying upon the more cumbersome tool of contract law… to the detriment of a free and flexible exchange of ideas?

‘Linked Open Data Rights Survey‘ image by Leigh Dodds, shared on Flickr under a Creative Commons license.

Related articles by Zemanta

• ISWC linked data and the law (opencontentlawyer.com)
• Iswc2009 I. (ivan-herman.name)
• CC0 endorsed in Nature opinion piece (sciencecommons.org)
• Linked Data: Interpretants and Interpretation (phaneron.rickmurphy.org)

Have a listen to hear about some of mySociety’s projects, and to learn Tom’s views on the current rush toward greater access to data.

As usual, links to the resources we discuss are available in show notes on the Talis site.

Related articles by Zemanta

• Parliamentary website TheyWorkForYou launches redesign (onlinejournalismblog.com)
• Mapumental: visualise any neighbourhood in the UK by transit times, house prices and “scenicness” (boingboing.net)

Have a listen, and see what you think.