An event may have plannedCoverages which include renditions which are technically associated.

• An example might be a main and a standby feed which are technically identical.

• Another example might be that the feed is available from diverse locations situated around the globe.

The issue

In an automated system being driven from the contents of NinJS documents, the system needs to know that the technical intent of each rendition.

From the current information in the schema, the automation system can infer that the technical standards of two renditions are identical.

But it is also possible that some of the technical standards for the standby rendition are different from those of the main rendition - such as a lower bitrate.

It might be that the system behind one rendition is provisioned to be the main and the other is provisioned to be the standby.

What is not clear is the how to specify the 'intent' of each rendition.

It might be that the two renditions are being produced from two geographically distanced cloud suppliers

What is not clear is the how to specify the location of the renditions origin.

Issue #241 might help in associating one rendition to another one, possibly identifying a "alternate" rendition to use were this rendition to become faulty.

Request

Is there any advice that could be offered in how automated systems may be able to use information already contained in NinJS to infer intent or location or relationships between renditions?

Or any suggestions on enhancements to NinJS which might help automated systems infer these properties in a NinJS centric way?