/irc-logs / w3c / #html-wg / 2007-05-07 / end

Options:

  1. # Session Start: Mon May 07 00:00:00 2007
  2. # Session Ident: #html-wg
  3. # [00:05] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  4. # [00:25] * Quits: heycam (cam@203.214.12.71) (Ping timeout)
  5. # [00:34] * Joins: hyatt (hyatt@24.6.91.161)
  6. # [00:51] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  7. # [00:51] * Joins: schepers (schepers@72.29.239.177)
  8. # [00:54] <zcorpan_> so... much... noise... on... public-...html... must... breathe
  9. # [00:56] <Dashiva> And 90% of it is echoed on www-html...
  10. # [00:56] <zcorpan_> glad i'm not subscribed to www-html then
  11. # [00:57] <jgraham> Philip`: Dunno. I'll file a bug
  12. # [00:57] <Philip`> Any ideas of some signal to feed in, to help the ratio and maybe give people some idea of what would be actual useful discussion?
  13. # [00:58] <Dashiva> I'm on the "em and i are used with no real difference, so just stop pretending they're different" side
  14. # [01:00] <Philip`> jgraham: Okay, thanks - I just deleted that page from my database so I don't have to worry about it any more :-)
  15. # [01:03] <jgraham> Hmm. I wonder how much signal I would loose just setting up a filter to delete all email containing the word "emphasis"?
  16. # [01:04] * jgraham has no intention of actually doing that
  17. # [01:04] <Dashiva> It would wipe out most of the mail, so you might end up with SNR undefined :)
  18. # [01:07] <jgraham> Philip`: Issue 35 filed http://code.google.com/p/html5lib/issues/detail?id=35
  19. # [01:14] * Joins: heycam (cam@130.194.72.84)
  20. # [01:17] * Parts: hasather (hasather@81.235.209.174)
  21. # [01:18] <Philip`> I'll see if I can reproduce the issue more easily...
  22. # [01:19] * Quits: edas (edaspet@88.191.34.123) (Client exited)
  23. # [01:19] * jgraham wonders if the <em>/<i> debate could be avoided for HTML6 by specifying default presentations in multiple media
  24. # [01:20] <jgraham> Of course, if this debate doesn't stop soon we're all going to be using Silverlight on Windows and there won't /be/ a HTML6
  25. # [01:21] <Dashiva> At this pace, we'll all be dead before HTML6 would come into being anyway
  26. # [01:21] <jgraham> s/6/5/
  27. # [01:21] <jgraham> ;)
  28. # [01:23] <Philip`> The WHATWG could make HTML6 and then implement an HTML6 web browser inside Silverlight so it can run on IE without Microsoft having to get involved
  29. # [01:24] <Dashiva> Replace the entire computer with a thin silverlight client?
  30. # [01:26] <Philip`> I like how the 'customer quotes' on the Silverlight page is from an online advertising company - I think I'd be perfectly happy if I couldn't see their content
  31. # [01:27] * Philip` wonders if it'd be useful as a way to implement <video> and <canvas>
  32. # [01:28] <wilhelm> Sounds painful.
  33. # [01:40] * Quits: heycam (cam@130.194.72.84) (Quit: bye)
  34. # [01:40] * Joins: heycam (cam@130.194.72.84)
  35. # [01:46] * Joins: MrNaz (Naz@203.214.95.166)
  36. # [01:49] * Quits: schepers (schepers@72.29.239.177) (Quit: Free at last!)
  37. # [01:49] <Philip`> Wouldn't people with aural browsers want <i> to be rendered in a different way to normal text so that they can disambiguate sentences like "<i>The Thing</i> was interesting" to the same extent that people with visual browsers can? Throwing away that information seems worse than rendering it in a potentially unsuitable tone of voice
  38. # [01:51] <Philip`> (in which case it'd be almost precisely identical to <em>, and everyone would just deduce the real semantics in their heads because that's what heads are good for)
  39. # [01:57] <jgraham> Philip`: I don't know. If <i> and <em> are really treated identically by all UAs then I don't see how anyone can argue the distinction is anything but academic
  40. # [01:58] * Joins: hyatt (hyatt@24.6.91.161)
  41. # [01:58] <jgraham> I think TV Raman said he had his UA set up like that but I think someone else said they didn't
  42. # [02:02] <Philip`> Would people stop arguing over it just because it's only academic?
  43. # [02:04] * Quits: gavin_ (gavin@74.103.208.221) (Ping timeout)
  44. # [02:10] * Joins: gavin_ (gavin@74.103.208.221)
  45. # [02:19] * Quits: AGraf (Ashe@213.47.199.86) (Quit: Quit)
  46. # [02:25] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  47. # [02:32] * Quits: zdenko (zdenko@84.255.203.169) (Quit: zdenko)
  48. # [02:34] * Quits: zcorpan_ (zcorpan@84.216.42.227) (Ping timeout)
  49. # [02:55] <cying> i wish for more brevity on the html-wg mailing list
  50. # [02:55] <cying> i feel compelled to read everything so i could be somewhat informed in raising future issues without being accidentally redundant
  51. # [02:57] <mjs> we're having a tempest tea party
  52. # [02:57] <mjs> cying: I'm trying to stop reading everything, as it is draining too much time
  53. # [02:58] <cying> mjs: i'll clarify. i've been unsuccessful at reading everything, i can get to roughly 20% of the traffic
  54. # [02:59] <cying> mjs: but i'm biding my time til something i'm knowledgable in comes up, like content authoring or graphics
  55. # [02:59] <mjs> I actually have been reading everything
  56. # [02:59] <mjs> I am hoping it will get easier once we have a spec
  57. # [02:59] <mjs> and then have specific focus areas for review
  58. # [02:59] <cying> ahhhh
  59. # [02:59] <cying> maybe people should tag their emails
  60. # [03:00] <cying> or some kind of communal tagging emaily thing
  61. # [03:02] <mjs> I'm mainly trying to focus a lot until we have a spec and a smoothly running process that's leading to forward progress
  62. # [03:02] <mjs> but it's a lot of work getting over that initial hump
  63. # [03:03] <cying> mjs: indeed
  64. # [03:07] * Quits: tH (r@87.102.20.82) (Quit: ChatZilla 0.9.78.1-rdmsoft [XULRunner 1.8.0.9/2006120508])
  65. # [03:07] <cying> i'm contemplating a simple python or ruby implementation of HTML5 to serve as a model to experiment with features and behavior
  66. # [03:08] <mjs> there's a python implementation of the parsing spec (not up to date though)
  67. # [03:08] <cying> oooh
  68. # [03:26] <Philip`> If you wanted to help update/fix/optimise the current html5lib, I believe that would be quite useful
  69. # [03:27] * Joins: hyatt (hyatt@24.6.91.161)
  70. # [03:38] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  71. # [04:03] * Joins: Zeros (Zeros-Elip@69.140.48.129)
  72. # [04:03] * Quits: Zeros (Zeros-Elip@69.140.48.129) (Quit: Leaving)
  73. # [04:04] <Hixie> man, a lot of threads have author patterns that go: A B A C A D A E A B A C A D A E A B A C A D A E
  74. # [04:04] <Hixie> how does A have so much time!
  75. # [04:05] <Hixie> and how come the non-A viewpoints are in such great majority and so coordinated in their responses!
  76. # [04:05] * Joins: hyatt (hyatt@24.6.91.161)
  77. # [04:05] <Hixie> are you guys taking turns fielding e-mails or something?
  78. # [04:12] * Quits: gavin_ (gavin@74.103.208.221) (Ping timeout)
  79. # [04:17] * Joins: gavin_ (gavin@74.103.208.221)
  80. # [04:20] <cying> Philip`: what's html5lib? the python parser?
  81. # [04:21] * Joins: dbaron (dbaron@72.29.239.177)
  82. # [04:22] <cying> Hixie: i'm actually an amalgam of doug schepers, john boyer, murray maloney, and you. ;-)
  83. # [04:22] * Joins: kazuhito (chatzilla@142.59.90.219)
  84. # [04:23] <Philip`> cying: Yes - http://code.google.com/p/html5lib/
  85. # [04:23] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  86. # [04:23] <cying> Hixie: maciej is also jim jewett and james graham
  87. # [04:23] <cying> Philip`: ooh i'll have a look
  88. # [04:24] <cying> Philip`: ooooh, very nice and clean
  89. # [04:37] * Joins: Zeros (Zeros-Elip@69.140.48.129)
  90. # [04:56] * Joins: hyatt (hyatt@24.6.91.161)
  91. # [05:21] * Quits: kazuhito (chatzilla@142.59.90.219) (Ping timeout)
  92. # [05:28] * Joins: kazuhito (chatzilla@142.59.90.219)
  93. # [05:59] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  94. # [06:00] * Joins: myakura (myakura@125.194.247.196)
  95. # [06:07] * Joins: hyatt (hyatt@24.6.91.161)
  96. # [06:08] * Quits: dbaron (dbaron@72.29.239.177) (Quit: 8403864 bytes have been tenured, next gc will be global.)
  97. # [06:19] * Quits: gavin_ (gavin@74.103.208.221) (Ping timeout)
  98. # [06:21] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  99. # [06:24] * Joins: gavin_ (gavin@74.103.208.221)
  100. # [07:23] * Joins: hyatt (hyatt@24.6.91.161)
  101. # [07:29] <hyatt> Hixie: yt?
  102. # [07:32] * Quits: Zeros (Zeros-Elip@69.140.48.129) (Quit: Leaving)
  103. # [08:21] * Quits: Lachy (Lachlan@203.214.143.196) (Connection reset by peer)
  104. # [08:21] * Joins: Lachy (Lachlan@203.214.143.196)
  105. # [08:26] * Quits: gavin_ (gavin@74.103.208.221) (Ping timeout)
  106. # [08:31] * Joins: gavin_ (gavin@74.103.208.221)
  107. # [08:44] <Hixie> hyatt: vaguely
  108. # [08:45] <hyatt> heh
  109. # [08:45] <Hixie> wassup?
  110. # [08:50] * Joins: loic (loic@90.29.107.221)
  111. # [08:52] <mjs> cying: I don't think I have any secret identities
  112. # [08:53] <cying> mjs: a likely story
  113. # [09:02] * Quits: heycam (cam@130.194.72.84) (Quit: bye)
  114. # [09:14] * Joins: schepers (schepers@208.38.57.47)
  115. # [09:31] * Joins: zdenko (zdenko@193.77.152.244)
  116. # [09:36] * Parts: inimino (chatzilla@75.71.88.233)
  117. # [09:45] * Quits: cying (cying@75.41.252.252) (Quit: cying)
  118. # [09:45] * Joins: ROBOd (robod@86.34.246.154)
  119. # [09:48] <anne> html5lib is further than the current spec, I think, mjs
  120. # [09:48] <anne> although it has some bugs
  121. # [09:48] * anne sees loads of e-mails about cleaning a house
  122. # [09:48] * anne ... spam!
  123. # [09:49] * Joins: heycam (cam@203.214.12.71)
  124. # [09:52] * Lachy wonders which post he could link to from a blog entry, which would give a realitively good overview of the discussion about b and i
  125. # [09:53] <hsivonen> Lachy: one from Tina, one from Murray
  126. # [09:53] <Lachy> I was thinking about one from mjs
  127. # [09:54] <hsivonen> Lachy: ok. then there's mine from January on the whatwg list
  128. # [09:54] <anne> 544 reasons to look at XForms...
  129. # [09:54] <Lachy> I'll do one from each, I just have to find one that illustrates their points of view
  130. # [09:54] <anne> did they suddenly start integrating with HTML4?
  131. # [09:54] <anne> and DOM Level 2 HTML?
  132. # [09:54] * anne missed the announcement
  133. # [09:55] <hsivonen> anne: they? integrate? is the Forms WG now defining how to put XForms in text/html?
  134. # [09:55] <Lachy> hsivonen, do you know specifically which one from you on whatwg?
  135. # [09:56] <anne> hsivonen, I don't think so
  136. # [09:56] <anne> hsivonen, but John thinks that 544 errata + new features (or 700) items make a good reason to look at XForms
  137. # [09:57] <Lachy> this is the blog entry draft http://lachy.id.au/temp/b-and-i
  138. # [09:58] <hsivonen> Lachy: http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2007-January/009060.html
  139. # [09:59] <hyatt> god this is getting really really complicated
  140. # [10:00] * hyatt beats his head against the desk
  141. # [10:00] * hyatt should just go back to the old slow way he was doing @font-face
  142. # [10:01] <Lachy> hsivonen, thanks
  143. # [10:02] <hyatt> it boggles my mind that this much email has been generated over <i>
  144. # [10:02] <Lachy> hyatt, it's called bikshedding
  145. # [10:02] <Lachy> bikeshedding*
  146. # [10:02] <hyatt> we could be advancing the web by developing all sorts of cool new features
  147. # [10:02] <hyatt> but no, let's waste 10000 messages talking about... <i>.
  148. # [10:03] <hyatt> Lachy: yeah, seriously.
  149. # [10:03] <hyatt> some serious bike shed painting going on
  150. # [10:08] <hyatt> yes, this works
  151. # [10:08] <hyatt> unbelievable
  152. # [10:08] <Lachy> what works?
  153. # [10:08] <hyatt> @font-face
  154. # [10:08] * hyatt has been hacking it up for webkit
  155. # [10:09] <Lachy> oh, I didn't think it was going to get implemented in favour of something easier
  156. # [10:09] <hyatt> meh tina pissed me off
  157. # [10:09] <hyatt> so i implemented it :)
  158. # [10:09] <Lachy> what happened to the idea of using font-family: url(font);
  159. # [10:09] <hyatt> plus it proves i'll implement a spec i hate
  160. # [10:09] <hyatt> :)
  161. # [10:09] <hsivonen> hyatt: what are you doing about panose?
  162. # [10:09] <hyatt> although after actually learning how @font-face works
  163. # [10:10] <hyatt> i see that it's way better than the URL solution
  164. # [10:10] <hyatt> the problem with the @font-face spec really is just that i don't think it needs to have as many features
  165. # [10:10] * Quits: loic (loic@90.29.107.221) (Ping timeout)
  166. # [10:10] <hyatt> hsivonen: nothing, not implementing that part
  167. # [10:10] <hsivonen> :-)
  168. # [10:11] <hyatt> i implemented (in the descriptor) font-weight, font-style, font-family
  169. # [10:11] <hyatt> and then fully implemented src (local support, format, url)
  170. # [10:11] <hyatt> i'll probably implement unicode-range and then declare victory
  171. # [10:11] <hyatt> the rest just seems way too geeky to me
  172. # [10:11] <anne> heh
  173. # [10:12] <hyatt> it's really neat that you can override serif, monospace, etc. from the user sheet
  174. # [10:12] <anne> says the guy who implement obscure CSS features :p
  175. # [10:12] <Lachy> what font files will be supported? Are you adding support for Microsoft's EOT files?
  176. # [10:12] <hyatt> Lachy: if i knew how to read them i would
  177. # [10:12] <hyatt> Lachy: but i don't
  178. # [10:12] <hyatt> Lachy: so .ttf
  179. # [10:12] <Lachy> ok
  180. # [10:12] <Lachy> cool
  181. # [10:12] <hyatt> basically just plain old .ttf
  182. # [10:13] <Lachy> what about .otf?
  183. # [10:13] <hyatt> yeah that will work too
  184. # [10:13] <Lachy> cool
  185. # [10:13] <hyatt> truetype or opentype
  186. # [10:13] * hsivonen hopes apple's ttf hintin engine protects against malicious fonts
  187. # [10:13] <hyatt> most of the time those files both have .ttf extensions, which is why i just said "ttf"
  188. # [10:13] <hyatt> hsivonen: yeah i hope so too
  189. # [10:13] <hyatt> hsivonen: but i think these fonts cancome in through PDF right now
  190. # [10:14] <hsivonen> ok
  191. # [10:14] <hyatt> hsivonen: so there is already an attack vector i think
  192. # [10:14] <hyatt> it's really cool though
  193. # [10:14] * Joins: inimino (inimino@75.71.88.233)
  194. # [10:14] <hsivonen> good point
  195. # [10:14] <hyatt> while the font is downloading i return a placeholder font
  196. # [10:14] <hyatt> that will measure
  197. # [10:14] <hyatt> but not render
  198. # [10:14] <hyatt> so tha i don't hold up the display of the page
  199. # [10:15] <hyatt> WinIE just goes ahead and draws the placeholder font it picks
  200. # [10:15] <hyatt> which looks terrible
  201. # [10:15] <hyatt> when the real font arrives
  202. # [10:15] <hyatt> really fun feature to work on
  203. # [10:16] <hyatt> wonder how hard it would be to code up in gecko
  204. # [10:16] <anne> what about all the copyright issues involved with fonts?
  205. # [10:16] * anne thought that was mostly slowing down adoption
  206. # [10:16] <hyatt> anne: i'm nervous about that
  207. # [10:16] <hyatt> anne: i'm not sure if there are any issues here that i'm not aware of
  208. # [10:17] <hyatt> anne: i.e., if the browser is liable for supporting downloadable .ttf
  209. # [10:17] <hyatt> anne: there are thousands of free fonts on the web though
  210. # [10:17] <anne> howcome run the font story for a while but copyright issues mostly slowed discussion down at least in the CSS WG
  211. # [10:17] <anne> yeah, that's a fair point
  212. # [10:17] <hyatt> really?
  213. # [10:18] <hyatt> mostly just a concern that nobody would use it without some kind of protection?
  214. # [10:18] <anne> I think the font people were mostly concerned
  215. # [10:18] <anne> That people could steal fonts and such (much like people can already do with images, etc.)
  216. # [10:19] <anne> I don't think I recall all though
  217. # [10:19] <schepers> implement SVG fonts in HTML... the shapes of fonts aren't copyrighted, just the "program" (the format)
  218. # [10:22] <Lachy> http://lachy.id.au/log/2007/05/b-and-i
  219. # [10:25] <anne> can't find the discussion
  220. # [10:25] * Lachy apologises for posting one last mail in the b and i debate
  221. # [10:25] <hyatt> anne: i guess my attitude is that we should support an unencumbered open font format like ttf
  222. # [10:26] * Lachy notes that it can be ignored by most people
  223. # [10:26] <hyatt> anne: if we need to also supports some kind of lightly-encrypted mess like .eot
  224. # [10:26] <hyatt> anne: that shouldn't preclude us from supporting .ttf
  225. # [10:26] <hyatt> err prevent us from supporting .ttf
  226. # [10:26] * Joins: loic (loic@90.29.152.121)
  227. # [10:27] <hyatt> mainly i wanted ot make sure there was no weird liability issue or legal issue with a browser supporting ttf openly
  228. # [10:27] <hyatt> everyone seems to have shied away from doing it
  229. # [10:27] <Lachy> don't browsers already support ttf? What legal issues could there be?
  230. # [10:28] <hyatt> well i think ttf has bits in the format itself that say "you can't embed me" or something
  231. # [10:28] <hyatt> which i am not paying attention to at all
  232. # [10:28] <hyatt> i'm not sure if i'm legally obligated to or something
  233. # [10:28] <anne> if people would expose bought fonts in this way nobody would buy the fonts
  234. # [10:29] <hyatt> right, this would obviously only work for free fonts
  235. # [10:29] * hyatt finds the whole concept of selling fonts silly though
  236. # [10:29] <hyatt> :)
  237. # [10:29] * anne would be fine with the market collapsing
  238. # [10:29] <anne> although we might get less nice fonts
  239. # [10:29] <Lachy> ah, sounds like some primitive form of DRM
  240. # [10:29] <hyatt> maybe the web needs a generic drm scheme
  241. # [10:30] <anne> xrm
  242. # [10:30] <Lachy> maybe the web needs absolutely no drm at all
  243. # [10:30] <hyatt> :)
  244. # [10:30] <anne> Extensible Rights Managements
  245. # [10:31] <anne> Initially it's just from you, until someone extends it
  246. # [10:32] <inimino> http://www.xrml.org/
  247. # [10:34] * Quits: gavin_ (gavin@74.103.208.221) (Ping timeout)
  248. # [10:34] <anne> http://piecesofrakesh.blogspot.com/2006/02/interviewing-ui-designers.html is funny
  249. # [10:34] <anne> inimino, crap
  250. # [10:35] <inimino> most of the bad ideas, like the good ones, are already taken
  251. # [10:35] <Lachy> xrml is defective by design
  252. # [10:39] * Joins: gavin_ (gavin@74.103.208.221)
  253. # [10:39] <anne> http://flickr.com/photos/tantek/487522534/ !
  254. # [10:39] <Lachy> I wish more interviews focussed on technical abilities like that. Most interviews I've been through focus more on you're ability to describe your own personality
  255. # [10:41] <anne> "Gareth Hay has left the HTML Working Group sysbot+ipp@w3.org"
  256. # [10:42] <Lachy> heh
  257. # [10:43] <Lachy> oh well, looks like I won't need to bother sending my response to him I have in my drafts
  258. # [10:44] <Lachy> maybe I'll just turn it into a blog entry instead
  259. # [10:57] * hyatt is now known as hyattSopranos
  260. # [11:01] * Lachy wonders if defining predefined class names with an _ prefix would resolve the debate
  261. # [11:01] <Lachy> so we'd have _copyright, _note, _error, etc.
  262. # [11:02] <Lachy> that would be consistent with predefined targat values
  263. # [11:02] <Lachy> and Selectors can still use class selectors without escaping. so ._copyright { ... }
  264. # [11:17] <Philip`> Either I've made a stupid mistake in my code or else zero pages out of ~2500 from a totally non-random sample use any underscore-prefixed class name
  265. # [11:18] <Philip`> (so it seems that would avoid any conflicts)
  266. # [11:21] <anne> i kind of like it
  267. # [11:21] <anne> as Jonas said, it's compatible with target=
  268. # [11:23] <hsivonen> it doesn't support bootstrapping with existing content
  269. # [11:24] <anne> yeah, maybe i don't really care :)
  270. # [11:24] <anne> although bootstrapping with existing content is nice
  271. # [11:24] <anne> (we could always argue that the DOCTYPe determines the language in use :p )
  272. # [11:25] <anne> (and that therefore people who don't trust existing content can use the DOCTYPE to determine the type of content they're looking at)
  273. # [11:26] <anne> XHR LC2 almost out of the door, once it's published XHR2 will be started :)
  274. # [11:28] <Philip`> Maybe authors should/must not use non-prefixed names that match the predefined ones, but content consumers may interpret non-prefixed names as equivalent to the prefixed name (so they can work with existing content, but they shouldn't do that if false positives are bad in that particular case)?
  275. # [11:28] <Philip`> (Oops, I missed one - http://www.roomster.net/ has _box_white_green_border)
  276. # [11:28] <anne> (that's actually relevant)
  277. # [11:28] <anne> (although maybe not)
  278. # [11:31] * xover likes Lachy's last on em/i...
  279. # [11:31] * hyattSopranos is now known as hyatt
  280. # [11:32] <Philip`> Urgh, http://www.monstertones.com/ has <section> and breaks html5lib with NotImplementedError again
  281. # [11:33] <Lachy> xover, thanks
  282. # [11:34] <anne> Philip`, my suggestion is that you go to the InBody state and remove <section> and go from the method dispatcher
  283. # [11:34] <anne> Philip`, so they'll be handled by the anything else case
  284. # [11:35] * Joins: tH (r@87.102.20.82)
  285. # [11:35] <anne> that should be quite a trivial change
  286. # [11:35] <Philip`> Ah, thanks, sounds like that could work - though I have to leave in about two minutes so I won't bother now and I'll probably forget by the time I get back
  287. # [11:36] <anne> heh
  288. # [11:36] <anne> s/go/co/
  289. # [11:38] * Quits: loic (loic@90.29.152.121) (Ping timeout)
  290. # [11:38] <Philip`> (I can see how these new elements are a problem for anyone who doesn't want to break the parsing of ~0.1% of sites)
  291. # [11:42] * Joins: tH_ (r@87.102.4.173)
  292. # [11:42] * Quits: tH (r@87.102.20.82) (Ping timeout)
  293. # [11:42] * tH_ is now known as tH
  294. # [11:44] <xover> Lachy: I'm like to still disagree, of course, but I still quite liked it. Clear, well-reasoned, balanced. I'm not sure that's even allowed on public-html any more. :-)
  295. # [11:45] * Joins: hyatt_ (hyatt@24.6.91.161)
  296. # [11:45] <xover> I suspect the entire difference in opinion boils down to the relative importance of the separation of structure and presentation.
  297. # [11:46] * Quits: hyatt_ (hyatt@24.6.91.161) (Client exited)
  298. # [11:46] * Quits: hyatt (hyatt@24.6.91.161) (Ping timeout)
  299. # [11:46] * Joins: hyatt (hyatt@24.6.91.161)
  300. # [11:47] <xover> Where I — and, I'm guessing, Tina — feel that separation is far more important than the opposing position holds.
  301. # [11:47] <xover> Hmm.
  302. # [11:48] <xover> There is also that (unfortunate, imo) combination of «Here's how you handle “tagsoup”» and «Here's what the language /should/ be.» in the WHATWG spec.
  303. # [11:50] <xover> I don't think anyone would argue — if you stipulate a need to specify how to deal with “tagsoup” — that b/i shouldn't be specified for that purpose.
  304. # [11:51] <Lachy> xover, I'm fairly sure we got past the debate about whether or not to specify processing requirements
  305. # [11:51] <xover> IOW, I've often advocated that HTML 4.01 should be updated to drop the Transitional bits.
  306. # [11:52] <xover> Lachy: Yeah, but I wonder whether it may not be one of the things fuelling the current i/em tempest.
  307. # [11:53] <xover> Similar to mjs' Prescriptive/Descriptive points of view observation.
  308. # [11:53] <Lachy> the only thing that seems to be fuelling that debate is the semantic purists who object to anything even remotely presentational, despite having clear use cases
  309. # [11:53] <hsivonen> the fact remains that Dreamweaver and Opera emit <em> when the user asked for italic
  310. # [11:53] <hsivonen> and Tidy encourages people to map <i> to <em>
  311. # [11:53] <Lachy> yeah, that's unfortunate
  312. # [11:54] <xover> hsivonen: I can predict the response to be “See why b/i shouldn't be allowed? It confuses people!”
  313. # [11:54] <Lachy> the validator beta, which has Tidy integrated into it as a way to clean up your source, will map <i> to <em> automatically
  314. # [11:55] <hsivonen> Lachy: clearly, that makes the documents much more semantic :-)
  315. # [11:55] <Lachy> xover, the other alternative would be to define <em> and <strong> like <i> and <b> are currently defined
  316. # [11:56] <Lachy> i.e. make their semantics context-sensitive
  317. # [11:56] <xover> Hmm. I comment on the ongoing discussion, and get sucked right into it.
  318. # [11:57] <xover> It's a black hole, and the event horizon seems to be at the edge of every communication channel the HTML WG posesses.
  319. # [11:57] <Lachy> that's why people need to stop arguing about whether or not it should be included, and just accept the reality fo the situation
  320. # [11:58] <xover> Lachy: My point was, the em/i debate is a proxy for the bigger, more fundamental, issues.
  321. # [11:58] <xover> That's why they're all so hell bent on not backing down.
  322. # [11:58] * Joins: AGraf (Ashe@213.47.199.86)
  323. # [11:58] <Lachy> what's the more fundamental issues?
  324. # [11:58] <xover> (me included, btw)
  325. # [11:59] <xover> Uhm. See above?
  326. # [12:00] <xover> I'd argue til I was blue about separation of structure and presentation; but I'm not entirely sure I care whether b/i are included.
  327. # [12:01] <xover> Or rather, they need to be included for the “tagsoup” spec; so it just boils down to in which section of the doc they should be, and what their accompanying prose should say.
  328. # [12:02] <xover> And that rather follows from what is eventually decided will be the level of importance assigned to separation of presentation and structure.
  329. # [12:02] <Lachy> xover, see the last paragraph in my last email. The separation doesn't need to be strictly adhered to for the sake of it. It's only useful when it actually achieves the real goal
  330. # [12:03] <xover> Lachy: My point exactly. /That's/ what we disagree on. b/i are just proxies in that fight.
  331. # [12:03] <Lachy> what exactly does a strict separation in all circumstances achieve?
  332. # [12:04] <Lachy> you have to be more pragmatic about the issue
  333. # [12:04] <hsivonen> xover: the thing is that even if the semantic markup proponents get their way in the spec, they don't have the power to make the world comply
  334. # [12:05] * Joins: edas (edaspet@88.191.34.123)
  335. # [12:05] <xover> hsivonen: Don't they?
  336. # [12:05] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  337. # [12:05] <xover> Have you never authored a requirements specification that mandated the conformance to som standard?
  338. # [12:05] <Lachy> xover, if you have a real argument to dispute the more pragmatic approach to separation of presentation and semantics, I'd like to hear it.
  339. # [12:06] <xover> Lachy: It's a big issue. One very much worth debating. ...
  340. # [12:06] <Lachy> xover, putting something in a spec doesn't make people comply
  341. # [12:06] <Lachy> I don't think it's worth debating, I'm just interested to hear what possible arguments there are
  342. # [12:07] <xover> ... But it'd be as big as the current em/i thing. Which, as a point in favor, might actually kill the em/i thing now and avod similar proxy fights in the future.
  343. # [12:08] <xover> Lachy: You don't think other points of view are wirthwhile. You just want to hear the arguemnts so you can shoot them down?
  344. # [12:08] <hsivonen> xover: they don't
  345. # [12:08] <Lachy> I just don't believe there are any more real arguments, just mof the same.
  346. # [12:08] <Lachy> s/mof/more of/
  347. # [12:09] <xover> For em/i, sure, that's going around in circles.
  348. # [12:09] <hsivonen> xover: past experience suggests that the masses of authors aren't going to ponder the finer points of semantics
  349. # [12:10] <xover> hsivonen: Perhaps not all authors are equally important (in this sense, please don't misconstrue this statement)...
  350. # [12:11] <xover> There will always be a great mass of hobbyist producers that have neither the skills the time nor interest for investing in these sorts of issues.
  351. # [12:11] <xover> ANd that's fine.
  352. # [12:11] <xover> I hope those will eventually be covered by authoring tools that get them much of the way there.
  353. # [12:11] <hsivonen> xover: I'm thinking in terms of what a consumer can realistically infer from Web content in general. Semantic proponents seem to consider communication inside a small club of semanticist, so the masses don't matter
  354. # [12:11] <hsivonen> xover: on the Web, we also have a great mass of unskilled professionals
  355. # [12:12] <xover> But even the best of tools cannot help them produce structured content when their way of conceiving of that content is not structured.
  356. # [12:12] <hsivonen> xover: exactly
  357. # [12:12] <xover> But the professional web worker can be influenced to do much better by a variety of means.
  358. # [12:13] <xover> And these are the ones producing, say, governement web sites providing services to the public.
  359. # [12:13] <hsivonen> xover: yeah, I'd be happy with gov't providing HTML, PDF and ODT instead of .doc
  360. # [12:14] <xover> hsivonen: Amen!
  361. # [12:14] * Joins: loic (loic@90.29.152.121)
  362. # [12:14] <anne> lol, someone from Germany called me to buy links on my site for 1000 euro a month
  363. # [12:14] <anne> this Google page rank thingie is apparently quite popular
  364. # [12:14] <hsivonen> anne: did you sell out?
  365. # [12:15] <anne> neh
  366. # [12:15] <xover> And as we've seen with the transition to CSS for formatting for even commercial web sites, even the cold hard capitalists can be persuaded to improve in this sense.
  367. # [12:15] <anne> I already have a job
  368. # [12:15] <anne> with which I can pay bandwidth and all that
  369. # [12:15] <anne> (and more :) )
  370. # [12:15] <Lachy> I got emailed an offer to do a link exchange on my site too. I initally deleted it as spam, though it turned out to be a legit request cause the guy chatted to me on msn
  371. # [12:16] <anne> oh, yeah, I get those more frequently too now
  372. # [12:16] <anne> but link exchange seems kind of silly
  373. # [12:16] <Lachy> perhaps I should just make my policy about advertising on my site more clear somehow
  374. # [12:19] <xover> Ugh. “The and Elements”...
  375. # [12:20] <Lachy> what?
  376. # [12:20] <xover> Either your feed is borked, or my feed reader is.
  377. # [12:20] <Lachy> it would be your feed reader
  378. # [12:21] <xover> Hmm. Yeah. Looks nicely wrapped to me.
  379. # [12:21] <xover> Unless there needs to be some double escaping or something else weird there.
  380. # [12:21] <Lachy> there are, unfortunately, some that require double escaping of entity refs
  381. # [12:21] <xover> right
  382. # [12:21] <Lachy> those are broken
  383. # [12:21] <Lachy> though it appears that /log/feed is sending RSS2.0 instead of Atom. I should fix that
  384. # [12:22] <Lachy> I need to upgrade my Word Press installation too
  385. # [12:22] <xover> It's an old version of NetNewWire. May be a bug fixed in a later version.
  386. # [12:22] <Lachy> yeah, anyway, that blog entry is roughly what I wrote in my last mail to the list
  387. # [12:28] <xover> «A cool off timer for this thread will prevent you from replying to any email in this thread for the next one hour. [Cancel]»
  388. # [12:28] <xover> heh heh
  389. # [12:32] * Quits: sbuluf (itqakvg@200.49.140.7) (Quit: sbuluf)
  390. # [12:44] * Parts: anne (annevk@213.236.208.22)
  391. # [12:45] * Joins: zcorpan_ (zcorpan@84.216.41.43)
  392. # [12:48] * Joins: anne (annevk@213.236.208.22)
  393. # [12:56] * Quits: inimino (inimino@75.71.88.233) (Quit: ChatZilla 0.9.78.1 [Firefox 2.0.0.3/2007031001])
  394. # [13:01] * Quits: ROBOd (robod@86.34.246.154) (Quit: http://www.robodesign.ro )
  395. # [13:04] <Lachy> I just noticed bikeshed.org gets a random background colour everytime it's loaded. Awesome!
  396. # [13:08] * Quits: kazuhito (chatzilla@142.59.90.219) (Connection reset by peer)
  397. # [13:11] <anne> Do people realize that role= implies RDF nonsense?
  398. # [13:11] <anne> Or do they think it's just a new kind of class=?
  399. # [13:11] <Bob_le_Pointu> Second option.
  400. # [13:11] <hsivonen> anne: the latter
  401. # [13:11] <hsivonen> anne: please explain how RDF is involved
  402. # [13:12] <anne> The XHTML2 role= takes qnames besides predefined values which, when resolved, point to RDF resources which describe the meaning of the value
  403. # [13:12] <anne> as far as I understand it
  404. # [13:12] <Lachy> role introduces qnmaes for attr values, which is a bigger problem
  405. # [13:12] <anne> There's has been some debate about renaming role= to rdf:type= too
  406. # [13:13] <anne> See http://www.w3.org/2007/04/25-xhtml-minutes#item02 for instance
  407. # [13:13] <Lachy> is there an article somewhere that discusses the problems with the role attribute that we could point people to?
  408. # [13:14] <anne> I discussed it on my blog, but that's far from useful "pointing people to" material
  409. # [13:16] <Lachy> http://annevankesteren.nl/2005/04/role-attribute
  410. # [13:17] * anne wonders if that's the one he had in mind
  411. # [13:18] <Lachy> there's also this one that briefly mentions it http://annevankesteren.nl/2006/06/accessibility-ideas
  412. # [13:19] <anne> Yeah, that's probably it
  413. # [13:19] <anne> It nicely contradicts the previous one
  414. # [13:20] <Lachy> it's interesting to see how your opinion of XHTML2, role attr, etc. have gradully gone from supportive to unsupportive :-)
  415. # [13:25] <anne> I appreciate it as well that I'm making progress rather than stagnating at some point in time.
  416. # [13:35] <Philip`> Lachy: See e.g. http://lightgoldenrodyellow.bikeshed.org/ too
  417. # [13:36] <anne> ah, it works exactly like that with comments on my blog
  418. # [13:36] <anne> simple topic: noise
  419. # [13:36] <anne> complex topic: signal
  420. # [13:37] <Lachy> anne, instead of disabling comments completely on the simple topic, you should raise the barrier to entry so that only those with important comments will bother taking the effort to post
  421. # [13:38] <Philip`> Require comments to be valid SVG, perhaps?
  422. # [13:38] <Lachy> heh
  423. # [13:38] <Lachy> yeah, valid XHTML is just too simple these days
  424. # [13:40] <anne> it's some weird subset of XHTML actually
  425. # [13:41] <anne> without namespace support etc.
  426. # [13:41] <anne> but it's indeed to trivial
  427. # [13:43] <anne> maybe someone an point http://lightgoldenrodyellow.bikeshed.org/ out to DanC as an argument of why this debating is wasting our time
  428. # [13:43] <anne> s/an point/can point/
  429. # [13:45] <Philip`> Actually, I think http://papayawhip.bikeshed.org/ is a much better site
  430. # [13:45] <anne> oh lol
  431. # [13:46] * anne gets the domain name now :)
  432. # [13:46] <gsnedders> :)
  433. # [13:50] <Lachy> it doesn't work properly with hex codes :-( http://09f911.bikeshed.org/
  434. # [14:25] * Joins: olivier (ot@128.30.52.30)
  435. # [14:59] * Joins: jdandrea (jdandrea@68.192.161.254)
  436. # [15:09] * Quits: loic (loic@90.29.152.121) (Quit: hoopa rules)
  437. # [15:13] * Joins: ROBOd (robod@86.34.246.154)
  438. # [15:20] * Quits: tH (r@87.102.4.173) (Ping timeout)
  439. # [15:42] * Lachy wishes the other Philip Taylor would *stop* CC'ing www-html!
  440. # [15:42] * Quits: schepers (schepers@208.38.57.47) (Quit: Free at last!)
  441. # [15:52] * Joins: tH (r@87.102.4.173)
  442. # [16:04] * Quits: MrNaz (Naz@203.214.95.166) (Quit: Leaving)
  443. # [16:09] * Quits: edas (edaspet@88.191.34.123) (Ping timeout)
  444. # [16:12] * Joins: kazuhito (chatzilla@72.29.239.177)
  445. # [16:40] * Joins: billmason (billmason@69.30.57.156)
  446. # [16:52] * Joins: dbaron (dbaron@72.29.239.177)
  447. # [16:53] * Joins: schepers (schepers@72.29.239.177)
  448. # [17:10] * Joins: MikeSmith (MikeSmith@mcclure.w3.org)
  449. # [17:17] * Quits: zdenko (zdenko@193.77.152.244) (Quit: zdenko)
  450. # [17:34] * Joins: edas (edaspet@88.191.34.123)
  451. # [17:37] * Joins: hasather (hasather@81.235.209.174)
  452. # [17:50] * Joins: zdenko (zdenko@84.255.203.169)
  453. # [18:08] <anne> @role is endorsed by the Mozilla Foundation?
  454. # [18:08] * anne wonders if that claim is accurate
  455. # [18:10] <Lachy> anne, there is some implementation of it in mozilla
  456. # [18:10] <myakura> for its implementation, maybe
  457. # [18:10] <anne> I'm aware of the implementation done by IBM
  458. # [18:11] <myakura> yeah
  459. # [18:12] <Lachy> I don't think the implementatation translates into support, though
  460. # [18:17] <anne> the chair speaks
  461. # [18:18] <mjs> so who here has been on W3C Working Groups besides Web API, WAF, SVG and CSS?
  462. # [18:19] <mjs> (and of course HTML?)
  463. # [18:19] <anne> I've been on CDF
  464. # [18:19] * MikeSmith points to MikeSmith
  465. # [18:19] <anne> I'm on CDF
  466. # [18:19] <anne> i mean :)
  467. # [18:20] <mjs> MikeSmith: which groups have you been on?
  468. # [18:21] <MikeSmith> Web Security Context wg, now team contact for Mobile Web Best Practices and Device Description WGs
  469. # [18:23] <MikeSmith> mjs - why do you ask? (just curious)
  470. # [18:24] <mjs> MikeSmith, anne: on these groups, when a decision has to be made and there's a vote, whether formal or informal, is it normal for all no votes to automatically count as Formal Objections?
  471. # [18:24] <mjs> I know that's not the case for SVG, Web API, WAF or CSS
  472. # [18:24] * Quits: gavin (gavin@63.245.208.169) (Ping timeout)
  473. # [18:24] <mjs> I've been discussing the matter with our chairs off-list
  474. # [18:24] <mjs> http://lists.w3.org/Archives/Public/www-archive/2007May/0040.html
  475. # [18:24] <mjs> so I wanted to do a broader check of what existing practice is
  476. # [18:25] <anne> This is not the case for CDF
  477. # [18:25] <anne> CDF is in fact the group I used as example yesterday, where real FOs are raised during LC if needed
  478. # [18:25] * Joins: gavin (gavin@63.245.208.169)
  479. # [18:25] <anne> And voting simply goes by majority
  480. # [18:26] <MikeSmith> true that not normal for other WGs, but then the HTML WG isn't a normal WG so not sure it can be compared
  481. # [18:26] <MikeSmith> most other WGs are maybe 15 or 20 people who all know each other
  482. # [18:27] <MikeSmith> and straw polls are the norm
  483. # [18:27] * zcorpan_ doesn't like polls
  484. # [18:29] <mjs> MikeSmith: I think the much larger size of the HTML WG actually makes it *less* suited to a model where every no vote is a Formal Objection, since 100% consensus in a group that large is almost impossible
  485. # [18:31] <MikeSmith> mjs - I suppose. but as anne notes, it is the same as for LC process -- where anybody (public) can raise an FO (not just WG members)
  486. # [18:32] <mjs> MikeSmith: yes, exactly
  487. # [18:43] * Quits: myakura (myakura@125.194.247.196) (Ping timeout)
  488. # [18:46] * Joins: myakura (myakura@125.194.247.196)
  489. # [18:53] * Quits: mjs (mjs@64.81.48.145) (Quit: mjs)
  490. # [19:16] * Quits: myakura (myakura@125.194.247.196) (Quit: Leaving...)
  491. # [19:21] * Joins: MrNaz (Naz@203.214.95.166)
  492. # [19:31] * Parts: asbjornu (asbjorn@84.48.116.134)
  493. # [19:39] <anne> heh, some of the people who haven't followed WHATWG make arguments about not knowing history
  494. # [19:39] * anne isn't sure how this all makes sense anymore
  495. # [19:45] <gsnedders> what I don't understand is how @role will be any better. we can't have any proper namespaces in HTML, and people will add invalid values to the attribute (thereby making under the arguments for not using @class impossible to add any further values in HTML6)
  496. # [19:50] <anne> People seem to want different things from @role
  497. # [19:50] <anne> 1. Semantics in attribute values to keep structure and semantics somewhat separate.
  498. # [19:50] <anne> 2. Easier to extend.
  499. # [19:50] <anne> 3. Tying in RDF like meaning to HTML.
  500. # [19:51] <anne> 4. Solving accessibility problems with HTML because people use <div class=slider> as opposed to some native control like <input type=slider> which would handle that for them.
  501. # [19:51] <anne> (My point 4 is a bit biased, but you get the idea.)
  502. # [19:57] * Lachy wonders how RDF actually helps with anything
  503. # [19:58] <Lachy> John Foliot is claiming that it can provide extensibility, but didn't explain how exactly
  504. # [19:58] <anne> It provides extensibility in theory, but in practice that hasn't been accomplished yet afaict.
  505. # [19:59] <anne> I'm of the opinion that new features should have clear practical benefits.
  506. # [20:00] * Joins: mjs (mjs@17.255.104.133)
  507. # [20:24] * Joins: hyatt (hyatt@24.6.91.161)
  508. # [20:25] * Quits: hyatt (hyatt@24.6.91.161) (Client exited)
  509. # [20:25] * Joins: hyatt (hyatt@24.6.91.161)
  510. # [20:27] * Quits: dbaron (dbaron@72.29.239.177) (Quit: 8403864 bytes have been tenured, next gc will be global.)
  511. # [20:30] * Quits: edas (edaspet@88.191.34.123) (Ping timeout)
  512. # [20:46] <anne> oh, more www-archive
  513. # [20:49] <jgraham> Seriously, I don't follow the argument that because something is new it won't be (ab)used in exactly the same way as current markup
  514. # [20:50] * Quits: hasather (hasather@81.235.209.174) (Client exited)
  515. # [20:50] <anne> maybe you need some non-logic
  516. # [20:50] * Joins: hasather (hasather@81.235.209.174)
  517. # [20:50] <zcorpan_> jgraham: because the new stuff will break in a drocanian way when you abuse it :)
  518. # [20:51] <zcorpan_> and all implementations will be perfect
  519. # [20:51] * Joins: ddailey (david_dail@24.144.172.117)
  520. # [20:51] <anne> that would require some language interpreter in new implementations
  521. # [20:51] <jgraham> And authors will suddenly start to understand RDF?
  522. # [20:52] <anne> right after they bite through namespaces, sure
  523. # [20:52] <ddailey> finally got IRC working in Opera
  524. # [20:52] <anne> heh, sorry if the UI was not intiutive
  525. # [20:52] <ddailey> never did chat before -- so who knows?
  526. # [20:53] <ddailey> it looks okay to me
  527. # [20:53] <ddailey> user error
  528. # [20:53] * anne though the latest in UI was that the user can't do wrong
  529. # [20:54] <ddailey> I like that
  530. # [20:54] <ddailey> then it's not my fault
  531. # [20:56] <ddailey> anne, I liked what you said about non-logic -- I think there is a study to be had there
  532. # [20:56] <mjs> zcorpan_: there
  533. # [20:56] <mjs> er
  534. # [20:56] <mjs> nevermind, I don't even want to talk about "role"
  535. # [20:57] <ddailey> It looks like one more thing to add to my reading list
  536. # [20:58] <ddailey> I got the idea from Dan that a lot of semantics in the "semantic web" sense can be done through GRDDL rather painlessly without adding markup to HTML
  537. # [20:58] * Quits: hyatt (hyatt@24.6.91.161) (Quit: hyatt)
  538. # [20:59] * anne has to go
  539. # [21:01] <ddailey> maciej, I wonder if we might be able to categorize the prescriptivist arguments.
  540. # [21:01] <ddailey> in some sort of descriptivist way
  541. # [21:02] <zcorpan_> mjs: sorry, forgot to use the <sarcasm> tag :)
  542. # [21:02] <gsnedders> Opera_9.20_Setup.dmg refuses to mount on Mac OS 10.4.9
  543. # [21:03] <gsnedders> zcorpan_: I thought the conclusion was that both start and end tags though required may be omitted? :)
  544. # [21:03] <zcorpan_> gsnedders: required and may be omitted at the same time?
  545. # [21:03] <mjs> ddailey: not sure what you mean
  546. # [21:04] <gsnedders> zcorpan_: like <html>, <head>, and <body>
  547. # [21:04] <ddailey> wondered how many different points of view they actually have
  548. # [21:04] <gsnedders> n^2 (where n is the number of members of the WG)
  549. # [21:04] <zcorpan_> gsnedders: ah, ok. so you meant that the element is required but the tags may be omitted :)
  550. # [21:04] <gsnedders> zcorpan_: yes :)
  551. # [21:04] <ddailey> I think some are saying -- look how scary the web will be if we don't clamp down on grammar now
  552. # [21:05] <ddailey> some seem to have something else going on
  553. # [21:05] <mjs> well, I don't want to be in the business of classifying arguments I don't really believe in
  554. # [21:05] <ddailey> if it's only n^2 it can be managed with a fairly simple grammar
  555. # [21:06] <gsnedders> mjs: anytime I try and say what I think they're saying I just get told that I'm trying to put words in their mouth…
  556. # [21:07] <ddailey> one might be able to hash out a compromise or a synthesis or something ifall those other points of view can be enumerated
  557. # [21:09] <ddailey> I am softening on design principles -- one really DOESN't want to have this particular debate again and again forever
  558. # [21:10] <ddailey> maybe if we had a token economy of some sort and we handed out finitely many words that any side of any debate could use
  559. # [21:17] <ddailey> ddailey should learn how to use 8-) and so forth (except I don't know what they mean) -- there are lots of humor tags inserted in some of the above
  560. # [21:17] <Philip`> Ooh, my message arrived on www-html, only four days late
  561. # [21:18] * Parts: ddailey (david_dail@24.144.172.117)
  562. # [21:18] <Philip`> *messages
  563. # [21:31] * Joins: ddailey (david_dail@24.144.172.117)
  564. # [21:31] <Philip`> Aha, now I can run XPath queries on ~2000 HTML documents in ~50 seconds, and get totally statistically insignificant results from a heavily biased sample, which might be handy
  565. # [21:32] * Quits: tH (r@87.102.4.173) (Ping timeout)
  566. # [21:34] * Joins: tH (r@87.102.4.173)
  567. # [21:34] * Joins: inimino (inimino@75.71.88.233)
  568. # [21:40] * Quits: olivier (ot@128.30.52.30) (Quit: Leaving)
  569. # [21:43] <ddailey> html-wg irc looks a lot more active when one just reads the logs -- nearly festive at times
  570. # [21:45] <Philip`> It's rather bursty, and seems to be going through a quiet patch now
  571. # [21:47] <ddailey> I tried dinking around with XPATH a little but was unable to write any code that worked across browsers.. Any recos on a good tutorial?
  572. # [21:49] <Philip`> Unfortunately I have no idea how to use it in browsers and not much idea how to use it out of browsers either - I'm just doing stuff in Python and copying-and-pasting examples
  573. # [21:50] * Joins: dbaron (dbaron@72.29.239.177)
  574. # [21:55] <ddailey> The XSLT code that Dan wrote to summarize the tasks volunteer questionnaire was pretty nifty looking. I was going to try to learn XSLT this semester until this WG came along. Maybe this summer. Shouldn't be much activity this summer should there be? Don't all you folks take big summer vacations? ;)
  575. # [22:15] * Quits: dbaron (dbaron@72.29.239.177) (Ping timeout)
  576. # [22:19] * Joins: dbaron (dbaron@72.29.239.177)
  577. # [22:39] * Quits: beowulf (carisenda@91.84.50.132) (Ping timeout)
  578. # [22:42] * Joins: beowulf (carisenda@91.84.50.132)
  579. # [22:47] <hsivonen> do the accessibility folks really believe that RDF will give AT more understanding?
  580. # [22:48] * Quits: dbaron (dbaron@72.29.239.177) (Ping timeout)
  581. # [22:49] <ddailey> I would guess that they are not all of one point of view
  582. # [22:49] <Lachy> hsivonen, that's what I'm wondering
  583. # [22:50] * Joins: dbaron (dbaron@72.29.239.177)
  584. # [22:51] * Quits: ROBOd (robod@86.34.246.154) (Quit: http://www.robodesign.ro )
  585. # [22:51] <mjs> hsivonen: people mistakenly think that the ability to write declarations for a custom vocabulary and put it in a namespace gives understanding without prior agreement
  586. # [22:52] <mjs> (well, mistakenly IMO anyway)
  587. # [22:52] <ddailey> mjs: by without prior agreement you mean
  588. # [22:53] <ddailey> oops hit the return button by accident
  589. # [22:53] <mjs> I mean that if you declare your own custom vocabulary in some formal way, that in no way aids anyone in understanding that vocabulary if they are not specifically aware of it
  590. # [22:54] <ddailey> Okay, yes that's what I thought
  591. # [22:54] <Lachy> it's like defining your own FooML and then expecting UAs to instantly understand it
  592. # [22:55] * gsnedders got told a few days ago that browsers already support XHTML2 :P
  593. # [22:55] <Lachy> gsnedders, of course the do! There's a working example on the web ;-)
  594. # [22:55] * mjs facepalms
  595. # [22:55] <mjs> anyway, Tina joined the XHTML2 WG, so that's one positive step from the flamage
  596. # [22:56] <Lachy> yeah, she joined last week
  597. # [22:56] <Lachy> gsnedders, http://w3future.com/html/examples.xml?notransform
  598. # [22:57] <Lachy> (they don't like telling anyone this, but that relies on proprietary extensions in major browsers to actually be functional)
  599. # [22:57] <gsnedders> Lachy: what extensions?
  600. # [22:57] <Lachy> view the CSS
  601. # [22:57] <mjs> does it work in Safari?
  602. # [22:58] <gsnedders> mjs: does for me
  603. # [22:59] <mjs> is that page itself allegedly XHTML2?
  604. # [22:59] <Lachy> ah, it's been changed since I last looked at it
  605. # [22:59] <gsnedders> Lachy: where? I see nothing proprietary skimming through it
  606. # [22:59] <gsnedders> mjs: with XSL, though
  607. # [22:59] <Lachy> they now use XSLT to transform it to HTML
  608. # [22:59] <mjs> it's XSLT transformed
  609. # [23:00] <Lachy> it used to contain properties like '-o-link' (I think that's it) for making the links work, and binding XBL1 for Mozilla
  610. # [23:01] <mjs> I wonder if their transform would actually handle xml-events and xforms (they declare the namespaces but don't use them)
  611. # [23:02] * mjs guesses no, since scripting would have to work on the post-transform DOM)
  612. # [23:02] <Lachy> yeah, that's weird
  613. # [23:02] <Lachy> XMLEvents is just another poorly designed technology though
  614. # [23:02] <Lachy> XBL makes it obsolete
  615. # [23:03] <ddailey> Does that that mean I don't have to learn it? goodie
  616. # [23:03] <mjs> xml-events makes easy things hard and hard things hard
  617. # [23:06] <Lachy> ddailey, you never have to learn anything that comes out of the XHTML2 and related groups
  618. # [23:06] <Lachy> did the XHTML2WG make xml events?
  619. # [23:06] <gsnedders> g'nite
  620. # [23:07] <Lachy> yep, they did
  621. # [23:07] <ddailey> The less the better
  622. # [23:09] <Lachy> wow, I love how they replace <img ... onclick=",,,"> with something even easier: ...
  623. # [23:09] <Lachy> <img src="button.gif" alt="OK">
  624. # [23:09] <Lachy> <script ev:event="activate" type="application/x-javascript">
  625. # [23:09] <Lachy> doactivate(event);
  626. # [23:09] <Lachy> </script>
  627. # [23:09] <Lachy> </img>
  628. # [23:13] <jgraham> ddailey: X-Path in browsers (well Firefox at least) http://www-xray.ast.cam.ac.uk/~jgraham/mozilla/xpath-tutorial.html
  629. # [23:13] * jgraham was sure that got moved to the Mozilla wiki somewhere
  630. # [23:20] * Joins: Sander (svl@71.57.109.108)
  631. # [23:20] <ddailey> thanks
  632. # [23:22] <ddailey> I'll give it a read. I got some stuff working in FF and Opera, and got some other stuff working in IE. It all seemed completely different, but then I didn't have the faintest idea what I was doing.
  633. # [23:23] <jgraham> I have no idea what IE does. If it doesn't follow the spec, that document won't help
  634. # [23:26] <ddailey> as I recall the expressions resolved similarly, but it was figuring out how to invoke them that was quirky
  635. # [23:39] * Joins: AGraf_ (Ashe@213.47.199.86)
  636. # [23:41] * Quits: AGraf (Ashe@213.47.199.86) (Ping timeout)
  637. # [23:45] * Joins: asbjornu (asbjorn@84.48.116.134)
  638. # [23:45] <ddailey> a problem I've had in trying to understand the discussions is this: where to draw a boundary on what is HTML -- where are its boundaries?
  639. # [23:46] <ddailey> we've got script with document.write, we've got some DOM, CSS is sorta there in a presentational sense, sorta in a semantic sense
  640. # [23:47] <ddailey> we've got events, we've got XML and object, and all the foreign content
  641. # [23:49] <ddailey> for reading and writing files we've got webforms (and various x-things) and I can't remember what the RFC was that covered file output
  642. # [23:50] <ddailey> when I find issues concerning say a weird document.write script that seems to change styles in one browser but not in another I have no way
  643. # [23:51] <ddailey> to figure out even which spec to begin looking in to know if it's a bug or my misunderstanding of how it's supposed to be -- the specs have gotten a bit spread out
  644. # Session Close: Tue May 08 00:00:00 2007

The end :)