| 01:48 | <Lachy> | Woo Hoo! The selectors api naming debate continues!!! :-) |
| 01:53 | <hober> | *groan* |
| 02:03 | <othermaciej> | Lachy: the bike shed needs to be *green*, dammit |
| 02:03 | <othermaciej> | I will stand for nothing less |
| 02:22 | <Lachy> | I don't have a problem with either selectorQuery, querySelector or matchSelector |
| 08:46 | <jgraham> | Lachy: What's the distinction between "DOM Processing" and "XML Processing"? Is DOM Processing just supposed to be normalising the content to use XMLisms where the XML way of doing something is different to the HTML5 way |
| 08:46 | <jgraham> | ? |
| 08:47 | <jgraham> | Also, it's not obvious to me that storage will always be as XHTML per-se (one could choose to store content in its original unaltered form or as XHTML-in-Atom or any other convenient format) |
| 08:48 | <jgraham> | (but in general I guess XHTML makes some sense) |
| 08:55 | <hsivonen> | Lachy: yes, the flowchart is reasonable. However, it is a matter of taste if you want to say "DOM" or something more abstract like "infoset processing" or somesuch |
| 08:55 | <Lachy> | ok, thanks |
| 09:00 | <hsivonen> | Lachy: the good thing with saying "DOM" is that the audience knows what it is. The bad thing is that in practice it sucks the most if you consider all the competing options you could plug there. |
| 09:01 | <Lachy> | I'm just getting sent a more professional looking version of it, which has changed a bit. I'll upload it now |
| 09:04 | <Lachy> | http://lachy.id.au/temp/CMS1.png |
| 09:05 | <hsivonen> | looks good |
| 09:06 | <Lachy> | Marcos created it for me |
| 09:06 | <annevk> | doesn't take into account editing etc. |
| 09:06 | <Lachy> | annevk, what do you mean? |
| 09:08 | <Lachy> | it doesn't have to be a completely accurate system flow chart, it's just an illustration to show how HTML and XHTML can be used together for use in my presentation |
| 09:09 | <annevk> | k |
| 09:10 | <karlUshi> | Lachy: you could also show that from the XML DB, you could serialize in many forms. Atom, PDF, HTML etc. |
| 09:12 | <Lachy> | yeah, I guess I could add a generic "Other Formats" output |
| 09:13 | <karlUshi> | which is one of the possible benefits of having an XML format somewhere. More tools available for this kind of conversion |
| 09:15 | <annevk> | just running HTML->DOM->XSLT works too |
| 09:18 | <karlUshi> | annevk: yes indeed if you develop your own tools |
| 09:18 | <karlUshi> | hmm time to move |
| 09:19 | <annevk> | most XSLT thingies have HTML support |
| 09:25 | <hsivonen> | If anyone wants to prove a point, I suggest hooking up the parser I've been writing to SAXON, so then other people would no longer have to develop their own tools. :-) |
| 09:25 | <hsivonen> | annevk: do you mean serialization support? |
| 09:25 | <annevk> | no, as input |
| 09:26 | <hsivonen> | annevk: oh. What XSLT thingies come with HTML support out of the box? |
| 09:26 | <Lachy> | new version http://lachy.id.au/temp/CMS1.png |
| 09:27 | annevk | thought several; might be mistaken |
| 09:37 | <zcorpan> | annevk: could you update http://html5.org/parsing-tests/testrunner.htm from trunk? |
| 10:30 | <hsivonen> | the whatwg blog spammers are getting more sophisticated. now the Polish pharmacy spammer something that actually relates to the post. |
| 11:15 | <hendry> | hsivonen: are you using akismet? |
| 11:15 | <hendry> | hsivonen: are you using akismet (wordpress spam filtering service)? |
| 11:16 | <hsivonen> | hendry: the whatwg blog is using it |
| 11:17 | <hsivonen> | hendry: I don't know how much spam it catches, but lately a number of spams have made it through the filter |
| 11:17 | <hsivonen> | hendry: generally German or Polish SEO attempts |
| 11:18 | <hendry> | i guess there is no moderation? i think you must have moderation too |
| 11:23 | <hsivonen> | hendry: Lachy and I are the moderators |
| 11:56 | <annevk> | zcorpan, updated |
| 12:14 | <hsivonen> | interesting bad UTF-8: http://photomatt.net/2007/07/13/on-php/ |
| 12:15 | <hsivonen> | near the string "Reluctant Acceptance" there are byte sequences 0xE2 0x80. I wonder how those came to be. |
