Fixes #221 - Add event_metadata to CAEP and RISC

[jischr]

Added event_metadata to CAEP and RISC for the transmitter to provide additional information about the event itself.

Fixes #221

[jischr]

@appsdesh

• what does it mean by action?

• that wording was taken from the issue. happy to remove or replace if it doesnt suit.

• how would we prevent bloating?

• I don't believe we need to prevent bloating as SETs do not have restrictions in place for event claims. if necessary, we could put restrictions on string length.

• Why are we singling this out "This claim SHOULD not be used to express information about the subject." needs more concrete guidance

• We need to differentiate the this claim for other claims that could have been added to the individual event schemas (that describes the subject). this is metadata. Guidance could be added to prevent this claim from becoming out of hand.

[iamseanodentity]

"action" here is needed, but we do not need to call it out in the description. In the event_metadata field it is setting the foundation to expand upon profile events that might be mandatory via a contract between the transmitter and receiver.

We need guidelines for this and a use case with event_metadata details.

• Don't overload this claim (size considerations of the JWT)
• Don't add in subject based information and keep it siloed to the event itself (i.e. correlation_id, enriched meta data info)
• Why and When to use it

[jischr]

@iamseanodentity do you can an example of this you can supply?

[iamseanodentity]

@iamseanodentity do you can an example of this you can supply?

I will get to this tonight. Would you like me to add inline or just here and you can handle the copy?

[jischr]

decided against this 4/15