Liccium plugins
Last updated
Last updated
Liccium plugins enable the integration of use-case- or industry-specific metadata to declarations or other services provided by 3rd parties to the Liccium app. These plugins enhance the app's generic functionality for creators and rightsholders. With Liccium they can seamlessly embed metadata and bind external metadata to their content, thereby customising the app to their specific needs.
Photographers and photojournalists currently use the IPTC standards to attach technical, descriptive, and administrative metadata or copyright information to their images. With Liccium, they can inseparably bind IPTC photo metadata to their content even if the content has been altered or manipulated, or metadata have been stripped from the content.
With the evolving landscape of AI, there's a pressing need for an application that allows content creators and rightsholders to declare their permissions regarding TDM.
The EU's DSM Directive on Copyright provides a default condition for TDM, but there's ambiguity when rightsholders want to opt-out or explicitly give permission. The TDM·AI protocol is motivated by the need to:
Provide clarity and ease for rightsholders to declare their TDM permissions.
Offer a decentralised, immutable, and verifiable system for these declarations.
Ensure that AI providers and other stakeholders can easily understand and respect these declarations.
Liccium offers a protocol to facilitate machine-readable opt-out declarations for Text and Data Mining (TDM) for AI providers based on the DSM Directive on Copyright 2019/790, Article 4, leveraging the benefits of the International Standard Content Code (ISCC) and Creator Credentials.
The declaration binds a machine-readable declaration to the content by the rightsholder limiting commercial TDM usage.
Using Liccium, users can create a C2PA manifest from the provided metadata and embed the manifest into media asset. The C2PA method stores information directly within the media file. If embedded metadata is removed or inaccessible, the content can’t be checked for authenticity.
That’s why Liccium not only includes C2PA metadata inside the file but additionally creates a separate record of the data outside the file. This record is inextricably connected to the content’s unique fingerprint (ISCC), ensuring the data can still be verified even if it’s removed from the file itself.
