Repository navigation
Does an entry name an algorithm or a deployment? #86
Description
The spec defines alg as identifying "the soft binding algorithm and version of that algorithm". The list now holds two kinds of entry:
- One algorithm, several entries. Meta's open VideoSeal model is entry 30 (
com.aiwatermark.videoseal.1) and entry 50 (me.reconize.videoseal.1), and Add be.immostory.videoseal.1 (entry 54) #84 adds a third. Are those entries interoperable? - One entry, several algorithms. 19 of the 53 entries declare more than one media type. Entry 3 (
io.iscc.v0), for example, covers separate image, audio, video and text algorithms under one identifier, with a header in each value saying which one produced it. The list does not say whether, or how, a validator can tell which algorithm produced a value.
Which should an entry denote?
- An algorithm, with deployments listed as resolvers in
softBindingResolutionApis. - A deployment, with an optional field such as
basedOnnaming the underlying algorithm. - Either, with each entry saying which it is.
This is not an objection to #84; the question applies to merged entries too.
Activity
jcollomosse commentedon Oct 14, 2026
A deployment, more specifically a deployment of a C2PA Manifest Repository. Indeed there are several examples of repositories using the same open source technologies for watermarking - some more overtly (based on the registry name) than others.
titusz commentedon Oct 14, 2026
That raises questions on the model and on its governance.
If an entry is a repository deployment:
typeand Trufo serves a watermark and a fingerprint?algin a soft binding assertion then identify a repository rather than the algorithm that produced the value?If an entry is an algorithm:
Either way:
softBindingResolutionApis, or only with the entry owner's consent?