-
Notifications
You must be signed in to change notification settings - Fork 79
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
EME registry: Establish a update process & home #104
Comments
Before we publish to a new URL, we should finalize the file structure: issue #105. |
@plehegar: How do we make progress on Issues 104 and 105? |
@paulbrucecotton sorry, I've been swamped. If I don't make progress by Tuesday, I'll ask @yfuna if he can help. |
The publication system isn't up to the task unfortunately. I'll set an alternative solution within 2 weeks. |
How about the following #147 ? Basically, all the files would appear under https://www.w3.org/html/media/ |
Can we also fix the current WD reference fro [EME-REGISTRY] that currently contains an incorrect URL that generates a 404? [EME-REGISTRY] David Dorwin; Adrian Bateman; Mark Watson. Encrypted Media Extensions Stream Format and Initialization Data Format Registry. URL: initdata-format-registry.html |
As soon the PR is merged, it will generate a new WD that will have the proper link. |
I think we should resolve #105 first so that the new paths are the permanent paths. |
My initial take was that this proposal was straightforward, but it seems an awkward split for ISOBMFF and CENC, which are closely coupled. Can you expand on scenarios you have in mind that would require this restructuring? |
Update on this front: Automatic publication will support Working Group notes within 10 days. So, I now feel comfortable recommending that path again since it will be easy to update the drafts. We should:
|
@plehegar: Since no one has expressed concern about your three items above can we proceed with publication of the WG Notes? |
The new structure has been merged. |
@plehegar expects to publish the non-REC track EME registry on Mon May 2. When that is done this issue will be closed. |
I'm still working on updating the JS to generate proper references. The locations will look like: https://www.w3.org/TR/eme-initdata |
I assume the above URLs will continue to return 404 until they are published on the TR page next week. |
correct. We're on track for publication on May 10. |
And we shipped. Next step is to make sure the /TR docs get updated on commits in this repo. |
|
The fix tries to use relative links with it's an ED and use /TR links when it's not. |
We need to establish a permanent location for the non-REC track EME registry as was done for the MSE registry MSE bug 25581.
@plehegar
The text was updated successfully, but these errors were encountered: