delivery-media-available.additionalProperties

Refused 400 schema

A field the schema does not allow, in the delivery-media-available payload schema.

Outcome	Refused, 400
Source	schema: The SOM 1.0 JSON Schema says no. The message is not valid SOM 1.0.
Checked at	SOM envelope, version and payload (see the order of checks)
Applies to	messages whose payload is checked against the delivery-media-available schema

What it means

The message breaks the delivery-media-available payload schema. A field the schema does not allow. Typical cause: A typo, a field withdrawn before 1.0 (voice_count, transform_id), or an extension that is not namespaced com.<vendor>.. For a message at a som_version newer than 1.0.0 (a later 1.x), this is tolerated instead: accepted, and listed under tolerated, as the SOM compatibility policy asks. At exactly 1.0.0 it is refused.

How to fix it

Remove or rename the field; put vendor data under extensions with a reverse-domain key. path in the violation points at the field.

---

Branch on the rule id, never on the violation's message text. All rules: rule catalogue.