Consolidating changes from multiple PRs (#117)

* Consolidating changes from PRs

Consolidating changes from PRs

1. #109
2. #108
3. #100

* Shayne's suggestion

Shayne's suggestion

* More places to fix MUST -> SHOULD

More places to fix MUST -> SHOULD

Author: appsdesh

openid-sharedsignals-framework-1_0.md

@@ -61,6 +61,12 @@ contributor:
         contribution: |
           Steve defined the format field of Complex Subjects
 
+      -
+        ins: A. Deshpande
+        name: Apoorva Deshpande
+        org: Okta
+        email: apoorva.deshpande@okta.com
+
 normative:
   CLIENTCRED:
     author:
@@ -787,9 +793,9 @@ following properties:
 
 stream_id
 
-> **Transmitter-Supplied**, A string that uniquely identifies the stream. Stream
-  IDs MUST be unique per Reciever.  This value is generated by the Transmitter
-  when the stream is created.
+> **Transmitter-Supplied**, A string that uniquely identifies the stream. A
+  transmitter MUST generate a unique ID for each of its non-deleted streams
+  at the time of stream creation.
 
 iss
 
@@ -818,13 +824,15 @@ events_requested
 > **Receiver-Supplied**, An array of URIs identifying the set of events that
   the Receiver requested. A Receiver SHOULD request only the events that it
   understands and it can act on. This is configurable by the Receiver. A
-  Transmitter MUST ignore any array values that it does not understand.
+  Transmitter MUST ignore any array values that it does not understand. This
+  array SHOULD NOT be empty.
 
 events_delivered
 
-> **Transmitter-Supplied**, An array of URIs which is the intersection of
-  "events_supported" and "events_requested". These events MAY be delivered over
-  the Event Stream. A Receiver MUST rely on the values received in this field
+> **Transmitter-Supplied**, An array of URIs identifying the set of events that
+  the Transmitter MUST include in the stream. This is a subset (not necessarily
+  a proper subset) of the intersection of "events_supported" and
+  "events_requested". A Receiver MUST rely on the values received in this field
   to understand which event types it can expect from the Transmitter.
 
 delivery
@@ -1160,7 +1168,8 @@ configuration in the body.
 The stream_id property MUST be present in the request. Other properties
 MAY be present in the request. Any Receiver-Supplied property present in the
 request MUST be updated by the Transmitter. Any properties missing in the
-request MUST NOT be changed by the Transmitter.
+request MUST NOT be changed by the Transmitter. If `events_requested` property is
+included in the request, it SHOULD NOT be an empty array.
 
 Transmitter-Supplied properties beside the stream_id MAY be present,
 but they MUST match the expected value. Missing Transmitter-Supplied
@@ -1246,7 +1255,8 @@ The stream_id and the full set of Receiver-Supplied properties MUST be present
 in the PUT body, not only the ones that are specifically intended to be changed.
 Missing Receiver-Supplied properties MUST be interpreted as requested to be
 deleted. Event Receivers MAY read the configuration first, modify the JSON
-{{RFC7159}} representation, then make a replacement request.
+{{RFC7159}} representation, then make a replacement request. If `events_requested` 
+property is included in the request, it SHOULD NOT be an empty array.
 
 Transmitter-Supplied properties besides the stream_id MAY be present,
 but they MUST match the expected value. Missing Transmitter-Supplied