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

Evaluate size of overall CMCD data. #122

Open
PCaponetti opened this issue Feb 15, 2024 · 0 comments
Open

Evaluate size of overall CMCD data. #122

PCaponetti opened this issue Feb 15, 2024 · 0 comments

Comments

@PCaponetti
Copy link
Collaborator

Through conversations with video providers it became clear that CMCD may get greater market penetration if the size of the overall data was smaller. CMCD fills logs, and logs cost money to store, analyze, and propagate. One might point to the fact that all keys are optional in CMCD v1, and the vast majority are optional in v2, but there are many video providers using third party players that have only the ability to turn CMCD on or off as a whole, not by key.

This issue is meant to be evaluated late in the CMCD v2 definition to be able to look across all keys and decide whether something should be done to mitigate these size concerns. Thoughts include putting size constraints on keys, or maybe defining different verbosity levels that group keys together for different use cases.

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

No branches or pull requests

1 participant