Open pac-work opened 5 months ago
The intent is that the flows allow multi-essence structurally, even if they are used single-essence in a particular application context. I agree the text of the document could be read at cross purposes to this., I will add this to the nits list for the text.
Thank you for addressing this, it will help to have clearer wording.
Media flow definition seems to be different in the text and in the JSON. Is it just one essence or more essences? The text says "A sequence of Media Elements belonging to the same media essence flow e.g. video, audio track which completely contain the essence" (sounds like single essence, for example audio only), but in the JSON the mediaFlow contains the mediaElement, which is an array containing video, audio and ancillary data. We would assume that flow is a collection of related essences, same as the README.md suggests.