CG Charter

[palemieux]

The following were used as a starting point:

• Kick-off message to the mailing list
• README.md

Closes #88

[annevk]

Liaisons should probably list the WHATWG HTML Workstream, GPU for the Web Working Group, and Khronos? And maybe AOM?

[chrisn]

I suggest also adding Media WG for WebCodecs.

[palemieux]

@annevk What would the be point of contact at the following?

• AOM
• Khronos
• WHATWG HTML Workstream

How do you see the interaction between W3C HTML WG and WHATWG HTML Workstream working out in practice?

[palemieux]

I have added W3C GPU for the Web WG and W3C Media WG.

[annevk]

@palemieux in practice I would expect the Color CG to directly interact with the WHATWG HTML Workstream as per the W3C/WHATWG Memorandum.

I suggested AOM for the various media formats that also include color representation and Khronos for its WebGL work, which also relies on color representation.

[palemieux]

in practice I would expect the Color CG to directly interact with the WHATWG HTML Workstream as per the W3C/WHATWG Memorandum.

Ok. What is the mode of contact/interaction with WHATWG HTML Workstream?

I suggested AOM for the various media formats that also include color representation and Khronos for its WebGL work, which also relies on color representation.

Ok. We need a point of contact in both orgs.

[annevk]

@palemieux you essentially file an issue on the GitHub repository (whatwg/html). I think the same works for AOM and WebGL.

[palemieux]

you essentially file an issue on the GitHub repository (whatwg/html)

This one?

https://github.com/whatwg/html

I think the same works for AOM

Ok. I do not think we can add a liaison until we know how to contact them.

[annevk]

Yeah. For AOM you'd file an issue on the relevant repo as well: https://github.com/AOMediaCodec. I've contacted them that way in the past successfully!

[annevk]

@palemieux apologies for assuming familiarity before. I think we were talking past each other a bit. Khronos would be https://github.com/KhronosGroup/WebGL. Thanks for making the changes!

[palemieux]

@annevk Added liaison Khronos WebGL

[palemieux]

@annevk Hopefully you will be able to join the CG to help with these liaisons.

[chrisn]

If we're adding AOM, should we also consider adding ITU-T SG16 and SMPTE? Whether we actually need contact with those groups I guess depends on the extent we need to coordinate with them in practice.

[palemieux]

If we're adding AOM, should we also consider adding ITU-T SG16 and SMPTE? Whether we actually need contact with those groups I guess depends on the extent we need to coordinate with them in practice.

I am reluctant to adding liaisons for which there are no volunteers that commit to managing them.

[svgeesus]

The "Out of Scope" section in charters is for things that look like they might be in scope, but are not. For example because another group or org is already doing that. As an example the Web Fonts WG specifically excludes changes to OFF/OpenType, which are instead done by liaison to SC29.

If there is nothing in that category (as here) then the section is simply deleted.

[palemieux]

The consensus during the 2022-12-05 telecon is to keep the list of liaison organizations as-is for now.