/irc-logs / freenode / #whatwg / 2009-09-21 / end

Options:

  1. # Session Start: Mon Sep 21 00:00:00 2009
  2. # Session Ident: #whatwg
  3. # [00:02] * Quits: heycam` (n=cam@210-84-32-112.dyn.iinet.net.au) ("bye")
  4. # [00:02] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  5. # [00:02] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  6. # [00:03] * Quits: masinter (n=user@c-76-102-104-162.hsd1.ca.comcast.net) (Remote closed the connection)
  7. # [00:05] * Quits: mitnavn (n=mitnavn@unaffiliated/mitnavn) (Read error: 110 (Connection timed out))
  8. # [00:10] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  9. # [00:13] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  10. # [00:15] * Joins: da3dg (n=opera@h11n1fls34o986.telia.com)
  11. # [00:15] * Quits: Midler (n=midler@212.37.124.233) (Read error: 60 (Operation timed out))
  12. # [00:16] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  13. # [00:19] * Joins: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  14. # [00:25] * Quits: da3d (n=opera@h11n1fls34o986.telia.com) (Read error: 110 (Connection timed out))
  15. # [00:29] * Quits: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  16. # [00:31] * Quits: nessy (n=nessy@124-170-205-120.dyn.iinet.net.au) ("This computer has gone to sleep")
  17. # [00:32] * Joins: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net)
  18. # [00:33] * Joins: dglazkov (n=dglazkov@67.188.0.62)
  19. # [00:33] * Joins: nessy (n=nessy@124-170-205-120.dyn.iinet.net.au)
  20. # [00:35] * da3dg is now known as da3d
  21. # [00:36] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  22. # [00:40] * Quits: starjive (i=beos@213-66-216-93-no30.tbcn.telia.com)
  23. # [00:45] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  24. # [00:48] * Joins: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  25. # [00:57] * Quits: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  26. # [00:57] * Joins: masinter (n=user@c-76-102-104-162.hsd1.ca.comcast.net)
  27. # [00:57] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  28. # [00:58] * Joins: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  29. # [01:00] * Quits: ttepasse (n=ttepas--@p5B0161E2.dip.t-dialin.net) ("?Q")
  30. # [01:05] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  31. # [01:05] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  32. # [01:07] * masinter wonders, "is this thing on?"
  33. # [01:07] * gsnedders notes there is a certain randomness to how busy this channel is, but seems to be busiest when both Europe and America is awake
  34. # [01:08] <gsnedders> s/is/are/
  35. # [01:08] <masinter> midnight in CET?
  36. # [01:08] <gsnedders> midnight in BST at the moment
  37. # [01:08] <mitnavn_> It's 1AM here
  38. # [01:08] <mitnavn_> CET
  39. # [01:09] <gsnedders> mitnavn_: No, you're CEST :P
  40. # [01:09] <mitnavn_> True
  41. # [01:09] <mitnavn_> But is there anyone not switching?
  42. # [01:09] * gsnedders blatantly needs to get onto saner living hours
  43. # [01:09] <gsnedders> mitnavn_: In CET? No.
  44. # [01:11] * Quits: mitnavn_ (n=mitnavn@0x5552b452.adsl.cybercity.dk)
  45. # [01:12] * Joins: mitnavn (n=mitnavn@unaffiliated/mitnavn)
  46. # [01:13] <masinter> i had a long discussion with Maciej about error handling in IRI processing, but it's not in th elog
  47. # [01:13] <masinter> well and Hixie, wonder what might have happened.
  48. # [01:13] <gsnedders> krijnh keeps on dying
  49. # [01:14] <gsnedders> If you (or anyone else can) email a copy of logs to krijn, then he can add them
  50. # [01:16] <masinter> i wish i'd kept it, it was a good case and relevant to the IRI spec
  51. # [01:17] <annevk42> masinter, several people here keep private logs; they should be able to help krijnh fix the logs
  52. # [01:18] <masinter> all discussions are destined to be repeated anyway, aren't they?
  53. # [01:18] <annevk42> well, there's that too :)
  54. # [01:18] <masinter> i think the case was about why it was a good idea not to specify precisely how illegal IRIs should be handled
  55. # [01:18] <annevk42> anyway, you were right about Europe, I need to fetch some sleep :)
  56. # [01:18] <annevk42> nn
  57. # [01:19] <gsnedders> nighty
  58. # [01:19] * Joins: murr4y` (n=murray@85.84-49-67.nextgentel.com)
  59. # [01:21] <masinter> if you have an IRI http://XXXZ/ where Z isn't a valid input to the punycode conversion algorithm, that it was good to say that the result should not result in a valid domain name in a URI, but leave it open whether the processor might signal an error or otherwise replace the domain name with something that was guaranteed not to be valid
  60. # [01:21] <masinter> signalling an error may be preferable in cases where you are, for example, doing resolution, but there are legitimate applications which cannot signal errors
  61. # [01:22] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Read error: 110 (Connection timed out))
  62. # [01:23] <masinter> back later
  63. # [01:23] * Quits: masinter (n=user@c-76-102-104-162.hsd1.ca.comcast.net) (Remote closed the connection)
  64. # [01:24] * Quits: nessy (n=nessy@124-170-205-120.dyn.iinet.net.au) ("This computer has gone to sleep")
  65. # [01:31] * Quits: murr4y (n=murray@85.84-49-67.nextgentel.com) (Read error: 110 (Connection timed out))
  66. # [01:33] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  67. # [01:47] * Quits: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net) ("8403864 bytes have been tenured, next gc will be global.")
  68. # [01:51] * Quits: dglazkov (n=dglazkov@67.188.0.62)
  69. # [01:51] * Quits: wakaba (n=wakaba@221.157.197.113.dy.bbexcite.jp) (Read error: 104 (Connection reset by peer))
  70. # [01:52] * Joins: wakaba (n=wakaba@221.157.197.113.dy.bbexcite.jp)
  71. # [01:52] * Quits: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  72. # [01:55] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  73. # [01:59] * Joins: miketaylr (n=miketayl@user-0cdf5gs.cable.mindspring.com)
  74. # [02:00] * Joins: slightlyoff (n=slightly@72.14.229.81)
  75. # [02:06] * Joins: eric_carlson__ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  76. # [02:06] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  77. # [02:15] * Quits: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  78. # [02:17] * Joins: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  79. # [02:24] * Quits: eric_carlson__ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  80. # [02:29] * Quits: mitnavn (n=mitnavn@unaffiliated/mitnavn) (Read error: 110 (Connection timed out))
  81. # [02:31] * Joins: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  82. # [02:31] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  83. # [02:33] * Quits: da3d (n=opera@h11n1fls34o986.telia.com) (Read error: 60 (Operation timed out))
  84. # [02:40] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  85. # [02:42] * Joins: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  86. # [02:43] * Joins: wakaba_ (n=wakaba_@122x221x184x68.ap122.ftth.ucom.ne.jp)
  87. # [02:48] * Quits: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley) ("This computer has gone to sleep")
  88. # [02:49] * Joins: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  89. # [02:50] * Quits: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  90. # [02:59] * Quits: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  91. # [03:08] * Quits: franksalim (n=frank@adsl-75-61-85-210.dsl.pltn13.sbcglobal.net) ("Leaving")
  92. # [03:12] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  93. # [03:23] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  94. # [03:23] * eric_carlson_ is now known as eric_carlson
  95. # [03:25] * Joins: mitnavn (n=mitnavn@unaffiliated/mitnavn)
  96. # [03:40] * Joins: cohitre (n=cohitre@24.18.158.106)
  97. # [03:41] * Quits: cohitre (n=cohitre@24.18.158.106) (Client Quit)
  98. # [03:43] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  99. # [03:53] * Quits: gavin_ (n=gavin@firefox/developer/gavin) (Read error: 110 (Connection timed out))
  100. # [03:54] * Joins: gavin_ (n=gavin@firefox/developer/gavin)
  101. # [03:54] * Joins: eric_carlson__ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  102. # [03:54] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  103. # [03:54] * eric_carlson__ is now known as eric_carlson
  104. # [04:02] * Quits: mitnavn (n=mitnavn@unaffiliated/mitnavn)
  105. # [04:04] * Quits: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  106. # [04:04] * Joins: taf2 (n=taf2@216-15-54-105.c3-0.grg-ubr3.lnh-grg.md.cable.rcn.com)
  107. # [04:05] * Joins: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  108. # [04:08] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  109. # [04:11] <GPHemsley> annevk42: Are you aware that the "Changed attributes" section of html5-diff is not capitalized like the rest of the sections?
  110. # [04:13] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  111. # [04:18] * Joins: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net)
  112. # [04:24] * Quits: eric_carlson_ (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  113. # [04:27] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  114. # [04:28] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  115. # [04:28] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  116. # [04:36] * Quits: eric_carlson (n=ericc@adsl-67-112-12-110.dsl.anhm01.pacbell.net) (Read error: 110 (Connection timed out))
  117. # [04:39] * Joins: nessy (n=nessy@124-170-205-120.dyn.iinet.net.au)
  118. # [04:40] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  119. # [04:40] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  120. # [04:41] * weinig_ is now known as weinig
  121. # [04:41] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  122. # [04:41] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  123. # [04:42] * weinig_ is now known as weinig
  124. # [04:45] * Joins: roc_ (n=roc@203-97-204-82.dsl.clear.net.nz)
  125. # [04:52] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  126. # [04:55] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  127. # [04:59] * Quits: roc (n=roc@203-97-204-82.dsl.clear.net.nz) (Read error: 110 (Connection timed out))
  128. # [04:59] * roc_ is now known as roc
  129. # [05:00] * Quits: othree (n=othree@admin39.ct.ntust.edu.tw) ("leaving")
  130. # [05:02] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  131. # [05:14] * Joins: othree (n=othree@admin39.ct.ntust.edu.tw)
  132. # [05:20] * Joins: cohitre (n=cohitre@c-24-18-158-106.hsd1.wa.comcast.net)
  133. # [05:32] * Quits: taf2 (n=taf2@216-15-54-105.c3-0.grg-ubr3.lnh-grg.md.cable.rcn.com)
  134. # [05:48] * Quits: othree (n=othree@admin39.ct.ntust.edu.tw) ("leaving")
  135. # [05:49] * Joins: othree (n=othree@admin39.ct.ntust.edu.tw)
  136. # [05:58] * Quits: mpt (n=mpt@canonical/mpt) (Read error: 110 (Connection timed out))
  137. # [06:01] * Joins: heycam (n=cam@clm-laptop.infotech.monash.edu.au)
  138. # [06:02] * Quits: nessy (n=nessy@124-170-205-120.dyn.iinet.net.au) ("Leaving")
  139. # [06:04] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  140. # [06:04] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  141. # [06:05] * weinig_ is now known as weinig
  142. # [06:11] * Quits: slightlyoff (n=slightly@72.14.229.81)
  143. # [06:14] * Joins: nessy (n=nessy@124-170-205-120.dyn.iinet.net.au)
  144. # [06:16] * Quits: cohitre (n=cohitre@c-24-18-158-106.hsd1.wa.comcast.net)
  145. # [06:29] * Joins: yutak_home (n=kee@M006079.ppp.dion.ne.jp)
  146. # [06:29] * Quits: miketaylr (n=miketayl@user-0cdf5gs.cable.mindspring.com)
  147. # [06:31] * Joins: JoePeck (n=JoePeck@cpe-74-69-85-249.rochester.res.rr.com)
  148. # [06:40] * Joins: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu)
  149. # [06:42] * Joins: zdobersek (n=zan@92.37.70.175)
  150. # [06:57] * Joins: fishd__ (n=darin@67.180.164.209)
  151. # [06:58] * Joins: fishd_ (n=darin@72.14.224.1)
  152. # [07:00] * Quits: roc (n=roc@203-97-204-82.dsl.clear.net.nz)
  153. # [07:04] * Quits: fishd_ (n=darin@72.14.224.1) (Read error: 104 (Connection reset by peer))
  154. # [07:04] * Joins: fishd_ (n=darin@72.14.224.1)
  155. # [07:06] * Quits: fishd__ (n=darin@67.180.164.209) (Read error: 145 (Connection timed out))
  156. # [07:09] * Quits: gavin_ (n=gavin@firefox/developer/gavin) (Read error: 110 (Connection timed out))
  157. # [07:10] * Joins: gavin_ (n=gavin@firefox/developer/gavin)
  158. # [07:14] * Quits: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
  159. # [07:24] * Joins: masinter (n=user@c-76-102-104-162.hsd1.ca.comcast.net)
  160. # [07:31] <masinter> I'm trying to figure out about percent-encoding the query component of IRIs in browsers, and maybe it's late, but it seems there is no good normative advice to give if the percent-encoding is delayed until the query-IRI is interpreted
  161. # [07:32] <masinter> it would seem like asking browsers to percent-encode the form data using the document character set BEFORE the IRI (with query) is constructed would give more consistent results
  162. # [07:33] <masinter> at least in the case where the document character set isn't Unicode-based
  163. # [07:33] <masinter> browsers might have to change their behavior in constructing the IRI-with-query-added, but the results would be more consistent and fewer bugs, and it wouldn't affect interpretation of any existing web pages
  164. # [07:39] * Joins: zalan (n=zalan@catv-89-135-144-193.catv.broadband.hu)
  165. # [07:39] * Quits: yutak_home (n=kee@M006079.ppp.dion.ne.jp) ("Ex-Chat")
  166. # [07:53] * Joins: cohitre (n=cohitre@c-24-18-158-106.hsd1.wa.comcast.net)
  167. # [07:55] * Quits: zdobersek (n=zan@92.37.70.175) ("Leaving.")
  168. # [08:08] * Quits: fishd_ (n=darin@72.14.224.1) ("Leaving")
  169. # [08:08] * Joins: zcorpan_ (n=zcorpan@c83-252-193-59.bredband.comhem.se)
  170. # [08:12] * Quits: jacobolus (n=jacobolu@dhcp-0059871802-99-6d.client.student.harvard.edu) (Remote closed the connection)
  171. # [08:15] * Joins: zcorpan (n=zcorpan@c83-252-193-59.bredband.comhem.se)
  172. # [08:17] * Quits: zcorpan_ (n=zcorpan@c83-252-193-59.bredband.comhem.se) (Read error: 104 (Connection reset by peer))
  173. # [08:17] * Quits: cohitre (n=cohitre@c-24-18-158-106.hsd1.wa.comcast.net)
  174. # [08:25] <othermaciej> masinter: what particular change do you have in mind relative to what was in the Web Address draft?
  175. # [08:28] * Joins: krijn (n=krijnhoe@89.205.165.4)
  176. # [08:29] <othermaciej> masinter: %-encoding the query part of the (pseudo)-IRI has to use the document encoding no matter where it comes from originally - it could be a result of form submission, or it could be present literally on the page as an href attribute, or it could be presented to an API such as assigning location
  177. # [08:29] <othermaciej> masinter: so it has to happen at the time you resolve the address (or at the time you convert it to a URI, if that is immediately after)
  178. # [08:29] <othermaciej> masinter: this means the rules have to diverge from processing as an IRI, unless the document encoding is UTF-8
  179. # [08:33] * Quits: zcorpan (n=zcorpan@c83-252-193-59.bredband.comhem.se) (Read error: 110 (Connection timed out))
  180. # [08:38] * Quits: sebmarkbage (n=miranda@h-73-244.A146.priv.bahnhof.se) ("http://calyptus.eu/")
  181. # [08:41] <Hixie> othermaciej: did you ever end up sending those summaries of the telecons that you mentioned you were going to send?
  182. # [08:42] <othermaciej> Hixie: no, but I will start doing it this week
  183. # [08:43] <othermaciej> last time I chaired the telecon I had to get on a plane immediately after
  184. # [08:43] <othermaciej> I don't think anything important was overlooked though
  185. # [08:44] * Quits: heycam (n=cam@clm-laptop.infotech.monash.edu.au) ("bye")
  186. # [08:46] * Joins: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl)
  187. # [08:50] <Hixie> othermaciej: i couldn't tell from the last three meetings' minutes whether there was anything i needed to know about for the spec
  188. # [08:50] <Hixie> any new feedback, plans that would affect the spec, or whatever
  189. # [08:50] <othermaciej> Hixie: there was not
  190. # [08:51] <othermaciej> the topics involved checking on people's actions (which may someday have indirect influence on the spec), closing out tracker issues (which reduces the possibility of needing further changes), and creating task forces
  191. # [08:51] <othermaciej> in the most recent telecon we discussed the Origin header and I mentioned your plan to either replace it with Sec-From or remove it
  192. # [08:51] <othermaciej> (since the end of the month is closing in I'm assuming remove is more likely)
  193. # [08:53] * Parts: krijn (n=krijnhoe@89.205.165.4)
  194. # [08:54] <Hixie> k
  195. # [08:54] <Hixie> i wonder if i should create a some task forces to
  196. # [08:54] <Hixie> o
  197. # [08:56] <Hixie> maybe i should have a summary="" annihilation task force
  198. # [08:56] <othermaciej> if you feel that would be a valuable use of your time, be my guest
  199. # [08:57] <Hixie> we could have a t-shirts made, "improving accessibility by research instead of dogmatism" or something
  200. # [08:57] <Hixie> maybe something more pithy
  201. # [09:00] <hsivonen> wow. according to roc's blog, MS implemented an IE6 mode for their authoring tool without actually using IE6
  202. # [09:01] <hober> Hixie: i7g a11y b0y r6h i5d o0f d7m
  203. # [09:01] * Joins: jacobolus (n=jacobolu@dhcp-0033909844-bb-e7.client.student.harvard.edu)
  204. # [09:04] * Joins: pesla (n=retep@procurios.xs4all.nl)
  205. # [09:12] * Quits: jacobolus (n=jacobolu@dhcp-0033909844-bb-e7.client.student.harvard.edu) (Remote closed the connection)
  206. # [09:21] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  207. # [09:22] <jgraham> hsivonen: Yeah. I'm glad I wasn't an engineer who went in one morning to be told "we want you to reimplement IE6. Yes, from scratch. No, with all the same quirks"
  208. # [09:23] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  209. # [09:26] * Joins: masinter` (n=user@76.102.104.162)
  210. # [09:27] <masinter`> missed some context here
  211. # [09:28] <masinter`> %-encoding the query part only has to use the document encoding when the pseudo-IRI is formed in the first place, rather than forming an IRI first and then %-encoding the result when trying to convert the IRI to URI (or, rather, URI-components)
  212. # [09:29] * Joins: jacobolus (n=jacobolu@dhcp-0061179998-3f-d5.client.student.harvard.edu)
  213. # [09:29] <annevk42> note that any input to the URL parsing algorithm is most likely UTF-16 and almost definitely Unicode based
  214. # [09:30] <masinter`> not sure how that's relevant, but sure
  215. # [09:30] <annevk42> well, you mentioned earlier about percent-encoding according to the relevant character earlier; I'm just saying that's not what's happening now
  216. # [09:30] <masinter`> i didn't think it was what was happening now
  217. # [09:31] <annevk42> ah right, you suggested it could be changed?
  218. # [09:31] <masinter`> what's happening now is a mess, inconsistent, and fragile
  219. # [09:32] <annevk42> it's highly unlikely that what I described in my first sentence will change
  220. # [09:32] <masinter`> yes, to propose that normative correct behavior for constructing pseudo-IRIs based on form submission should do the percent-encoding at the time the pseudo-IRI is constructed
  221. # [09:33] <annevk42> but maybe I just don't understand what you're proposing since I'm not familiar with pseudo-IRIs and such
  222. # [09:33] <masinter`> in the special case of http URIs and when the document character encoding isn't UTF-8 or UTF-16
  223. # [09:33] <masinter`> well, say you have a form in a a page that is ISO-8859-1
  224. # [09:33] <GPHemsley> annevk42: Did you get my message earlier?
  225. # [09:33] <masinter`> and you click submit on the form, and some of the form data is typed in, not in ASCII
  226. # [09:34] <masinter`> and it constructs an IRI and then interprets the IRI
  227. # [09:34] <annevk42> GPHemsley, yes
  228. # [09:34] <GPHemsley> k
  229. # [09:34] <annevk42> GPHemsley, can't really fix it now, but will do hopefully later
  230. # [09:34] <masinter`> the form construction and IRI interpretation happens all during the uesr interaction
  231. # [09:34] <GPHemsley> annevk42: Sounds good
  232. # [09:34] <masinter`> the IRI may be available to scripting? I'm not sure
  233. # [09:35] <masinter`> pseudo-IRI constructed as a result of form processing
  234. # [09:35] <annevk42> not the URI, but the things the user has typed in will be
  235. # [09:35] <masinter`> huh?
  236. # [09:35] <annevk42> and what the user has typed in will be encoded as UTF-16 or some such typically
  237. # [09:35] * Joins: heycam (n=cam@210-84-32-112.dyn.iinet.net.au)
  238. # [09:35] <annevk42> masinter, what the user types in is exposed to script
  239. # [09:36] <masinter`> before the pseudo-IRI is constructed
  240. # [09:36] <annevk42> the URL is constructed at submission, so yes
  241. # [09:36] <masinter`> but at some point an IRI is constructed from the user input
  242. # [09:37] * Joins: fishd (n=darin@72.14.224.1)
  243. # [09:37] <masinter`> currently the IRI is constructed by using the unicode of the input directly
  244. # [09:37] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 110 (Connection timed out))
  245. # [09:38] <masinter`> and the burden is on the IRI interpretation to then percent-encode the result by remembering the document character set of the origin of the IRI
  246. # [09:38] <annevk42> well, it's an input to the resolving algorithm
  247. # [09:39] <masinter`> the IRI could be constructed by percent-encoding the form data in the query part, using the IRI's associated character encoding at the time of constructing the IRI
  248. # [09:40] <masinter`> this IRI is never stored because it's passed directly to IRI resolution
  249. # [09:40] <annevk42> if you can figure out the query part while not properly parsing the URL I suppose you can do that
  250. # [09:41] * Joins: zcorpan (n=zcorpan@pat.se.opera.com)
  251. # [09:42] * Quits: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley) ("This computer has gone to sleep")
  252. # [09:42] <masinter`> the query part is constructed, not 'figured out'
  253. # [09:42] <masinter`> if you mean 'parsed and interpreted' as figuring out
  254. # [09:44] * Quits: jacobolus (n=jacobolu@dhcp-0061179998-3f-d5.client.student.harvard.edu) (Remote closed the connection)
  255. # [09:45] <masinter`> i'll be back in the morning
  256. # [09:53] * Joins: fishd_ (n=darin@c-67-180-164-209.hsd1.ca.comcast.net)
  257. # [09:54] <masinter`> new version of iri 'fork' document for beating up http://larry.masinter.net/iribis-hack.html
  258. # [09:56] * Quits: GarethAdams_ (n=GarethAd@pdpc/supporter/active/GarethAdams)
  259. # [10:03] <Hixie> that doesn't seem to be anything like what webaddresses did, unless i'm missing something
  260. # [10:05] <Hixie> where's the definition of how to resolve a url given another url with, e.g. the encoding changing from utf-16 to utf-8, and the document base address having an effect, and backslashes being changed to slashes, etc?
  261. # [10:05] * Quits: fishd (n=darin@72.14.224.1) (Read error: 110 (Connection timed out))
  262. # [10:05] <Hixie> also missing seems to be the algorithm for parsing an arbitrary strings into components
  263. # [10:05] <Hixie> unless again i'm missing something
  264. # [10:05] * Quits: zalan (n=zalan@catv-89-135-144-193.catv.broadband.hu) (Read error: 110 (Connection timed out))
  265. # [10:05] <Hixie> also it seems to be contrary to the goals of the effort to have these rules be in a separate section... shouldn't they just be the rules that apply to all UAs?
  266. # [10:05] <Hixie> surely we don't want different UAs doing different things
  267. # [10:06] * Joins: webben (n=benh@nat/yahoo/x-ydpmeojjjaejrteg)
  268. # [10:10] * Joins: drunknbass (n=drunknba@cpe-76-173-187-247.socal.res.rr.com)
  269. # [10:10] <Hixie> it also seems to lack a definition of "absolute url" that works for invalid iris
  270. # [10:11] * Joins: jacobolus (n=jacobolu@140.247.142.153)
  271. # [10:12] <masinter`> i think you're missing something
  272. # [10:13] <masinter`> the backslash question is listed as an issue
  273. # [10:13] <Philip`> Is there an online version of HTML5 that defines the details of what the document base URL is?
  274. # [10:13] <masinter`> the goal of this document is not to provide a line-for-line replacement for the webaddress document
  275. # [10:13] <Hixie> oh
  276. # [10:14] <Hixie> that could be a problem
  277. # [10:14] <masinter`> it's to fix IRIs so that HTML can make a normative reference to it
  278. # [10:14] <Hixie> since that's what i'm looking for :-)
  279. # [10:14] * Joins: webben_ (n=benh@nat/yahoo/x-txbemgmxvapsovvt)
  280. # [10:14] <Hixie> well whatever happens i need the following:
  281. # [10:15] <masinter`> the goal is to allow a definition of IRI that doesn't need overriding or a willful violation
  282. # [10:15] * Philip` finds it in http://www.w3.org/TR/2009/WD-html5-20090423/
  283. # [10:16] * Quits: webben (n=benh@nat/yahoo/x-ydpmeojjjaejrteg) (Client Quit)
  284. # [10:16] <masinter`> and to get IDNA and the IRI folks to agree to the changes necessary
  285. # [10:16] * Quits: webben_ (n=benh@nat/yahoo/x-txbemgmxvapsovvt) (Client Quit)
  286. # [10:16] <masinter`> so IDNA needs to bless it, as well as Martin and Roy
  287. # [10:16] <Hixie> * a definition of a valid IRI that handles encodings other than UTF-8 (e.g. saying that in non-UTF-8 contexts, the query needs to not be non-ASCII)
  288. # [10:16] * Joins: webben (n=benh@217.12.14.241)
  289. # [10:16] <masinter`> IRIs aren't defined in terms of encodings
  290. # [10:16] * Quits: fishd_ (n=darin@c-67-180-164-209.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  291. # [10:16] <masinter`> an IRI is a sequence of characters, not of octets
  292. # [10:16] <Hixie> * a definition of absolute IRI that handles having invalid strings be absolute, e.g. http://www.example.com/%X being an "absolute IRI"
  293. # [10:16] <masinter`> single percent was added to the IRI bnf
  294. # [10:17] <masinter`> and whether something is absolute or relative should be determined by whether there's a scheme
  295. # [10:17] <masinter`> but whether something is a 'valid IRI' will be narrower than what browsers do
  296. # [10:17] <Hixie> * an algorithm that defines how to take an arbitrary string (including one that isn't a valid IRI of any form) and get out the scheme, host, port, hostport, path, query, fragment, and host-specific (as those were defined in [WEBADDRESSES])
  297. # [10:18] <masinter`> the algorithm for getting out those parts are in the document
  298. # [10:18] <masinter`> section 3.2
  299. # [10:18] <Hixie> * an algorithm that takes an arbitrary string, an encoding, and an absolute IRI (as defined above) and returns an absolute IRI
  300. # [10:19] <masinter`> the specification of a protocol element can be done by providing syntax and processing rules without using an algorithm
  301. # [10:19] <Hixie> * the algorithm to get the document Web base address, again as in [WEBADDRESSES]
  302. # [10:19] <Hixie> ...and where all these algorithms are such that the browser vendors are willing to implement them exactly, with no deviations whatsoever
  303. # [10:19] <masinter`> the document web base address is a feature of the language in which the IRI is embedded and the method of retrieving it, not a feature of the IRI itself
  304. # [10:20] <masinter`> I know more than this document is needed
  305. # [10:21] <masinter`> but getting at least the terminology and direction is a prerequisite to not having IRIs in web browsers work differently or be spec'd differently than IRIs in email, voice over IP, instant messaging, newsfeeds, and all of the other standards that need IRIs
  306. # [10:21] <Hixie> what is section 7 for then?
  307. # [10:22] <masinter`> you don't think section 7 is useful?
  308. # [10:22] <masinter`> what part of section 7 do you object to?
  309. # [10:22] <masinter`> section 1.3 contains terms that refer to section 7
  310. # [10:22] <Hixie> well it seems like if the goal is to just make IRIs work properly and interoperably, section 7 would presumably not need to exist
  311. # [10:22] <hsivonen> masinter`: speaking of section 7, section 7 of the current IRI RFC is marked as informative but uses "should". That's confusing.
  312. # [10:23] <masinter`> hmm, lots of documents have a section 7, but why should section 7 of the current IRI RFC have anything to do with section 7 of this rewrite of Martin's internet draft?
  313. # [10:23] * masinter` wonders if the HTML5 document has a section 7
  314. # [10:24] <masinter`> the document contains an extensive writeup of the goals
  315. # [10:24] <masinter`> section 12 lists the goals
  316. # [10:25] * Parts: annevk2 (n=annevk@83.85.115.44)
  317. # [10:25] <masinter`> Maciej had some comments on the goals as I originally posted them, which I tried to incorporate or address
  318. # [10:26] <Hixie> i don't really understand section 3.2. What parts of it are normative? I don't see any RFC2119 terms, and it's not clear to me what "parse" means in this context
  319. # [10:26] * Joins: tndH (n=Rob@cpc2-leed18-0-0-cust427.leed.cable.ntl.com)
  320. # [10:26] <Hixie> parse how?
  321. # [10:27] <Hixie> does it mean "try to match the string against the abnf"? if so, against which production?
  322. # [10:27] <Hixie> surely the parsing of a URI shouldn't be based on scheme-specific rules? that would mean that the same URL would parse different based on whether the UA knew the scheme or not
  323. # [10:29] <Hixie> as a general comment, this is a difficult draft to follow. It's not clear for example where the HTML5 spec should hook in and how to follow from that entry point (wherever it is) to the nitty gritty with the "must" requirements for actually parsing something
  324. # [10:29] <masinter`> i need to patch in more of RFC 3986
  325. # [10:29] <masinter`> the major surgery was to move from "map IRI to URI and then parse according to RFC 3986 using greedy parsing" to "parse first, then map if you need to"
  326. # [10:30] <masinter`> but i need to pull in more of the RFC 3986 definition of what normative parsing is
  327. # [10:30] <masinter`> good catch
  328. # [10:31] <masinter`> the document with through lots of revisions with lots of comments from lots of groups, i agree it's hard to follow
  329. # [10:31] <masinter`> i did more surgery than martin is comfortable with, and wound up rewriting or rewording big chunks for clarity, but it needs a lot more
  330. # [10:32] <hsivonen> masinter`: I'm just whining about the standing IRI RFC.
  331. # [10:32] <masinter`> and i agree that hooking this into the HTML5 spec is some work, but frankly, even though this document has problems, some of the difficulty is certainly due to the structure of the HTML5 spec
  332. # [10:33] <hsivonen> masinter`: "section 7" together with "IRI" reminded me
  333. # [10:33] <masinter`> i only worked on the first 9 versions of it, and Martin and Michel did the other 10 versions, so i blame them for all of the RFC's problems
  334. # [10:34] <hsivonen> masinter`: I hope the bug of using "should" in an informative section gets fixed in bis (I haven't checked if it has been fixed already)
  335. # [10:34] <masinter`> Martin and Michel did the first 5 versions of this document and I'm only on my second pass
  336. # [10:34] <masinter`> i think i got that one, but i'm sure there are tons of problems left
  337. # [10:35] <masinter`> this isn't going to get out of IETF until IDNA gets agreement on it
  338. # [10:35] <Hixie> masinter`: if there's anything i can do to make hooking html5 into it easier, let me know
  339. # [10:36] <masinter`> we probably should sort out the requirements and see if there's agreement on "what belongs in IRI/URI and what belongs in HTML"
  340. # [10:36] * Quits: annevk42 (n=annevk@5355732C.cable.casema.nl)
  341. # [10:36] <masinter`> and see if we can get Fielding & Duerst & Klensin to go along
  342. # [10:37] <masinter`> and Vint said he would help with the IDNA coordination
  343. # [10:38] <masinter`> we probably need to update mailto: also
  344. # [10:38] <masinter`> and there might be changes needed to http URI
  345. # [10:38] * Joins: mat_t (n=mattomas@91.189.88.12)
  346. # [10:38] <masinter`> isn't it common for browsers to have an option to send uTF8 paths?
  347. # [10:39] <masinter`> the previous method of converting from IRI to URI generically, parsing, and then selectively converting back to IRI basically is broken, it is likely information-lossy in some important cases
  348. # [10:40] * Joins: roc (n=roc@121-72-162-140.dsl.telstraclear.net)
  349. # [10:40] <masinter`> so this draft at least turns IRI handling into something resembling what browsers do which is to parse first
  350. # [10:44] <masinter`> hsivonen: people try to be sticklers about MUST, MAY, SHOULD, but the notion of separating "Normative" from "Informative" isn't always followed in IETF documents, so reviewers might not notice it as much
  351. # [10:45] <masinter`> For me, the main thing is to make sure that you can really identify what it means to "implement" a "feature" and link that to normative requirements
  352. # [10:45] <masinter`> so that "interoperable implementations of every feature" means something
  353. # [10:45] <masinter`> http://larry.masinter.net/draft-ietf-newtrk-interop-reports-00.html
  354. # [10:48] <masinter`> Peter Saint-Andre actually tried to do that for XMPP (Jabber), http://xmpp.org/internet-drafts/draft-saintandre-xmpp-interop-report-00.html
  355. # [10:48] * Joins: mpt (n=mpt@canonical/mpt)
  356. # [10:48] <masinter`> it would be interesting to look at HTML and think about what the "protocol feature set" would look like, and which of the normative requirements have anything to do with anything that could be tested.
  357. # [10:50] * Joins: Phae (n=phaeness@gateb.mh.bbc.co.uk)
  358. # [10:50] * Joins: ROBOd (n=robod@89.122.216.38)
  359. # [10:52] * masinter` needs to sleep, will check back later
  360. # [10:52] * Quits: masinter` (n=user@76.102.104.162) ("ERC Version 5.2 (IRC client for Emacs)")
  361. # [10:52] * Philip` likes being able to link feature tests to normative requirements
  362. # [10:53] <Philip`> http://philip.html5.org/tests/canvas/suite/tests/results.html tries to do that and is mostly successful
  363. # [11:02] <AryehGregor> Broken link: http://wiki.whatwg.org/wiki/FAQ#When_will_we_be_able_to_start_using_these_new_features.3F
  364. # [11:03] <AryehGregor> Hmm.
  365. # [11:03] <AryehGregor> Is it?
  366. # [11:03] <AryehGregor> Yeah . . .
  367. # [11:04] <Philip`> "namespace deceleration attributes" - quick, don't let those speeding namespaces get away!
  368. # [11:04] <AryehGregor> Ah, there we go: http://wiki.whatwg.org/index.php?title=FAQ&diff=4024&oldid=3992
  369. # [11:08] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  370. # [11:17] * Quits: garbeam_ (n=arg@garbe.us) (Read error: 104 (Connection reset by peer))
  371. # [11:17] * Joins: adactio (n=adactio@host86-138-101-27.range86-138.btcentralplus.com)
  372. # [11:31] * Joins: EruditeHermit (n=EH3@unaffiliated/eruditehermit)
  373. # [11:31] <EruditeHermit> hi
  374. # [11:32] <EruditeHermit> can anyone help me with the video tag?
  375. # [11:32] <EruditeHermit> when I try to do width and height by %, It leaves a huge gap between the video and the controls
  376. # [11:32] <EruditeHermit> and it also leaves a huge gap between the above element and the video
  377. # [11:32] <AryehGregor> What exact code are you using, in which browser?
  378. # [11:32] <EruditeHermit> firefox
  379. # [11:33] <EruditeHermit> 3.5
  380. # [11:34] * Quits: Lachy (n=Lachlan@85.196.122.246) ("This computer has gone to sleep")
  381. # [11:34] <EruditeHermit> http://pastebin.com/m6eb15836
  382. # [11:36] <AryehGregor> The width and height attributes don't accept percentage values, AFAICT. They're pixel values. http://www.whatwg.org/specs/web-apps/current-work/multipage/the-map-element.html#attr-dim-width
  383. # [11:37] <AryehGregor> Also, the align attribute doesn't work on <video>.
  384. # [11:37] <AryehGregor> You need to use CSS.
  385. # [11:37] <AryehGregor> Do percentage widths and heights even work on <img>?
  386. # [11:37] <EruditeHermit> if I do style="width height align etc does it work?
  387. # [11:37] <EruditeHermit> I get the same problem using css height and width in percentages
  388. # [11:38] * Joins: mat_t (n=mattomas@91.189.88.12)
  389. # [11:39] <AryehGregor> Can you get the desired sizing with <img> or any other HTML element, or is this really specific to <video>?
  390. # [11:39] <EruditeHermit> I can get the desired sizing with div
  391. # [11:39] <EruditeHermit> let me try img
  392. # [11:40] <EruditeHermit> yeah img works fine
  393. # [11:41] <AryehGregor> I'm not sure of the answer offhand, sorry. Maybe someone else will be able to answer.
  394. # [11:41] <mookid> you know
  395. # [11:41] <mookid> this still realy pisses me off
  396. # [11:42] <mookid> [13:31] <Hixie> yes but HTTP conneg, as previously discussed, is a bad idea
  397. # [11:42] <mookid> and that was almost a year ago
  398. # [11:42] <Philip`> That should have been plenty of time to calm down and accept the notion
  399. # [11:43] <mookid> it's a bullshit notion made by an ignorant fool
  400. # [11:43] <mookid> so no.
  401. # [11:43] <mookid> :)
  402. # [11:44] <Philip`> EruditeHermit: Is the desire for it to be 70% of the screen size?
  403. # [11:45] <EruditeHermit> yes
  404. # [11:45] <EruditeHermit> well 70% of the size of the container div
  405. # [11:46] <EruditeHermit> but that it will fit on a screen is my goal
  406. # [11:46] <EruditeHermit> so I want to use %
  407. # [11:47] * Joins: Lachy (n=Lachlan@pat-tdc.opera.com)
  408. # [11:48] <Philip`> EruditeHermit: Hmm, I'm not sure how CSS sizing is meant to interact with <video width height>
  409. # [11:48] <Philip`> I'd expect the CSS to be the same as for div/img/etc, but I have no idea how it'd be rendered
  410. # [11:49] <EruditeHermit> I don't want to specify pixel height and width because screens are so different these days
  411. # [11:52] * Quits: mpt (n=mpt@canonical/mpt) (Read error: 104 (Connection reset by peer))
  412. # [11:52] * Joins: mpt_ (n=mpt@canonical/mpt)
  413. # [11:53] <AryehGregor> EruditeHermit, <video style="width: 70%; height: 70%"> doesn't work?
  414. # [11:53] <EruditeHermit> it makes it smaller yes
  415. # [11:53] <EruditeHermit> but it leaves a huge gap between the element above and the video
  416. # [11:53] <EruditeHermit> and also if you have controls
  417. # [11:53] <EruditeHermit> there is a huge gap between the controls and the bottom of the video
  418. # [11:54] * Joins: cmrn` (n=cmrn@ppp59-167-55-21.lns1.cbr1.internode.on.net)
  419. # [11:55] <mookid> ok hold on a second
  420. # [11:56] <mookid> Philip`: where does "URL decomposition IDL attributes" come from?
  421. # [11:57] <Philip`> mookid: Why should I know that?
  422. # [11:58] <Philip`> mookid: Anyway, I'd suggest trying http://whatwg.org/html5#url-decomposition-idl-attributes
  423. # [11:58] <mookid> no idea, sorry - trying to work out where a URL was decided to have a 'query' component
  424. # [11:59] <Philip`> (Definitions and headings get ids that are lowercased hyphenated strings, so they're usually easy to find that way)
  425. # [11:59] <AryehGregor> EruditeHermit, do you have a publicly-accessible page to look at, maybe?
  426. # [11:59] <AryehGregor> (although I have to go in a few minutes)
  427. # [11:59] <AryehGregor> I can't tell what's wrong from looking at the markup.
  428. # [12:01] <EruditeHermit> hmm
  429. # [12:02] <EruditeHermit> not sure I can do that in a few minutes
  430. # [12:02] <EruditeHermit> let me try though
  431. # [12:03] <AryehGregor> Maybe someone else can help when I leave.
  432. # [12:03] <AryehGregor> Good luck, anyway.
  433. # [12:03] <EruditeHermit> thanks
  434. # [12:03] <EruditeHermit> maybe i'll catch you tomorrow or something
  435. # [12:03] <EruditeHermit> how long before you leave?
  436. # [12:04] <mookid> Philip`: thanks I found the RFC I was looking for
  437. # [12:04] <AryehGregor> Um, I should be leaving now, actually.
  438. # [12:04] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  439. # [12:04] <EruditeHermit> ok
  440. # [12:05] <EruditeHermit> AryehGregor, thanks for helpingme
  441. # [12:08] * Quits: cmrn` (n=cmrn@ppp59-167-55-21.lns1.cbr1.internode.on.net) ("Leaving...")
  442. # [12:08] * Quits: benward (n=benward@98.210.154.133)
  443. # [12:14] * Parts: mookid (i=mookid@ROFL.name)
  444. # [12:19] * Joins: krijn (i=8d5d2075@gateway/web/freenode/x-cyevubqrszxbqpmt)
  445. # [12:19] * Joins: NetBen (n=chatzill@213.208.242.186)
  446. # [12:23] <krijn> http://www.quirksmode.org/blog/archives/2009/09/the_html5_drag.html
  447. # [12:24] <pesla> </rant>
  448. # [12:25] * Hixie commented already
  449. # [12:26] * Joins: matijsb (n=matijsb@hotfusion.demon.nl)
  450. # [12:30] <Philip`> He seems to have a peculiarly strong reaction to the need to write two lines of code to disable some events
  451. # [12:31] <NetBen> and he's right..
  452. # [12:32] <Hixie> yeah it is a pretty horrible api
  453. # [12:32] <Hixie> but i'm sure none of the people arguing in favour of decentralised extensibility will learn the same lesson from this as i did...
  454. # [12:33] <NetBen> name calling here and there is a bit... meh tho
  455. # [12:35] * Quits: othree (n=othree@admin39.ct.ntust.edu.tw) (Read error: 110 (Connection timed out))
  456. # [12:40] <Lachy> if you ignore the unnecessary swearing and insults, he does appear to make some valid points about it.
  457. # [12:41] <Lachy> it's a shame there's not much we can do about it without breaking compat
  458. # [12:41] <jgraham> If only praise for _not_ doing work was always this forthcoming
  459. # [12:42] * Joins: Midler (n=midler@212.37.124.233)
  460. # [12:42] <Lachy> jgraham, that praise won't last long if Opera decides to implement the API soon
  461. # [12:43] <Lachy> but I'm not sure how essential it is. I'm not aware of any sites that actually use it. Though, I assume there must be some, given that Firefox and Safari were motivated to implement it.
  462. # [12:50] <jgraham> Lachy: I wasn't being quite serious :)
  463. # [12:50] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  464. # [12:51] <jgraham> If no sites actually use it, why do we need IE compatibility?
  465. # [12:51] <jgraham> Are we assuming that they don't want to implement two D&D APIs?
  466. # [12:51] <jgraham> Has anyone asked them to copnfirm this?
  467. # [12:51] <jgraham> *confirm
  468. # [12:52] <krijn> Why not use something like Scriptaculous or jQuery UI as a baseline?
  469. # [12:54] * Joins: da3d (n=opera@h11n1fls34o986.telia.com)
  470. # [12:54] <jgraham> krijn: Those APIs aren't obviously very DOM-like are they?
  471. # [12:54] <krijn> Why not?
  472. # [12:55] <zcorpan> if ie crashes when you try to use the api, it seems like it would degrade better in ie if it was a new incompatible api
  473. # [12:56] <krijn> Something like http://jqueryui.com/demos/draggable/, natively, would be awesome
  474. # [12:57] <NetBen> well as it currently is, people will use js frameworks for D&D, compat is not an issue
  475. # [12:57] <krijn> Agreed
  476. # [12:58] <krijn> So it's probably something for JS libs to implement
  477. # [12:58] <krijn> Why don't they use the native APIs in browsers that support it?
  478. # [12:58] <krijn> JohnResig? :)
  479. # [12:58] <jgraham> krijn: For example the DOM is typically event based rather than callback based
  480. # [12:59] <jgraham> Even though callback-based stuff is arguably a better fit for ecmascript
  481. # [12:59] <NetBen> ah, we need to differentiate between api and the way it's implemented
  482. # [12:59] <krijn> jgraham: UI is event based as well
  483. # [12:59] <krijn> (Mostly)
  484. # [12:59] <krijn> (Or I don't get your point :)
  485. # [13:01] <jgraham> krijn: I was just looking at the example element.draggable({"start":callback})
  486. # [13:01] <jgraham> which seems nice but not very DOM-like
  487. # [13:01] <krijn> Then create an ondragstart thingy for that
  488. # [13:01] <NetBen> addEventListener("dragstart", callback)
  489. # [13:02] <jgraham> krijn: Right, at which point you no longer have the jQuery-ui API
  490. # [13:02] <krijn> (Although there is already one like that ;)
  491. # [13:02] <jgraham> I agree that if we were to redesign this it would be good to take inspiration from js libaries and ensure that the'r functionaility could be replicated using the native api
  492. # [13:03] <NetBen> the troubs with the API is how the events work (or dont work) and some events being redundant, methods isn't really the issue I believe
  493. # [13:03] <jgraham> *their
  494. # [13:03] <Philip`> So you'd want to copy the concepts from JS libraries, but not the syntax?
  495. # [13:04] <NetBen> exactly
  496. # [13:04] <NetBen> and not really the concepts either actually, just the derived logic on how people actually use drag and drop
  497. # [13:05] <krijn> Yeah, JS libs can build wrappers/syntaxes around it
  498. # [13:05] <NetBen> instead of something that got obviously lost in outdated specs written in a time when bad practises where common and no one really had a clue on web
  499. # [13:05] <NetBen> standards
  500. # [13:05] <NetBen> I assume
  501. # [13:07] <jgraham> The IE API was never a standard. It was reverse engineered for HTML5 at a time when it was asssumed that IE would not put significant effort into HTML5 support
  502. # [13:07] <NetBen> so the spec is reverse enginered from IE specs?
  503. # [13:07] <NetBen> for compatibility?
  504. # [13:07] <jgraham> From IE behaviour
  505. # [13:08] <jgraham> for IE6 compatibility
  506. # [13:08] <jgraham> Which is still an argument in favour of the current spec but maybe a weaker one than it was in 2004
  507. # [13:09] * Joins: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  508. # [13:09] <Philip`> Presumably there should still be a spec that says something compatible with existing content
  509. # [13:09] <krijn> Perhaps we need data about how much this API is used on the web? :)
  510. # [13:09] <NetBen> ok, chances of this spec actually being used in RL is?
  511. # [13:10] <Philip`> (though it might say nothing, if there's no existing content worth worrying about)
  512. # [13:10] <jgraham> Oh everyone else just said that
  513. # [13:10] <NetBen> =P
  514. # [13:10] <NetBen> WhatWG != WhatWH
  515. # [13:10] <NetBen> hopefully =P
  516. # [13:12] <Lachy> NetBen, what does "WhatWH" stand for?
  517. # [13:12] <NetBen> What we have
  518. # [13:12] <Lachy> oh
  519. # [13:12] <Philip`> Millions of people use stuff like <body ondragstart="return false"> it seems
  520. # [13:13] <jgraham> Philip`: Is that to stop people "stealing" content?
  521. # [13:13] <Philip`> Not sure how many rely on it for important behaviour
  522. # [13:13] <NetBen> and it can stay that way np
  523. # [13:13] <Philip`> <body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" oncontextmenu="return false" ondragstart="return false" onselectstart ="return false" onselect="document.selection.empty()" oncopy="document.selection.empty()" onbeforecopy="return false" onmouseup="document.selection.empty()">
  524. # [13:14] <Philip`> jgraham: Looks like it might be, in most cases
  525. # [13:14] <krijn> I use that all the time
  526. # [13:14] <krijn> Clients want me to!
  527. # [13:14] <krijn> :)
  528. # [13:14] <NetBen> just say no...
  529. # [13:14] <Philip`> (That was from a .gov.cn site)
  530. # [13:16] <Philip`> krijn: I guess showing the clients how trivial it is to disable scripting in one's browser and freely copy text would just result in them telling you to turn all the text into images
  531. # [13:16] <krijn> (I wasn't serious, btw)
  532. # [13:18] <Philip`> Good, but clearly there's other people who want to prevent copying and other people who implement it :-(
  533. # [13:18] <NetBen> sounds like a good salespitch to sell pdf's
  534. # [13:19] <Philip`> What if they know about Acrobat's text selection tool?
  535. # [13:20] <Philip`> Hmm, I suppose PDFs probably support some flag to disable text selection
  536. # [13:20] <NetBen> basicly, you cant protect content
  537. # [13:20] <NetBen> then you have image to text translators
  538. # [13:20] <gsnedders> Make your content a huge CAPTCHA!
  539. # [13:21] <Philip`> so: What if they know about KPDF's "Obey DRM limitations" checkbox in its option dialog box?
  540. # [13:21] <NetBen> captcha has been broken already...
  541. # [13:21] <krijn> They should use WG telcons to spread their information!
  542. # [13:21] <Lachy> Philip`, that sounds like a preference that every use would obviously choose to leave enabled! :-)
  543. # [13:21] <Philip`> gsnedders: That would be excellent
  544. # [13:22] <Philip`> Lachy: I expect most will, since it's enabled by default and it very rarely prevents users doing what they want
  545. # [13:22] <Philip`> so they have no reason to change it
  546. # [13:23] <Philip`> I think I only ever found one PDF where it was an issue
  547. # [13:23] <Lachy> is that because most PDFs don't bother with DRM?
  548. # [13:23] <Philip`> Yeah
  549. # [13:23] <Philip`> or at least most PDFs that I ever look at
  550. # [13:23] * jgraham tries email the list about the D^D API
  551. # [13:23] <jgraham> D&D, even
  552. # [13:24] <jgraham> silly swedish keyboard
  553. # [13:27] * Joins: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  554. # [13:30] <Mrmil> Hi all, I have to ask, which one is more correct? <kbd>Alt</kbd> + <kbd>Shift</kbd> + <kbd>1</kbd> _or_ <kbd>Alt + Shift + 1</kbd> _or_ <kbd>Alt Shift 1</kbd>?
  555. # [13:36] <Philip`> Mrmil: The third seems wrong to me because the page should display the '+' characters to make it clear the keys are all pressed together
  556. # [13:37] <Philip`> The second seems wrong to me because it's ambiguous whether the + is meant to be a key just like all the others
  557. # [13:38] <Philip`> so if you had e.g. an Alt plus '+' key combination, the markup and presentation wouldn't distinguish them at all
  558. # [13:38] <Philip`> so the first seems more correct
  559. # [13:38] * Parts: EruditeHermit (n=EH3@unaffiliated/eruditehermit) ("Ex-Chat")
  560. # [13:38] <Philip`> The HTML5 spec suggests <kbd><kbd>Alt</kbd> + ...</kbd> which seems more correcter since the whole thing is still marked up as keyboard input
  561. # [13:39] <Philip`> and then you can style the individual keys differently
  562. # [13:39] <Mrmil> I'm looking at it, looks probably like the most correct of all I mentioned above.
  563. # [13:42] <Mrmil> Who/what can actually use this information?
  564. # [13:42] * Joins: mat_t (n=mattomas@91.189.88.12)
  565. # [13:43] <Philip`> CSS can style it in a visually distinctive way
  566. # [13:45] <Mrmil> Hm, thought there would be a better use for that...
  567. # [13:46] <Philip`> (Hmm, I vaguely remember seeing an example which used nested <kbd>s to draw little keyboard-like grey rectangles around keys, but I can't find it anywhere now...)
  568. # [13:47] <Mrmil> Well I do that, so now I'll have to change my styles because I'll have nested kbd's = nested rectangles :)
  569. # [13:49] <Philip`> Mrmil: The information conveyed by inline semantic elements seems to be very rarely used for anything other than styling, and <kbd> is of extremely limited relevance compared to most other elements so I wouldn't expect anyone to bother doing anything interesting with it
  570. # [13:50] <Mrmil> I see, thanks for feedback :)
  571. # [13:50] <Philip`> (It's only in HTML5 because some people use it (for the styling effect) and it's not actively harmful so there's no point getting rid of it, rather than because it's actually a valuable feature)
  572. # [13:50] <zcorpan> Mrmil: Alt+Shift+1 is correct
  573. # [13:52] <Mrmil> Philip`: Definitelly shorter than <span class="key">Alt</span>...
  574. # [13:52] <Philip`> Mrmil: But longer than <tt>Alt</tt>, and longer than Alt
  575. # [13:53] <Mrmil> :)
  576. # [13:53] <Philip`> Oh, HTML5 doesn't allow <tt> :-(
  577. # [13:53] <Philip`> Not much shorter than <code>Alt</code> then, if you want that default rendering
  578. # [14:01] * Joins: othree (n=othree@admin39.ct.ntust.edu.tw)
  579. # [14:05] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  580. # [14:07] * Quits: svl (n=me@ip565744a7.direct-adsl.nl) ("And back he spurred like a madman, shrieking a curse to the sky.")
  581. # [14:09] <Mrmil> The HTML5 spec is so much better than XHTML 1.0 spec. (For a find-some-usage-info-about-this-tag person.)
  582. # [14:09] * Joins: pmuellr (n=pmuellr@129.33.49.251)
  583. # [14:12] * Joins: svl (n=me@ip565744a7.direct-adsl.nl)
  584. # [14:14] <Lachy> Mrmil, that's because the XHTML1 spec is just a delta spec. All the element definitions remained as is in HTML4
  585. # [14:14] * Joins: mat_t (n=mattomas@91.189.88.12)
  586. # [14:15] <Mrmil> Lachy: Hm. :)
  587. # [14:19] * mpt_ is now known as mpt
  588. # [14:21] <Mrmil> They could at least show something like this http://www.w3.org/TR/xhtml11/doctype.html#s_doctype. If they did, though, it is burried somewhere where no-one can find it...
  589. # [14:21] * jgraham notices he splet Philip's name wrong
  590. # [14:22] * jgraham apologises
  591. # [14:30] * Parts: Mrmil (n=ut_ollie@host-77-236-204-8.blue4.cz)
  592. # [14:30] * Quits: roc (n=roc@121-72-162-140.dsl.telstraclear.net)
  593. # [14:44] * Joins: GPHemsley (n=GPHemsle@pdpc/supporter/student/GPHemsley)
  594. # [14:46] * Joins: mitnavn (n=mitnavn@unaffiliated/mitnavn)
  595. # [15:00] * Joins: maikmerten (n=maikmert@BAE2731.bae.pppool.de)
  596. # [15:05] * Joins: zdobersek (n=zan@cpe-92-37-65-68.dynamic.amis.net)
  597. # [15:07] * Joins: aroben (n=aroben@unaffiliated/aroben)
  598. # [15:07] <Philip`> jgraham: Oh, I didn't notice
  599. # [15:09] * Joins: miketaylr (n=mtaylor@38.117.156.163)
  600. # [15:20] * Joins: fishd_ (n=darin@c-67-180-164-209.hsd1.ca.comcast.net)
  601. # [15:22] * Quits: annodomini (n=lambda@wikipedia/lambda)
  602. # [15:22] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  603. # [15:36] * Joins: erlehmann (n=erlehman@80.187.109.85)
  604. # [15:42] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 104 (Connection reset by peer))
  605. # [15:47] * Quits: jacobolus (n=jacobolu@140.247.142.153) ("Leaving...")
  606. # [15:52] * Quits: fishd_ (n=darin@c-67-180-164-209.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  607. # [16:01] * Parts: Midler (n=midler@212.37.124.233) ("Leaving.")
  608. # [16:02] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  609. # [16:06] * Joins: ttepasse (n=ttepas--@p5B0149DA.dip.t-dialin.net)
  610. # [16:10] * Joins: annevk2 (n=annevk@pat-tdc.opera.com)
  611. # [18:14] * Disconnected
  612. # [18:15] * Attempting to rejoin channel #whatwg
  613. # [18:15] * Rejoined channel #whatwg
  614. # [18:15] * Topic is 'WHATWG (HTML5) -- http://www.whatwg.org/ -- Logs: http://krijnhoetmer.nl/irc-logs/ -- Please leave your sense of logic at the door, thanks!'
  615. # [18:15] * Set by annevk3 on Wed Sep 09 23:23:54
  616. # [18:17] * Quits: JoePeck (n=JoePeck@cpe-74-69-85-249.rochester.res.rr.com)
  617. # [18:18] * Quits: webben (n=benh@217.12.14.241) (Read error: 145 (Connection timed out))
  618. # [18:20] <hsivonen> grr. defer scripts effectively make eof like </script> only more complex
  619. # [18:20] * Joins: da3d (n=opera@h11n1fls34o986.telia.com)
  620. # [18:24] * Quits: mpt (n=mpt@canonical/mpt) (Read error: 104 (Connection reset by peer))
  621. # [18:25] * Joins: mpt (n=mpt@canonical/mpt)
  622. # [18:26] * Joins: ap (n=ap@17.246.19.174)
  623. # [18:27] * Quits: othermaciej (n=mjs@c-69-181-42-237.hsd1.ca.comcast.net)
  624. # [18:30] * hsivonen wonders why IE8 on Windows 7 Enterprise claims to be "Media Center" and "Tablet"
  625. # [18:30] * hsivonen also wonders what OfficeLivePatch is
  626. # [18:36] * Joins: clownabuser (n=brucel@92-236-144-120.cable.ubr10.smal.blueyonder.co.uk)
  627. # [18:36] * Quits: NetBen (n=chatzill@213.208.242.186) ("ChatZilla 0.9.85 [Firefox 3.0.14/2009082707]")
  628. # [18:36] * Joins: mlpug (n=mlpug@a88-115-164-40.elisa-laajakaista.fi)
  629. # [18:37] * clownabuser is now known as brucel
  630. # [18:37] <brucel> Hi crazy WHATWG types
  631. # [18:37] <gsnedders> brucel: How are you in the freezing west?
  632. # [18:38] * gsnedders realizes he had misremembered
  633. # [18:38] * Quits: Phae (n=phaeness@gateb.mh.bbc.co.uk)
  634. # [18:39] <brucel> Am still west of sweden, gsnedders.
  635. # [18:40] <gsnedders> brucel: But I'm not in Sweden :P
  636. # [18:40] <brucel> So, Dear Cabal: I got emailed a request for html5 doctor for a simple guide to the new content types now block-level, inline are gone and we have a whole host of others.
  637. # [18:41] <brucel> Is there a simple guide to what they are and what they mean anywhere?
  638. # [18:41] <gsnedders> flow is basically the same as it was in HTML 4.01 Trans, i.e., block or inline
  639. # [18:43] <gsnedders> phrasing content is basically inline
  640. # [18:44] * gsnedders realizes he sucks at really explaining this…
  641. # [18:44] * Quits: da3d (n=opera@h11n1fls34o986.telia.com) (Read error: 110 (Connection timed out))
  642. # [18:45] * Joins: da3d (n=opera@h11n1fls34o986.telia.com)
  643. # [18:45] * Joins: ttepass- (n=ttepas--@p5B0161DB.dip.t-dialin.net)
  644. # [18:48] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  645. # [18:50] * Joins: dave_levin (n=dave_lev@74.125.59.65)
  646. # [18:52] * Quits: erlehmann (n=erlehman@tmo-109-85.customers.d1-online.com) (Read error: 54 (Connection reset by peer))
  647. # [18:53] * Joins: erlehmann (n=erlehman@tmo-109-85.customers.d1-online.com)
  648. # [18:53] <brucel> gsnedders I tried to explain it. and reaslied i suck at explaining it
  649. # [18:54] * Joins: tantek (n=tantek@70.36.139.108)
  650. # [18:56] * Joins: maikmerten_ (n=maikmert@Zb307.z.pppool.de)
  651. # [19:06] * Quits: ttepasse (n=ttepas--@p5B0149DA.dip.t-dialin.net) (Read error: 110 (Connection timed out))
  652. # [19:07] * Joins: zdobersek (n=zan@92.37.79.128)
  653. # [19:11] * Quits: maikmerten (n=maikmert@BAE2731.bae.pppool.de) (Read error: 110 (Connection timed out))
  654. # [19:16] * Parts: adactio (n=adactio@host86-138-101-27.range86-138.btcentralplus.com)
  655. # [19:23] * Quits: erlehmann (n=erlehman@tmo-109-85.customers.d1-online.com) (Read error: 104 (Connection reset by peer))
  656. # [19:24] * Joins: fearphage (n=fearphag@cogjam.com)
  657. # [19:25] * Joins: jwalden (n=waldo@c-98-248-40-206.hsd1.ca.comcast.net)
  658. # [19:26] * Quits: Darxus (n=darxus@panic.chaosreigns.com) (Remote closed the connection)
  659. # [19:30] * Parts: brucel (n=brucel@92-236-144-120.cable.ubr10.smal.blueyonder.co.uk)
  660. # [19:31] * Quits: zdobersek (n=zan@92.37.79.128) (Remote closed the connection)
  661. # [19:32] * Joins: benward (n=benward@nat/yahoo/x-nhfzvaihzrmguogz)
  662. # [19:33] * Joins: gunderwonder (n=gunderwo@172.80-202-84.nextgentel.com)
  663. # [19:36] * Joins: dbaron (n=dbaron@nat/mozilla/x-ohqupwwzhsbbckwd)
  664. # [19:36] * Quits: gunderwonder (n=gunderwo@172.80-202-84.nextgentel.com) (Client Quit)
  665. # [19:36] * Joins: gunderwonder (n=gunderwo@172.80-202-84.nextgentel.com)
  666. # [19:42] * Joins: weinig (n=weinig@17.246.16.129)
  667. # [19:43] * Quits: fearphage (n=fearphag@xbmc/user/fearphage) (verne.freenode.net irc.freenode.net)
  668. # [19:58] * Joins: masinter` (n=user@76.102.104.162)
  669. # [19:58] * Quits: masinter` (n=user@76.102.104.162) (Client Quit)
  670. # [19:59] * Joins: masinter` (n=user@76.102.104.162)
  671. # [20:00] * Joins: zdobersek (n=zan@cpe-92-37-79-128.dynamic.amis.net)
  672. # [20:01] * masinter` missed discussion about copy protection
  673. # [20:02] * Quits: masinter (n=user@c-76-102-104-162.hsd1.ca.comcast.net) ("ERC Version 5.2 (IRC client for Emacs)")
  674. # [20:04] * Joins: slightlyoff (n=slightly@nat/google/x-gqdafjgyolfbggqv)
  675. # [20:09] * Joins: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  676. # [20:09] * Joins: taf2 (n=taf2@38.99.201.242)
  677. # [20:09] * masinter` is now known as masinter
  678. # [20:11] * Quits: Dashiva (i=Dashiva@wikia/Dashiva)
  679. # [20:13] * Joins: Dashiva (i=Dashiva@wikia/Dashiva)
  680. # [20:14] * Joins: webben (n=benh@82.152.36.121)
  681. # [20:14] * Quits: mat_t (n=mattomas@91.189.88.12) ("This computer has gone to sleep")
  682. # [20:21] * aroben is now known as aroben|lunch
  683. # [20:37] * ap is now known as ap|away
  684. # [20:54] <masinter> I don't understand how Rowat links the complexity of the spec to difficulties for authors
  685. # [20:54] <masinter> the weakness of authoring conformance requirements makes it hard to figure out what really is or isn't a good idea
  686. # [20:55] <masinter> and there aren't guidelines for how to be compatible with deployed browsers as well as new ones
  687. # [20:55] <masinter> but those guidelines can be written, although most technical language specifications for a 'new version' of something often contain such guidelines directly
  688. # [20:56] <masinter> the main problem is that a complex spec adds an enormous burden for implementors, especially for consumers of HTML; producers can just ignore the parts they don't care about
  689. # [20:57] <masinter> talking about this on the mailing list isn't too effective -- mailing list is just filled with posturing
  690. # [20:57] <Hixie> hsivonen: wait, didn't we make it so document.write() always blows away the document in defer=""ed scripts?
  691. # [20:58] * Quits: mpt (n=mpt@canonical/mpt) (Read error: 148 (No route to host))
  692. # [21:00] * Joins: virtuelv (n=virtuelv@125.175.251.212.customer.cdi.no)
  693. # [21:00] * Joins: othermaciej (n=mjs@nat/apple/x-tikjfvebsdsktstf)
  694. # [21:02] <hsivonen> Hixie: didn't you agree to change that per sicking's feedback?
  695. # [21:02] * hsivonen doesn't remember
  696. # [21:04] <gsnedders> masinter: It's hard to simplify the implementer stuff without hurting web compat., as far as I can tell, though.
  697. # [21:06] * Joins: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com)
  698. # [21:06] <Hixie> hsivonen: we ended up changing something simpler, namely that defer="" doesn't apply to inline scripts
  699. # [21:07] <hsivonen> Hixie: oh ok.
  700. # [21:07] * aroben|lunch is now known as aroben
  701. # [21:07] * Joins: Darxus (n=darxus@64.71.152.40)
  702. # [21:07] <Hixie> same lovely compatibility goodness, and half the transfats
  703. # [21:07] <masinter> i think we've gone around this several times, including two days ago, but i'll try once more. "web compat." is a stalking horse for a lot of things that are unrelated
  704. # [21:07] <gsnedders> (Also, I find CSS 2.1 much harder to understand what the expected rendering is.)
  705. # [21:08] <gsnedders> masinter: Well it's mainly a question of _how_ you simplify it
  706. # [21:08] <masinter> there's compatibility with existing content, with the main dominant browser (IE), with other existing browsers, with existing creation tools, with existing analysis tools, with search engines
  707. # [21:09] <Hixie> masinter: hsivonen and i mean the same thing by it, so it's ok :-)
  708. # [21:09] <masinter> and with what current browser development teams are willing to agree to implement.
  709. # [21:09] <masinter> hmmm
  710. # [21:10] * masinter tries to remember if tweedledee and tweedledum are humpty-dumpty twins
  711. # [21:10] <gsnedders> masinter: with existing content is more or less the same as with the main dominant browser, and existing creation tools mainly have existing content
  712. # [21:10] <masinter> no, existing content *could* work with many different implementations
  713. # [21:11] <gsnedders> It could. But how much existing content does not work with the dominant browser? How much relies upon specific behaviour that only exists in the dominant browser?
  714. # [21:11] <masinter> you have a narrow interpretation of "work with" which is taken as "works exactly the same as", which may not be the same as "the author and the reader have a satisfactory communication experience"
  715. # [21:12] <masinter> which leads you to a narrow interpretation of "specific behavior"
  716. # [21:12] <masinter> Maciej had an interesting discussion about error behavior for IRIs when they contain, for example, illegal characters
  717. # [21:13] <gsnedders> Where do you draw the line between the two, though?
  718. # [21:13] <masinter> "two"?
  719. # [21:13] <tantek> masinter - perhaps you could add an entry about "What does 'web compat' mean?" to the WHATWG FAQ: http://wiki.whatwg.org/wiki/FAQ documenting the issues/ambiguities in the expression.
  720. # [21:13] <tantek> (that you've expressed)
  721. # [21:13] <gsnedders> "work exactly the same as" and "the author and the reader have a satisfactory communication experience"
  722. # [21:13] * masinter tries to find something there is two of
  723. # [21:14] <masinter> I wrote about what I thought "interoperability" should mean in http://tools.ietf.org/html/draft-ietf-newtrk-interop-reports-00
  724. # [21:14] <gsnedders> I wouldn't say we had to create an identical DOM as IE, but I wouldn't say we could come up with a DOM that made deployed scripts (that currently work in UAs with only tree-shaped DOMs) not work any more, for example
  725. # [21:15] * Joins: ttepasse (n=ttepas--@p5B015B39.dip.t-dialin.net)
  726. # [21:15] <masinter> it's especially risky when you rely on black-box reverse engineering rather than open-box examination, because it's easy to infer the wrong generalization of behavior
  727. # [21:16] <masinter> for example, whether query strings are encoded using the document charset or using UTF8, the answer was different for mailto:
  728. # [21:16] <gsnedders> We can't do anything else but that for the dominant UA, and when sites rely upon behaviour only present there, what choice do we have?
  729. # [21:17] <hsivonen> masinter: you can open-box examine Gecko and WebKit
  730. # [21:17] <gsnedders> I agree it's suboptimal, but this is the world we're in.
  731. # [21:17] <masinter> when was the last time you tried actually asking MS what IE does, rather than relying on reverse engineering of what IE does?
  732. # [21:18] <masinter> and why do people say "the dominant browser" rather than IE, like IE was some dirty word?
  733. # [21:18] <hsivonen> masinter: maybe we should ask MS more often
  734. # [21:18] * masinter dares to speak the name of "Internet Explorer", shaking down the building
  735. # [21:19] <hsivonen> masinter: in my experience about mode sniffing, though, one shouldn't just trust MSDN for instance, but one should always test the hypothesis, too
  736. # [21:19] <gsnedders> It's something that has been done in the past, and more or less there's either been no response or, "I'm asking for permission to publish that…" and then nothing more ever coming out
  737. # [21:19] * masinter thinks asking Paul Cotton for specific help getting answers to specific technical questions about what IE does would go a long way
  738. # [21:19] <gsnedders> masinter: I was just using it because you had earlier, and because the statements are generally true (and saying IE would limit them to a specific subset of time, not that that is really a problem though).
  739. # [21:21] * Joins: dglazkov_ (n=dglazkov@nat/google/x-objgfpxkwcatdzla)
  740. # [21:21] <masinter> the question on the IRI issue is whether translating an IRI with an illegal character in the domain name should be specified as signalling an error, translating to pct-encoded bytes which would be illegal when later translated to punycode, to some otherwise illegal host name, or whether it was OK to leave it unspecified
  741. # [21:22] <masinter> and the issue is that signalling an error is the safest -- and most appropriate if you're doing resolution -- but that some implementations and processes can't really accept an error signal, so there needs to be alternatives which are also conforming
  742. # [21:23] <othermaciej> Paul Cotton does not know much about IE, and has very clearly stated as much
  743. # [21:23] <masinter> uh, i didn't think he would answer directly
  744. # [21:23] * Quits: webben (n=benh@82.152.36.121) (Read error: 110 (Connection timed out))
  745. # [21:23] <othermaciej> he does, however, work at the same company as the IE people, so may be better positioned to ask them
  746. # [21:23] <othermaciej> though I would think asking Adrian Bateman might skip a step
  747. # [21:23] <masinter> quite likely
  748. # [21:24] <masinter> i didn't suggest asking paul for answers, if you actually read what I said, Maciej
  749. # [21:24] <othermaciej> Microsoft is often either unwilling or unable to correctly describe how IE works
  750. # [21:24] * gsnedders notes we're still waiting for a copy of the stylesheet IE8 uses for quotations marks in various languages in q that has been pending approval for release since last TPAC, and Chris tried to push to get it released several times
  751. # [21:25] * masinter bows to authority on the subject of what Microsoft is or isn't unwilling to answer
  752. # [21:25] <othermaciej> s/is often/has often been/
  753. # [21:25] <masinter> clearly you're all experts on this subject, I confess I've never asked
  754. # [21:25] <masinter> I do know that it's easier to get answers to questions than it is to get anyone to release any software
  755. # [21:26] <gsnedders> masinter: I'd be up for asking them a lot more… if there was much chance at all at getting a response.
  756. # [21:26] * masinter repeats, "masinter thinks asking Paul Cotton for specific help getting answers to specific technical questions about what IE does would go a long way"
  757. # [21:26] <masinter> note I didn't say "asking Paul Cotton for answers"
  758. # [21:26] <othermaciej> Microsoft is more engaged in the HTML WG now so it may be more fruitful to ask them questions about their implementation
  759. # [21:27] <masinter> that was my point, thanks
  760. # [21:27] <gsnedders> My point is that past experience makes me still very dubious
  761. # [21:27] <masinter> standards only work when the implementations that need to follow the standard are actually working on the standard
  762. # [21:28] <masinter> otherwise you're playing a game of "we're standard and you're not nyah nyah nyah"
  763. # [21:29] <masinter> which may be fun and satisfying and vindictive, but doesn't actually help make stuff work
  764. # [21:29] * Quits: dglazkov (n=dglazkov@216.239.45.4) (Read error: 145 (Connection timed out))
  765. # [21:29] * dglazkov_ is now known as dglazkov
  766. # [21:31] <masinter> Hixie: Vint suggested a phone conference on the IRI issue and coordination, could you help set that up?
  767. # [21:33] <masinter> It would be great to get Vint, Klensin, Fielding, Martin, you, me, maybe MNot; not sure who else would be a core group. The goal would be to see if there's a way of fast-tracking agreement. Some folks who might be reluctant to join a meeting might do so if Vint asks them nicely.
  768. # [21:35] <masinter> Maciej, hope that addresses your process questions on IRI progress?
  769. # [21:36] * Quits: ttepass- (n=ttepas--@p5B0161DB.dip.t-dialin.net) (Read error: 110 (Connection timed out))
  770. # [21:36] <masinter> maybe getting someone from MS IRI implementation team might be a good addition? not sure
  771. # [21:36] <masinter> Michel was their guy but he's not at MS any more, don't hear from him much
  772. # [21:36] * tantek points out Hixie's post on telecons. http://lists.w3.org/Archives/Public/public-html/2009Jun/0616.html
  773. # [21:37] <masinter> that's "weekly telecons"
  774. # [21:37] * gsnedders also points out Hixie does not own a phone
  775. # [21:37] <masinter> i'm sure Vint would let him use his phone
  776. # [21:38] <masinter> brb
  777. # [21:38] <tantek> masinter - the *subject* says weekly telecons, but his message addresses "Teleconference calls" and "Teleconferences" in general.
  778. # [21:38] * Quits: tantek (n=tantek@70.36.139.108)
  779. # [21:43] <masinter> this is getting silly. [10:35] <Hixie> masinter`: if there's anything i can do to make hooking html5 into it easier, let me know
  780. # [21:44] <masinter> getting stuff into an IETF document that some IETF participants don't think belongs in the IETF document is the bottleneck
  781. # [21:44] <masinter> and a meeting about requirements and processes was Vint's suggestion for how to unblock the bottleneck, and I agree that normally that would be a good first step
  782. # [21:45] <masinter> and the participants are around the world, the next time for a possible physical meeting would be IETF in Hiroshima in November, the week after the TPAC
  783. # [21:45] <masinter> i've tried to reserve time at the IETF meeting for a "BOF" to discuss it, but making progress on this before November would be much better
  784. # [21:46] * Quits: maikmerten_ (n=maikmert@Zb307.z.pppool.de) (Remote closed the connection)
  785. # [21:47] <masinter> a phone conference with at least one person with some authority from the concerned parties does seem to me to be a good idea
  786. # [21:47] <masinter>
  787. # [21:48] <masinter> "anything i can do" should cover somehow finding a telphone and participating in a 1-2 hour phone conference
  788. # [21:51] <masinter> at most, maybe less
  789. # [21:53] <hober> what does getting people on the phone get you that publically-archived email doesn't (besides the ability to say things off the record)
  790. # [21:53] <hober> I mean, why not just email the people you're talking about getting on the phone
  791. # [21:54] * Joins: mpilgrim2 (n=mark@32.170.121.253)
  792. # [21:54] * Quits: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com) (Nick collision from services.)
  793. # [21:54] * Joins: cying (n=cying@70.90.171.153)
  794. # [21:54] <Philip`> Lower latency?
  795. # [21:54] * mpilgrim2 is now known as mpilgrim
  796. # [21:55] * Parts: zdobersek (n=zan@cpe-92-37-79-128.dynamic.amis.net)
  797. # [21:55] * Joins: [1]mpilgrim (n=mark@96.10.240.189)
  798. # [21:55] <masinter> well, for example, I just made some comments about the phone meeting, about error handling in IRIs, and a couple of other topics, and gotten just silence. On a phone conference, I oculd ask "Well, how about it?" and expect people to answer. Here, who knows? and in email, people can just repeat their stock positions and stonewall an actual discussion
  799. # [21:56] * Joins: Steve^ (n=steve@92.40.247.106.sub.mbb.three.co.uk)
  800. # [21:57] <masinter> that can happen in a phone conference too, of course, but it's more obvious when it's happening
  801. # [21:57] <mpilgrim> yes, standards are much easier when a few good men get together and work out their differences over beers
  802. # [21:57] <hober> beer++
  803. # [21:57] <masinter> funny
  804. # [21:57] <mpilgrim> how dare we give the uninvited hoi polloi a chance to respond
  805. # [21:58] <masinter> oh exactly, the hoi polloi should definitely have a meeting
  806. # [21:58] <jgraham> masinter: IRC is only occasionally sychronous
  807. # [21:58] <mpilgrim> we're all aware of your opinion about the openness of the htmlwg
  808. # [21:58] <masinter> oh really? gosh
  809. # [21:58] <masinter> are you now?
  810. # [21:59] <mpilgrim> well I am
  811. # [21:59] * masinter listens, then
  812. # [21:59] <mpilgrim> as is anyone else who bothers to read ac-forum
  813. # [22:00] <jgraham> secret mailing lists ftw
  814. # [22:00] <Steve^> secret-secret mailing lists even better
  815. # [22:01] <masinter> sigh, definitely private meetings should be outlawed, and private conversations too
  816. # [22:01] <Steve^> masinter, do you want a camera in my bathroom also?
  817. # [22:01] * Quits: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 104 (Connection reset by peer))
  818. # [22:02] * masinter laughs
  819. # [22:02] <masinter> i cant tell if you're trying to be funny, maybe i shouldn't assume you aren't if you don't use :) ?
  820. # [22:02] <masinter> honestly, if you want my opinion about something, you really can just ask me
  821. # [22:02] <Steve^> I wasn't sure if you referred only to whatwg or life in general
  822. # [22:02] <mpilgrim> your love of false dichotomies and other logical fallacies might go a long way towards explaining why you can't seem to find constructive conversation in any medium
  823. # [22:03] <masinter> could you give me an example of a 'false dichotomy'?
  824. # [22:03] <masinter> or a 'logical fallacy'? other than something that you just disagree with?
  825. # [22:03] <mpilgrim> read your own backscroll
  826. # [22:03] <masinter> aww, c'mon, i just asked for an exmaple
  827. # [22:03] <mpilgrim> look in a mirror
  828. # [22:03] <masinter> if you're going to insult me, at least back it up
  829. # [22:04] <masinter> aww, that really hurts, are you going to call me ugly now too?
  830. # [22:04] <jgraham> "private meetings should be outlawed and private conversations too"
  831. # [22:04] <masinter> hey i was joking
  832. # [22:04] <mpilgrim> "sigh, private meeting should be outlawed"
  833. # [22:04] <masinter> yes, that was reducio ad absurdum
  834. # [22:05] <masinter> I suppose I really do need to be more careful among the literal-minded
  835. # [22:05] * Joins: webben (n=benh@dip5-fw.corp.ird.yahoo.com)
  836. # [22:05] <masinter> "yes, standards are much easier when a few good men get together and work out their differences over beers"
  837. # [22:05] <jgraham> Hmm, I don't think it has anything to do with being literal minded; it's just not a compelling argument
  838. # [22:05] <masinter> i was going to object that you left out women and vodka
  839. # [22:06] * Joins: julianreschke (n=chatzill@p508FD4E2.dip.t-dialin.net)
  840. # [22:06] <jgraham> "private mailing lists are bad" "yeah why don't we outlaw private meetings"
  841. # [22:06] <masinter> and cigars, I suppose, but the smoke-filled rooms aren't legal any more in most parts of the world
  842. # [22:06] <mpilgrim> when I came in, you were complaining that no one had responded to your questions for all of 10 minutes
  843. # [22:06] * julianreschke can't resist joining a chat that is about Hixie joining a telco
  844. # [22:07] <mpilgrim> and said that wouldn't happen if you held a teleconf
  845. # [22:07] <Steve^> julianreschke, how did you know?
  846. # [22:07] * Joins: fishd__ (n=darin@nat/google/x-gqpieqwiyzntaljl)
  847. # [22:07] <mpilgrim> and then listed 6 men whom you deemed worthy to join said teleconf
  848. # [22:07] <masinter> I wasn't complaining, i was answering a question about why phone meetings were effective
  849. # [22:07] <mpilgrim> they're not
  850. # [22:07] * Joins: cying_ (n=cying@70.90.171.153)
  851. # [22:08] <masinter> and that wasn't my proposal. my proposal was to have a BOF at the next IETF meeting
  852. # [22:08] * julianreschke sometimes looks at chat logs while test cases are running slowly
  853. # [22:08] <masinter> Vint Cerf replied to my call for a BOF, and *he* suggested a phone conference
  854. # [22:08] <Steve^> psst julianreschke, what's a BOF?
  855. # [22:08] <mpilgrim> but you can't see why, because you think you've produced an exhaustive list of everyone with worthwhile oponions, and invited them
  856. # [22:08] <mpilgrim> just like you want to do with the entire htmlwg
  857. # [22:09] <julianreschke> Steve, I think "birds of a feather" meeting
  858. # [22:09] <julianreschke> Steve, something you set up in order to get a WG
  859. # [22:09] <masinter> http://trac.tools.ietf.org/bof/trac/wiki
  860. # [22:09] <masinter> IRIs: Status: received preliminary request from Larry Masinter. Some deep-reaching issues around the IRI architecture would seem to require a WG to be able to decide on possibly major changes. Agenda: in progress, Draft: in progress, Mailing list: uri@w3.org, public-iri@w3.org, Responsible AD: Alexey Melnikov
  861. # [22:10] <julianreschke> http://www.ietf.org/tao.html#anchor34
  862. # [22:11] <masinter> so i'm in favor of open discussion on an open mailing list in the ietf open process. but Vint suggested a phone call to see if things could be fast-tracked, and Maciej was concerned about schedule and process and how to get this done before last call, and so a phone call among the editors of the documents that need to be coordinated and the chairs of their working groups seemed like it was effective
  863. # [22:11] <masinter> the six people I mentioned were either editors or chairs
  864. # [22:11] <masinter> so it wasn't a random list. i did select, among all the editors and chairs, a smaller set of those who seemed to be active and 'up' on the issues
  865. # [22:12] <masinter> and yes, a meeting of the editors of documents that need to be coordinated about how to go about coordination is more effective than inviting discussion on an open list
  866. # [22:12] <masinter> and mpilgrim's sarcastic comments about this were really juvenile and out of line
  867. # [22:13] <julianreschke> in particular when trying to make progress asynchronously hasn't been quite successful
  868. # [22:13] <masinter> especially when the agenda for the meeting isn't about the substantive content so much as the method for organizing coordination
  869. # [22:14] <masinter> it's useful to be public about the meeting and the participation to make sure that someone who really needs to be there isn't left out, though
  870. # [22:15] <masinter> brb, lunch, snark away
  871. # [22:15] <mpilgrim> your comments on the secret ac-forum mailing list about the htmlwg being a "failed experiment" were juvenile and out of line, but of course they were secret so you get to play good cop in public
  872. # [22:16] * Quits: julianreschke (n=chatzill@p508FD4E2.dip.t-dialin.net) ("ChatZilla 0.9.85 [Firefox 3.5.3/20090824101458]")
  873. # [22:21] * Quits: webben (n=benh@dip5-fw.corp.ird.yahoo.com) (Read error: 104 (Connection reset by peer))
  874. # [22:21] * Joins: dpranke (n=Adium@nat/google/x-ayhejjdvrlbciggf)
  875. # [22:22] * Joins: webben (n=benh@82.152.36.121)
  876. # [22:23] * Quits: cying (n=cying@70.90.171.153) (Connection timed out)
  877. # [22:23] * cying_ is now known as cying
  878. # [22:24] * Quits: fishd_ (n=darin@nat/google/x-qhsheyqpcgppacxb) (Read error: 110 (Connection timed out))
  879. # [22:26] * Quits: mpilgrim (n=mark@32.170.121.253) (Remote closed the connection)
  880. # [22:26] * [1]mpilgrim is now known as mpilgrim
  881. # [22:28] <othermaciej> masinter: fwiw, if a phone call helps progress, then I think it is a fine move; and it makes me think that maybe it is remotely possible for a document to be ready in time for HTML WG Last Call
  882. # [22:29] <othermaciej> masinter: however, it does not tell me what should happen if, despite best efforts, such a document is not ready in time, so it doesn't answer my questions
  883. # [22:29] <masinter> i'm not sure what the set of fallbacks should be
  884. # [22:30] <masinter> the last resort is to put stuff back into the HTML document and mark it as "should be replaced but going to last call with this"
  885. # [22:31] <masinter> i don't know how tentative last call documents can be, but i suppose if the working group agrees that it's ok, then that would be a last-resort fallback
  886. # [22:31] <othermaciej> that would be acceptable to me as a last resort; not sure if the rest of the HTML WG would agree, but I hope so
  887. # [22:31] <othermaciej> obviously, having at least an Internet-Draft to reference that contains the needed info would be much preferred
  888. # [22:31] <masinter> well, it would have to be clear that other routes to progress were unavoidably blocked
  889. # [22:32] * Quits: weinig (n=weinig@17.246.16.129)
  890. # [22:32] * Quits: cying (n=cying@70.90.171.153)
  891. # [22:32] * Quits: mlpug (n=mlpug@a88-115-164-40.elisa-laajakaista.fi) (Remote closed the connection)
  892. # [22:32] <masinter> i think it's getting closer, but there are still gaps to a citable document
  893. # [22:32] * Joins: weinig (n=weinig@17.246.16.129)
  894. # [22:33] <masinter> the 'issue' isn't just the technical content, it was also the process and conformance requirements
  895. # [22:33] <masinter> there wouldn't be an 'issue' at all if there weren't other standards that people want to work the same in HTML
  896. # [22:34] <masinter> right? It's not really a technical issue, it's a coordination issue
  897. # [22:34] <masinter> (lunch ready, back in 10)
  898. # [22:34] <othermaciej> ok, see you after lunch perhaps
  899. # [22:34] <masinter> 10 min
  900. # [22:39] * Quits: mitnavn (n=mitnavn@unaffiliated/mitnavn)
  901. # [22:41] * masinter returns to the den of trolls
  902. # [22:42] <Steve^> trolls live under bridges
  903. # [22:43] <masinter> maciej, Hixie pointed out that the 'parsing' from the URI spec wasn't actually referenced in my IRI draft; it used to be IRI -> URI and parse URI so it didn't need to be spec'd, but now that it is "parse IRI" first, I need to add some normative text for that
  904. # [22:43] <Philip`> Steve^: Tolkien's trolls don't, and I wouldn't want to accuse him of being wrong
  905. # [22:44] <masinter> there are still some things that were in the HTML document that aren't in the IRI document, but some of those really are specific to HTML; I suppose we could err on the side of including them and moving them back into HTML if necessary
  906. # [22:44] <Steve^> Philip`, good point. If he's correct the trolls are free to come and eat you.
  907. # [22:44] <othermaciej> masinter: regarding the nature of the issue - I believe from the HTML point of view, what is desired is suitable technical content to normatively reference, said content consisting of producer and consumer conformance requirements, and definitions (including definitions of some algorithms)
  908. # [22:45] * Quits: pmuellr (n=pmuellr@129.33.49.251)
  909. # [22:46] <othermaciej> masinter: I think the reason there is a coordination issue is because it is controversial in some quarters to define processing for HTML that aligns with legacy UAs and content rather than strictly following the relevant specifications, which are also used in non-HTML contexts
  910. # [22:47] * Quits: hobertoAtWork (n=hobertoa@gw1.mcgraw-hill.com) ("Nettalk6 - www.ntalk.de")
  911. # [22:47] <masinter> uh, i'm having trouble parsing that, lemme see if I can sort it out
  912. # [22:48] <othermaciej> my apologies for the clumsy sentence structure
  913. # [22:48] <masinter> well, just going through it, it's ok
  914. # [22:49] <masinter> I think the document i posted may be buggy, but it has "suitable technical content to normatively reference, said content consisting of producer and consumer conformance requirements, and definitions (including definitions of some algorithms)"
  915. # [22:50] <othermaciej> link?
  916. # [22:50] <masinter> although you might argue that the "definitions of some algorithms" are given by constraints and examples. but at least that's certainly the intent, and my goal was to note any issues and questions and known bugs in the text if they weren't resolved
  917. # [22:51] <othermaciej> (though I would probably leave the detailed technical review to people with more time and expertise than me)
  918. # [22:52] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  919. # [22:52] * Joins: jre (n=chatzill@mail.greenbytes.de)
  920. # [22:52] * Joins: jianli (n=jianli@74.125.59.73)
  921. # [22:54] * Quits: webben (n=benh@82.152.36.121) (Client Quit)
  922. # [22:54] <masinter> sigh, i posted the link here, but the message itself wasn't delivered. it's there now: http://lists.w3.org/Archives/Public/public-iri/2009Sep/0075.html
  923. # [22:54] <othermaciej> I see, thanks
  924. # [22:55] <masinter> hixie already had some comments. i tried to address your comments about the design goals in http://larry.masinter.net/iribis-hack.html#anchor22
  925. # [22:56] <othermaciej> is there a definition of how to extract the traditional hierarchical URI components from a string that may or may not be a valid IRI?
  926. # [22:57] <othermaciej> your design goals sound good
  927. # [22:57] <masinter> see http://krijnhoetmer.nl/irc-logs/whatwg/20090921#l-257
  928. # [22:58] <masinter> i thought what was wanted was IRI components, not URI components
  929. # [22:59] <masinter> i think probably what needs to happen is to allow anything in the BNF, and then make illegal characters in components non-conforming afterwards
  930. # [22:59] <masinter> i only started hacking the BNF itself at the last minute, though
  931. # [23:00] <masinter> what the draft now does is suggest that all illegal characters be percent-encoded before parsing
  932. # [23:01] <masinter> which probably has the same result, except for illegal characters in domain names
  933. # [23:01] <othermaciej> BNF is not that useful for defining error-tolerant rules for extracting subcomponents
  934. # [23:02] <othermaciej> it seems to me that there is an ill-defined concept in 3.2, namely the idea of matching a nonterminal production in a grammar in a string that does not satisfy the grammar
  935. # [23:02] <masinter> that's an interesting general statement we could debate, and i'm sure come up with lots of examples where BNF has been useful, even when defining error-tolerant rules
  936. # [23:02] <masinter> there are two issues
  937. # [23:03] <masinter> one is that the syntax doesn't really match ? and there's some failure? Not sure that can happen with the generic parsing, although it can happen with scheme-specific parsing
  938. # [23:03] <masinter> second is that there are otherwise illegal characters
  939. # [23:04] <masinter> the second issue i think is handled by pre-processing: stripping or percent-encoding illegal characters so they odn't appear by the time you get to 3.2
  940. # [23:04] <masinter> the first, well, it was in the original HTML copy of the its spec for "URL"
  941. # [23:05] <masinter> the plan was to allow HTML5 to normatively reference the "IRI" or "IRI reference" non-terminal as the "conforming producer" requirements, but to mandate "WebAddress processing" for "conforming liberal consumer"
  942. # [23:05] <othermaciej> I think you likely need a state-machine-like formalism to make the definition of component extraction unambiguous for strings that don't match the grammar
  943. # [23:06] <othermaciej> there may be other ways to do it, but I don't recall seeing a successful one in my experience
  944. # [23:06] <othermaciej> Web Address used a state machine formalism: http://www.w3.org/html/wg/href/draft.html#parsing-urls
  945. # [23:07] <masinter> that's certainly another way of approaching the problem, but unlikely to win support from the implementors of other specifications that use IRIs
  946. # [23:07] <jgraham> Why?
  947. # [23:07] <masinter> URIs haven't had a state-machine-like formalism, is there a serious interoperability failure for parsing?
  948. # [23:08] * Quits: BlurstOfTimes (n=blurstof@168.203.117.59) ("Leaving...")
  949. # [23:08] <mpilgrim> yes
  950. # [23:08] <othermaciej> a) implementors of other specifications that use IRIs don't need to use the algorithm for extracting components from a possibly-invalid string
  951. # [23:08] <masinter> example?
  952. # [23:08] <mpilgrim> but nobody in your group cares, because it's only browsers
  953. # [23:08] <othermaciej> b) what jgraham said
  954. # [23:08] <masinter> they don't?
  955. # [23:08] <mpilgrim> well, roy doesn't
  956. # [23:09] * masinter sighs
  957. # [23:09] <jre> othermaciej, RFC3986 already has an example for that: http://greenbytes.de/tech/webdav/rfc3986.html#regexp
  958. # [23:09] * Joins: webben (n=benh@dip5-fw.corp.ukl.yahoo.com)
  959. # [23:09] <jre> I think that works with IRIs as well
  960. # [23:09] <hsivonen> masinter: the Jena IRI lib implements, IIRC, about six distinct URL-like things but none of them provide my app the behavior I need to make img src resolve the way it does in browsers
  961. # [23:10] * hsivonen should really be asleep already
  962. # [23:10] * masinter wonders why a state-machine algorithm is better than a regular expression
  963. # [23:11] <masinter> they're both implementations. i'd think the regexp would be just as precise and much less wordy
  964. # [23:11] <masinter> no offense to Jena, but was this a spec problem, or were they just trying to be compatible with six different implementations?
  965. # [23:12] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Client Quit)
  966. # [23:12] * mpilgrim sighs
  967. # [23:12] <masinter> i mean, the problem with reverse-engineering URIs is that there are lots of different implementations, it's not the same game as trying to get out in front of IE
  968. # [23:12] <gsnedders> masinter: URI, IRI, XML's URI thingy in SYSTEM, I can't remember the others
  969. # [23:13] <mpilgrim> we need a spec that says how img src resolves in browsers
  970. # [23:13] <mpilgrim> you can call it whatever you like
  971. # [23:13] <masinter> mpilgrim: not sure which of your comments i should respond to first
  972. # [23:13] <mpilgrim> call it the "img src attribute spec"
  973. # [23:13] <mpilgrim> whatever
  974. # [23:14] <mpilgrim> i don't care
  975. # [23:14] <masinter> http://larry.masinter.net/iribis-hack.html#anchor22 lists what i thought the goals were
  976. # [23:14] <masinter> for the document in which they appear
  977. # [23:15] <masinter> and "Consistency of web and other Internet applications" argues against just defining the "img src attribute spec"
  978. # [23:15] <mpilgrim> i don't know how much clearer i can be
  979. # [23:15] <mpilgrim> that's a fun-looking set of design goals
  980. # [23:15] <masinter> if it's different for HTML and me sending you a URI via IRC
  981. # [23:15] <mpilgrim> go have fun with that
  982. # [23:15] <mpilgrim> we'll find someone else to spec the img src attribute
  983. # [23:16] * Joins: webben (n=benh-aga@217.12.15.52)
  984. # [23:16] * Quits: webben (n=benh-aga@217.12.15.52) (Client Quit)
  985. # [23:16] <Philip`> Seems like the consistency goal is already lost, if Jena has to have six URL-like things
  986. # [23:16] <mpilgrim> actually, we'll just use what we already wrote
  987. # [23:16] <jgraham> (epecially if hsivonen has to implement a seventh to get the behaviour he needs)
  988. # [23:16] <mpilgrim> and then handed off to you, before you broke it
  989. # [23:17] <masinter> mpilgrim: i was trying to actually address the issue that was raised
  990. # [23:17] <masinter> and you might not agree that the issue needs to be addressed at all
  991. # [23:17] <gsnedders> masinter: IRI, RDF URI reference, XML Schema anyURI, XML System ID, xlink:href are the six Jena IRI lib supports
  992. # [23:17] <gsnedders> + URI
  993. # [23:18] <masinter> yes, that's the result of people going off and writing their own spec in a snit, rather than actually trying to coordinate
  994. # [23:18] <mpilgrim> ^-- do any of these define any kind of error handling?
  995. # [23:18] <masinter> so there can be a 7th one, called "HTML5 URL" and an 8th and 9th too
  996. # [23:19] <mpilgrim> there *is* a 7th one
  997. # [23:19] <mpilgrim> you can call it whatever you like
  998. # [23:19] <mpilgrim> and you can spec it, or not
  999. # [23:19] <mpilgrim> but you can not -- i repeat, can not -- will it out of existence
  1000. # [23:19] <masinter> hmmmm
  1001. # [23:19] <mpilgrim> it will continue to exist, whether you document it or not
  1002. # [23:19] <mpilgrim> me, i prefer things like that to be documented
  1003. # [23:20] * masinter wonders if i am going to be forbidden to put cheese on toast next
  1004. # [23:20] <jgraham> ?
  1005. # [23:21] <masinter> i'm not sure what i'm trying to will out of existence
  1006. # [23:21] <mpilgrim> the algorithm used to resolve an img src attribute
  1007. # [23:21] <othermaciej> jre: interesting
  1008. # [23:21] <jre> mpilgrim, I don't think anybody proposed not to document it; what's controversial is how exactly to do that
  1009. # [23:21] <othermaciej> jre: it's very hard for me to tell what that regexp is doing or if it is correct
  1010. # [23:22] <mpilgrim> jre, trust me, there are people who do not want to document it
  1011. # [23:22] <mpilgrim> because it involves *gasp* error handling
  1012. # [23:22] <mpilgrim> and defining error handling is simply not done
  1013. # [23:22] <mpilgrim> in polite society
  1014. # [23:22] <mpilgrim> or something
  1015. # [23:22] * jgraham agrees with othermaciej
  1016. # [23:23] <jgraham> And presumbly it would be even worse with error handling
  1017. # [23:23] <othermaciej> masinter: I believe finite state machines and regular expressions are equivalent in what languages they can recognize
  1018. # [23:23] <jre> mpilgrim, I have no problem in defining the error handling UAs do
  1019. # [23:23] <mpilgrim> me neither
  1020. # [23:23] <othermaciej> masinter: so a regexp is just a compact (and possibly hard to understand, or maybe easy to understand) way of defining a state machine
  1021. # [23:23] <mpilgrim> i'm just telling you that there are people who do, most definitely, have a problem defining the error handling UAs do
  1022. # [23:23] <jre> but I do have a problem requiring *everybody* to do that
  1023. # [23:23] <masinter> well, there is at least 30 years of experience in writing parsers that implement languages based on grammers given for the language
  1024. # [23:24] * mpilgrim waits for masinter to mention interlisp
  1025. # [23:24] <jre> Maciej, the regexp was written by Roy, so it must be correct
  1026. # [23:24] * jre ducks
  1027. # [23:24] <jgraham> From the point of view of a QA it is difficult to tell from that regexp what the unusual cases i.e. the most likely interoperability problems are
  1028. # [23:24] <masinter> yuk yuk, we're getting funny again
  1029. # [23:25] <jgraham> (actually it's pretty difficult to tell *anything* from that regexp...)
  1030. # [23:25] <mpilgrim> s/have a problem defining/have a problem WITH defining/
  1031. # [23:25] <masinter> i don't think the regexp is normative, so maybe that's moot
  1032. # [23:26] * Quits: starjive (i=beos@213-66-216-93-no30.tbcn.telia.com)
  1033. # [23:26] * mpilgrim wonders, again, if any of the 6 specs gsnedders listed define error handling
  1034. # [23:26] <othermaciej> jgraham: you could rewrite the regexp formally as a finite state machine
  1035. # [23:26] * Joins: roc (n=roc@203-97-204-82.dsl.clear.net.nz)
  1036. # [23:26] <masinter> mpilgrim, those weren't 'specs' they were implementations
  1037. # [23:26] <jgraham> othermaciej: Indeed. I'd rather not have to if that's alright with you :)
  1038. # [23:26] <masinter> specs constrain implementations that are intended to be compliant with them
  1039. # [23:26] <mpilgrim> IRI is not a spec?
  1040. # [23:26] <othermaciej> jgraham: that is probably what I would do if I was really determined to find out if it processes things in a suitable way
  1041. # [23:27] <gsnedders> masinter: RDF isn't a spec?
  1042. # [23:27] <mpilgrim> and right away, we're done here
  1043. # [23:27] <mpilgrim> your view of a "spec" is narrow and naive
  1044. # [23:27] <masinter> he was tlaking about 6 implementations that are intended to be compliant with 6 specs
  1045. # [23:27] * Joins: ojan (n=ojan@72.14.229.81)
  1046. # [23:27] <masinter> mpilgrim, how many specs have you written or edited?
  1047. # [23:28] <mpilgrim> and i clearly meant "do any of the 6 specs which jeni implements" define error handling
  1048. # [23:28] <mpilgrim> again with the appeals to authority
  1049. # [23:28] <mpilgrim> don't forget interlisp!
  1050. # [23:28] <othermaciej> jgraham: actually, I can sort of tell what it's doing when I stare real close
  1051. # [23:28] * masinter sighs
  1052. # [23:28] * Joins: webben (n=benh-aga@217.12.15.52)
  1053. # [23:28] * Quits: webben (n=benh-aga@217.12.15.52) (Client Quit)
  1054. # [23:28] <Philip`> Is there some common formalism for finite state machines with capturing groups?
  1055. # [23:28] * Joins: webben (n=benh@dip5-fw.corp.ukl.yahoo.com)
  1056. # [23:29] * Quits: webben (n=benh@dip5-fw.corp.ukl.yahoo.com) (Client Quit)
  1057. # [23:29] <othermaciej> jgraham: essentially each component has a potential set of stop characters, and keeps going until you see one of those
  1058. # [23:29] <masinter> i think "define error handling" isn't very clear
  1059. # [23:29] * Joins: webben (n=benh@dip5-fw.corp.ukl.yahoo.com)
  1060. # [23:29] * Quits: virtuelv (n=virtuelv@125.175.251.212.customer.cdi.no) (Read error: 110 (Connection timed out))
  1061. # [23:29] <Philip`> (The regexp matches any string at all, so the capturing is the only interesting part of it)
  1062. # [23:29] <masinter> it's a shorthand for something that really has a lot of possible ways of accomplishing it
  1063. # [23:29] <jgraham> othermaciej: Yeah. But it is hardly obvious
  1064. # [23:29] <othermaciej> Philip`: other than a regexp, I think the common ways to describe FSMs are prose or state transition diagrams
  1065. # [23:29] <othermaciej> state transition diagrams could have capture of part of the input as a transition action
  1066. # [23:30] <jre> mjs, exactly; and surprise, that's how people implement it in practice
  1067. # [23:30] <mpilgrim> oh for christ's sake
  1068. # [23:30] <mpilgrim> even the xml spec defines error handling
  1069. # [23:30] <mpilgrim> (it's simplistic, naive, harmful-to-the-web draconian error handling, but it tells you what to do with something that purports to be xml but isn't)
  1070. # [23:30] * jre sees an appeal to authority
  1071. # [23:31] * jgraham sees the appeal of bedtime
  1072. # [23:32] <othermaciej> masinter: in the context of URI/IRI/URL/*R*, "define error handling" means that the various operations you can perform on a resource identifier have well-defined behavior when applied to a string that is not a conforming resource identifier of the appropriate kind
  1073. # [23:32] * Philip` sees a peal of bells
  1074. # [23:32] <othermaciej> operations such as "dereference", "extract the host component", "compare for equality to another *R*" , etc
  1075. # [23:33] <othermaciej> and in the context of *R* in Web browsers, the defined behavior of those operations has some legacy constraints and cannot simply be "signal an error"
  1076. # [23:34] <masinter> well, let me go through those
  1077. # [23:34] <masinter> "dereference" is a complex process, that involves parsing and then translating into some protocol action
  1078. # [23:35] <masinter> and the activities of dereferencing URIs (and IRIs) is delegated to the spec for the scheme
  1079. # [23:35] <masinter> so how to dereference a http URI is different than how to dereference a 'data:' or 'about' URI
  1080. # [23:35] <masinter> there's a gap between the HTML and URI/IRI and HTTP specs about where the spec now in HTML belongs, I admit
  1081. # [23:36] <masinter> which I think i could argue that it belongs in the HTTP spec, except for the parsing part, since the HTTP spec includes the http URI scheme
  1082. # [23:37] <masinter> "extract the host component", I think that's in the IRI draft, and that it should cover non-conforming input at least to some degree
  1083. # [23:37] * Quits: fishd__ (n=darin@nat/google/x-gqpieqwiyzntaljl) (Read error: 110 (Connection timed out))
  1084. # [23:38] <masinter> although we had that long conversation about whether it was really a good idea, for example, to not allow implementations to choose whether "signal an error or exception" or "pass through some error signal as error output"
  1085. # [23:38] <masinter> because which is preferable and correct might depend on legtimate differences in implementation mode
  1086. # [23:39] <masinter> compare for equality: the draft has long contained a ladder of comparison methods
  1087. # [23:39] <masinter> and if the four (five? don't remember) different comparison methods listed aren't specified sufficiently, that would be a bug
  1088. # [23:41] <masinter> re: "the defined behavior of those operations has some legacy constraints and cannot simply be "signal an error", the goal was to provide some way of calling for a parsing method which wouldn't have any such error states, by removing otherwise illegal characters
  1089. # [23:43] * Quits: taf2 (n=taf2@38.99.201.242)
  1090. # [23:43] * Quits: gsnedders (n=gsnedder@host217-44-35-222.range217-44.btcentralplus.com)
  1091. # [23:44] * Quits: Maurice (i=copyman@5ED548D4.cable.ziggo.nl)
  1092. # [23:44] <othermaciej> I guess Hixie also named the need for an absoluteness test that can be applied to a possibly nonconforming possibly relative IRI reference
  1093. # [23:45] <masinter> yes, the 'absolute' test should be whether or not there's a scheme, independent of whether the rest of it is legal
  1094. # [23:45] <othermaciej> and also a way to resolve an IRI reference relative to a base where one or both may be nonconforming
  1095. # [23:45] <masinter> that used to be inherited from URI because IRI -> URI translation was done first
  1096. # [23:46] <masinter> there are a couple of things i'm not sure of
  1097. # [23:46] <masinter> for example, how could you ever get a 'base' with a fragment identifier?
  1098. # [23:46] <othermaciej> <base> tag in HTML for instance
  1099. # [23:47] <othermaciej> <base href=""> can make an arbitrary string your base
  1100. # [23:47] <masinter> sorry, hmmm, someone was asking me whether fragment should be stripped
  1101. # [23:47] <masinter> yes, i mean, but why would anyone do that, that's what i meant
  1102. # [23:48] <masinter> at one point i was convinced that we needed to update the URI spec so that the relative + base algorithm could be updated
  1103. # [23:48] <masinter> and that might be still be the conclusion
  1104. # [23:49] <othermaciej> I don't think there is a good reason to do it, but I suspect there are people doing it inadvertently and relying on certain behavior
  1105. # [23:49] <masinter> the IRI document already swiped the BNF from URI and just tweaked it in place, probably the right thing to do is the same for the relative + base calculation
  1106. # [23:50] <othermaciej> it would probably be best to define both in one spec, and make "conforming URI" a strict subset of "conforming IRI"
  1107. # [23:50] <othermaciej> typing and reading the term "IRI" hurts me
  1108. # [23:50] <masinter> yeah, it's just harder to get there process-wise
  1109. # [23:51] <masinter> well, that's what i wanted to do, but i was convinced "one step at a time"
  1110. # [23:51] <jre> "conforming URI" *is* a subset of "conforming IRI"
  1111. # [23:51] <masinter> i mean, Roy was at least willing to admit that updating the URI spec might happen *sometime*
  1112. # [23:52] <othermaciej> coffee break, adieu for now
  1113. # [23:52] * Joins: fishd__ (n=darin@nat/google/x-uhnmeisermowtpyb)
  1114. # [23:52] <masinter> probably in the same time frame as HTML5 reaching Rec
  1115. # [23:53] <masinter> mpilgrim, you said a lot of things in passing that i didn't respond to, wonder if you want to go back and talk about any of them? "failed experiment", "secret AC mailing list postings", "interlisp", "false dichotomy" or "logical fallacy"
  1116. # [23:54] <masinter> or are you just the troll from Google?
  1117. # [23:55] <mpilgrim> "interlisp" is a reference to this epic thread on public-html a few months ago: http://lists.w3.org/Archives/Public/public-html/2009May/0571.html
  1118. # [23:55] <mpilgrim> "failed experiment" is what you have repeatedly called the HTML WG
  1119. # [23:55] <masinter> let's take 'em one at a time, ok?
  1120. # [23:55] <mpilgrim> a "logical fallacy" is an error in reasoning
  1121. # [23:56] <mpilgrim> a "false dichotomy" is a kind of logical fallacy
  1122. # [23:56] <mpilgrim> where you act as if there are only two options (usually polar opposites), when in fact there are more options
  1123. # [23:56] <masinter> so, Interlisp is some work I did mainly in the 70s
  1124. # [23:56] <masinter> can we do this one at a time, or do you want to overwhelm me with your fancy footwork?
  1125. # [23:56] <masinter> and I didn't bring it up
  1126. # [23:56] <masinter> God knows, Roy did
  1127. # [23:57] <masinter> and frankly, i wouldn't bring up Interlisp in a standards discussion; i'm not ashamed of it, but it was a long time ago, got some recognition so that's ok
  1128. # [23:57] <mpilgrim> ac-forum is, in fact, a secret mailing list
  1129. # [23:57] <mpilgrim> not that its existence is a secret
  1130. # [23:57] <masinter> i did work on the common lisp standard
  1131. # [23:57] <mpilgrim> but that its contents are only available to w3c members
  1132. # [23:57] <mpilgrim> and not to the general public
  1133. # [23:58] <masinter> sigh ok, i'm going to respond one at a time?
  1134. # [23:58] <masinter> or do you want to talk about all of these at once? what's your preference?
  1135. # [23:58] <mpilgrim> let's start with the "failed experiment" bit
  1136. # [23:58] <masinter> and still, i don't think i need to rest on 'authority' here, and I don't htink i need to
  1137. # [23:58] <masinter> ok
  1138. # [23:58] <masinter> so, i really put a lot of effort into the W3C process document
  1139. # [23:59] <masinter> and i've really thought a lot about standards processes, i've worked in ANSI and ISO and IETF and W3C and watched other groups as well
  1140. # [23:59] <masinter> and the HTML-WG is different from most other W3C groups
  1141. # [23:59] <masinter> and it was explained as an "experiment"
  1142. # [23:59] <masinter> right?
  1143. # Session Close: Tue Sep 22 00:00:00 2009

The end :)