Hi Marcos, (from 11/28/13): > Knowing what the differences are is important. If there are none, that's ok. But please make that clear. ... > I'd be satisfied if the above is addressed before proceeding. Just a sentence or two would make a big difference! Makes sense. We’ve clarified this in the spec: — snip from https://dvcs.w3.org/hg/notifications/raw-file/tip/Overview.html This feature is also being worked on by the WHATWG <http://www.whatwg.org/>. The bulk of the text of this specification is available in the WHATWG Notifications API Standard <http://notifications.spec.whatwg.org/>, under a license that permits reuse of the specification text. The two specifications are normatively identical up to WHATWG revision 998421f <https://github.com/whatwg/notifications/commit/998421f> (W3C revision 498b5397ed3f <https://dvcs.w3.org/hg/notifications/raw-file/498b5397ed3f/Overview.html>). Since that revision, the WHATWG is exploring new features which may be incorporated into future levels of this specification. Bugfixes and editorial changes have been merged to minimize divergence. — snip (from 12/1/13): > If the bulk of implementers are working off the W3C of, then the WHATWG version should layer it’s extensions on top of the W3C one, no? That’s not really for me to say—it is up to the WHATWG to determine how they wish to craft their spec in relation to the W3C’s. > It sounds like the two specs are diverging - and this makes me worry. The W3C version is the stable, v1 snapshot of the spec. IMO, the differences that have been introduced in the WHATWG version consist of refactoring and new features, which could be used as the basis of a future version of the W3C spec if we as a WG decide to pursue rechartering to work on a v2. Jon
Received on Friday, 21 November 2014 23:30:30 UTC