Add statement in Endpoint spec that message.ID needs to be unique

xregistry / spec

xRegistry related specifications

https://xRegistry.io

Apache License 2.0

35 stars 6 forks source link

Add statement in Endpoint spec that message.ID needs to be unique #146

Open duglin opened 3 months ago

duglin commented 3 months ago

under "messages" it already has to be unique because it's in a map. but the "messagegroups" attribute could cause dups. We may not be able to make it a MUST, so SHOULD might be good enough and just warn people.

Proposal: STRONGLY RECOMMENDED that they do it

duglin commented 1 month ago

Agreed on the 9/24 call

duglin commented 3 weeks ago

Need to revisit this since this would not work in cases where there are two message definitions for the same event(message) but in 2 different formats (xml vs json).