- From: youennf <notifications@github.com>
- Date: Mon, 02 Sep 2019 05:39:13 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 2 September 2019 12:39:34 UTC
> Having two living specs has been a source of confusion for developers Agreed. My fear is that going forward with v1 as a REC might further increase confusion, especially since v1, by the time it becomes a REC, might be quite different from the living standard that browsers will implement. > Going to CR is part of W3C's legal process, but I understand that once we've done that for V1, we can continue with a living standard, Is it going to CR or REC which is a prerequisite? Going from CR to PR and then REC will probably take some substantial time and energy, at least to the chairs and editors. For instance, there will be a need to show full interoperability of the spec. There will be a need to prove that all issues related to v1 have been properly dealt with. > we already know we want to move to a "living spec" model once v1 is done, but not for v1 I am not clear whether the group does not want to do that or cannot do that. @ylafon, can you clarify this? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1458#issuecomment-527133175
Received on Monday, 2 September 2019 12:39:34 UTC