Is this diagram useful, btw? I can't decide. My hesitation to remove it may be colored by hours I spent hand-coding it :P

I would love more diagrams in specifications and once I find a sensible way to generate them I would include them elsewhere too. It helps a lot with checking the overall flow or interdependencies.

(In reply to Dimitri Glazkov from comment #1)
> Is this diagram useful, btw? I can't decide. My hesitation to remove it may
> be colored by hours I spent hand-coding it :P

(In reply to Anne from comment #2)
> I would love more diagrams in specifications

Agreed with Anne here. I think in general spec readers/reviewers/implementors really appreciate and benefit from good diagrams, so trying to provide good ones is a great goal.

(And I think diagrams are one of those things that users of the spec often end up just taking for granted when they have them; it's one of those many things that reviewers don't take time to make positive comments about. Instead, you're only going to hear from them when there's something wrong in the diagram. That suggests that if you want to measure whether a diagram is being used, you should put some easter-eggish error into it to see how many people notice and comment...)

Moved to https://github.com/w3c/webcomponents/issues/158