Re: Call for Adoption (CfA) as a Working Group deliverable: "Signature-based Integrity"

This CfC has passed without objection. Thanks for your participation!

I'd suggest, though, that instead of publishing a separate document for
this feature, we should use approval of this CfC to justify folding the
patches suggested in
https://wicg.github.io/signature-based-sri/#monkey-patch-sri into the
editor's draft of SRI once it's published as a working draft.

As SRI's editor, does that sound reasonable to you, Freddy?

-mike


On Wed, Mar 12, 2025 at 3:42 PM Simone Onofri <simone@w3.org> wrote:

> Dear Group,
>
> This is a Call for Adoption (CfA) as a Working Group deliverable of
> "Signature-based Integrity”
>
> During the meeting of 2025-02-19, the participants had already agreed to
> the adoption:
>
>
> https://github.com/w3c/webappsec/blob/main/meetings/2025/2025-02-19-minutes.md#reviving-require-sri-for
>
> The specification is available for inspection here:
>
> https://github.com/WICG/signature-based-sri
>
> The GitHub Issues lists are currently here:
>
> https://github.com/WICG/signature-based-sri/issues
>
> In response, please state one of the following:
>
> * I support the adoption of "Signature-based Integrity".
> * I object to the adoption of the specification due to Issues filed in
> open bug <#number>
>
> If there are no further objections, we will confirm the decision by March
> 19, 2025, at midnight Pacific time.
>
> Note that if the proposal is adopted, the specification will be marked as
> an Editor's Draft (https://www.w3.org/standards/types/#x2-3-editor-s-draft),
> which does not imply endorsement by W3C.
>
> Thank you,
>
> Simone
>
>
>