Development
The European Parliament's resolution on copyright and generative AI entered the Official Journal on 26 August, five months after Parliament adopted it on 10 March.
The text calls on the European Commission to propose transparency and source-documentation measures for copyright-protected material used by general-purpose AI models and systems placed or made available in the EU. For continuous crawling connected to inference and retrieval-augmented generation, Parliament asks for identifiable crawlers and detailed crawling records while acknowledging trade-secret and confidential-business-information concerns.
The resolution also recommends a sector-based voluntary licensing role for EUIPO, asks for an assessment of the current EU copyright framework, advocates fair and proportionate remuneration mechanisms, and calls for clearer treatment and labelling of purely AI-generated content. It separately addresses non-consensual replicas of personal characteristics.
Why it matters
The text points toward an evidence problem. Rights holders often cannot see the records held inside a model provider or its suppliers. Product teams may rely on datasets, model versions, crawlers, rights reservations, and vendor representations that are documented in different systems or not documented at all.
A useful readiness test is simple: which training sources, crawler identities, licence decisions, rights reservations, model versions, and complaint records could the organization produce today? Which claims depend on information held by a vendor? Who owns the gap when that vendor cannot supply it?
The resolution also preserves important distinctions. Copyright, remuneration, personality rights, labelling, and deceptive replicas can intersect, but they are not one legal category.
What to watch next
This is a non-legislative resolution. Publication in the Official Journal does not turn its requests into binding law, amend the CDSM Directive, create a new licence, or establish a crawler registry.
Policy coverage should keep three columns separate: what current law requires, what Parliament has requested, and what a later Commission proposal or legislative act actually changes. Any later proposal or enacted measure must be assessed separately from this resolution.
Treating the resolution as law would overstate it. Ignoring the evidence direction until law changes would leave product teams late.