One of the most contentious areas of the Hargreaves proposals is the Digital Copyright Exchange.
Some critics claim that it’s, for example, “not well organised, nor is it always very clear”. Well, I’m not surprised – a system specification wasn’t part of the brief. You don’t get into the database design before the project gets the green light (unless, of course you’re the NHS).
What I’ve tried to do here is, I’m afraid, a rather technical document, outlining how this proposal could work in practice.
So what would the DCE look like ?
Firstly, this isn’t going to be a single database. The different media types have – as Hargreaves identified – different dynamics, in terms of production, consumption and replication. Most photographs are created by individuals, for example, and may be created for individual or collective consumption. They may be created under commission, or on spec.
Most feature films, OTOH, are created by large studios. And a number of individuals may have a “slice” of the rights – the director and leading actors may well earn “points” of the box-office. Those rights may be different for different distribution media – DVD sales, cable or network broadcast may each have a unique formula.
As an aside : most TV/media companies will already have complex systems to manage that side of the equation, so they should already have a means of referencing their intellectual estates.
Books typically fall in between, although again there are new media implications (eBooks, Audio Books) which may carry different rights (the actor reading the book, for example).
Music is different again with samples from one track often being remixed into a derivative track. The music industry – which of course contains relatively few major players – seems to have found a way to measure (and award royalties for) the rights between each of many samples in a track.
… And there will be similar unique requirements for other IP, such as games and software.
So Hargreaves – if I read it right – recommended that each medium has its own repository. In some cases (section 4.22) he sees that the UK element may be part of a global repertoire database.
Critically, however, he identifies that these repositories would be a “network of interoperable databases to provide a common platform for licensing transactions” (my italics).
The interoperability is important – there should be a common language to define the license transactions. From an automation perspective, it would mean that software – particularly to search for and evaluate licenses – would need defining only once. More importantly, upgrades would involve only once development cost.
Won’t this be very complicated ?
Of course. And Hargreaves identifies that the design shouldn’t be left to government – who don’t have the best track record in commissioning software in any case.
Again, critically, he identifies that any solution must be “open” and “standardised”. Well, goody, that leads us into the realm of XML. This is how a huge amount of the web is driven now. For those who aren’t familiar with it:
- It’s an open technology, that can be accessed through development languages, spreadsheets and web browsers.
- Subsets – to perform specific purposes – can be defined. So there’s a subset for companies to deliver their accounts to the Stock Exchange. The same format is used to submit Tax Returns. There’s another for Google to find the pages in your website (although it then ignores much of the content) – and this has a subsubset for images within the pages.
- Photographers may be familiar with Adobe Photoshop’s .xmp “sidecar” files. Yup. That’s XML again.
So the technology’s there. What is needed is the definition of what the content should look like. This is the bit that geeks love – at least, a special kind of geek – a Data Analyst. If you think this may be geek chic, take a look at the Dublin Core work.
These guys start by working out a “schema”.
After a few consultation drafts, the schema is proposed as a standard and (if it doesn’t break) eventually gets adopted.
There’s an example of this going on in your browser updates right now – as HTML5 functionality is gradually integrated. Different browsers (Firefox, IE, Safari etc.) are implementing these features at different speeds.
Anyhow… So yes, it’s complicated, but it’s not rocket science. (Although NASA does use XML as well ..)
If it’s complicated, won’t we lose control ? Will we be left out ?
I suspect that this maybe at the heart of some of the concerns.
The nice thing about using XML is that it can be extended as new conditions arise. So if a new class of rights arises, then that should be capable of definition within the standard.
And that means that the software houses can build software to deal with it.
So in the same way that Lightroom and iPhoto can upload to on-line services such as Flickr, they would (within a short space of time, and most probably through a plugin) be able to upload image reference data to the DCE. This may or may not include your metadata tags, so the images could be searched – the IPTC taxonomy (also, of course, XML) already defines content for many media.
There may even be open-source projects initiated to perform some of the rights management functions. And I’m sure there’d be an app for it.
So you (as a creator) would be have your copyright covered and (quite possibly) the capacity to reach a greater market, without having to do much more than at present.
IPTC also defines the creator and copyright holder (yes, I know these get stripped but the would be recorded on the DCE).
The big gap to be defined is probably the license terms. Again, this need not be difficult – in broad terms, you need to recognise that a license has been sold. But these have parallels in English Property Law.
- There may be constraints about the uses to which a photo can be put – no model release may mean no commercial use. In the same way that a covenant may limit a propert to residential use only.
- There may be an exclusive license for a period of time – paralleling a leasehold tenancy. Or a perpetual licence (effectively, the sale of a leasehold)
- Or there may be many different “tenancies”, as licensees are each able to reproduce the content for different periods and rents (and, in fact, different media)
All of these rights models are capable of being defined and modelled – and the rights recorded. Again, there’s an opportunity for software houses to help copyright holders to manage the licenses on their “property” – possibly including interaction with the DCE. Or a web front-end could allow manual recording of licenses.
Oh … and using XML, you aren’t limited to a single, fixed-length record. You can have multiple records (for multiple licenses), and not all fields have to be populated.
So all of this would save time in automating searches for those seeking to buy rights – if they wanted exclusive rights, then they could exclude images where a licence was already granted.
Similarly, searches could ignore those images where the content had already been licensed exclusively.
So … that’s how I read Hargreaves talk of removing “Deadweight administrative costs” (1.11). Not just the metadata entry (where, yes, the rights holder may have to do a little bit more work), or the requirement to record details of licences (although that could actually add value to creators*). But the time needed by the consumers of the content to track down the rights holder and agree a fee.
And that means that the real pressure is likely to fall on the Image libraries, who will find it difficult to justify their commissions, They will be competing with more agile competitors, who could have access to (if not exclusive licenses to) a massive pool of content.
[Edit 4/7/2011 10:30]
Moving On …
I can understand that people are concerned about this, but there are huge parts that have yet to be defined. And yet we know that they can be defined. I feel that creatives (or their representatives) need to participate in this process to get the solution we need, rather than assuming some master plan.
The difficult part to get through is that, as Hargreaves has said, that one size won’t fit all. So don’t pick on the bits that may be appropriate for music (or books) and extrapolate it to photographs. There’s a real risk that – like the blind men describing an elephant – we think that the DCS should only reflect what we want.
But each sector needs to define its own needs.
So, rather than worrying about Hargreaves’ agenda, we need to start a debate, so we can make sure the data structures have the right shape. Or the IPO will end up parachuting in something unworkable.
* Adding value to creators : If the DCE structure allows creators to record some of their own data, then there’s an inventory of IP assets – potentially in different (web) locations.
And if customers can enquire, then they won’t need to bother you with a question on their rights.
And there’s the potential for additional use licenses to be automated. No negotiation needed – the extension could be agreed, the money goes straight into the bank, and the license is recorded on the database.
There are actually about three business opportunities in this paper. I really must activate my Chennai development team …