| 06:22 | <annevk> | URL Standard's Twitter hook failed due to an authentication failure... |
| 06:22 | <annevk> | miketaylr: didn't you have something similar with Compat? |
| 06:31 | <cvrebert> | FYI: w3bug.com is now a thing, just like crbug.com etc; e.g. http://w3bug.com/28673 |
| 06:33 | <annevk> | Now it works again... |
| 06:34 | <annevk> | cvrebert: interesting default redirect :-) |
| 06:34 | <annevk> | cvrebert: note that we're mostly migrating everything to GitHub at this point |
| 06:35 | <cvrebert> | annevk: HTML itself seeming to be the exception :-) |
| 06:35 | <annevk> | cvrebert: patience :-) |
| 06:36 | cvrebert | adds a calendar event for one eon from now |
| 09:41 | <annevk> | TabAtkins: if I have for=URL for the model, what would make sense to describe syntax? |
| 09:42 | <annevk> | TabAtkins: for=url-syntax or some such? |
| 11:02 | <annevk> | philipj: any chance getting updates on https://github.com/whatwg/xhr/issues/19 at some point? |
| 11:02 | <philipj> | annevk: that would be nice, yeah |
| 11:03 | <philipj> | I'll ping some more |
| 11:47 | <annevk> | Bit annoying to see Blink deprecate getUserMedia() outside of secure contexts now, while earlier opposing this in the standards venue. |
| 11:48 | <annevk> | https://lists.w3.org/Archives/Public/public-media-capture/2014Oct/thread.html#msg79 |
| 12:39 | <Ms2ger> | annevk, r? https://github.com/w3c/web-platform-tests/pull/2078 |
| 12:41 | <annevk> | Ms2ger: r+ |
| 12:41 | <Ms2ger> | Ta |
| 13:12 | <annevk> | SimonSapin: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26398 |
| 13:12 | <annevk> | SimonSapin: note also that HTML currently contains the exact same algorithm |
| 13:12 | <annevk> | SimonSapin: that bit hasn't merged yet |
| 13:18 | <annevk> | JakeA: https://twitter.com/jaffathecake/status/632178499915284480 heh. This applies to writing standards too. |
| 13:19 | <annevk> | JakeA: fortunately the couple dozen folks that read a standard will then use that knowledge to change browsers and the web. So there's some ROI. |
| 13:23 | <JakeA> | Yeah, with standards the benefit is huge even if very few read. I guess in some way it's pretty cool how far developers can get with the web with only a vague understanding of the spec beneath |
| 13:35 | <TabAtkins> | annevk: Don't use hyphens unless absolutely necessary |
| 13:39 | <jgraham> | Whereas em dashes should — it goes without saying — be used with reckless abandon. |
| 13:49 | <SimonSapin> | annevk: I haven’t done the testing I said I’d do… a year ago :/ |
| 14:00 | <annevk> | TabAtkins: or maybe syntax can be a different type? |
| 14:02 | <Ms2ger> | Surely em-dashes�unlike en-dashes�should not have spaces around them |
| 14:02 | <TabAtkins> | "grammar" is a type, but I don't know what you're using it for |
| 14:03 | <jgraham> | Ms2ger: If you want them to look like crap because it says in a book somewhere it's "right" then sure |
| 14:06 | <annevk> | TabAtkins: I want to rewrite https://url.spec.whatwg.org/#url-writing and make it use <dfn>s that are not equivalent to <dfn for=URL> |
| 14:06 | <annevk> | TabAtkins: but I'll probably reuse some terms |
| 14:06 | <annevk> | TabAtkins: it's basically syntax productions |
| 14:49 | <annevk> | SimonSapin: I figured. I fixed a couple of your issues though, most over a year old... Quick test here with application/x-www-form-urlencoded shows that most code points are escaped by Firefox, so I'll leave that as-is for now at least until HTML references this algorithm rather than a duplicate. |
| 14:50 | <SimonSapin> | ok |
| 15:21 | <caitp> | you guys were really patient with whatwg/xhr#24, nice |
| 15:26 | <annevk> | caitp: I'm trying to improve, but I notice I'm still very brief at times |
| 15:27 | <annevk> | caitp: changing habits is hard, fortunately there's tyoshino who does the right thing by default :-) |
| 15:47 | <miketaylr> | annevk: yeah, but i think it only error'd for the first commit/tweet |
| 15:48 | <annevk> | miketaylr: sortof similar here |
| 16:17 | <micahf> | hey there! i'm interested in making a "yaml-like" ontology format for myself |
| 16:18 | <micahf> | (for my blog) |
| 16:18 | <micahf> | so the idea is, i will write my blog in plain html (or whatever plain text format i choose) |
| 16:19 | <micahf> | then i will make metadata description files that are basically just yaml with little bits of xpath or regular expressions |
| 16:20 | <micahf> | so say I use an unordered list for "tags". "tags" would be a property of a blog post |
| 16:22 | <micahf> | then in the yaml there would be a property "tag", with an xpath string that points to the list item values |
| 16:24 | <annevk> | what's holding you back? |
| 16:26 | <micahf> | annevk, well, i've heard and read about web ontology formats, but i'm not so familiar with the goals and challenges faced when standards like OWL/RDF were created |
| 16:26 | <micahf> | annevk, part of me wants to get a better understanding, but maybe that would taint my raw, innocent creative spirit |
| 16:27 | <annevk> | micahf: I see, this might be wrong place |
| 16:27 | <micahf> | annevk, how's that? |
| 16:28 | <annevk> | micahf: there's not much semantic web discussion here, I think #swig might be a place where you can go |
| 16:29 | <micahf> | annevk, thanks! |