Re: [w3c/charter-html] Charter must state a reason when duplicating work done elsewhere (#139)

> We have a pretty good understanding with IETF about where their scope
ends and where our scope begins.

Indeed IETF and W3C typically don't step on each others toes, there isn't really a problem to be solved there.

The problem is with WHATWG documents. I do not think we should be stepping on each others toes just because we're used to do so, and merely stating that we'll make an effort to avoid hurting each other along the way is a too weak. If either party simply stopped working on specs the other is working on, there would be no divergence and duplication of effort. From a WebPlatform WG point of view, why the WHATWG will not stop working on such specs is immaterial. They've made it clear that they would not. If that were to change, we'd take that into account, but for now, it's not changing.

So we can decide to unilaterally stop the duplication. If we chose not to, and decide to bear the cost, and take the compatibility and confusion risk of having diverging specs, we need a reason.

And as I said above, the various reasons I've heard seem to demand conflicting courses of action, as I discuss in my previous comment. So we not only need to have "at least one reason", we need to be explicit about what we're after, so as to make sure that the actions taken are not in conflict with that.

-- 
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/charter-html/issues/139#issuecomment-301732797