Why it Matters

The House Judiciary Subcommittee on Courts, Intellectual Property, Artificial Intelligence, and the Internet is convening on June 30 to examine how intellectual property frameworks designed four decades ago are holding up in today's digital economy.

The internet is entering middle age, and the legal structures governing copyrights, patents, and content distribution were built for a different era. This hearing will surface tensions between legacy media companies fighting to protect existing revenue models and tech platforms operating under rules written before their business models existed.

How Congress treats IP on the internet will reshape everything from what you can watch online to how creators get paid to whether platforms face liability for user-generated content. The hearing comes as the Supreme Court grapples with massive copyright damages in cases like Cox Communications v. Sony Entertainment, where justices were described as deeply skeptical of the figures being sought.

Lobbying Pressure

The subcommittee has invited testimony but specified no particular legislation to address, although the hearing occurs amid significant lobbying activity. Fox Corp. has been a sustained presence in Washington on these exact issues, filing disclosures totaling more than $4 million across the past year and a half. The company has lobbied specifically on copyright and content carriage issues, Section 230 of the Communications Decency Act, and online privacy matters. The American Gaming Association has also invested heavily, spending $1.34 million in the same period on similar matters.

The timing reflects a broader reckoning in Congress about whether 40-year-old IP frameworks can survive in an era of streaming, AI-generated content, and platform liability questions. Rep. Darrell Issa of California chairs the subcommittee, and Rep. Hank Johnson Jr. of Georgia is the panel's ranking Democrat.

Access the Legis1 platform for comprehensive political news, data, and insights.

Spot something wrong? Report an issue with this article