WebRTC needs mechanism to handle the metadata needed to re-aggregate Pinned audio content

[RealJoshue108]

Filed on behalf of @JaninaSajka.

For pinned audio content, there is a need to handle and support the metadata that allows the client engine to re-aggregate pinned content, eg. French Sign Language translation of the French language speaker interpreting the English speaking member of the Canadian Parliament.

Not all of our atomic items necessarily are pinned next to other atomic elements, but some clearly are, and this must be an extensible mechanism.

For example, if we have multiple atomic data points destined for an 80 char braille display that has been sectioned to display 4 atomic items in up to 19 spaces each (leaving at least one blank cell for spacing.

[RealJoshue108]

Relates to #22

[RealJoshue108]

@JaninaSajka we may need to aggregate or route or a combination of both.

[RealJoshue108]

@joshueoconnor JOC: Adding a reference to sending atomic content to different sections of the braille display would be helpful to readers to understand the user need for atomic output.

[RealJoshue108]

For pinned content, there is a need to handle and support the metadata that allows the client engine to re-aggregate or re-route pinned content.

TBD: Not all atomic items necessarily are pinned next to other atomic elements but some may be dependent, related or updated synchronously.

For example, if we have multiple atomic data points destined for an 80 char braille display that has been sectioned to display 4 atomic items in up to 19 spaces each (leaving at least one blank cell for spacing.

[RealJoshue108]

Discussed by RQTF: 6th Jan 2021 https://www.w3.org/2021/01/06-rqtf-minutes.html

[RealJoshue108]

This could be a new requirement for RAUR https://www.w3.org/TR/raur/#window-anchoring-and-pinning

NEW REQ 1e: For pinned content, there is a need to handle and support the metadata that allows the client engine to re-aggregate or re-route pinned content.

NOTE: Not all atomic items necessarily are pinned next to other atomic elements but some may be dependent, related or updated synchronously.

User need notes on this: For example, if we have multiple atomic data points destined for an 80 char braille display that has been sectioned to display 4 atomic items in up to 19 spaces each (leaving at least one blank cell for spacing).