[{"author": "Orie Steele", "text": "<p>hello</p>", "time": "2023-08-28T15:05:33Z"}, {"author": "Hannes Tschofenig", "text": "<p>Hi Orie</p>", "time": "2023-08-28T15:06:31Z"}, {"author": "Dmitri Zagidulin", "text": "<p>hi everyone!</p>", "time": "2023-08-28T15:07:17Z"}, {"author": "Orie Steele", "text": "<p>New draft that we hope will help the API progress faster: <a href=\"https://github.com/ietf-scitt/draft-birkholz-scitt-scrapi\">https://github.com/ietf-scitt/draft-birkholz-scitt-scrapi</a></p>", "time": "2023-08-28T15:07:18Z"}, {"author": "Raymond Lutz", "text": "<p>where is slack channel?</p>", "time": "2023-08-28T15:08:33Z"}, {"author": "Orie Steele", "text": "<p>we want a structure for the feed.</p>", "time": "2023-08-28T15:37:51Z"}, {"author": "Orie Steele", "text": "<p>One example of a \"standard feed\" we might support would be \"issuer: information... related to authentication keys...</p>", "time": "2023-08-28T15:43:56Z"}, {"author": "Orie Steele", "text": "<p><code>/iss/:iss/jwks</code> etc...</p>", "time": "2023-08-28T15:44:42Z"}, {"author": "Orie Steele", "text": "<p><code>/iss/jwks?iss=did:example:123</code></p>", "time": "2023-08-28T15:45:28Z"}, {"author": "Orie Steele", "text": "<p>etc.</p>", "time": "2023-08-28T15:45:33Z"}, {"author": "Orie Steele", "text": "<p>\"feeds are not for only public information\"</p>", "time": "2023-08-28T15:45:56Z"}, {"author": "Orie Steele", "text": "<p>a feed is an endpoint that can have whatever security policy that the server wants to apply.</p>", "time": "2023-08-28T15:46:17Z"}, {"author": "Jon Geater", "text": "<p>I would agree with Orie about the URL being the most likely requirement for feed identity structure. The question we need to answer in order to minimise work in this WG and also be useful for systems built on SCITT is to decide what that URL points at. Is it a web page with visual content? Is it a REST endpoint in some TBD SCRAPI entry? Is it _exactly_ the same as the ID passed in the header of a statement submission? Any of these and more have benefits over the other but we shouldn\u2019t encourage different implementations making different choices as it won\u2019t work well for client integrations</p>", "time": "2023-08-28T15:48:16Z"}, {"author": "Orie Steele", "text": "<p>the caller can construct the transparency statement after they receive the receipt from the server.</p>", "time": "2023-08-28T15:49:11Z"}]