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

EME registry: Establish a update process & home #104

Closed
ddorwin opened this issue Oct 19, 2015 · 23 comments
Closed

EME registry: Establish a update process & home #104

ddorwin opened this issue Oct 19, 2015 · 23 comments
Assignees
Milestone

Comments

@ddorwin
Copy link
Contributor

ddorwin commented Oct 19, 2015

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

@ddorwin
Copy link
Contributor Author

ddorwin commented Oct 20, 2015

Before we publish to a new URL, we should finalize the file structure: issue #105.

@paulbrucecotton
Copy link

@plehegar: How do we make progress on Issues 104 and 105?

@plehegar
Copy link
Member

@paulbrucecotton sorry, I've been swamped. If I don't make progress by Tuesday, I'll ask @yfuna if he can help.

@plehegar
Copy link
Member

plehegar commented Feb 2, 2016

The publication system isn't up to the task unfortunately. I'll set an alternative solution within 2 weeks.

@plehegar
Copy link
Member

How about the following #147 ?

Basically, all the files would appear under https://www.w3.org/html/media/

@paulbrucecotton
Copy link

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

@plehegar
Copy link
Member

As soon the PR is merged, it will generate a new WD that will have the proper link.
If someone is willing to give a +1, I'll do the merge.

@ddorwin
Copy link
Contributor Author

ddorwin commented Feb 18, 2016

I think we should resolve #105 first so that the new paths are the permanent paths.

@jdsmith3000
Copy link
Contributor

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?

@ddorwin
Copy link
Contributor Author

ddorwin commented Feb 26, 2016

See #105 for the "correctness" reason and #106 for the practical reason.

@plehegar
Copy link
Member

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:

  1. be ok that we want the registries as Working Group Notes
  2. be ok with plh taking a snapshot and push those manually for the first publication
  3. be ok with plh setting up the automatic publishing system on every commit for those documents.

@paulbrucecotton
Copy link

@plehegar: Since no one has expressed concern about your three items above can we proceed with publication of the WG Notes?

@ddorwin
Copy link
Contributor Author

ddorwin commented Apr 22, 2016

Let me land PR #167 for #105 first.

There will be some work necessary to get the links between the WD and Notes version of the spec and registry, respectively, to point to each other. Currently, the ED of both reference each other correctly.

@ddorwin ddorwin removed the blocked label Apr 26, 2016
@ddorwin
Copy link
Contributor Author

ddorwin commented Apr 26, 2016

The new structure has been merged.

@paulbrucecotton
Copy link

@plehegar expects to publish the non-REC track EME registry on Mon May 2. When that is done this issue will be closed.

@plehegar
Copy link
Member

plehegar commented May 3, 2016

@paulbrucecotton
Copy link

I assume the above URLs will continue to return 404 until they are published on the TR page next week.

@plehegar
Copy link
Member

plehegar commented May 5, 2016

correct. We're on track for publication on May 10.

@plehegar
Copy link
Member

And we shipped. Next step is to make sure the /TR docs get updated on commits in this repo.

@paulbrucecotton
Copy link

paulbrucecotton commented May 16, 2016

@plehegar - Since these documents have been published, I believe we can close this issue.

@plehegar plehegar added this to the V1Editorial milestone May 17, 2016
@plehegar plehegar removed this from the V1 milestone May 17, 2016
@ddorwin
Copy link
Contributor Author

ddorwin commented Jun 1, 2016

@plehegar:

  1. The URLs above do not work. Only dated URLs like https://www.w3.org/TR/2016/NOTE-eme-stream-webm-20160510/ were pubished.
  2. The registry URLs in the published spec (i.e. for WD and later maturities) are still relative rather than pointing to https://www.w3.org/TR/eme-initdata, etc. See https://www.w3.org/TR/encrypted-media/#bib-EME-INITDATA-REGISTRY. This likely needs to be fixed in encrypted-media.js, but it also depends on the first item.

@ddorwin ddorwin modified the milestones: V1NonBlocking, V1Editorial Jun 1, 2016
@plehegar
Copy link
Member

plehegar commented Jun 2, 2016

The fix tries to use relative links with it's an ED and use /TR links when it's not.

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

4 participants