<div dir="ltr">Hi Phillip,<div>A "subject" claim, as specified here: <a href="https://github.com/openid/sharedsignals/blob/ae0cf793477bff3953001b1f4ef04da78b9325e1/openid-sharedsignals-framework-1_0.txt#L2656">https://github.com/openid/sharedsignals/blob/ae0cf793477bff3953001b1f4ef04da78b9325e1/openid-sharedsignals-framework-1_0.txt#L2656</a></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 20, 2023 at 5:34 PM Phillip Hunt <<a href="mailto:phil.hunt@independentid.com">phil.hunt@independentid.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Atul,<div><br></div><div>Are you referring to the sub_id claim? </div><div><br></div><div><div dir="ltr">Phil</div><div dir="ltr"><br><blockquote type="cite">On Jun 20, 2023, at 4:54 PM, Atul Tulshibagwale <<a href="mailto:atul@sgnl.ai" target="_blank">atul@sgnl.ai</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Hi Phil,<div>If all SSF events were required to have a top-level "subject" field with the subject identifier in it, would the issue be still as bad? In my new PR, The spec (11.1.2) requires all events to have a subject field. There were a few exceptions, but we have now addressed them in this PR: <a href="https://github.com/openid/sharedsignals/pull/70" target="_blank">https://github.com/openid/sharedsignals/pull/70</a></div><div><br></div><div>Atul</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 20, 2023 at 4:46 PM Phillip Hunt <<a href="mailto:phil.hunt@independentid.com" target="_blank">phil.hunt@independentid.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Apologies for not making the call it seems tuesdays are often conflicting<div><br></div><div>I was a little confused about stream id vs subject id in today’s discussion.</div><div><br></div><div>In my issue I would like to see the subject of the event identified in the top-level of an event so that a router does not have to parse the event body itself if it is doing things like filtering out subjects that are not part of an individual stream (to facilitate add/remove subject in stream management). For example the router receivers an event from a source and then re-publishes to one or more streams. </div><div><br></div><div>AFAIK there is no need to put stream id in an event itself.</div><div><br><div dir="ltr">Phil</div><div dir="ltr"><br><blockquote type="cite">On Jun 20, 2023, at 11:07 AM, Atul Tulshibagwale via Openid-specs-risc <<a href="mailto:openid-specs-risc@lists.openid.net" target="_blank">openid-specs-risc@lists.openid.net</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr">Hi all,<br><div>Thanks to those who attended the call today. The notes are pasted below and stored <a href="https://hackmd.io/@oidf-wg-sse/wg-meeting-20230620" target="_blank">here</a>.</div><div><br></div><div>Atul</div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span><div dir="ltr" style="margin-left:0pt" align="left"><table style="border:none;border-collapse:collapse"><colgroup><col width="142"><col width="482"></colgroup><tbody><tr style="height:0pt"><td style="vertical-align:middle;overflow:hidden"><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><a href="https://sgnl.ai" target="_blank"><span style="font-size:11pt;font-family:"Work Sans",sans-serif;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:137px;height:68px"><img src="https://lh3.googleusercontent.com/aO7jB_JqOxA0tVDXsAotNQnsfEkxEORgtkVnVFrmkR7O8j3B4lbbRsGFuprzQhfDmri2YH8_dnjPiZnGMZxIcT9xRcdY6rYm-xGophLkgvl_v8istAefyh4qkSVINQtPfcmq5BZiKbfFHmursSUHyll1jEWBTd--nw26MIMKd86Br32rGZkvJwnEED_nzQ" width="137" height="68" style="margin-left: 0px; margin-top: 0px;"></span></span></a></p></td><td style="vertical-align:top;padding:5pt;overflow:hidden"><p dir="ltr" style="line-height:1.44;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:"Work Sans",sans-serif;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">Atul Tulshibagwale</span></p><p dir="ltr" style="line-height:1.44;margin-top:0pt;margin-bottom:0pt"><span style="font-size:11pt;font-family:"Work Sans",sans-serif;color:rgb(102,102,102);background-color:transparent;vertical-align:baseline;white-space:pre-wrap">CTO </span></p><p dir="ltr" style="line-height:1.2;margin-top:0pt;margin-bottom:0pt"><font size="1"><span style="font-family:"Work Sans",sans-serif;color:rgb(17,85,204);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:20px;height:27px"><a href="https://linkedin.com/in/tulshi" target="_blank"><img src="https://lh6.googleusercontent.com/ezm4lDcLtajK4RMqqHALoRgXyaC4HRlw0wWsR2Jvms0V9Wrxr3x5G66zsUrYpRXyeJ3RwLS3GdKUwO0Ui5mXPodSkUx8Xsarf_vj6WlJ05Y1qJoMFTlCZnEgtHvlJ7_7Dr7zWNjkvf3nMW9u1P5ye76SeHgz2QqGQ_rm-sjqYOS-vH1UZL7Yiewi4UO3Qw" width="20" height="27" style="margin-left: 0px; margin-top: 0px;"></a> </span></span><span style="font-family:"Work Sans",sans-serif;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline;white-space:pre-wrap"><span style="border:none;display:inline-block;overflow:hidden;width:20px;height:27px"><a href="https://twitter.com/zirotrust" target="_blank"><img src="https://lh6.googleusercontent.com/HAnAvykj318aQf5zTUZkjIJDtwelDecFi5d-idBrpUDBj7aKTdup5Mfia6UIbXTAP46zg7gigNnroQ9he3j81Sf9qCRRSS-w_nZ3oSXJnYLbPlCXgt6IqoifgHXETuJSRvFIZRIdn_aAbtp8ilKFyIVuTXjVe6cNAfXc5KZNwJeYinwfZZxVvHHaR5uIdQ" width="20" height="27" style="margin-left: 0px; margin-top: 0px;"></a> </span></span><a href="mailto:atul@sgnl.ai" target="_blank"><img src="https://lh3.googleusercontent.com/63PpVJLMybZyfD61JVu0TVH_KkP_IhneeBpDNvbd1KeSFJn6KZzWCgp4hFbrTrIxfksYyM-_wOjNKbjEhSQ2khRXVI3XKcwABLNLI_bFjkN0_NgVoijs_nIRcVJKeQm0s0MRdtkUkCOp5Omyv1faqcNiQxGEUyAvmE9HkeeQCeHa-LxleK0oHSAyQrDY6g" width="21" height="21" style="background-color: transparent; color: rgb(0, 0, 0); font-family: Arial; white-space: pre-wrap; margin-left: 0px; margin-top: 0px;"></a></font></p></td></tr></tbody></table><br></div><div dir="ltr" style="margin-left:0pt" align="left"><div style="box-sizing:border-box;margin-right:0px;margin-left:0px;height:1014px;color:rgb(51,51,51);font-family:"Source Sans Pro",Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.35px"><div style="box-sizing:border-box;height:1014px;overflow:hidden auto;padding-left:15px;padding-right:15px"><div id="m_-5031924209701220851m_-4112059126506135503gmail-doc" style="box-sizing:border-box;padding:40px 15px;margin-right:45px;margin-left:auto;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI","Helvetica Neue",Helvetica,Roboto,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;line-height:1.5;max-width:758px;overflow:visible"><h1 id="m_-5031924209701220851m_-4112059126506135503gmail-WG-Meeting-2022-06-20" style="box-sizing:border-box;margin:0px 0px 16px;font-family:inherit;line-height:1.25;color:inherit;padding-bottom:0.3em;border-bottom:1px solid rgb(238,238,238)"><span style="box-sizing:border-box">WG Meeting: 2022-06-20</span></h1><h2 id="m_-5031924209701220851m_-4112059126506135503gmail-Agenda" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;padding-bottom:0.3em;border-bottom:1px solid rgb(238,238,238)"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Agenda" title="Agenda" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Agenda</span></h2><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">Which Issues must be addressed before requesting another implementer’s draft</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Issue </span><a href="https://github.com/openid/sharedsignals/issues/53" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">#53</span></a><span style="box-sizing:border-box"> - ComplexSubject should have a format field</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Issue </span><a href="https://github.com/openid/sharedsignals/issues/52" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">#52</span></a><span style="box-sizing:border-box"> - Should subject identifier be pulled out of the event definitions?</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Issue </span><a href="https://github.com/openid/sharedsignals/issues/60" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">#60</span></a><span style="box-sizing:border-box"> - Are subjects required in SSF events?</span></li></ul><h2 id="m_-5031924209701220851m_-4112059126506135503gmail-Attendees" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;padding-bottom:0.3em;border-bottom:1px solid rgb(238,238,238)"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Attendees" title="Attendees" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Attendees</span></h2><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">Atul Tulshibagwale (SGNL)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Topher ()</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Shayne Miel (Cisco)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Mike Kiser (SailPoint)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Tim Cappalli (Microsoft)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Apoorva Deshpande (Okta)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Eric Karlinsky (Okta)</span></li></ul><h2 id="m_-5031924209701220851m_-4112059126506135503gmail-Notes" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;padding-bottom:0.3em;border-bottom:1px solid rgb(238,238,238)"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Notes" title="Notes" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Notes</span></h2><h3 id="m_-5031924209701220851m_-4112059126506135503gmail-Which-Issues" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;font-size:1.25em"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Which-Issues" title="Which-Issues" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Which Issues</span></h3><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">[Atul] Let’s try to submit a new implementer’s draft for review in the next 10 days. (Before June 30th)</span></li></ul><h3 id="m_-5031924209701220851m_-4112059126506135503gmail-Issue-53---ComplexSubject-should-have-a-format-field" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;font-size:1.25em"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Issue-53---ComplexSubject-should-have-a-format-field" title="Issue-53---ComplexSubject-should-have-a-format-field" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Issue </span><a href="https://github.com/openid/sharedsignals/issues/53" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">#53</span></a><span style="box-sizing:border-box"> - ComplexSubject should have a format field</span></h3><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">Steve Venema’s suggestion on email: Add value for the field “format” as “complex”</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Tim] Would this lead to an issue in nesting, where a nested value could also be complex</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Shayne] Suggesting something like this:</span></li></ul><pre style="box-sizing:border-box;overflow:auto;font-family:Menlo,Monaco,Consolas,"Courier New",monospace;font-size:13.6px;padding:16px;margin-top:0px;margin-bottom:16px;line-height:1.45;word-break:break-all;background-color:rgb(247,247,247);border-radius:3px;border:inherit"><code style="box-sizing:border-box;font-family:Menlo,Monaco,Consolas,"Courier New",monospace;font-size:13.6px;padding:0px;background:transparent;border-radius:3px;display:inline;overflow:visible;margin:0px;word-break:normal;border:0px;line-height:inherit;color:inherit">subject<span style="box-sizing:border-box;color:rgb(154,110,58);background:rgba(255,255,255,0.5)">:</span> <span style="box-sizing:border-box;color:rgb(153,153,153)">{</span>
<span style="box-sizing:border-box;color:rgb(153,0,85)">"format"</span> <span style="box-sizing:border-box;color:rgb(154,110,58);background:rgba(255,255,255,0.5)">:</span> <span style="box-sizing:border-box;color:rgb(102,153,0)">"complex"</span><span style="box-sizing:border-box;color:rgb(153,153,153)">,</span>
<span style="box-sizing:border-box;color:rgb(153,0,85)">"user"</span> <span style="box-sizing:border-box;color:rgb(154,110,58);background:rgba(255,255,255,0.5)">:</span> <span style="box-sizing:border-box;color:rgb(153,153,153)">{</span>
<span style="box-sizing:border-box;color:rgb(153,153,153)">}</span><span style="box-sizing:border-box;color:rgb(153,153,153)">,</span>
<span style="box-sizing:border-box;color:rgb(153,0,85)">"tenant"</span><span style="box-sizing:border-box;color:rgb(154,110,58);background:rgba(255,255,255,0.5)">:</span> <span style="box-sizing:border-box;color:rgb(153,153,153)">{</span>
<span style="box-sizing:border-box;color:rgb(153,153,153)">}</span><span style="box-sizing:border-box;color:rgb(153,153,153)">,</span>
<span style="box-sizing:border-box;color:rgb(153,0,85)">"device"</span><span style="box-sizing:border-box;color:rgb(154,110,58);background:rgba(255,255,255,0.5)">:</span> <span style="box-sizing:border-box;color:rgb(153,153,153)">{</span>
<span style="box-sizing:border-box;color:rgb(153,153,153)">}</span>
<span style="box-sizing:border-box;color:rgb(153,153,153)">}</span>
</code></pre><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">[Shayne] So we just add a field named “format”:“complex” and keep the rest of the spec the same</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Atul] The Array option we discussed the last time allows for duplicate entries</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Shayne] Prefer either this new one we discussed today or the first one in last week’s </span><a href="https://hackmd.io/@oidf-wg-sse/wg-meeting-20230613" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">notes</span></a><span style="box-sizing:border-box"> (a field named format, and a field named value)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Shayne] Any component could benefit from using the “format” field to make a decision on subject processing</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Tim] We could get the same effect by adding a field named “type”, which could be “simple” or “complex”, and then the subject value</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Tim] We could go with Steve’s proposal but we may now have to add processing logic in the spec (not just because of Steve’s proposal, but because of the complexity in general)</span></li></ul><h3 id="m_-5031924209701220851m_-4112059126506135503gmail-Issue-52---Should-subject-identifier-be-pulled-out-of-the-event-definitions" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;font-size:1.25em"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Issue-52---Should-subject-identifier-be-pulled-out-of-the-event-definitions" title="Issue-52---Should-subject-identifier-be-pulled-out-of-the-event-definitions" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Issue </span><a href="https://github.com/openid/sharedsignals/issues/52" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">#52</span></a><span style="box-sizing:border-box"> - Should subject identifier be pulled out of the event definitions?</span></h3><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">[Shayne] This was Phil’s request from a couple of calls ago</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Why did RISC originally move the subject identifiers to a different claim than the top-level “sub” claim in JWTs?</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">Mike Kiser to ask Phil for clarification</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Tim] We can add a stream ID in the event for clarity / routing purposes. It could help in auditing</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Apoorva] A Transmitter implementation may become complex if we add a stream ID in the event, because the Transmitter cannot reuse the event across different streams</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Tim] It’s optional so should it be a problem</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Atul] Will it affect interoperability</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Tim] JSON objects are intended to have optional values, without affecting interoperability</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Atul] Won’t the transmitter have to generate a new event for every receiver anyway (event-id, aud, etc.)</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Apoorva] ‘aud’ is a list, so you could define a list of all receivers, and reuse the same event</span></li></ul><h3 id="m_-5031924209701220851m_-4112059126506135503gmail-Issue-60---Are-subjects-required-in-SSF-events" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;font-size:1.25em"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Issue-60---Are-subjects-required-in-SSF-events" title="Issue-60---Are-subjects-required-in-SSF-events" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Issue </span><a href="https://github.com/openid/sharedsignals/issues/60" rel="noopener" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none" target="_blank"><span style="box-sizing:border-box">#60</span></a><span style="box-sizing:border-box"> - Are subjects required in SSF events?</span></h3><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">[Shayne] We can add a qualification that the subject value is required for all events other than “stream updated” and “verification” events.</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Eric] It feels a little contorted to do it this way. Can we instead make the “stream updated” event not SSF conformant?</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Atul] We can add a stream ID subject in the “stream updated” event.</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Shayne, Eric] We should have thst subject to be opaque, and specify how it should be defined</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Eric, Shayne, Atul] like the “Add stream id as subject” option more</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Shayne] what about subscription to that subject?</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Atul] Should be automatic</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Shayne] The receiver should be able to remove that subject if needed</span></li><li style="box-sizing:border-box;padding-top:0.25em"><span style="box-sizing:border-box">[Atul] That could be problematic, we should not allow removal of that subject</span></li></ul><h2 id="m_-5031924209701220851m_-4112059126506135503gmail-Action-Items" style="box-sizing:border-box;font-family:inherit;line-height:1.25;color:inherit;margin-top:24px;margin-bottom:16px;padding-bottom:0.3em;border-bottom:1px solid rgb(238,238,238)"><a href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#Action-Items" title="Action-Items" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1" target="_blank"><span style="box-sizing:border-box;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a><span style="box-sizing:border-box">Action Items</span></h2><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em"><li style="box-sizing:border-box"><span style="box-sizing:border-box">Atul to add PR to add subject to “stream updated” and “verification” events</span></li></ul><div dir="ltr" style="box-sizing:border-box;overflow:hidden;max-width:100%;margin-bottom:0px"><div style="box-sizing:border-box;overflow:hidden;max-width:100%"><div style="box-sizing:border-box;width:612px;height:2730px"></div></div><div style="box-sizing:border-box;overflow:hidden;max-width:100%"><div style="box-sizing:border-box;width:1204.4px;height:5439.9px"></div></div></div></div><div style="box-sizing:border-box;margin-left:8px"><div style="box-sizing:border-box;float:left"><a id="m_-5031924209701220851m_-4112059126506135503gmail-tocLabel" href="https://hackmd.io/Pjy4fZvuTLGxfJYpez6YgA#" role="button" aria-haspopup="true" aria-expanded="false" title="Table of content" style="box-sizing:border-box;background-color:rgb(230,230,230);color:rgb(134,134,134);text-decoration-line:none;display:inline-block;padding:10px 4px;margin-bottom:0px;line-height:1.42857;text-align:center;vertical-align:middle;background-image:none;border:none;border-radius:0px 4px 4px 0px;height:40px" target="_blank"><span style="box-sizing:border-box;display:inline-block;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-kerning:auto;font-feature-settings:normal;font-stretch:normal;line-height:1;font-family:FontAwesome;font-size:inherit"></span></a></div></div></div></div><div style="box-sizing:border-box;color:rgb(51,51,51);font-family:"Source Sans Pro",Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.35px"></div><span style="box-sizing:border-box;color:rgb(51,51,51);font-family:"Source Sans Pro",Helvetica,Arial,sans-serif;font-size:14px;letter-spacing:0.35px;width:auto;padding:0px;white-space:pre-wrap">Select a repo</span></div></span></div></div></div>
<span>_______________________________________________</span><br><span>Openid-specs-risc mailing list</span><br><span><a href="mailto:Openid-specs-risc@lists.openid.net" target="_blank">Openid-specs-risc@lists.openid.net</a></span><br><span><a href="https://lists.openid.net/mailman/listinfo/openid-specs-risc" target="_blank">https://lists.openid.net/mailman/listinfo/openid-specs-risc</a></span><br></div></blockquote></div></div></blockquote></div>
</div></blockquote></div></div></blockquote></div>