Steps to transition the spec in case of WG closure

Hello,

During the call yesterday, I said I would investigate the steps needed to be able to further incubate the TV Control API in another group in the event where the Working Group gets closed. Good news is that we would not need to do anything, because the charter of the TV Control WG clearly says that the group will use the W3C Software and Document License for all its deliverables:
http://www.w3.org/2016/03/tvcontrol.html#licensing

That license allows the creation of derivatives.

Bad news is that this seems to have fallen through the cracks in practice and drafts of the TV Control API have actually been published under the more restrictive W3C Document License. I apologize for this. That's an oversight. Next update we publish (either a Working Draft or a WG Note) should use the right license, and I prepared a PR for that:
https://github.com/w3c/tvcontrol-api/pull/58

For what it's worth, please note that patent commitments do not apply outside of the Recommendation track, so they would not transition to whichever group takes over the spec.

There is no need to e.g. nominate a specific Community Group that could take over edition of the spec either.

If the Working Group closes, per process, the TV Control API specification will have to be published as a Working Group Note. That Note may only include a warning that says "work discontinued" and not the actual API, or it can contain the warning *and* the rest of the text. That is up to the group to decide. If we follow the former approach (no API), the group should publish an updated Working Draft that contains the whole API published under the right license first.

Thanks,
Francois.

Received on Wednesday, 3 May 2017 15:30:32 UTC