
A rushed compulsory licence could undermine copyright safeguards, distort royalty flows, and expose India to international trade challenges, while also stifling trust in AI development.
India’s policy debate sits at the intersection of rapid AI growth and evolving copyright law. The DPIIT’s hybrid licence model mirrors global attempts to balance innovation with creators’ rights, yet it emerges amid high‑profile litigation like ANI Media v. OpenAI that is still defining what constitutes lawful dataset acquisition. By proposing a blanket payment structure, the Working Paper seeks certainty, but without a factual record, it risks codifying assumptions that courts may later overturn, echoing past missteps such as the U.S. Music Modernization Act’s unintended ambiguities.
A core challenge lies in the definition of “lawfully accessible” content. ARI’s commentary stresses that developers should bear the burden of proof, supplying auditable provenance for every training datum before qualifying for the licence. Without standardized metadata—ISBN, ISRC, ISWC—traceability collapses, making royalty distribution speculative. Moreover, the proposal overlooks personality and identity rights, an area where Indian courts are increasingly protective, especially regarding synthetic voice or likeness replication. Embedding independent audit rights and persistent identifiers would transform a theoretical payment scheme into a enforceable framework.
If calibrated correctly, the licence could spur domestic AI investment while preserving the creative economy. However, an overbroad or low‑rate structure may violate the Berne Convention and TRIPS three‑step test, inviting WTO disputes and eroding national treatment principles. Clear territorial scope, treaty‑aligned rates, and robust enforcement mechanisms are essential to avoid a boomerang effect that harms both foreign and Indian creators. Thoughtful, evidence‑driven legislation can thus deliver the promised speed without sacrificing legal certainty or artistic incentives.
Comments
Want to join the conversation?
Loading comments...