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

broaden the purpose #391

Open
RufaelDev opened this issue Dec 2, 2019 · 1 comment
Open

broaden the purpose #391

RufaelDev opened this issue Dec 2, 2019 · 1 comment

Comments

@RufaelDev
Copy link

Section on purpose may be a bit more elaborative. "expected interoperability" should not be the only purpose, the spec should also attempt to improve quality/playback and stability, and perhaps load on servers. This is what would make it interesting for people to consider this work.

@sandersaares
Copy link
Member

Well, DASH-IF publishes implementation guidelines for interoperability, first and foremost. I believe this has always been the case and is unlikely to change. Interoperability is the core reason the organization even exists.

When other beneficial traits come along for the ride with interoperability guidelines, that's nice, but I think any broadening of the agenda is a bigger topic than suitable for handling in the context of the timing model. Perhaps you would like to put forward the case for scope expansion in the main IOP group discussions? I will move this issue from the timing model tracker to the main IOP tracker so it can be more visible for consideration by the wider audience.

@sandersaares sandersaares transferred this issue from Dash-Industry-Forum/Guidelines-TimingModel Dec 4, 2019
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

2 participants