Certainly. I'll turn to the Conductor question first. Conductor is a software solution that we've developed for internal purposes over the past five or six years. It does everything from ingesting the deals that we use when we enter into a new agreement with a writer or we purchase a catalogue.... All that information goes into Conductor. All of the works that are part of that deal are populated into that software. It takes care of ensuring that the works are properly registered around the world and with all the various societies, including SOCAN and its counterparts.
Most importantly, it pulls in the data that we receive from hundreds of different service providers, collective societies, and rights management agencies around the world. As you can imagine, that data doesn't always perfectly align. In fact, I would say it mostly doesn't. Our software works to conform that data, so that we can properly match it and ensure that we're not sitting with massive pending lists of unmatched royalties. It essentially ensures that we're distributing royalties accurately to our rights holders and that we're not missing anything.
That's the essence of what that software does. It sort of takes everything from the deal side all the way through to the user side and pulls all that data into one place. It does it very effectively. That's something we've developed over the past several years and it's been very helpful. Obviously, as part of the move to digital, the challenge we face is in data and ensuring that the data can be processed effectively, that royalties don't get missed, and that the reporting we receive is complete and accurate.
As for the move to digital, and the challenges, and what the committee and the government can do for us.... It goes back to the recommendations that we've all made. It's to ensure that, at the end of the day, we have the leverage we need, as creators and investors in creative output, to negotiate fair value for our rights. Essentially, that means revisiting some of the exceptions that were introduced in 2012.
Even the charity exception that Mr. Daigle mentioned is an example of how there's a slippery slope when you introduce user rights in the form of exemptions, where they're open to interpretation. They can be misinterpreted or applied in a way that doesn't necessarily reflect the original intention. I think that's what needs to be done here with the exceptions that we've identified, to ensure that we have the leverage that we need as rights holders to negotiate fair value for the use of our property.