- From: Marcos Caceres <w3c@marcosc.com>
- Date: Fri, 29 Nov 2013 13:59:31 +0000
- To: Andrew Wilson <atwilson@google.com>
- Cc: Jon Lee <jonlee@apple.com>, public-web-notification <public-web-notification@w3.org>, Arthur Barstow <art.barstow@nokia.com>
On Friday, 29 November 2013 at 08:51, Andrew Wilson wrote: > I don't think the W3C spec can or should claim primacy over the WHATWG specification - they are just different (albeit related) entities. In fact, I'd argue that it's not the role of the W3C spec to highlight differences between itself and any other specs out there, nor should it be instructing implementors to ignore other specifications. But this one just copy/pastes from the other one, no? That's completely different than saying "this spec is different from some other spec". If one spec is going to copy/paste from another one, then it should be clear that they are exactly the same bar the boilerplate (and are being synchronised and how often). If the spec has modified the source spec (the WHATWG one), then it should be clear in what way they differ. I don't know which spec to review otherwise. Or why I should bother paying attention to this one (not as a judgement, but from an implementation perspective). Also, what happens if the WHATWG changes once you enter LC or CR in a substantive way? > In this specific case, the WHATWG spec is a living document, so any attempt to enumerate differences would quickly become stale. Does that mean that you are planning to freeze this spec? Did you copy and paste from a particular date in time and fork from there? Is this a fork? -- Marcos Caceres
Received on Friday, 29 November 2013 13:58:34 UTC