Re: Google opening the door to a discussion about AI opt-out

Expanding on Leonard's point, not only is it important to recognize that
the content owner might not always be the same entity that owns, manages,
or controls the website where the content is shared, especially in cases
like content distribution on social media. It is a necessity that the
declaration is bound to the content and not the location where the content
is published.

Furthermore, a critical consideration is whether the entity making a claim,
such as an opt-out, is both identifiable and possesses the legal authority
to enact that claim.

The use of digital signatures and/or verifiable credentials ensure that
declarations are verifiable and facilitate certified and accurate
attribution (in a scalable and machine-readable way) – which currently is
supported by the C2PA system and ISCC declarations, externally inseparably
binding the opt-out to the content-derive Identifier.

With best regards,
Sebastian






On Mon, 30 Oct 2023 at 03:40, Leonard Rosenthol <lrosenth@adobe.com> wrote:

> I also attending the webinar and am glad to see Google getting into the
> act and doing so by taking input and wanting to work through a standards
> process…All good!
>
>
>
> The current problem with the robots.txt direction is the same as the
> current TDM specification – which is that it assumes that the owner of the
> content also owns/manages/controls the web site on which it is hosted.
> That may help the professional publisher who maintains their sites, but
> it’s not helpful for the average user putting their content up on social
> media, stock image services, etc.
>
>
>
> Leonard
>
>
>
> *From: *Laurent Le Meur <laurent@edrlab.org>
> *Date: *Sunday, October 29, 2023 at 3:06 PM
> *To: *public-tdmrep@w3.org <public-tdmrep@w3.org>
> *Subject: *Google opening the door to a discussion about AI opt-out
>
> *EXTERNAL: Use caution when clicking on links or opening attachments.*
>
>
>
> On Thursday, 26/10, the Google "The AI Web Publisher Control Development
> Team" has organized a first webinar (not a discussion, a presentation)
> "about developing machine-readable means to provide web publisher choice
> and control for emerging AI and research use cases."
>
> I listened to the webinar, and I hope some of you could participate too.
>
> This is the first time an AI Actor opens the door for discussion, and this
> is a big one.
>
>
>
> The team seems open to standardizing a method with a standards body - they
> are considering working with the IETF.
>
>
>
> During the call, they developed the different issues to be solved:
> alignment of the different existing options for blocking crawlers,
> transparency of the ownership and purpose of crawlers, the granularity of
> the access control, with the notion of a taxonomy of crawl purposes (ex.
> "search engines" "generative AI applications"), and how to incentivize the
> adoption of shared standards.
>
>
>
> In summary, these notions are crossing our current interrogations and it
> is time to discuss them also in this group.
>
>
>
> The Google team seems inclined to use an evolution of robots.txt for that..
> They seem ready to add lots of semantics to its current basic model. They
> didn't speak about robots tags, which should be added to the discussion.
>
> Personally, I see no problem moving from our current implementation of
> this tdmrep.json file to the good old robots.txt IF the semantics of the
> latter evolve.
>
>
>
> The Google team is now releasing a questionnaire. I received a password
> for accessing it. Please consider joining this effort, from this blog post
>
>
>
>
>
> A principled approach to evolving choice and control for web content
> <https://blog.google/technology/ai/ai-web-publisher-controls-sign-up/>
>
> blog.google
> <https://blog.google/technology/ai/ai-web-publisher-controls-sign-up/>
>
>
>
> and form
>
> AI Web Publisher Controls Mailing List Sign-Up
> <https://services.google.com/fb/forms/ai-web-publisher-controls-external/>
>
> services.google.com
> <https://services.google.com/fb/forms/ai-web-publisher-controls-external/>
>
> [image: favicon.ico]
> <https://services.google.com/fb/forms/ai-web-publisher-controls-external/>
>
>
>