Why is it important to provide optionality between full-url vs request-response vs all in notification-url-location? Can you please just give implementers a single, workable path forward? Without any background on this extension, it feels like a crazy and unnecessary amount of twiddly configuration. (ValueSet: http://hl7.org/fhir/uv/subscriptions-backport/2021JAN/ValueSet-backport-notification-url-location-value-set.html#expansion). Also, what does it mean for payload to be id-only, but notification-url-location to be none? Again, I'm likely missing background, but it seems like this spec should merely require servers to always do "all" and that "none" is a bug in the spec that conflicts with the id-only payload.

Existing Wording:

Each Bundle\.entry for id-only notification SHALL contain a relevant resource URL in the fullUrl, request, and/or response elements\. The Subscription’s notificationUrlLocation element describes the behavior which should be used\.

(Comment 23 - imported by: Gino Canessa)