| mid-September tumbling | |
| @m_ott @mmatuzo I’d add @Hixie, @annevk, @zcorpan. | |
| @zcorpan @foolip @sundress @soMelanieSaid @Hixie @annevk Yeah, I’m pretty sure I picked up this pronunciation from Anne. | |
| RT @hober: It’s increasingly obvious to me that not including @Hixie’s Baby Steps in the Design Principles doc before it got parked was a b… | |
| It’s increasingly obvious to me that not including @Hixie’s Baby Steps in the Design Principles doc before it got parked was a big mistake. | |
| @stevefaulkner I think it's a stretch to say there have been no objections to it. How do you characterize @hixie's emails as not objecting? | |
| @rwaldron did we read the same email? @Hixie’s mail was measured and dispassionate, unlike your unprofessional tweet just now. | |
| @mattmay the real tragedy is that @hixie was required to make such a change in the first place. #a11ytheater #html5 | |
| @WHATWG yo dawg, I heard you like commands, so @hixie put a command='' in your <command> so you can reference other commands. | |
| @rmondello you just pulled a @Hixie. | |
| @meyerweb both specs have the same source. @hixie would have to add script to his publishing workflow to s/section/div.section/ in one case. | |
| Not everyone likes @Hixie's spec writing style, but it makes implementing the tokenizer require almost no thought. This is a *good* thing. | |
| Nice. @Hixie paves another cowpath worth writing down somewhere, and we get <select required> as a side effect. http://hbr.me/27FxPN | |
| @cssquirrel: WRT joining the HTMLWG, I think @hixie's writeup makes the most sense: http://bit.ly/3usk4J | |
| Might skip writing up my rant on prefix-based indirection & ISSUE-41, as @Hixie nailed it: http://tr.im/prefix_antipattern #html5 #rdfa #w3c | |
| @Hixie: hCard has a pattern for that: fn == org and no explicit n specified | |
| Anglospheric governance for online communities — BarCamp San Diego 2 — Theresa O’Connor | |
| Interoperability | |
| HTML 5 | |
| Roll your own standards body | |