Congrats, W3C, your plagiarism confused yet another developer:https://twitter.com/antumbral/statuses/460723070743752704 …
@tabatkins @BrendanEich they are incorporating the spec into the canon of approved W3C specs, which is what CC0 is trying to enable.
-
-
@wycats They're incorporating an *out-of-date fork* into W3C canon, pretending that two other people did anything... -
@wycats ...and confusing developers the world over with this bullshit. It's dishonest and actively harmful. -
@tabatkins there's a lot more going on here and you know it. Let's get the W3C licensing policy fixed posthaste. -
@wycats I'm confused. None of the problems with this are about the W3C's licensing policy. -
@tabatkins they are.@annevk does work at WHATWG and not W3C because of the licensing policy. Follow the yellow brick road. - 1 more reply
New conversation -
-
-
@wycats@tabatkins@BrendanEich CC0 is to enable http://annevankesteren.nl/2013/03/zero and nothing else. -
@annevk@tabatkins@BrendanEich the point of CC0 is that you don't get to decide what it facilitates. -
-
@tabatkins@annevk complaining about "plagiarism" obscures the real issue, which is W3C intransigence around fixing its licensing. -
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.