removed special case for single-stream transmitters

Author: tulshi

openid-sharedsignals-framework-1_0.html

@@ -3706,8 +3706,7 @@ <h5 id="name-verification-event">
 <li class="normal ulEmpty" id="section-7.1.4.1-7.1">
                 <p id="section-7.1.4.1-7.1.1">REQUIRED. The value of the <code>subject</code> field in a Verification Event MUST always
   be set to have a simple value of type <code>opaque</code>. The <code>id</code> of the value MUST be
-  the <code>stream_id</code> of the stream being verified. If the Transmitter does not
-  support multiple streams, this value MUST be set to "none"<a href="#section-7.1.4.1-7.1.1" class="pilcrow">¶</a></p>
+  the <code>stream_id</code> of the stream being verified.<a href="#section-7.1.4.1-7.1.1" class="pilcrow">¶</a></p>
 </li>
             </ul>
 <ul class="normal ulEmpty">
@@ -3895,8 +3894,7 @@ <h4 id="name-stream-updated-event">
               <p id="section-7.1.5-10.1.1">REQUIRED. Specifies the Subject Principal for whom the status has been updated.
   If the event applies to the entire stream, the value of the <code>subject</code> field
   MUST be of format <code>opaque</code>, and its <code>id</code> value MUST be the unique ID of the
-  stream. If the Transmitter does not support multiple streams, then the value
-  of the <code>id</code> field MUST be the string "none".<a href="#section-7.1.5-10.1.1" class="pilcrow">¶</a></p>
+  stream.<a href="#section-7.1.5-10.1.1" class="pilcrow">¶</a></p>
 </li>
           </ul>
 <ul class="normal ulEmpty">
@@ -3959,7 +3957,7 @@ <h4 id="name-stream-updated-event">
     "https://schemas.openid.net/secevent/ssf/event-type/stream-updated": {
       "subject": {
         "format": "opaque",
-        "id" : "none"
+        "id" : "f67e39a0a4d34d56b3aa1bc4cff0069f"
       },
       "status": "paused",
       "reason": "Internal error"

openid-sharedsignals-framework-1_0.md

@@ -1722,8 +1722,7 @@ subject
 
 > REQUIRED. The value of the `subject` field in a Verification Event MUST always
   be set to have a simple value of type `opaque`. The `id` of the value MUST be
-  the `stream_id` of the stream being verified. If the Transmitter does not
-  support multiple streams, this value MUST be set to "none"
+  the `stream_id` of the stream being verified.
 
 > Note that the subject that identifies a stream itself is always implicitly
   added to the stream and MAY NOT be removed from the stream.
@@ -1855,8 +1854,7 @@ subject
 > REQUIRED. Specifies the Subject Principal for whom the status has been updated.
   If the event applies to the entire stream, the value of the `subject` field
   MUST be of format `opaque`, and its `id` value MUST be the unique ID of the
-  stream. If the Transmitter does not support multiple streams, then the value
-  of the `id` field MUST be the string "none".
+  stream. 
 
 > Note that the subject that identifies a stream itself is always implicitly
   added to the stream and MAY NOT be removed from the stream.
@@ -1900,7 +1898,7 @@ subject
     "https://schemas.openid.net/secevent/ssf/event-type/stream-updated": {
       "subject": {
         "format": "opaque",
-        "id" : "none"
+        "id" : "f67e39a0a4d34d56b3aa1bc4cff0069f"
       },   
       "status": "paused",
       "reason": "Internal error"

openid-sharedsignals-framework-1_0.txt

@@ -2279,17 +2279,17 @@ Tulshibagwale, et al.        Standards Track                   [Page 40]
       REQUIRED.  The value of the subject field in a Verification Event
       MUST always be set to have a simple value of type opaque.  The id
       of the value MUST be the stream_id of the stream being verified.
-      If the Transmitter does not support multiple streams, this value
-      MUST be set to "none"
 
       Note that the subject that identifies a stream itself is always
       implicitly added to the stream and MAY NOT be removed from the
       stream.
 
-
-
-
-
+   Upon receiving a Verification Event, the Event Receiver SHALL parse
+   the SET and validate its claims.  In particular, the Event Receiver
+   SHALL confirm that the value for "state" is as expected.  If the
+   value of "state" does not match, an error response of "setData"
+   SHOULD be returned (see Section 2.3 of [DELIVERYPUSH] or
+   [DELIVERYPOLL]).
 
 
 
@@ -2298,13 +2298,6 @@ Tulshibagwale, et al.        Standards Track                   [Page 41]
                               SharedSignals                   March 2023
 
 
-   Upon receiving a Verification Event, the Event Receiver SHALL parse
-   the SET and validate its claims.  In particular, the Event Receiver
-   SHALL confirm that the value for "state" is as expected.  If the
-   value of "state" does not match, an error response of "setData"
-   SHOULD be returned (see Section 2.3 of [DELIVERYPUSH] or
-   [DELIVERYPOLL]).
-
    In many cases, Event Transmitters MAY disable or suspend an Event
    Stream that fails to successfully verify based on the acknowledgement
    or lack of acknowledgement by the Event Receiver.
@@ -2349,6 +2342,13 @@ Tulshibagwale, et al.        Standards Track                   [Page 41]
 
 
 
+
+
+
+
+
+
+
 Tulshibagwale, et al.        Standards Track                   [Page 42]
 
                               SharedSignals                   March 2023
@@ -2471,9 +2471,7 @@ Tulshibagwale, et al.        Standards Track                   [Page 44]
       REQUIRED.  Specifies the Subject Principal for whom the status has
       been updated.  If the event applies to the entire stream, the
       value of the subject field MUST be of format opaque, and its id
-      value MUST be the unique ID of the stream.  If the Transmitter
-      does not support multiple streams, then the value of the id field
-      MUST be the string "none".
+      value MUST be the unique ID of the stream.
 
       Note that the subject that identifies a stream itself is always
       implicitly added to the stream and MAY NOT be removed from the
@@ -2517,6 +2515,8 @@ Tulshibagwale, et al.        Standards Track                   [Page 44]
 
 
 
+
+
 Tulshibagwale, et al.        Standards Track                   [Page 45]
 
                               SharedSignals                   March 2023
@@ -2531,7 +2531,7 @@ Tulshibagwale, et al.        Standards Track                   [Page 45]
        "https://schemas.openid.net/secevent/ssf/event-type/stream-updated": {
          "subject": {
            "format": "opaque",
-           "id" : "none"
+           "id" : "f67e39a0a4d34d56b3aa1bc4cff0069f"
          },
          "status": "paused",
          "reason": "Internal error"