Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define 'Presentation Compositor' [TAG review] #58

Closed
rhiaro opened this issue Nov 24, 2022 · 4 comments · Fixed by #61
Closed

Define 'Presentation Compositor' [TAG review] #58

rhiaro opened this issue Nov 24, 2022 · 4 comments · Fixed by #61
Assignees
Milestone

Comments

@rhiaro
Copy link
Member

rhiaro commented Nov 24, 2022

Please forgive my ignorance as I get up to speed with this work.

The IMSC HRM spec contains the term 'Presentation Compositor' several times but does not link to or define what this is. Could you provide or point me to an explanation?

(cc w3ctag/design-reviews#788)

@palemieux
Copy link
Contributor

The Presentation Compositor is one of the processing steps of the HRM -- see Figure 2.

@rhiaro
Copy link
Member Author

rhiaro commented Nov 24, 2022

Aha thanks, that explains why ctrl+f didn't find it.

@rhiaro rhiaro closed this as completed Nov 24, 2022
@palemieux
Copy link
Contributor

I suggest reopening this issue since this is something others are likely to run into.

@rhiaro rhiaro reopened this Nov 24, 2022
@himorin
Copy link
Contributor

himorin commented Nov 29, 2022

Section 6 defines architectural components and their processing diagrams (Figure 2), but marked as non-normative. As above, some of defined components have normative SHALL texts for their behavior. (Also some part of diagrams seem to be only described in section 6, like switching between non-empty ISD and empty ISD?)
Are these (both components and diagrams) better to be normatively described at somewhere else than non-normative section 6??

(note, I lack enough experience on these normativeness, so comments should be wrong...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants