Atul Tulshibagwale

A few comments / observations: 1. If it's not a single document, how will all such documents be organized? 2. The initial issue talks about event versioning, but the detailed...

@FragLegs , what is the status of this issue?

Since this event is already in use by a few companies, how should we address this concern such that we don't break their implementations?

This was intended to be done using the "stream updated" event. But now I see that the Stream Updated event specifies that the subject should always be the Stream ID....

@appsdesh what is the status of this issue? Do the spec changes in the run up to ID-2 fix this?

Thanks, I have created this issue: https://github.com/cncf/tag-security/issues/1359 On Thu, Aug 29, 2024 at 12:24 AM Karena Angell ***@***.***> wrote: > @tulshi please submit a presentation issue > > to give...

> [@tulshi](https://github.com/tulshi) please [submit a presentation issue](https://github.com/cncf/tag-security/issues/new?assignees=&labels=usecase-presentation%2C+triage-required&template=presentation.md&title=%5BPresentation%5D+Presentation+Title) to give an overview of the project to [TAG Security](https://github.com/cncf/tag-security/) Hi @angellk , FYI we had our presentation today in the Security TAG.

Thank you for the amazingly smooth decision process! I look forward to the onboarding. Atul On Tue, Jan 21, 2025, 7:01 AM Bob Killen ***@***.***> wrote: > Congrats! > With...

This can be a change to the SSF spec, where we add recommended language about any additional data that needs to be sent in an event SHOULD be sent using...

I'd like to understand why this should be in the CAEP / RISC specs versus being in the SSF spec. I'm thinking the "event_data" field is something we will need...