/irc-logs / freenode / #whatwg / 2008-03-24 / end

Options:

  1. # Session Start: Mon Mar 24 00:00:00 2008
  2. # Session Ident: #whatwg
  3. # [00:14] * Joins: roc (n=roc@123-2-74-70.static.dsl.dodo.com.au)
  4. # [00:15] * Quits: csarven (n=csarven@on-irc.csarven.ca) ("http://www.csarven.ca")
  5. # [00:19] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  6. # [00:24] * Joins: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  7. # [00:30] <Hixie> the links in http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2006-June/006498.html suggest that maybe presentational mathml is not an accessibility problem after all
  8. # [00:38] <webben_> Hixie: also http://firevox.clcworld.net/features.html
  9. # [00:42] <webben_> I'd guess http://www.nfbnet.org/mailman/listinfo/blindmath would be good folks to ask though
  10. # [00:58] * Joins: BenMillard (n=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  11. # [01:04] * Quits: qwert666 (n=qwert666@acav241.neoplus.adsl.tpnet.pl) ("Leaving")
  12. # [01:05] * weinig|away is now known as weinig
  13. # [01:17] * weinig is now known as weinig|away
  14. # [01:24] * Parts: BenMillard (n=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  15. # [01:54] * Quits: tndH (i=Rob@83.100.254.190) ("ChatZilla 0.9.81-rdmsoft [XULRunner 1.8.0.9/2006120508]")
  16. # [02:01] * Joins: gavin (n=gavin@firefox/developer/gavin)
  17. # [02:03] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  18. # [02:24] * Joins: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  19. # [02:38] * Joins: MikeSmith (n=MikeSmit@EM117-55-12-45.pool.emnet.ne.jp)
  20. # [02:59] * Quits: MikeSmith (n=MikeSmit@EM117-55-12-45.pool.emnet.ne.jp) ("Less talk, more pimp walk.")
  21. # [03:35] * Quits: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  22. # [03:36] * Joins: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  23. # [03:42] * Quits: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  24. # [03:52] * Joins: MikeSmith (n=MikeSmit@dhcp-246-231.mag.keio.ac.jp)
  25. # [03:57] * Quits: starjive (i=beos@81-233-18-73-no30.tbcn.telia.com)
  26. # [05:08] * Quits: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  27. # [05:28] * Joins: MacDome (n=eric@adsl-76-216-10-139.dsl.pltn13.sbcglobal.net)
  28. # [05:45] <heycam> Hixie, i'd use sequence<any> rather than sequence<Object> for executeSql()
  29. # [05:46] <heycam> to avoid unnecessary conversions of Number/String/etc. values to their object equivalents
  30. # [05:59] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  31. # [06:03] * Joins: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  32. # [06:05] * Quits: MacDome (n=eric@adsl-76-216-10-139.dsl.pltn13.sbcglobal.net) (Read error: 110 (Connection timed out))
  33. # [06:25] * Joins: MacDome (n=eric@70-2-85-143.area5.spcsdns.net)
  34. # [06:38] * weinig|away is now known as weinig
  35. # [06:57] * Quits: jruderman (n=jruderma@c-67-180-15-227.hsd1.ca.comcast.net)
  36. # [07:00] <Hixie> heycam: can you send me that by e-mail? i'm in the middle of the namespace stuff right now
  37. # [07:00] * Joins: jruderman (n=jruderma@c-67-180-15-227.hsd1.ca.comcast.net)
  38. # [07:00] * Quits: MacDome (n=eric@70-2-85-143.area5.spcsdns.net)
  39. # [07:01] * Quits: dbaron (n=dbaron@c-67-160-251-228.hsd1.ca.comcast.net) ("8403864 bytes have been tenured, next gc will be global.")
  40. # [07:10] * Joins: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  41. # [07:20] <heycam> Hixie, ok
  42. # [07:21] <Hixie> thanks
  43. # [07:21] <Pavlov_> hrm
  44. # [07:21] <Pavlov_> Hixie: know anyone who knows stuff about css font things?
  45. # [07:21] <Pavlov_> spec things
  46. # [07:21] <Hixie> elaborate?
  47. # [07:22] <Pavlov_> well, for example, opentype doesn't really define font weights very well aside from giving 100-900 names
  48. # [07:22] <Pavlov_> there are a bunch of fonts with weights of say 950 or 1000
  49. # [07:22] <Pavlov_> (not many with 1000, but a few. quite a few 950s)
  50. # [07:23] <Pavlov_> (and i've seen other x50 ones)
  51. # [07:24] <Pavlov_> just trying to understand what the best thing to do is/if the spec should change
  52. # [07:25] <Pavlov_> like, if i have a 900 and a 1000, i should probably ignore the 1000 (or use it/support it?) but if i don't have a 900 i should probably round the 950/1000 down
  53. # [07:26] <Pavlov_> if i have 100, 150, 200, 250, 300, ... 950 should i support them all? bolder/lighter do what?
  54. # [07:30] * Disconnected
  55. # [07:30] * Attempting to rejoin channel #whatwg
  56. # [07:30] * Rejoined channel #whatwg
  57. # [07:30] * Topic is 'WHATWG (HTML5) -- http://www.whatwg.org/ -- Logs: http://krijnhoetmer.nl/irc-logs/ -- Please leave your sense of logic at the door, thanks!'
  58. # [07:30] * Set by gsnedders on Tue Dec 18 21:41:19
  59. # [07:31] <Pavlov_> imho, supporting more than that is feasable
  60. # [07:31] <Pavlov_> like, the spec says "If the font family already uses a numerical scale with nine values (like e.g. OpenType does), the font weights should be mapped directly."
  61. # [07:32] <Hixie> yeah if you have more than 2 weight above bold (700) then the spec just says to drop some
  62. # [07:32] <Pavlov_> except that OpenType doesn't specify just 9 steps
  63. # [07:32] * Quits: MikeSmith (n=MikeSmit@dhcp-246-231.mag.keio.ac.jp) (brown.freenode.net irc.freenode.net)
  64. # [07:32] * Quits: roc (n=roc@123-2-74-70.static.dsl.dodo.com.au) (brown.freenode.net irc.freenode.net)
  65. # [07:32] * Quits: webben_ (n=benh@91.84.250.9) (brown.freenode.net irc.freenode.net)
  66. # [07:32] * Quits: Yudai (n=Yudai@p9258c3.kngwnt01.ap.so-net.ne.jp) (brown.freenode.net irc.freenode.net)
  67. # [07:32] * Quits: jgraham__ (n=jgraham@81-86-216-20.dsl.pipex.com) (brown.freenode.net irc.freenode.net)
  68. # [07:32] * Quits: tomg (n=tom@unable.to.resolve.host.name) (brown.freenode.net irc.freenode.net)
  69. # [07:32] * Quits: doublec (n=chris@li5-223.members.linode.com) (brown.freenode.net irc.freenode.net)
  70. # [07:32] * Quits: didymos (i=jho@rapwap.razor.dk) (brown.freenode.net irc.freenode.net)
  71. # [07:32] * Quits: krijnh (n=krijnhoe@ktk.xs4all.nl) (brown.freenode.net irc.freenode.net)
  72. # [07:32] * Quits: tantek_ (n=tantek@72.158.245.34) (brown.freenode.net irc.freenode.net)
  73. # [07:32] <Hixie> well, 9 weight is probably enough for now -- most pages don't bother with more than 2 levels anyway
  74. # [07:32] <Pavlov_> yeah
  75. # [07:33] <Pavlov_> 1000 is pretty rare
  76. # [07:33] <Hixie> if there really are fonts that have more weights, i would invent keywords -moz-1000, -moz-1100, etc
  77. # [07:33] <Pavlov_> think i've seen 2 fonts with it?
  78. # [07:33] <Pavlov_> 950 is pretty common thouhg
  79. # [07:33] <Hixie> so i would say map the boldest one to 900
  80. # [07:33] <Hixie> map the main bold one to 700
  81. # [07:33] <Hixie> and if there are any between those to, map the middle one of those to 800
  82. # [07:34] <Pavlov_> which direction would you map x50s to if you don't have an exact number for it?
  83. # [07:34] <Pavlov_> like, say you have 100, 250, 400
  84. # [07:34] * Joins: didymos (i=jho@rapwap.razor.dk)
  85. # [07:35] <Pavlov_> maybe you map both 200 and 300 to that
  86. # [07:35] * weinig is now known as weinig|zZz
  87. # [07:35] <Pavlov_> if you have 100, 200, 350, 400, i guess you could round 350 down
  88. # [07:36] <Pavlov_> and if you have 100, 200, 300, 350, 400, just skip 350?
  89. # [07:36] <Hixie> map the main medium weight to 400
  90. # [07:36] <Hixie> map the lightest one to 100
  91. # [07:37] <Pavlov_> i'm saying if i have 5 opentype fonts of the same family that have all 5 of those weights
  92. # [07:37] <Pavlov_> or 3 or 4 of them
  93. # [07:37] <Hixie> then just drop one
  94. # [07:37] <Pavlov_> what should I do with x50 weights?
  95. # [07:37] <Pavlov_> what i suggested?
  96. # [07:38] <Hixie> so, map the main medium weight to 400, the lightest one to 100, and for 200 and 300 just pick some that are equidistant from lightest to medium
  97. # [07:38] <Hixie> soif you just have one extra, just drop one of them, doesn't matter which
  98. # [07:38] <Hixie> i wouldn't map the opentype numbers straight to the 100-900 numbers like the spec says, if you have any x50 weights
  99. # [07:39] <Pavlov_> well, there is no other concept of "main medium weight" face
  100. # [07:39] <Pavlov_> you either have 400 or you don't
  101. # [07:40] <Pavlov_> many bold faces if you treat them as a family only have a 700 weight
  102. # [07:40] * Joins: webben (n=benh@91.84.250.9)
  103. # [07:40] <Hixie> i'd just sort them per weight, pin 100, 400 (the "regular" weight), 700 ("bold"), and 900, and fill the others in a linear way so that they are distributed uniformly
  104. # [07:40] <Pavlov_> k
  105. # [07:40] <Hixie> well if you have fewer weights, the spec defines how you fill things in
  106. # [07:40] <Pavlov_> right
  107. # [07:40] <Pavlov_> fewer isn't the problem as much
  108. # [07:40] <Hixie> k
  109. # [07:41] * Joins: roc (n=roc@123-2-74-70.static.dsl.dodo.com.au)
  110. # [07:44] * Joins: webben_ (n=benh@91.84.250.9)
  111. # [07:44] * Joins: Yudai (n=Yudai@p9258c3.kngwnt01.ap.so-net.ne.jp)
  112. # [07:44] * Joins: krijnh (n=krijnhoe@ktk.xs4all.nl)
  113. # [07:44] * Joins: doublec (n=chris@li5-223.members.linode.com)
  114. # [07:44] * Joins: tomg (n=tom@unable.to.resolve.host.name)
  115. # [07:44] * Joins: jgraham__ (n=jgraham@81-86-216-20.dsl.pipex.com)
  116. # [07:44] * Joins: tantek_ (n=tantek@72.158.245.34)
  117. # [07:44] * Joins: MikeSmith (n=MikeSmit@133.27.246.231)
  118. # [07:47] * Quits: webben_ (n=benh@91.84.250.9) (Connection timed out)
  119. # [07:48] * Quits: krijnh (n=krijnhoe@ktk.xs4all.nl) (Read error: 110 (Connection timed out))
  120. # [08:23] * Quits: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  121. # [08:25] * Joins: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  122. # [08:30] * Quits: roc (n=roc@123-2-74-70.static.dsl.dodo.com.au)
  123. # [08:30] * Quits: MikeSmith (n=MikeSmit@133.27.246.231) ("Less talk, more pimp walk.")
  124. # [08:43] * Joins: Thezilch (n=fuz007@cpe-76-170-22-179.socal.res.rr.com)
  125. # [09:37] * Joins: jason3 (n=chatzill@203-211-84-110.ue.woosh.co.nz)
  126. # [09:44] * Quits: jason3 (n=chatzill@203-211-84-110.ue.woosh.co.nz) ("ChatZilla 0.9.81 [Firefox 3.0b4/2008030714]")
  127. # [09:50] * Joins: MikeSmith (n=MikeSmit@eM60-254-197-41.pool.emnet.ne.jp)
  128. # [09:53] * Quits: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  129. # [09:54] * Joins: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  130. # [09:55] * Quits: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net) (Client Quit)
  131. # [09:56] * Joins: ROBOd (n=robod@89.122.216.38)
  132. # [10:11] * Joins: qwert666 (n=qwert666@acae100.neoplus.adsl.tpnet.pl)
  133. # [10:14] * Joins: met_ (n=Hassman@r5bx220.net.upc.cz)
  134. # [10:14] * Quits: MikeSmith (n=MikeSmit@eM60-254-197-41.pool.emnet.ne.jp) ("Less talk, more pimp walk.")
  135. # [11:14] * Joins: tndH (i=Rob@83.100.254.190)
  136. # [11:16] * Quits: Thezilch (n=fuz007@cpe-76-170-22-179.socal.res.rr.com) (Read error: 104 (Connection reset by peer))
  137. # [11:21] * Quits: jgraham (n=james@81-86-216-20.dsl.pipex.com) ("I get eaten by the worms")
  138. # [11:22] * Joins: jgraham (n=james@81-86-216-20.dsl.pipex.com)
  139. # [12:06] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  140. # [12:33] * Joins: aroben (n=aroben@unaffiliated/aroben)
  141. # [12:56] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  142. # [13:02] * Joins: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  143. # [13:06] * Joins: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  144. # [13:27] * Quits: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  145. # [13:39] * Quits: virtuelv (n=virtuelv@109.80-202-65.nextgentel.com) (Read error: 104 (Connection reset by peer))
  146. # [13:44] * Joins: ROBOd (n=robod@89.122.216.38)
  147. # [13:46] * Joins: aroben_ (n=aroben@unaffiliated/aroben)
  148. # [13:50] * Quits: aroben (n=aroben@unaffiliated/aroben) (Read error: 110 (Connection timed out))
  149. # [13:50] <hsivonen> Hixie: table is no longer in ARIA
  150. # [13:51] * Joins: myakura (n=myakura@p1215-ipbf3008marunouchi.tokyo.ocn.ne.jp)
  151. # [14:02] * Joins: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  152. # [14:05] * Quits: aroben_ (n=aroben@unaffiliated/aroben) (Read error: 110 (Connection timed out))
  153. # [14:21] * Quits: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  154. # [14:36] * Quits: jgraham (n=james@81-86-216-20.dsl.pipex.com) ("I get eaten by the worms")
  155. # [14:42] * Joins: csarven (i=csarven@on-irc.csarven.ca)
  156. # [14:52] * Quits: csarven (i=csarven@on-irc.csarven.ca) (Read error: 104 (Connection reset by peer))
  157. # [14:53] * Quits: myakura (n=myakura@p1215-ipbf3008marunouchi.tokyo.ocn.ne.jp) ("Leaving...")
  158. # [14:58] * Joins: csarven (i=csarven@on-irc.csarven.ca)
  159. # [15:00] * Joins: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk)
  160. # [15:12] * Quits: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk) (Remote closed the connection)
  161. # [15:13] * Joins: jgraham (n=james@xport5.ast.cam.ac.uk)
  162. # [15:18] * Joins: Ketsuban (n=ketsuban@cpc2-oxfd8-0-0-cust335.oxfd.cable.ntl.com)
  163. # [15:19] * Quits: Ketsuban (n=ketsuban@cpc2-oxfd8-0-0-cust335.oxfd.cable.ntl.com) (Read error: 104 (Connection reset by peer))
  164. # [15:23] * Joins: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk)
  165. # [15:26] * Quits: jgraham (n=james@xport5.ast.cam.ac.uk) ("I'll hit the bottom and escape")
  166. # [15:35] * Quits: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk) (Remote closed the connection)
  167. # [15:41] * Joins: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk)
  168. # [15:43] * Quits: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk) (Remote closed the connection)
  169. # [15:49] * Joins: jgraham (n=james@xport5.ast.cam.ac.uk)
  170. # [15:50] * Joins: phsiao (n=shawn@nat/ibm/x-a4e8bcd4b2fe2173)
  171. # [15:52] * Joins: billmason (n=billmaso@ip235.unival.com)
  172. # [16:22] * Quits: KevinMarks (n=KevinMar@c-98-207-134-151.hsd1.ca.comcast.net) ("The computer fell asleep")
  173. # [16:34] * Joins: starjive (i=beos@81-233-18-73-no30.tbcn.telia.com)
  174. # [16:40] * Joins: zcorpan_ (n=zcorpan@c-cb21e353.1451-1-64736c12.cust.bredbandsbolaget.se)
  175. # [16:57] * Quits: weinig|zZz (n=weinig@c-71-198-176-23.hsd1.ca.comcast.net)
  176. # [17:12] * Joins: andersca (n=andersca@nat/apple/x-fef8b7fa765d6fbc)
  177. # [17:13] * Parts: zcorpan_ (n=zcorpan@c-cb21e353.1451-1-64736c12.cust.bredbandsbolaget.se)
  178. # [17:27] <hsivonen> http://blog.ianbicking.org/2008/03/23/html-accessibility/
  179. # [17:33] <jgraham> http://blog.ianbicking.org/2008/03/23/html-accessibility/#comment-16200 is particularly interesting
  180. # [17:34] * BenMillard is reading through
  181. # [17:38] <hsivonen> jgraham: regarding ARIA and outline integration, it seems to me that aria-level may be a bigger issue than role=heading
  182. # [17:40] * Joins: gsnedders (n=gsnedder@host86-138-199-53.range86-138.btcentralplus.com)
  183. # [17:43] <BenMillard> comment #7: "the web is filled with bad HTML and we are stuck with it, so let’s learn to deal with it instead of despise it."
  184. # [17:44] <BenMillard> some of it is too broken to work unless authors make adjustments, such as using <td> with no attributes or <b> or <strong> for table headers
  185. # [17:45] <BenMillard> in general, inline-level markup can be anything you want and it will adapt well enough
  186. # [17:46] * webben tries to work out how to create a "succint" alt attribute for a complex chart or diagram.
  187. # [17:47] <BenMillard> providing sensible alt for graphical links and buttons is something you can't really get around...unless we require such images to have readable filenames :P
  188. # [17:48] * Joins: annevk (n=annevk@84.77.28.156)
  189. # [17:49] <annevk> hmm, over 600 e-mails
  190. # [17:51] * hsivonen has been sending email mostly to http://lists.w3.org/Archives/Public/public-pfwg-comments/2008JanMar/ instead of public-html...
  191. # [17:51] <annevk> 80 marked as spam
  192. # [17:52] * Joins: weinig (n=weinig@17.203.15.180)
  193. # [17:52] <BenMillard> http://lists.w3.org/Archives/Public/public-pfwg-comments/2008JanMar/author.html#msg54 - hsivonen's messages
  194. # [17:54] <annevk> ah, my e-mail was not just since yesterday though :)
  195. # [18:03] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  196. # [18:09] * Joins: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk)
  197. # [18:12] * Joins: KevinMarks (n=KevinMar@nat/google/x-74c8b9eeea489616)
  198. # [18:20] <BenMillard> hsivonen, http://hsivonen.iki.fi/aria-html5/ times out for me (tried 3 times)
  199. # [18:27] <annevk> works now
  200. # [18:27] <BenMillard> yep
  201. # [18:37] <jgraham> hsivonen: <h1 aria-level=2></h1><h2 aria-level=1></h2>? Fun fun fun.
  202. # [18:38] * Quits: KevinMarks (n=KevinMar@nat/google/x-74c8b9eeea489616) ("The computer fell asleep")
  203. # [18:38] <jgraham> "In many cases the user agent may be able to calculate the level of an item if it can be determined correctly from the document structure. This property may be used to provide an explicit indication of the level if that is not possible from the document structure. User agent automatic support for automatic calculation of level may vary; it is recommended that authors test with user agents and assistive technologies to determine whether this property
  204. # [18:38] <jgraham> is needed."
  205. # [18:39] <jgraham> What kind of spec text is that?
  206. # [18:40] <jgraham> "You might want to consider using this property in some undefined set of circumstances when some undefined other mechanisms for achieving the same thing fail in some undefined set of software you have access to"
  207. # [18:43] * Joins: zcorpan_ (n=zcorpan@c-cb21e353.1451-1-64736c12.cust.bredbandsbolaget.se)
  208. # [18:43] <jgraham> Possible steps to fixing this:
  209. # [18:43] <BenMillard> perhaps: "The aria-level property must not be used on elements which are specified to indicate a level natively."
  210. # [18:43] <jgraham> a) identify the set of circimstances in which aria-level is needed
  211. # [18:44] <jgraham> b) try to reduce that set to 0 by adding features to HTML
  212. # [18:44] <jgraham> dunno if that will work though
  213. # [18:44] <BenMillard> followed by: "If it is used on such elements, it is ignored."
  214. # [18:45] <webben> jgraham: Note that if support for those new features trails support for aria-level, web developers may be forced to use both to support older UAs.
  215. # [18:45] <jgraham> webben: Sure
  216. # [18:46] * Joins: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  217. # [18:47] <BenMillard> ARIA is itself a new feature which older UAs don't support, though?
  218. # [18:47] <jgraham> (for some definition of "forced")
  219. # [18:47] <jgraham> BenMillard: Well it looks like ARIA will be supported faster than e.g. <datagrid>
  220. # [18:47] <webben> BenMillard: older UAs being the current crop (IE8, Fx 2-3, Opera 9.5)
  221. # [18:48] <webben> + the current crop of AT of course
  222. # [18:49] <jgraham> webben: The nice thing is that browser upgrade cycles are much faster than AT upgrade cycles.
  223. # [18:49] <jgraham> And exposing e.g. <datagrid> is a browser problem
  224. # [18:50] <webben> jgraham: That doesn't help if the browser upgrades require AT upgrades (as IE7 did, for example)
  225. # [18:50] <jgraham> That sucks. I assumed they all used these standard APIs.
  226. # [18:51] <webben> if all that changed between releases was the browser recognized more native HTML5 elements and treated them the same as the aria attributes when exposing to accessibility frameworks, all would be well. But that's not all that changes.
  227. # [18:51] <webben> jgraham: Well part of the underlying problem is MSAA is old and crusty; and UI Automation isn't widely used.
  228. # [18:52] <webben> jgraham: And with Apple, you need to upgrade your entire OS to get the full benefits of accessibility improvements in WebKit.
  229. # [18:52] <jgraham> In any case, what BenMillard said is a more viable short-term solution (i.e. change the wording to forbid using aria-level where it isn't appropriate and make native semantics take precedence)
  230. # [18:52] <webben> the most stable system is perhaps GNOME AT-SPI, oddly enough.
  231. # [18:52] <webben> (Firefox3+Orca basically)
  232. # [18:53] <webben> jgraham: But how do you define "where it isn't appropriate" in a way that doesn't exclude using aria attributes for backwards compatibility?
  233. # [18:53] <BenMillard> jgraham, yay a useful contribution. :)
  234. # [18:53] <Philip`> webben: The most stable system is a dead one :-)
  235. # [18:53] <jgraham> the first part of that (conformance criteria) should be easy. The second part (browser behavior) goes against current thinking
  236. # [18:54] <webben> Philip`: well, Apple would be much the same if the upgrades were free.
  237. # [18:54] <webben> but the unfreeness creates a longer upgrade cycle
  238. # [18:55] <webben> jgraham: I can't see the point of forbidding web developers from doing stuff that doesn't break newer browsers and makes old browsers work. It's a dead letter conformance requirement.
  239. # [18:55] <jgraham> webben: What sort of back-compat scenario requires html-headings (for example) to be labelled with explicit aria-levels
  240. # [18:56] <webben> jgraham: Well, the spec could list a specific set of /currently/ widely supported elements not to use it on.
  241. # [18:56] <webben> that's a bit messy though
  242. # [18:57] <webben> jgraham: Oh actually. There might be one.
  243. # [18:57] <jgraham> webben: The problem is that you want a consistent view of the document regardless of whether you view it through AT or through a normal browser
  244. # [18:57] <webben> jgraham: HTML5 changes how headings should be ordered (thanks to section).
  245. # [18:57] <webben> Browsers and AT don't support that yet.
  246. # [18:57] <webben> AFAIK.
  247. # [18:57] <annevk> we should allow text/html with root-<svg>
  248. # [18:57] <annevk> that'd be cool
  249. # [18:57] <webben> If they already support aria-level, then there would be rationale for allowing aria-level on headings.
  250. # [18:58] <BenMillard> webben and jgraham, the important thing for AT users is the text use an element somewhere between <h1> and <h6>. the exact number is less important
  251. # [18:58] <BenMillard> (inclusive)
  252. # [18:58] <webben> BenMillard: It's /less/ important. It's not irrelevant.
  253. # [18:59] <webben> But don't take my word for it: http://video.yahoo.com/video/play?vid=514676 (on importance of heading levels in understanding structure of page)
  254. # [18:59] <BenMillard> I saw that months ago, thanks :)
  255. # [19:00] <BenMillard> considering how rare it is for content to use *any* heading element, we should not forget what's important
  256. # [19:00] <webben> I see no reason as a web developer to make content less accessible in order to satisfy arbitrary conformance criteria.
  257. # [19:00] * Joins: KevinMarks (n=KevinMar@nat/google/x-75670787cca81a43)
  258. # [19:00] <BenMillard> me neither. do you have any examples where that is happening?
  259. # [19:01] <webben> BenMillard: I just posited one.
  260. # [19:01] <jgraham> webben: The conformance criteria aren't arbitrary. It's needed for logical consistency.
  261. # [19:02] * webben doesn't really see how.
  262. # [19:02] <webben> I'm more worried about the logical inconsistency between heading levels in different versions of HTML, myself.
  263. # [19:03] <webben> Sounds like aria-level would provide a way to work around that.
  264. # [19:03] <jgraham> I suppose theoretically you could make the criteria "aria-level used on heading elements must produce an outline structure that is identical to that produced by the html5 algorithm"
  265. # [19:03] <jgraham> but hsivonen might kill you ;)
  266. # [19:04] <webben> I think we're in different countries, so I'm probably safe for the moment. ;)
  267. # [19:04] <jgraham> webben: There is no logical inconsistency between HTML versions
  268. # [19:04] <jgraham> HTML4 had no structure
  269. # [19:04] <jgraham> except one that you inferred the authors probably meant
  270. # [19:04] <webben> It didn't have "no structure".
  271. # [19:05] <webben> Certainly not once you take WCAG and actual implementations into account.
  272. # [19:05] <BenMillard> webben, if you want backward-compatible headings (as do I) you just choose the correct number for each heading (whatever your feeling of "correct number" is). there is no need for aria-level in this respect, afaict.
  273. # [19:05] <jgraham> webben: There is no text anywhere in HTML 4 that says what heading structure <h1>,
  274. # [19:05] <jgraham> erm..
  275. # [19:05] * Quits: psa (n=yomode@71.93.19.66) (Remote closed the connection)
  276. # [19:05] <jgraham> <h1><h2> corresponds to, let alone <h2><h1><h6~>
  277. # [19:05] <jgraham> s/~//
  278. # [19:06] <webben> BenMillard: Yeah, I'd believe that more if HTML5 authorial conformance criteria required Hx headings to be used that way.
  279. # [19:07] * Joins: a-ja (n=chatzill@adsl-70-237-201-197.dsl.stlsmo.sbcglobal.net)
  280. # [19:07] <webben> jgraham: "There are six levels of headings in HTML with H1 as the most important and H6 as the least." (http://www.w3.org/TR/html401/struct/global.html#edef-H1)
  281. # [19:07] * Joins: dbaron (n=dbaron@corp-241.mountainview.mozilla.com)
  282. # [19:07] <jgraham> define "important"
  283. # [19:07] <jgraham> many web authors think headings in side bars are "less important"
  284. # [19:07] <webben> define "structure"
  285. # [19:07] <jgraham> eh?
  286. # [19:07] <webben> Headings in side bars may well be less important.
  287. # [19:08] <webben> And to that extent, putting them at a lower level is fine.
  288. # [19:08] <jgraham> I guess I should have said "outline structure"
  289. # [19:09] <Philip`> BenMillard: "considering how rare it is for content to use *any* heading element" - I see <h1> on over a fifth of pages, so it doesn't seem that rare
  290. # [19:09] <webben> Does HTML5 say that h1s in different positions of the "outline structure" have the same "importance"? Are the notions of "importance" and "outline structure" incompatible anyways?
  291. # [19:09] <jgraham> Which I define as a tree-like view of the document in which only the text of headings is visible and the headings of subsections are children of their parent headings (and probably some more stuff to deal with siblings)
  292. # [19:10] <BenMillard> Philip`, that means it isn't used on somewhere nera 80% of pages, then. :)
  293. # [19:10] <jgraham> webben: The problem with having "less important" headings in sidebars is that it breaks this outline view
  294. # [19:10] * Joins: psa (n=yomode@71.93.19.66)
  295. # [19:10] <jgraham> So putting them at a lower level isn't fine
  296. # [19:10] <webben> jgraham: That's debatable.
  297. # [19:11] <webben> It's not ideal, sure.
  298. # [19:11] <Philip`> BenMillard: Compared to most other HTML features, that's hugely popular :-)
  299. # [19:11] <webben> But I don't think it breaks the view.
  300. # [19:11] <jgraham> webben: That's not what I found
  301. # [19:12] <webben> what was your test for breakage?
  302. # [19:12] <BenMillard> Philip`, consider it's popularity from a user's perspective: 80% of the time they can't get around the page easily
  303. # [19:12] <BenMillard> fixing that 80% so they use heading elements *at all* is the priority, as I see it
  304. # [19:12] * Quits: zcorpan_ (n=zcorpan@c-cb21e353.1451-1-64736c12.cust.bredbandsbolaget.se) (Read error: 110 (Connection timed out))
  305. # [19:13] <webben> BenMillard: That doesn't follow necessarily. Maybe they just stick with webpages that are coded better.
  306. # [19:13] <a-ja> hsivonen: ping
  307. # [19:13] <BenMillard> webben, the research I want to do into use of headings on the web would throw light on this. haven't quite secured sponsorship for it, yet
  308. # [19:14] <BenMillard> despite taking this whole month off work, I might add :(
  309. # [19:14] <webben> BenMillard: Well, good luck getting sponsorship from whomever you're trying to get it from :)
  310. # [19:16] <jgraham> webben: My test for breakage was whether it made sense in my Firefox outliner extension
  311. # [19:16] <webben> jgraham: I think I more meant your test for "making sense" then ;)
  312. # [19:16] <Philip`> BenMillard: Hmm, how much harder does a lack of headings make it to use a page? (I'm wondering if that's more/less of a problem than ~50% of images not using alt)
  313. # [19:16] <webben> Philip`: That very much depends on the complexity of the page doesn't it?
  314. # [19:17] <webben> (and what /else/ is on the page to navigate by)
  315. # [19:17] <webben> (oh and what else the user knows (s)he can navigate by)
  316. # [19:17] <jgraham> webben: Well the harshest test is whether there was ever a "subsection" in the outline that clearly wasn't a logical child of the parent
  317. # [19:17] <BenMillard> Philip` and webben, absence of headings is similarly problematic to absence of sensible alt
  318. # [19:17] <Philip`> webben: That sounds sensible; I've got no idea how that works out in practice, though
  319. # [19:18] <jgraham> That often happened when the sidebar came out as a child of the last "content" section
  320. # [19:19] <webben> jgraham: Was the sidebar only a sidebar to the last content section?
  321. # [19:19] <webben> If not, maybe the choice of level didn't really reflect its importance
  322. # [19:19] <jgraham> No, to the whole page
  323. # [19:19] <jgraham> Also, things around the page header often broke
  324. # [19:20] <jgraham> with subtitles often causing confusion
  325. # [19:20] <BenMillard> http://projectcerbera.com/web/articles/heading-numbers - this article I wrote was well received by website developers on Accessify Forum.
  326. # [19:20] <BenMillard> Basically, authors interpret the vague specs differently. So I think a strict, tree-based outline algorithm is doomed to failure for web content, sadly.
  327. # [19:20] <webben> Philip`: Well, in the simplest case, if you only have one heading on a gallery page, alt is going to be more crucial than <h1>
  328. # [19:21] * Quits: MacDome (n=eric@c-69-181-78-198.hsd1.ca.comcast.net)
  329. # [19:21] <webben> Yeah, I don't think strict, tree-based algorithms need to be 100% successful for the lousy semantics established by HTML4 and common practice to be useful
  330. # [19:22] <BenMillard> I think we should let authors use heading numbers however they want, because at least they're actually using heading elements that way
  331. # [19:23] <webben> If using heading numbers in some sort of meaningful logic helps, I don't see any reason to do that.
  332. # [19:23] <webben> in practice, authors are going to make mistakes anyways
  333. # [19:23] <BenMillard> encouraging them to be consistent throughout the website is wortwhile, as WCAG 1.0 requires
  334. # [19:24] <jgraham> In principle HTML 5 solves all these problems with <section> and <header>
  335. # [19:24] <BenMillard> you trust authors to get that right? I wouldn't :)
  336. # [19:25] <jgraham> BenMillard: No, but at least the results when they get it wrong will be well defined
  337. # [19:26] <jgraham> So it will be wrong in the same way for everyone - easier for people to complain, easier for a conformance checker to provide an outline view
  338. # [19:26] <jgraham> (or an accessibility checker, for that matter)
  339. # [19:26] <webben> BenMillard: If Joe Bloggs gets it wrong on a minor website, it's less crucial than Google, Yahoo!, MSN, the New York Times, the BBC etc getting it right on theirs.
  340. # [19:27] <webben> because people spend more time on big websites than small ones
  341. # [19:28] <BenMillard> more people use one big website than use one small website. the time each person spends on each website is random
  342. # [19:28] <BenMillard> I hardly spend any time on big websites, for example
  343. # [19:28] <webben> BenMillard: I don't think that's typical.
  344. # [19:28] <webben> Don't know of any market research to back that up off-hand though.
  345. # [19:29] <BenMillard> webben, are you saying I'm weird?
  346. # [19:29] <BenMillard> actually don't answer that...
  347. # [19:29] <webben> BenMillard: No! :)
  348. # [19:29] <webben> just a different "demographic" ;)
  349. # [19:30] <webben> somebody must have done some actual research on this though
  350. # [19:31] <BenMillard> the goal is to make *every* website accessible as soon as possible?
  351. # [19:31] <jgraham> http://blog.compete.com/2007/01/25/top-20-websites-ranked-by-time-spent/
  352. # [19:32] * jgraham postulates that facebook has risen somewhat
  353. # [19:32] <webben> jgraham: Hmm... is that collective time.
  354. # [19:32] <webben> Because that's slightly different.
  355. # [19:33] <jgraham> webben: It's hard to see how to get meaningful data without averaging large groups
  356. # [19:33] <webben> "Read as: Of all time spent online by all US Internet users"
  357. # [19:33] <webben> jgraham: sure, but that's still measuring something very different.
  358. # [19:33] <jgraham> Unless you start trying to subdivide the data based on real/imagined patterns
  359. # [19:33] <webben> what one would want to do is establish which sites are big, then average how much time is actually spent on those by each person.
  360. # [19:34] <webben> so let's say myspace is big
  361. # [19:34] <webben> but how much time does the average person spend on Myspace (as opposed to everywhere else)
  362. # [19:34] <jgraham> How do you define "big" in an independent way?
  363. # [19:34] <BenMillard> hang on, we are trying to make *everything* accessible. not just the big, time-consuming sites?
  364. # [19:34] <webben> jgraham: It can be arbitrarily defined, e.g. top 100 websites by traffic
  365. # [19:34] <webben> jgraham: might get better if you subgrouped more
  366. # [19:35] <webben> e.g. maybe everyone spend's most of their time on like 10 websites.
  367. # [19:35] <webben> BenMillard: Yes. But that doesn't mean the accessibility of every site is equally important.
  368. # [19:36] <jgraham> So one definition which would fit handily with the data that I happened to turn up is that we define "bigness" by time spent and define "big" sites to be those which are in the top 20 by bigness. If we do that we find that 39% of all time is spent on big sites
  369. # [19:36] <jgraham> ;)
  370. # [19:36] <webben> BenMillard: So one wouldn't needn't get too depressed by figures suggesting inaccessibility is widespread in absolute terms.
  371. # [19:37] <webben> BenMillard: But would need to get very depressed by figures showing inaccessibility is common on highly popular sites (which of course it is).
  372. # [19:37] <BenMillard> in practice, site owners decide if accessibility is important enough to them to pay for it
  373. # [19:38] <webben> Well sure, but only if the developers charge them extra for it.
  374. # [19:38] <webben> Rather than just doing it right.
  375. # [19:38] <BenMillard> FWIW, sdesign1, the company I work for, doesn't charge extra for accessibility
  376. # [19:38] <jgraham> webben: Arguably technologies like aria encourage that because doing it right is considerably more effort than just doing it
  377. # [19:39] <BenMillard> prioritising the important things, like using heading elements at all, is what site owners need to know about
  378. # [19:39] <webben> (There are edge cases where that's not the case, where site owners need to stump up for accessible content though)
  379. # [19:39] <webben> jgraham: ARIA was mainly designed to build accessibility into div-based widgets systems.
  380. # [19:39] <webben> Once built into those systems (like Dojo), the cost of using an ARIA-fied widget is the same as using a non-ARIA-fied widget.
  381. # [19:40] <jgraham> webben: I know. Your argument works iff everyone is using off-the-shelf widgets
  382. # [19:40] <webben> people who actually build widgets are already a very select grouo
  383. # [19:40] <webben> *group
  384. # [19:40] * Quits: dbaron (n=dbaron@corp-241.mountainview.mozilla.com) (Excess Flood)
  385. # [19:40] * Joins: dbaron (n=dbaron@corp-241.mountainview.mozilla.com)
  386. # [19:41] <BenMillard> I've used widgets. they are built terribly, on the whole
  387. # [19:41] <jgraham> Does e.g. the new bbc design use entirely off the shelf widgets?
  388. # [19:41] <webben> I wouldn't /expect/ the BBC design to use entirely off-the shelf widgets.
  389. # [19:41] <webben> I'd expect Joe Bloggs building his intranet app in a hurry to use them etc
  390. # [19:43] <webben> I'd expect the BBC to be the sort of place which would hire web developers who could build custom widget sets.
  391. # [19:43] <jgraham> I'm sure the bbc, in particular, is since they have a very strong commitment to such things
  392. # [19:44] <BenMillard> expectations are irrelevant. resistance is futile. you will be laid out in a <table>
  393. # [19:44] <BenMillard> if HTML5 makes accessibility seem hard, that will just put people off
  394. # [19:44] <BenMillard> we need basic accessibility to be dead simple
  395. # [19:44] <BenMillard> refined accessibility can be harder, if necessary
  396. # [19:44] <webben> There's no point in making accessibility seem simpler than it is.
  397. # [19:45] <webben> I do see your point about quick wins.
  398. # [19:45] <webben> But I don't think the place to encourage quick wins is in the conformance criteria.
  399. # [19:45] <webben> Most people don't care about conformance criteria.
  400. # [19:46] * jgraham suggests there is a high correlation between caring about conformance criteria and caring about accessibility
  401. # [19:46] <webben> sure.
  402. # [19:46] <BenMillard> caring about either is rare
  403. # [19:46] <jgraham> Not that I have evidence to back that up or anthing
  404. # [19:46] <webben> but people who really care about accessibility aren't going to be put off because it needs thinking
  405. # [19:46] <BenMillard> we need accessibility to be more accessible :)
  406. # [19:46] <webben> Hmm maybe.
  407. # [19:47] <jgraham> webben: Not true. People might want to be accessible but fail because it's too hard
  408. # [19:47] <webben> The biggest obstacles to making stuff accessible tend to be further down the chain though.
  409. # [19:47] <webben> e.g. "What? Blind people can use computers? But how?" etc
  410. # [19:47] <jgraham> which way is down?
  411. # [19:47] <BenMillard> s/down the chain/up the chain, imho
  412. # [19:47] <BenMillard> i.e. managers rather than developers
  413. # [19:48] <webben> jgraham: Down is managers/commissioners of websites. Down is a million miles away from the spec and conformance criteria and the HTML.
  414. # [19:48] <jgraham> and up is users?
  415. # [19:48] <webben> no up is implementors, developers, testers
  416. # [19:48] <webben> and the spec and the code
  417. # [19:49] <jgraham> where are users in this chain
  418. # [19:49] <jgraham> Where is AT?
  419. # [19:49] <webben> they're not.
  420. # [19:49] <jgraham> Browsers?
  421. # [19:49] <webben> (users aren't anyhow)
  422. # [19:49] * jgraham envisioned a chain connecting content to users
  423. # [19:49] <webben> I'd say for AT and browsers there's a similar chain.
  424. # [19:49] <BenMillard> ah, I think webben is talking about the process of building websites, rather than the process of using websites?
  425. # [19:49] <BenMillard> and that these are 2 different chains?
  426. # [19:49] <webben> Sorry, yeah, I thought we all were.
  427. # [19:50] <BenMillard> my approach to building websites involves users, which is what threw me
  428. # [19:50] * jgraham suggests a chain is too 1D
  429. # [19:50] <webben> jgraham: If you're talking about, the end-product (users being able to access content/functionality) then yes.
  430. # [19:51] <webben> users/disability organizations/governments/AT/browsers/operating systems - all sorts of factors
  431. # [19:52] <webben> Also, down is in people's level of interest. A lot of sitepoint comments on the target case were from apparent webdevs surprised/outraged that blind people can use the internet.
  432. # [19:53] <webben> *down is people's level of knowledge rather.
  433. # [19:53] <webben> remembering that a lot of people developing websites aren't very interested in the front-end
  434. # [19:55] <BenMillard> making accessibility seem like a grand and difficult struggle puts devs off, in my experience (I am often contracted by other companies)
  435. # [19:56] <BenMillard> showing a code sample where <p><font size face><span style><b> is replaced by <h1> has a more positive reaction
  436. # [19:56] <webben> I don't think accessibility has to be made grand and difficult.
  437. # [19:56] <webben> Actually, I'm not sure accessibility at the HTML level is /that/ difficult.
  438. # [19:57] <webben> it gets a lot trickier with scripting and CSS.
  439. # [19:57] <webben> and there's only a limited amount HTML5 can do about either.
  440. # [19:58] <gsnedders> We need CSS5 and ECMAScript5.
  441. # [19:58] * Quits: starjive (i=beos@81-233-18-73-no30.tbcn.telia.com)
  442. # [19:58] <webben> gsnedders: Well, a lot of accessibility problems produced through CSS derive from implementations.
  443. # [19:59] * gsnedders closes implied sarcasm element
  444. # [20:00] <BenMillard> Hixie's e-mail "several messages about tables and related subjects" says: "I also looked in detail at the information that Ben and James provided, which was incredibly useful." yay us!
  445. # [20:00] <jgraham> :)
  446. # [20:00] <webben> scripting ... well maybe if HTML5 comes up with a nice solution for exposing shortcuts to functionality or something.
  447. # [20:00] * Joins: grimeboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk)
  448. # [20:03] * Quits: jruderman (n=jruderma@c-67-180-15-227.hsd1.ca.comcast.net)
  449. # [20:04] * Quits: KevinMarks (n=KevinMar@nat/google/x-75670787cca81a43) ("The computer fell asleep")
  450. # [20:08] * Joins: eseidel (n=eseidel@nat/google/x-99449d41d2290bd3)
  451. # [20:08] * Quits: eseidel (n=eseidel@nat/google/x-99449d41d2290bd3) (Read error: 104 (Connection reset by peer))
  452. # [20:08] * Joins: eseidel (n=eseidel@nat/google/x-aa6c6bed7b4ed10e)
  453. # [20:11] * Joins: KevinMarks (n=KevinMar@nat/google/x-fd473102676ee352)
  454. # [20:14] * Quits: grimeboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk) (Remote closed the connection)
  455. # [20:15] <annevk> hsivonen, http://hsivonen.iki.fi/rdf/ s/is assumes/assumes/
  456. # [20:15] * Quits: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk) (Read error: 110 (Connection timed out))
  457. # [20:16] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  458. # [20:17] * Joins: sayrer (n=chatzill@66.37.169.174)
  459. # [20:22] * Quits: othermaciej (n=mjs@dsl081-048-145.sfo1.dsl.speakeasy.net)
  460. # [20:24] * Quits: csarven (i=csarven@on-irc.csarven.ca) (Read error: 110 (Connection timed out))
  461. # [20:26] * Quits: dbaron (n=dbaron@corp-241.mountainview.mozilla.com) ("8403864 bytes have been tenured, next gc will be global.")
  462. # [20:26] <jgraham> http://www.openplans.org/projects/opencore/blog/2008/03/24/accessibility-on-our-site/ does he just have something wrong with his NVDA installation?
  463. # [20:27] <jgraham> s/just/"just"/
  464. # [20:28] * Quits: mfinkle (n=mfinkle@c-71-58-73-95.hsd1.pa.comcast.net) (Read error: 104 (Connection reset by peer))
  465. # [20:28] * Joins: mfinkle (n=mfinkle@c-71-58-73-95.hsd1.pa.comcast.net)
  466. # [20:38] <andersca> Hixie?
  467. # [20:47] <webben> jgraham: he helpfully doesn't say what version he's using
  468. # [20:48] <jgraham> webben: I would presume he just got 0.5
  469. # [20:51] * Joins: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk)
  470. # [20:53] <hsivonen> a-ja: pong
  471. # [20:53] <a-ja> hi henri
  472. # [20:54] <a-ja> hsivonen: re: your "ARIA in HTML5" strawman "Strong Native Role—No Override" section
  473. # [20:54] <a-ja> thing like article only allowing region, e.g.
  474. # [20:55] <a-ja> should those also be allowed the "landmark" roles?
  475. # [20:55] <a-ja> like main or secondary?
  476. # [20:55] <Hixie> andersca: here
  477. # [20:55] <Hixie> BenMillard: i don't believe i've ever looked at so many tables before :-)
  478. # [20:56] <Hixie> BenMillard: i ended up covering two whiteboards with little table diagrams
  479. # [20:56] <andersca> Hixie: correct me if I'm wrong, but
  480. # [20:56] <andersca> Hixie: manifest lines can't have leading whitespace, right?
  481. # [20:57] <BenMillard> hixie, I can well imagine!
  482. # [20:57] <hsivonen> a-ja: I don't know.
  483. # [20:57] <a-ja> possibly secondary for aside, e.g. vs just note possible?
  484. # [20:57] <hsivonen> a-ja: could make sense. I'm not sure.
  485. # [20:57] <BenMillard> hixie, I think I looked at thousands overall because I wanted to see how consistent each site was
  486. # [20:58] <andersca> Hixie: brb
  487. # [20:58] * Quits: andersca (n=andersca@nat/apple/x-fef8b7fa765d6fbc)
  488. # [20:58] <hsivonen> a-ja: in any case, I think eventually a good outcome is that if the landmarks are really important, they have native HTML5 elements
  489. # [20:58] <Hixie> BenMillard: thanks for that, it made my life much easier :-)
  490. # [20:58] <hsivonen> a-ja: those would be good questions to raise on the public-html and public-pfwg-comments lists
  491. # [20:59] <BenMillard> hixie, I'm happy to be useful. not bad for a noob :P
  492. # [20:59] <hsivonen> a-ja: the problem is that the landmarks and native HTML5 elements don't have a one-to-one mapping
  493. # [20:59] * Joins: csarven (i=csarven@on-irc.csarven.ca)
  494. # [20:59] <hsivonen> a-ja: I gather landmarks are more controversial than ARIA widgets. I wouldn't be surprised if landmarks changed still.
  495. # [21:00] <a-ja> yeah,,,know what you mean
  496. # [21:00] <Hixie> BenMillard: :-)
  497. # [21:01] * Joins: andersca (n=andersca@17.255.100.240)
  498. # [21:01] <a-ja> hsivonen: was it decided one role allowed or multiple? been a while
  499. # [21:01] * Joins: jruderman (n=jruderma@guest-225.mountainview.mozilla.com)
  500. # [21:02] <hsivonen> a-ja: (I can't associate your IRC nick with an email name)
  501. # [21:02] <Hixie> andersca: 4.6.3.2. Parsing cache manifests
  502. # [21:02] <hsivonen> a-ja: It's only one role per element in ARIA 1.0
  503. # [21:02] <Hixie> andersca: steps 13 and 15
  504. # [21:02] <hsivonen> a-ja: multiple values are for later extensions
  505. # [21:02] <a-ja> ajabanyon at gmail
  506. # [21:02] <a-ja> ah
  507. # [21:03] <jgraham> Is there a reasonable mailing list to subscribe to to keep track of aria?
  508. # [21:03] <andersca> Hixie: ah
  509. # [21:03] <BenMillard> hixie, what specifically did you find useful about it? was it just having links to lots of genuine data tables in one place?
  510. # [21:03] <hsivonen> jgraham: public-pfwg-comments
  511. # [21:03] <hsivonen> jgraham: the main list in Member-only
  512. # [21:04] * Joins: dbaron (n=dbaron@guest-225.mountainview.mozilla.com)
  513. # [21:04] <jgraham> hsivonen: Can you actually subscribe to that? Maybe I've ben misled by the archve page which only had unsubscribe links
  514. # [21:04] <jgraham> s/b en/been/
  515. # [21:04] <hsivonen> jgraham: I don't know.
  516. # [21:05] <hsivonen> jgraham: I'm not subscribed to any ARIA lists.
  517. # [21:05] <hsivonen> jgraham: I go with CCs and the Web archive interface
  518. # [21:05] <jgraham> The problem with the web archive interface is that it's hard to guess when there will be interesting content
  519. # [21:05] <annevk> I think you can subscribe
  520. # [21:06] <andersca> Hixie: thanks
  521. # [21:06] * Quits: andersca (n=andersca@17.255.100.240)
  522. # [21:06] * Quits: KevinMarks (n=KevinMar@nat/google/x-fd473102676ee352) ("The computer fell asleep")
  523. # [21:07] * jgraham tries subscribing
  524. # [21:08] * Joins: tndH_ (i=Rob@adsl-87-102-32-184.karoo.KCOM.COM)
  525. # [21:08] <a-ja> hsivonen: don't think header should necessarily always have banner role....since aisdes/sections/articles can all have header
  526. # [21:08] * Quits: grimboy (n=grimboy@78-105-162-250.zone3.bethere.co.uk) (Remote closed the connection)
  527. # [21:09] <a-ja> s/aisdes/asides/
  528. # [21:09] <jgraham> Well that appears o have worked
  529. # [21:10] <Hixie> BenMillard: that was a big part of it
  530. # [21:10] <Hixie> BenMillard: but also your analyses were useful to clue me in to what was important and useful
  531. # [21:10] <hsivonen> a-ja: what use case does role='header' fulfill that HTML native h1...h6 don't?
  532. # [21:11] <Hixie> BenMillard: also your stats were very useful as a way to quantify the qualitative experience of the many tables and the anecdotal impression of the distribution of the types of tables
  533. # [21:11] <annevk> jgraham, sure?
  534. # [21:11] <annevk> doesn't look like it
  535. # [21:12] <a-ja> well....as container for h1 title, h2 subtitle, p slogan sorta thing
  536. # [21:12] <jgraham> annevk: No, I'm not sure but I got a "reply to this to confirm" type message
  537. # [21:12] <BenMillard> hixie, that's good to know. if/when I do more research, I'll concentrate the resulting document(s) on these useful aspects
  538. # [21:13] * Joins: andersca (n=andersca@nat/apple/x-41381a0e67f9759b)
  539. # [21:13] <Hixie> BenMillard: awesome
  540. # [21:15] <andersca> Hixie: haha, I had implemented the parser according to your steps and it already handled leading whitespace :)
  541. # [21:16] <annevk> jgraham, ah
  542. # [21:16] * Joins: othermaciej (n=mjs@17.255.109.49)
  543. # [21:16] <Hixie> andersca: nice
  544. # [21:17] <othermaciej> Hixie: can I give you an acid3 bug report? or should I send mail?
  545. # [21:17] <Hixie> whats the bug report?
  546. # [21:19] <othermaciej> Hixie: test 79, two of the advances are wrong, it expects there to be an advance before the first code point of a surrogate pair and the second
  547. # [21:19] <Hixie> dude, get with the program
  548. # [21:19] <othermaciej> Hixie: the advance should be after the second
  549. # [21:19] <Hixie> i fixed that ages ago
  550. # [21:19] <Hixie> :-P
  551. # [21:19] <othermaciej> oh
  552. # [21:19] <othermaciej> I wasn't sure if Cc-ing you would be enough
  553. # [21:19] <Hixie> (i commented on the bug and everything)
  554. # [21:19] <othermaciej> thanks
  555. # [21:20] <Hixie> actually so long as the bug says "acid" somewhere in the bugmail, it ends up in my inbox
  556. # [21:20] <othermaciej> that test revealed 6 webkit bugs (well, missing features in some cases)
  557. # [21:20] <Hixie> bugmail that doesn't say "acid" anywhere gets read much later
  558. # [21:20] <othermaciej> Hixie: thanks for the fix
  559. # [21:20] <Hixie> np
  560. # [21:21] <Hixie> thank _you_ for finding it!
  561. # [21:21] <othermaciej> that test case is pretty evil
  562. # [21:21] <othermaciej> I mean, not to someone who actually knows anything about SVG or text layout
  563. # [21:21] <othermaciej> but I know very little about either
  564. # [21:22] <Hixie> heh
  565. # [21:22] <Hixie> i didn't write it
  566. # [21:22] <Hixie> though i did introduce the aforementioned error
  567. # [21:22] * Joins: virtuelv (n=virtuelv@109.80-202-65.nextgentel.com)
  568. # [21:22] <othermaciej> Yeah, I gather heycam did originally, I wrongly blamed him for the error
  569. # [21:23] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  570. # [21:23] * Joins: othermaciej (n=mjs@17.255.109.49)
  571. # [21:25] * Hixie decides to use a wiki page to note down the problems raised in the namespace folder
  572. # [21:26] * Quits: tndH (i=Rob@83.100.254.190) (Read error: 110 (Connection timed out))
  573. # [21:27] * Joins: othermaciej_ (n=mjs@17.255.109.49)
  574. # [21:27] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  575. # [21:27] <jgraham> Hixie: Some super-secret Hixie wiki or...?
  576. # [21:27] <Hixie> whatwg.org
  577. # [21:27] <hsivonen> a-ja: that use case works with HTML5 <header> but does it work with role=header?
  578. # [21:28] * Joins: thiessenp (n=thiessep@utl-194-219.library.utoronto.ca)
  579. # [21:29] <hsivonen> BenMillard: apparently my server had a maintenance break earlier
  580. # [21:29] * Joins: hober (n=ted@unaffiliated/hober)
  581. # [21:32] <a-ja> hsivonen: i'd think yes for header, no for heading....OIW not all headers are banners, but all banners are headers
  582. # [21:32] <hsivonen> annevk: typo noted. thanks. (I'll fix when connectivity to the server comes back)
  583. # [21:34] * Quits: dbaron (n=dbaron@guest-225.mountainview.mozilla.com) ("8403864 bytes have been tenured, next gc will be global.")
  584. # [21:35] <Hixie> http://wiki.whatwg.org/wiki/New_Vocabularies
  585. # [21:35] <hsivonen> a-ja: yeah, the implicit role mappings aren't perfect matches
  586. # [21:36] <a-ja> hsivonen: i'm no ARIA experts by any means though...just a site dev trying to make sense of landmarking mapping to html5 elements
  587. # [21:37] <hsivonen> Actually, I don't like the introduction of the landmark stuff when implementing the HTML5 new landmark containers would be relatively low-hanging fruit
  588. # [21:37] <hsivonen> Hixie: I think typography comes before maintainability when it comes to math markup
  589. # [21:37] <hsivonen> Hixie: maintainability is abstracted behing itex2mml
  590. # [21:38] <hsivonen> behind
  591. # [21:38] <Hixie> it wasn't an ordered list
  592. # [21:38] <Hixie> :-)
  593. # [21:39] <Hixie> and to be honest, i wouldn't necessarily agree that quality comes first
  594. # [21:39] * Joins: davidb (n=davidb@142.150.154.101)
  595. # [21:39] <Hixie> one of the main pieces of feedback i got from the video discussion was that in reality, contrary to common belief, the priority was sustainable frame rate, not video quality
  596. # [21:39] * davidb wave to BenMillard
  597. # [21:39] <Hixie> i imagine the same applies here
  598. # [21:39] <jgraham> I think ease-of-creation is paramount and that ease of creation means LaTeX syntax
  599. # [21:40] <a-ja> hsivonen: e.g. been taking hyml4 sites with landmarking incorporated in link rels and trying to shoehorn them to html5 elements with roles instead
  600. # [21:40] <jgraham> (because that's what authors already know)
  601. # [21:40] <Hixie> jgraham: i am continuously amazed that nobody seems to be able to say anything in these discussions without linking the problem with the solution :-)
  602. # [21:40] <jgraham> Hixie: I know.
  603. # [21:40] <jgraham> :-p
  604. # [21:41] <jgraham> OK, let me rephrase. The problem is that the primary body of content authors has no interest in learning a new authoring format to create content.
  605. # [21:41] <hsivonen> a-ja: do you mean using an HTML5 element *and* a role attribute on it?
  606. # [21:42] * Quits: davidb (n=davidb@142.150.154.101)
  607. # [21:42] <jgraham> I don't see how to fully explain that problem without reference to the extant widely known formats
  608. # [21:42] <hsivonen> Hixie: I'm linking the solution to it, because I think one of the problems is minimizing the implementation delta from here to there in certain Web engines
  609. # [21:43] <a-ja> hsivonen: yeah, like role=main on article
  610. # [21:43] <a-ja> instead of link rel=main pointing to a div
  611. # [21:43] <Hixie> hsivonen, jgraham: wiki page updated
  612. # [21:43] <jgraham> In particular ease of authoring doesn't cover the problem I referred to because a new easy format would still not leverage the bias toward the old format
  613. # [21:43] <hsivonen> a-ja: OK. my sense of language design aesthetics revolts at that, but practically speaking we should probably allow explicit declaration of the implicit role
  614. # [21:44] <jgraham> Hixie: I suppose the parenthetical covers it
  615. # [21:44] * Quits: othermaciej_ (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  616. # [21:44] <Hixie> jgraham: if a new format is easier to author than the known format, including cost of switching, then it'll most likely win
  617. # [21:44] * Joins: othermaciej (n=mjs@17.255.109.49)
  618. # [21:45] <jgraham> Hixie: Tell that to all the scientists who insist on using Fortran for everything
  619. # [21:45] <Hixie> jgraham: the cost of switching is probably high for them
  620. # [21:47] <jgraham> Indeed. But given the large timescales involved (decades) and the possibility of integrating old and new solutions (by calling old fortran from new whatever) there has to be an element of unwillingness
  621. # [21:47] <jgraham> beyond the purely rational
  622. # [21:48] <a-ja> hsivonen: maybe an outer article needs to automagically have main role, and inner articles secondary, or somesuch...less generic than region
  623. # [21:49] <jgraham> biab
  624. # [21:49] * Quits: jgraham (n=james@xport5.ast.cam.ac.uk) ("I get eaten by the worms")
  625. # [21:49] <BenMillard> hsivonen, you say "[...] we should probably allow explicit declaration of the implicit role" but that is likely to make authors think they must always supply it just in case their markup would be too vague if they omit it
  626. # [21:50] <hsivonen> BenMillard: that's why I don't like this landmark stuff at all
  627. # [21:52] * BenMillard waves back to davidb, somewhat belated!
  628. # [21:53] <BenMillard> I have an urgent appointment with a cottage pie. bye all!
  629. # [21:53] * Parts: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  630. # [21:54] * Hixie blogs on the whatwg blog
  631. # [21:55] * Joins: dbaron (n=dbaron@corp-241.mountainview.mozilla.com)
  632. # [21:55] <hsivonen> Opera on S60 is already pretty good at guessing what the "main" content is without role=main
  633. # [21:55] * Quits: othermaciej (n=mjs@17.255.109.49) (Connection reset by peer)
  634. # [21:55] * Joins: othermaciej (n=mjs@17.255.109.49)
  635. # [21:55] <hsivonen> Hixie: typo: tablular
  636. # [21:56] <Hixie> fixed thanks
  637. # [21:56] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  638. # [21:57] * Joins: othermaciej (n=mjs@17.255.109.49)
  639. # [21:58] <a-ja> hsivonen: just curious...screenie of the S60 UI for that, perchance?
  640. # [21:58] * Joins: starjive (i=beos@81-233-18-73-no30.tbcn.telia.com)
  641. # [21:59] <hsivonen> a-ja: I don't know how to take screenshots on S60. the UI is a one-pixel horizontal line in the scrollbar and a keybinding that jumps to that point, to the end and to the start
  642. # [22:00] <a-ja> sounds nice & simple
  643. # [22:05] <a-ja> well, gotta go, too. hope your draft gets feedback from the aria gurus, so discussion to nail some/most of it down can occur in reasonable timeframe
  644. # [22:05] <a-ja> ttfn
  645. # [22:05] <hsivonen> see you
  646. # [22:06] * Parts: a-ja (n=chatzill@adsl-70-237-201-197.dsl.stlsmo.sbcglobal.net)
  647. # [22:06] * Parts: thiessenp (n=thiessep@utl-194-219.library.utoronto.ca)
  648. # [22:10] <hsivonen> jgraham__: are you going to send feedback about aria-level?
  649. # [22:11] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  650. # [22:11] * Joins: othermaciej (n=mjs@17.255.109.49)
  651. # [22:12] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  652. # [22:26] <hsivonen> it seems to me that ARIA treegrid may kill <datagrid> as a native element
  653. # [22:26] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  654. # [22:27] * Joins: othermaciej (n=mjs@17.255.109.49)
  655. # [22:27] <Hixie> how so? does aria treegrid have any effect on non-screen-reader software?
  656. # [22:27] <hsivonen> I predict the <datagrid> API will resurface as a JS library written on top of HTML <table role=treegrid>
  657. # [22:27] <hsivonen> Hixie: It doesn't but a JS library changing a table would have
  658. # [22:27] <Hixie> i think you've been breathing the accessibility koolaid for too long and have come to the mistaken assumption that most people care about accessibility
  659. # [22:28] <Hixie> and even consider it a priority in any sense
  660. # [22:28] <hsivonen> I think they care about compat with browsers that don't have native <datagrid>
  661. # [22:28] <othermaciej> breathing kool-aid, hah
  662. # [22:28] <Hixie> othermaciej: these days it's distributed in aerosol form
  663. # [22:28] <othermaciej> my impression is that the average content author does not care much about accessibility, *but*
  664. # [22:29] <othermaciej> some people have a business need to have their apps in some way "certified" for accessibility
  665. # [22:29] <Hixie> hsivonen: i'd hope we'd see libraries implement <datagrid>, yes, just like i hope to see the same for WF2
  666. # [22:29] <othermaciej> for instance for government use
  667. # [22:29] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 104 (Connection reset by peer))
  668. # [22:30] * Joins: othermaciej (n=mjs@17.255.109.49)
  669. # [22:30] <othermaciej> and toolkit developers therefore want their toolkits to be able to enable compliance
  670. # [22:31] <Hixie> sure
  671. # [22:31] <othermaciej> and browser developers want JS library developers to like them
  672. # [22:31] <othermaciej> sorry about spotty connectivity
  673. # [22:31] <Hixie> sure
  674. # [22:31] <Hixie> but the point is that it's not aria that would drive library development
  675. # [22:31] <Hixie> it might be added on afterwards as an afterthought
  676. # [22:31] <othermaciej> that's basically what drives ARIA, the dependency chain of gov't contract requirements
  677. # [22:31] <Hixie> but that's wholly different
  678. # [22:31] <othermaciej> I don't think anyone would code ARIA-first, no
  679. # [22:32] <othermaciej> but toolkits like Dojo seem hot on adding it
  680. # [22:32] <Hixie> sure
  681. # [22:32] <Hixie> i'm just disagreeing with hsivonen's original statement
  682. # [22:32] * Joins: KevinMarks (n=KevinMar@nat/google/x-61d899179307427a)
  683. # [22:32] * Joins: jgraham (n=james@81-86-216-20.dsl.pipex.com)
  684. # [22:32] <hsivonen> what's a "pivot table"?
  685. # [22:33] <hsivonen> "Note: If the expanded property is provided, it applies only to the individual cell. It is not a proxy for the container row, which also can be expanded. The main use case for providing this property on a cell is pivot table type behavior."
  686. # [22:34] <hsivonen> oh. it's on wikipedia
  687. # [22:35] * Quits: andersca (n=andersca@nat/apple/x-41381a0e67f9759b) ("a")
  688. # [22:37] * Joins: andersca (n=andersca@nat/apple/x-86bc19534f8352dd)
  689. # [22:38] <jgraham> hsivonen: Sure I'll email about aria-level
  690. # [22:38] * Quits: KevinMarks (n=KevinMar@nat/google/x-61d899179307427a) ("The computer fell asleep")
  691. # [22:38] <hsivonen> jgraham: great
  692. # [22:42] * Quits: jruderman (n=jruderma@guest-225.mountainview.mozilla.com)
  693. # [22:42] * Joins: BenMillard (i=cerbera@cpc1-flee1-0-0-cust285.glfd.cable.ntl.com)
  694. # [22:43] * Joins: KevinMarks (n=KevinMar@nat/google/x-8862dbedf1161bc1)
  695. # [22:49] * Quits: phsiao (n=shawn@nat/ibm/x-a4e8bcd4b2fe2173)
  696. # [22:49] * Quits: eseidel (n=eseidel@nat/google/x-aa6c6bed7b4ed10e)
  697. # [22:50] <jgraham> Is aria using RFC 2119 terminology? Section 6.2 seems to be using it but it's not clear if the rest of the document is or not
  698. # [22:52] * Joins: jruderman (n=jruderma@guest-225.mountainview.mozilla.com)
  699. # [22:53] <hsivonen> jgraham: that would merit another comment :-)
  700. # [22:54] * Quits: csarven (i=csarven@on-irc.csarven.ca) ("http://www.csarven.ca")
  701. # [22:54] <jgraham> hsivonen: Yeah, I'm starting o accrue a stack of comments
  702. # [22:55] * Joins: zcorpan_ (n=zcorpan@c-cb21e353.1451-1-64736c12.cust.bredbandsbolaget.se)
  703. # [22:55] <jgraham> (reading the introduction to try and work out what terminology was being used reminded me of several minor issues I thought merited attention there)
  704. # [22:56] <jgraham> argh, pushed the send buton by mistake :(
  705. # [22:56] <Philip`> Press "undo" quickly
  706. # [22:57] <Hixie> so
  707. # [22:57] <Hixie> many
  708. # [22:57] <Hixie> e-mails
  709. # [22:58] <gsnedders> Hixie: mind if I send you a message, broken into one character per email?
  710. # [22:58] <Hixie> yes
  711. # [22:58] <Hixie> but these e-mails are long
  712. # [22:58] <Hixie> that's the real problem
  713. # [22:59] <gsnedders> "What is the most widely known language for authoring mathematics?" — Can I take a guess at LaTeX?
  714. # [22:59] <Hixie> no guesses
  715. # [23:00] <jgraham> gsnedders: In principle it could be MS-Word or ascii art of something
  716. # [23:01] * Joins: eseidel (n=eseidel@nat/google/x-0f25595987077e00)
  717. # [23:01] <jgraham> s/of/or/
  718. # [23:01] <hsivonen> the answer might depend on what kind of math
  719. # [23:01] <zcorpan_> pen/paper?
  720. # [23:01] <gsnedders> jgraham: Issue one: What is a language?
  721. # [23:01] <hsivonen> I expect Word to be used less and LaTeX more as the math gets more complex
  722. # [23:01] <gsnedders> We're lacking a good enough definition of what the question actually means to be able to answer it.
  723. # [23:01] <jgraham> I guess there's also a lot of math typeset in high end publishing programmes
  724. # [23:01] <zcorpan_> 42
  725. # [23:02] <gsnedders> I mean, is pen/paper well enough known? :P
  726. # [23:02] <jgraham> s/programmes/programs/
  727. # [23:02] <hsivonen> jgraham: does InDesign have a decent math typesetter?
  728. # [23:02] <gsnedders> zcorpan_: that's definitely the correct answer.
  729. # [23:02] * Hixie removed the word language from the wiki a few minutes ago
  730. # [23:02] <hsivonen> or is it all TeX and Frame?
  731. # [23:02] <zcorpan_> gsnedders: yeah. but what's the question? :)
  732. # [23:02] <hsivonen> what about Quark
  733. # [23:02] <gsnedders> zcorpan_: 6 times 9
  734. # [23:03] * hsivonen isn't sure what the "high end publishing programme" landscape looks like these days
  735. # [23:03] <jgraham> hsivonen: I dunno. All I know is that with Blackwells publishing all one's carefully typeset mathematics gets redone in some way
  736. # [23:03] <jgraham> (usually introducing errors in the process)
  737. # [23:03] <Hixie> Processing namespace e-mail... [## ] 10%
  738. # [23:03] <hsivonen> jgraham: do you mean you send in LaTeX and they do something else?
  739. # [23:04] * hsivonen though TeX was the high end when it comes to math typesetting
  740. # [23:04] <jgraham> hsivonen: Yep. Although I don't know what "something else" is
  741. # [23:04] <hsivonen> thought even
  742. # [23:04] <gsnedders> hsivonen: it is
  743. # [23:04] <jgraham> (the final thing still says 'this document was prepared from a manuscript typeset by the author' or somesuch)
  744. # [23:08] <BenMillard> jgraham said "gsnedders: In principle it could be MS-Word or ascii art of something" and that possibility is somewhat supported by me finding ASCII-art data tables for astronomy
  745. # [23:09] * gsnedders notes that's jgraham's subject
  746. # [23:11] <hsivonen> I'm tempted to take the ostrich approach to aria-owns
  747. # [23:14] * Joins: virtuelv_ (n=virtuelv@109.80-202-65.nextgentel.com)
  748. # [23:14] * Joins: othermaciej_ (n=mjs@nat/apple/x-2206649a4124a8f5)
  749. # [23:14] * jgraham notes that the common forms for expressing maths are undoubtedly different to those for authoring it
  750. # [23:14] <jgraham> on the web
  751. # [23:17] <Hixie> Processing namespace e-mail... [#### ] 20%
  752. # [23:17] * Hixie goes to get a drink
  753. # [23:19] * jgraham considers complaining that the aria spec expressing its conformance requirements in RDF makes it inaccessible to people who don't think that RDF is human-readable
  754. # [23:19] * Quits: sayrer (n=chatzill@66.37.169.174) (Read error: 113 (No route to host))
  755. # [23:22] <hsivonen> jgraham: I'm reading the tables. I'm not reading RDF.
  756. # [23:23] <hsivonen> I figured it wouldn't be cost-effective to try to generate stuff from the RDF
  757. # [23:24] <jgraham> hsivonen: I'm reading the tables too. But section 6.1 is clear that documents must conform to the RDF but doesn't seem to mention the tables
  758. # [23:25] <Philip`> As far as I've seen, computer science seems to be almost exclusively LaTeX, but areas like biology use Word a lot more, so you can draw very different conclusions depending on what subset of math-writers you look at
  759. # [23:26] <jgraham> Philip`: Undoubtedly there are far more biologists than physical+computer scientists but they probably generate fewer equations each, on average
  760. # [23:28] * Joins: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com)
  761. # [23:29] * Quits: othermaciej (n=mjs@17.255.109.49) (Read error: 110 (Connection timed out))
  762. # [23:32] * Quits: virtuelv_ (n=virtuelv@109.80-202-65.nextgentel.com) ("Ex-Chat")
  763. # [23:32] * Quits: virtuelv (n=virtuelv@109.80-202-65.nextgentel.com) (Read error: 110 (Connection timed out))
  764. # [23:32] * Quits: andersca (n=andersca@nat/apple/x-86bc19534f8352dd)
  765. # [23:40] * Joins: andersca (n=andersca@nat/apple/x-6b0de794f1c79dd0)
  766. # [23:42] * Quits: gsnedders (n=gsnedder@host86-138-199-53.range86-138.btcentralplus.com) ("Partying in teh intarwebs")
  767. # [23:44] * Quits: webben (n=benh@91.84.250.9) (Connection timed out)
  768. # [23:45] <annevk> Hixie, fwiw, using the wiki more would be great
  769. # [23:45] <annevk> (as you're doing now)
  770. # [23:46] <annevk> it seems that people are missing some kind of entry point to find arguments for and against certain ideas that have already been discussed and "resolved"; having that documented somewhere other than in piles of e-mail is nice :)
  771. # [23:50] * Joins: dglazkov (n=dglazkov@adsl-074-229-248-021.sip.bhm.bellsouth.net)
  772. # [23:53] * Parts: annevk (n=annevk@84.77.28.156)
  773. # [23:54] * Quits: met_ (n=Hassman@r5bx220.net.upc.cz) ("Chemists never die, they just stop reacting.")
  774. # Session Close: Tue Mar 25 00:00:00 2008

The end :)