Generic Language for prescriptive SETs - Issue 255

[iamseanodentity]

In reference to Issue 255 marked for v1 Final per the discussion last week in the SSWG Call.

I added a sub section under Section 4 called "SSF Prescriptive SETs" and an example figure of what a prescriptive SET may look like under Section 5.

Open to feedback on the example. I took the IPSIE action out as defined here and replaced it with a duplicative session-revoked event to convey that the transmitter is expecting the action to be taken is to revoke a session even though the SET is referencing the same event. I am all for using an IPSIE profile in there to convey cross standard usage of SSF but wanted to get some feedback from the reviewers.

I thought Section 4 was a decent place to call out that the Events in a SET can be treated as prescriptive. For those following along I will add the text here for brevity. I tried to keep it clean and concise and added a new section called SSF Prescriptive SETs. See below:
The Shared Signals Framework allows each deployment or integration to define its own event processing behaviors, ranging from informational input to additional processing needed, to mandatory enforcement (e.g., session revoke). See {{Referenced Example I created in Section 5}}.