My short, 4 min intervention is available, now:

FAIA – FAIR AI Attribution: Flagging Synthetic Media Using Open Standards

webcast.wipo.int/video/WIPO_I...

Follow @faia.io and FAIA.liccium.com

As a short introduction to the project, Jan Ainali from Wikimedia Sweden has created a superb and lovely video that you should definitely watch. You will see the first ISCC bot in action :)

www.commonsdb.org/blog/connect...
2/2

TDM·AI is a protocol that lets creators and rightsholders express preferences for text and data mining (TDM) for their digital content: tdmai.org 4/4

TDMAI.org can also help AI developers meet transparency and compliance requirements under the EU AI Act and Copyright Law. 3/4

We explained how registry-based opt-outs using ISCC fingerprints can provide creators and rightsholders with a persistent and reliable way to declare their rights and reservations with regards to training models and applications of generative AI. 2/4

Funded by @ec.europa.eu, #CommonsDB creates a prototype registry for Public Domain/openly licensed works.

Driven by Open Future, the initiative is a joint effort with @liccium.com @europeana.bsky.social @wikimediase.bsky.social and @ivir-uva.bsky.social.

Learn more: www.commonsdb.org

Third parties, such as AI model providers, can identify the user intent only by having access to the media assets by generating the ISCC, matching nearest neighbours and resolving the manifest. – We presented our approach at the IETF conference on AI control.

How it works: ISCC codes are generated from text or other media assets in blobs, the user intent is added to form a manifest, which is digitally signed and publicly declared on federated registries. Verifiable credentials bind did:key, did:plc and other attestations to provide proper attribution.

With @liccium.com we are working on a way to bind rights and metadata ("intend") to the actual content, resp. The content-derived ISCC (ISO 24138). These declarations may include AI preferences: tdmai.org. Your RFC could becime a Liccium plugin.

We also use did:web as one verification step for issuers of VCs (creator credentials) --> docs.creatorcredentials.com

As creator or rightsholder you can use it to digitally sign your original works --> Liccium.com

A publisher/repository could bind this information/update to the ISCC and make a public declaration. Then it this update for one version could potentially reach a user for all versions.

Thanks for your interest. I would not claim that @liccium.bsky.social prevents illegal misappropriation. However, it allows to inseparably bind your rights and licences to your content. So e.g. your creator name and copyright notice can't be stripped away (without using watermarking).