[{"author": "Roy Williams", "text": "<p>I could envision limiting types of content written on a product.  The suppliers of evidence of a build is not the world</p>", "time": "2023-06-19T15:13:57Z"}, {"author": "Roy Williams", "text": "<p>In a situation where there is public SCITT, and each organization has a \"edge\" instance of SCITT, the writers to that edge instance are under the control of the organization.</p>", "time": "2023-06-19T15:15:10Z"}, {"author": "Neal McBurnett", "text": "<p>I suspect we will want to see feeds which simply repeat statements from other feeds, without necessarily agreeing with content. i.e. \"this is worth considering but we take no position on the truth of it\". They can surface potentially useful content from less-well-known feeds.</p>", "time": "2023-06-19T15:21:07Z"}, {"author": "Raymond Lutz", "text": "<p>@Roy, I did respond to your comments.</p>", "time": "2023-06-19T15:25:18Z"}, {"author": "Neal McBurnett", "text": "<p>Spam causes workload problems not just for the transparency service itself, but also for relying parties.</p>", "time": "2023-06-19T15:35:45Z"}, {"author": "Raymond Lutz", "text": "<p>I believe we should start with the concept of a strict model, but allow the lower layers to handle both strict and a free-for-all model. But honestly, for supply chain control, we need a strict model for ow can submit.</p>", "time": "2023-06-19T15:37:28Z"}, {"author": "Orie Steele", "text": "<p>You only need to submit the author's signature over that payload.... not that file.</p>", "time": "2023-06-19T15:49:10Z"}, {"author": "Raymond Lutz", "text": "<p>yes, let's schedule discussion of this at hackathon as it provides real case to sink our teeth into.</p>", "time": "2023-06-19T16:00:05Z"}, {"author": "Neal McBurnett", "text": "<p>Ray, what is a strict model?</p>", "time": "2023-06-19T16:03:55Z"}, {"author": "Neal McBurnett", "text": "<p>And how would relying parties discover other statements they care about?</p>", "time": "2023-06-19T16:04:49Z"}]