Remove uri-reference validation for xdm:deliveryURL and xdm:linkURL

[137bpm]

What are the schemas that are affected by the issue

decisioning/content-component-details.schema.json

With chain of references in:

1. decisioning/content-details.schema.json

   • decisioning/contents.schema.json
     • decisioning/fallback-content-option.schema.json
       • offer-management/fallback-content-offer.schema.json
     • decisioning/personalized-content-option.schema.json
       • offer-management/personalized-content-offer.schema.json

2. decisioning/option-detail.schema.json

   • decisioning/decisionevent.schema.json
     • campaign-experienceevent.schema.json
     • decisioning/decisionevent-all.schema.json
     • decisioning/proposition-details.schema.json
   • decisioning/proposition-detail.schema.json
   • decisioning/proposition-interaction-detail.schema.json
     • decisioning/experienceevent-proposition-interaction.schema.json
   • offer-management/offer-detail.schema.json
     • campaign/offer-detail.schema.json

What are examples of products that are impacted by the issue

Adobe Experience Platform interacts with a backend service for storing Decisioning objects, such as Fallback Offers and Personalized Offers.

The backend service has already removed the uri-reference validation for these business objects, but the XDM schemas used by the Smarts deployments are present on the adobe/xdm open source project.

The backend service sends a change data capture event. A Smarts deployment reacts to it and validates the payload. Since the payload contains characters that are not allowed in a uri-reference, the event is discarded with an error.