/irc-logs / freenode / #whatwg / 2009-05-10 / end

Options:

  1. # Session Start: Sun May 10 00:00:00 2009
  2. # Session Ident: #whatwg
  3. # [00:01] * Joins: olliej (n=oliver@76.14.74.242)
  4. # [00:18] * Quits: olliej (n=oliver@76.14.74.242)
  5. # [00:21] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  6. # [00:23] * Joins: olliej (n=oliver@76.14.74.242)
  7. # [00:28] * Quits: olliej (n=oliver@76.14.74.242) (Client Quit)
  8. # [00:41] * Joins: olliej (n=oliver@76.14.74.242)
  9. # [00:44] * Joins: shepazu (n=schepers@d-132-204-220-5.res.umontreal.ca)
  10. # [00:54] * Joins: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  11. # [00:58] * Joins: webben (n=benh@91.85.210.172)
  12. # [00:58] * Quits: dimich (n=dimich@98.125.176.23)
  13. # [01:06] * gsnedders squints
  14. # [01:06] <gsnedders> A tourist page about Switzerland referencing Lac Léman, and not Lac de Genevè
  15. # [01:06] <gsnedders> * Genève
  16. # [01:09] * Quits: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  17. # [01:14] <jwalden> gsnedders: note that & doesn't necessarily mean implicitly-pointer, consider inlined functions may never even move a value into memory
  18. # [01:14] * gsnedders points out his knowledge of C++ is for most intents non-existant
  19. # [01:17] <Philip`> Explicit pointers with * might not even move the value into memory, so there's no difference :-)
  20. # [01:18] <jwalden> true enough
  21. # [01:18] <jwalden> although it may require a smarter compiler to notice that, with references you get it for free
  22. # [01:19] <Philip`> I'd except references vs pointers to be purely a frontend feature, and the code that's passed to the optimiser would be identical
  23. # [01:19] <Philip`> *expect
  24. # [01:23] * Philip` discovers the Status: header in CGI, and wonders where it's meant to be documented
  25. # [01:23] <Philip`> (Actually FastCGI but I think it's meant to be the same)
  26. # [01:26] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  27. # [01:28] * Quits: shepazu (n=schepers@d-132-204-220-5.res.umontreal.ca)
  28. # [01:31] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  29. # [01:32] * Quits: olliej (n=oliver@76.14.74.242)
  30. # [01:32] * Joins: slightlyoff (n=slightly@204.14.154.244)
  31. # [01:33] * Quits: slightlyoff (n=slightly@204.14.154.244) (Remote closed the connection)
  32. # [01:38] * Joins: shepazu (n=schepers@d-132-204-220-5.res.umontreal.ca)
  33. # [01:40] * Joins: heycam (n=cam@203-217-72-53.dyn.iinet.net.au)
  34. # [01:44] * Quits: shepazu (n=schepers@d-132-204-220-5.res.umontreal.ca)
  35. # [01:57] * Quits: ZombieLoffe (n=e@unaffiliated/zombieloffe)
  36. # [02:04] * Joins: myakura (n=myakura@p1120-ipbf2303marunouchi.tokyo.ocn.ne.jp)
  37. # [02:18] * Quits: myakura (n=myakura@p1120-ipbf2303marunouchi.tokyo.ocn.ne.jp) ("Leaving...")
  38. # [02:33] * Joins: myakura (n=myakura@p1120-ipbf2303marunouchi.tokyo.ocn.ne.jp)
  39. # [02:35] * Quits: Rik|work (n=Rik|work@fw01d.skyrock.net) (Read error: 113 (No route to host))
  40. # [02:44] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  41. # [02:48] * Quits: drostie (n=hopkins@5354256F.cable.casema.nl) (Read error: 110 (Connection timed out))
  42. # [02:53] * Joins: olliej (n=oliver@76.14.74.242)
  43. # [02:57] * Quits: Maurice (i=copyman@5ED548D4.cable.ziggo.nl) ("Disconnected...")
  44. # [02:58] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 110 (Connection timed out))
  45. # [03:01] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  46. # [03:05] * Quits: archtech (n=stanv@83.228.56.37)
  47. # [03:12] * Joins: dimich (n=dimich@98.125.176.23)
  48. # [03:16] * Quits: olliej (n=oliver@76.14.74.242)
  49. # [03:18] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  50. # [03:33] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  51. # [03:44] * Joins: myakura_ (n=myakura@p3202-ipbf3505marunouchi.tokyo.ocn.ne.jp)
  52. # [03:54] * Joins: myakura__ (n=myakura@p3087-ipbf6705marunouchi.tokyo.ocn.ne.jp)
  53. # [04:01] * Quits: myakura (n=myakura@p1120-ipbf2303marunouchi.tokyo.ocn.ne.jp) (Read error: 110 (Connection timed out))
  54. # [04:09] * Quits: myakura_ (n=myakura@p3202-ipbf3505marunouchi.tokyo.ocn.ne.jp) (Read error: 113 (No route to host))
  55. # [04:14] * Joins: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  56. # [04:15] * Joins: olliej (n=oliver@76.14.74.242)
  57. # [04:16] * Quits: olliej (n=oliver@76.14.74.242) (Remote closed the connection)
  58. # [04:56] * Joins: olliej (n=oliver@76.14.74.242)
  59. # [04:56] * Quits: olliej (n=oliver@76.14.74.242) (Remote closed the connection)
  60. # [05:04] * Joins: olliej (n=oliver@76.14.74.242)
  61. # [05:05] * Quits: olliej (n=oliver@76.14.74.242) (Client Quit)
  62. # [05:34] * Quits: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  63. # [05:57] * Joins: Rik|work (n=Rik|work@fw01d.skyrock.net)
  64. # [05:58] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  65. # [06:20] * Joins: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  66. # [06:22] * Quits: dimich (n=dimich@98.125.176.23)
  67. # [06:28] * Joins: sid0_ (n=sid0@unaffiliated/sid0)
  68. # [06:32] * Quits: sid0 (n=sid0@unaffiliated/sid0) (Read error: 60 (Operation timed out))
  69. # [06:48] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  70. # [07:14] * Quits: myakura__ (n=myakura@p3087-ipbf6705marunouchi.tokyo.ocn.ne.jp) ("Leaving...")
  71. # [07:25] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  72. # [07:34] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  73. # [07:34] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  74. # [07:40] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  75. # [07:48] * weinig_ is now known as weinig
  76. # [07:56] * sid0_ is now known as sid0
  77. # [08:00] * Joins: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  78. # [08:13] * Joins: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  79. # [08:23] * Quits: kinetik (n=kinetik@121.98.132.55) (Read error: 104 (Connection reset by peer))
  80. # [08:23] * Joins: kinetik_ (n=kinetik@121.98.132.55)
  81. # [09:13] * Quits: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  82. # [09:20] * Joins: archtech (n=stanv@83.228.56.37)
  83. # [09:22] * Joins: ap (n=ap@194.154.88.40)
  84. # [09:23] * weinig is now known as weinig|zZz
  85. # [09:36] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  86. # [09:41] * Joins: shepazu (n=schepers@modemcable203.65-70-69.static.videotron.ca)
  87. # [09:42] * Quits: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au) ("Tomorrow to fresh woods, and pastures new.")
  88. # [09:42] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  89. # [09:51] * Quits: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au) ("Tomorrow to fresh woods, and pastures new.")
  90. # [09:52] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  91. # [09:52] * Joins: williamcwilliams (n=williamc@c-24-8-182-168.hsd1.co.comcast.net)
  92. # [10:00] * Joins: olliej (n=oliver@76.14.74.242)
  93. # [10:01] * Joins: drostie (n=hopkins@5354256F.cable.casema.nl)
  94. # [10:04] * Joins: hdh (n=hdh@58.187.202.93)
  95. # [10:05] * Quits: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Read error: 110 (Connection timed out))
  96. # [10:14] <williamcwilliams> Oh man. I just want to thank you good people for cutting HTML 5's doctype declaration to <!DOCTYPE html>. And thank you for helping to phase out DTDs so I don't have to learn its convoluted syntax.
  97. # [10:15] <Hixie> our pleasure :-)
  98. # [10:25] * Joins: roc_ (n=roc@121-72-178-31.dsl.telstraclear.net)
  99. # [10:28] * Quits: olliej (n=oliver@76.14.74.242)
  100. # [10:37] * Joins: roc (n=roc@121-72-178-31.dsl.telstraclear.net)
  101. # [10:44] * Quits: roc_ (n=roc@121-72-178-31.dsl.telstraclear.net) (Read error: 110 (Connection timed out))
  102. # [10:49] * Joins: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  103. # [10:51] * Joins: Maurice (i=copyman@5ED548D4.cable.ziggo.nl)
  104. # [11:01] * Joins: maikmerten (n=maikmert@U3882.u.pppool.de)
  105. # [11:11] * Joins: myakura (n=myakura@p3087-ipbf6705marunouchi.tokyo.ocn.ne.jp)
  106. # [11:19] * Joins: ZombieLoffe (n=e@unaffiliated/zombieloffe)
  107. # [11:32] * Quits: Hish (n=chatzill@mail2.n-e-s.de) (Remote closed the connection)
  108. # [11:48] <Hixie> wow, json allows duplicate names in an object
  109. # [11:48] <Hixie> i had no idea
  110. # [11:48] <Hixie> (well, they're a SHOULD NOT, but that's it)
  111. # [11:50] * Quits: hdh (n=hdh@58.187.202.93) (Read error: 113 (No route to host))
  112. # [11:58] * Joins: hdh (n=hdh@58.187.201.173)
  113. # [12:11] <williamcwilliams> I can only see trouble coming out of such a thing.
  114. # [12:11] <Hixie> i expect it's a mistake, people seem to say SHOULD in specs when they mean MUST all the time
  115. # [12:11] <Philip`> Do they say "SHOULD" or "should"?
  116. # [12:11] <Hixie> SHOULD in this case
  117. # [12:13] * Philip` likes the HTML5 style of SHOULD/MUST/etc usage, since it makes it clear what behaviour needs to be tested
  118. # [12:16] <Philip`> Sometimes I think other specifications are mostly written for users (who want to know how they can expect their implementations to behave) and implementors (who want to know how their implementations should behave), neither of whom care much about the difference between 'should' and 'must'
  119. # [12:16] <Philip`> whereas something like HTML5 is also written for test writers, who do care about subtle differences between conformance requirements
  120. # [12:17] <Hixie> in practice, both of those groups (users and implementors) are hurt by the should/must confusion
  121. # [12:17] <Hixie> but yes, in general you are right
  122. # [12:19] <Philip`> I'd expect they're hurt mostly by the lack of defined error handling when there's duplicate names, rather than by the use of should/must
  123. # [12:26] <Hixie> i just mean they're hurt by lack of interop in general
  124. # [12:27] <Philip`> That seems largely independent of any should/must confusion
  125. # [12:28] <Philip`> e.g. the JSON spec requires quotes around keys, but lots of JSON implementations let you turn that off because it saves some bytes and it works in some parsers
  126. # [12:28] <Philip`> and it seems they don't really care about interoperability
  127. # [12:28] <jgraham> should/must confusion that prevents you writing tests hampers interop
  128. # [12:29] <jgraham> (also: in the case of JSON there is/was a clause that said roughly 'implementations may have any other behaviour they like'. Which rather undermines the rest of the specification)
  129. # [12:32] <Philip`> On an unrelated topic: Automated tests are great, but running them on a wide variety of web browsers is time-consuming. What we could do is sign up to an online ad system that lets you put arbitrary HTML in your ads, and then immediately get hundreds of thousands of testers with no effort and very low financial cost
  130. # [12:33] <jgraham> Then we'd have to pay to write tests
  131. # [12:34] <jgraham> It would be much better to create our own ad network so that we could inject html tests into other people's ads, and make money at the same time
  132. # [12:34] <Philip`> (and the HTML we put in the ads would be executing the tests and then sending the results (plus UA strings etc) back to the central server)
  133. # [12:34] <Philip`> jgraham: Uh, not quite sure what you mean
  134. # [12:35] * Hixie gets into his flame-proof bunker and sends an e-mail to the list
  135. # [12:35] <jgraham> Philip`: Instead of running the tests on some other ad network, set up our own ad network
  136. # [12:35] <jgraham> Sell ads on the network -> make money
  137. # [12:36] <Philip`> jgraham: But that would be extremely hard
  138. # [12:36] <jgraham> Also run tests on the network -> get useful data
  139. # [12:36] <Philip`> and would take years to build up
  140. # [12:36] * Joins: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  141. # [12:36] <Hixie> abarth has done tests on an ad network
  142. # [12:36] <Philip`> and to get on enough sites to get significant numbers of visitors
  143. # [12:36] <Hixie> you might want to speak to him
  144. # [12:36] <zcorpan_> http://blog.whatwg.org/media/vim-checker.png is a 404 (referenced from http://blog.whatwg.org/vim-checker )
  145. # [12:36] <jgraham> Philip`: Hard yes, extremely hard presumably not. And we have 'till 2022 :)
  146. # [12:37] * Philip` was inspired by abarth's work on this :-)
  147. # [12:38] * Quits: virtuelv (n=virtuelv@084202133045.customer.alfanett.no) ("Ex-Chat")
  148. # [12:40] <Philip`> Hixie: Haven't you seen any World War 2 movies? Bunkers are the worst place to be if you're expecting flames, because someone will break down the door and you'll be trapped and will burn to death and it won't be very nice at all
  149. # [12:40] <Hixie> crap
  150. # [12:40] <Hixie> where should i hide then?
  151. # [12:40] <Philip`> You could go scuba diving
  152. # [12:40] * Hixie goes scuba diving in a hurry
  153. # [12:41] <Hixie> ahblblublublbolbullblubloblub?
  154. # [12:42] <williamcwilliams> Say, I'm peering at the JSON specification via http://www.ietf.org/rfc/rfc4627.txt and it mentions in section 1.1 that it uses "MUST" and "SHOULD" as described in RFC2119. This leads me to believe that Mr. Crockford definitely intended such specific uses of those terms... Sorry if this is a crazy blast from the past here.
  155. # [12:43] <Hixie> a lot of spec writers put that boilerplate there without really understanding it, sad to say
  156. # [12:43] <Hixie> dunno if this is the case is doug's case
  157. # [12:44] <Hixie> but if he really meant SHOULD there, that's mighty odd
  158. # [12:45] <zcorpan_> " The names within an object SHOULD be unique."
  159. # [12:45] <Philip`> HTML5 had the same boilerplate and then proceeded to use the terms in ways that were not described in RFC2119
  160. # [12:45] <Hixie> indeed
  161. # [12:45] <Philip`> so it's a common problem :-)
  162. # [12:46] <williamcwilliams> That is pretty funny! Yet frustratrating at times, I'm sure.
  163. # [12:46] <jgraham> Hixie: Just skimming your new email; is it really necessary to do <span item id=a><span property="com.example.name">a</span></span> rather than something like <span id=a property="com.example.name>a</span>?
  164. # [12:47] <zcorpan_> Philip`: in HTML5's case it was more because of RFC2119 not expecting the classes of products that HTML5 was having, right?
  165. # [12:47] * Philip` is thinking of the use of phrases like "must only", which have meaning only in English and not in RFC2119
  166. # [12:47] <Hixie> jgraham: you need the item="" attribute to declare the new group of name-value pairs
  167. # [12:48] <jgraham> Hixie: At the very least it would be good if <span item property> acted like <span item><span property>
  168. # [12:48] <Hixie> jgraham: you can't do item="" property="" on the same element in this case, because when you do that it means the new group is the value of the given property on whatever the corresponding "parent" item is
  169. # [12:48] <zcorpan_> Philip`: ah, ok
  170. # [12:49] <Hixie> jgraham: e.g. <span item="vcard"> <span property="agent" item="vcard"> <span property="...">...</span> </span> </span>
  171. # [12:49] <Hixie> jgraham: the middle one there is saying that "agent" is a property of the outer item, whose value is itself an item.
  172. # [12:49] <Hixie> luckily, that's basically as complex as this stuff gets.
  173. # [12:49] * Joins: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  174. # [12:49] <jgraham> Hixie: Hmm. I will think about this more when I have understood the proposal beter, but my initial reaction is that people will get this wrong and be surprised
  175. # [12:50] <Hixie> i don't think the case of those bulbs will be a common case
  176. # [12:51] <jgraham> OK.
  177. # [12:51] <jgraham> I'll see what other people say
  178. # [12:52] * Quits: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  179. # [12:54] <williamcwilliams> Hixie: Do you mean that if, in your example, the second tag didn't have the the item attribute explicitly set, it would still have item="vcard" like its parent?
  180. # [12:55] <Hixie> if the second tag didn't have the item attribute explicitly set, the third one would set a "..." property on the first one, instead of the second
  181. # [12:55] <Hixie> so the first one would have two properties, "agent" and "..."
  182. # [12:55] <Hixie> instead of the first one having a property "agent" which itself has a property "..."
  183. # [13:01] * Quits: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu) ("KVIrc 3.4.0 Virgo http://www.kvirc.net/")
  184. # [13:02] <Philip`> Reversed domain names aren't sufficient for people with shared hosting on a single domain
  185. # [13:02] <Philip`> which seems a bit of a pain
  186. # [13:02] <Hixie> why not?
  187. # [13:02] <Hixie> just stick your path components on the end
  188. # [13:02] * Joins: ZombieL (n=e@80.217.235.198)
  189. # [13:02] <Philip`> If everyone on Geocities uses com.geocities.* then there's no convention to avoid conflicts
  190. # [13:03] <Hixie> if everyone on Geocities uses microdata, I will hand in my spec editor's badge.
  191. # [13:03] <Philip`> If two people on Geocities use com.geocities.* then there's no convention to avoid conflicts
  192. # [13:03] <Philip`> and s/Geocities/something like Geocities that isn't dead yet/
  193. # [13:03] <Hixie> so buy a domain
  194. # [13:03] <Hixie> it's like $5 a year
  195. # [13:03] <Hixie> or hope for the best and use com.geocities.philip.foo
  196. # [13:04] <Hixie> (or use a uri, those are still allowed too, for teh crazy people who think uris are better!)
  197. # [13:08] <Philip`> I haven't read the spec so I don't know what it suggests; I'm just thinking that if it suggests a convention, it should suggest a convention that can work for independent people who share a domain name, even if it's something vague like adding a unique-in-that-domain identifier onto the end
  198. # [13:08] <Hixie> the spec doesn't have any informative text on that topic yet
  199. # [13:09] <Hixie> i'll make a note to add something to the intro section though
  200. # [13:09] <Hixie> thanks
  201. # [13:12] <Philip`> If I want to write a page containing data about two cats, and say that cat A is the parent of cat B, and cat B is a child of cat A, can I do that nicely?
  202. # [13:13] <Hixie> not yet. I have considered a a <ref> element to do that in a future version, but none of the use cases I had actually needed it, so I punted on it for now.
  203. # [13:13] <Philip`> It looks like the new microdata stuff is purely tree-shaped and can't do graphs, and there isn't any way for one item to refer to another
  204. # [13:13] <Philip`> since items don't have identifiers
  205. # [13:13] <Hixie> items have id="" attributes like any other html element
  206. # [13:13] <Hixie> but yes, there's no way to make arbitrary graphs yet
  207. # [13:15] <Philip`> Hmm, I suppose the API could be extended to expose $item->id() and $microdata->get_item_by_id('...')
  208. # [13:15] <Philip`> but then it won't work if I put each cat on a separate page, and want them to refer to each other
  209. # [13:15] <Philip`> (i.e. being in separate items of @docs)
  210. # [13:16] <Hixie> none of the use cases needed that
  211. # [13:16] <Philip`> so one would have to refer to items by a full URI instead
  212. # [13:16] <Hixie> but yeah, if we really wanted to support that, we could just have <ref> support cross-document references too
  213. # [13:17] <Hixie> usemap="" showed that wasn't too hot, though
  214. # [13:21] * Quits: williamcwilliams (n=williamc@c-24-8-182-168.hsd1.co.comcast.net) ("Chatzilla 0.9.75.1 [SeaMonkey 1.1.16/2009040306]")
  215. # [13:23] * Quits: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  216. # [13:23] <Hixie> ok i just checked in a brief intro section. bed time now. I'm sure when I wake up I'll have record amounts of mail.
  217. # [13:23] <Hixie> nn
  218. # [13:27] <jgraham> Hixie: It would be nice if the corresponding item algorithm was written in priority order rahter than reverse priority order
  219. # [13:27] <jgraham> also: gn
  220. # [13:39] <Philip`> Hixie: s/desireable/desirable/
  221. # [13:39] * Joins: wakaba (n=wakaba@EM114-51-38-211.pool.e-mobile.ne.jp)
  222. # [13:42] <Philip`> Hixie: "Properties can also have values that are URLs. This is achieved using the a element and its href attribute." - but the example uses <img src> instead
  223. # [13:43] * ap is now known as ap|away
  224. # [14:41] * Joins: nessy (n=nessy@124-171-63-74.dyn.iinet.net.au)
  225. # [14:42] * Quits: nessy (n=nessy@124-171-63-74.dyn.iinet.net.au) (Remote closed the connection)
  226. # [14:42] * Joins: nessy (n=nessy@124-171-63-74.dyn.iinet.net.au)
  227. # [14:45] * Joins: zdobersek (n=zan@cpe-92-37-79-141.dynamic.amis.net)
  228. # [14:47] * Joins: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  229. # [14:53] <Philip`> Is there some DOM API that will return a resolved URL?
  230. # [14:53] <Philip`> (and that works in real browsers)
  231. # [14:53] <Philip`> given a relative URL as input
  232. # [15:06] * Joins: akamike (n=mikerobi@92.3.35.15)
  233. # [15:08] * Quits: nessy (n=nessy@124-171-63-74.dyn.iinet.net.au) ("This computer has gone to sleep")
  234. # [15:12] * Quits: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  235. # [15:17] <Philip`> http://philip.html5.org/demos/microdata/demo.html
  236. # [15:18] * krijnh likes the proposal
  237. # [15:19] <Philip`> Hmph, Gmail's 'basic HTML' UI doesn't let you select your From address :-(
  238. # [15:30] <Philip`> At least the proposal is easy to implement
  239. # [15:30] <Philip`> though JQuery is a bit rubbish because its attribute selectors only work half the time
  240. # [15:30] <krijnh> They do?
  241. # [15:31] <Philip`> $('[item]') finds <div item> in Opera (10) but not in Firefox (3.0); $(...).parents('[item]') doesn't find it in either
  242. # [15:31] <krijnh> Weird
  243. # [15:31] * Philip` presumes it's to do with optimising some cases with querySelector or whatever it's called
  244. # [15:31] <krijnh> Yeah
  245. # [15:32] <krijnh> But JohnResig might know :)
  246. # [15:32] <Philip`> $('*').filter(function() { return this.getAttribute('item') !== null }) makes me unhappy
  247. # [15:32] <krijnh> http://james.padolsey.com/javascript/a-better-data-selector-for-jquery/ - just extend the selector, and create an :item selector
  248. # [15:33] <Philip`> That sounds even less efficient
  249. # [15:33] <krijnh> It probably is
  250. # [15:34] <krijnh> But jQuery users don't care too much about efficiency ;) *runs*
  251. # [15:34] <Philip`> I think my code is already O(n^2) but I don't want to make it slower
  252. # [15:35] <krijnh> (I'm a jQuery user as well btw)
  253. # [15:36] <Philip`> (I think I could make it O(n) without too much trouble, but I'm lazy and this way works)
  254. # [15:37] <Philip`> ((The problem is finding the properties with a specific corresponding item))
  255. # [15:39] * Joins: ROBOd (n=robod@89.122.216.38)
  256. # [15:45] <Philip`> Oh, and JQuery's node.is('time') fails in (at least) Opera 10
  257. # [15:48] * Quits: wakaba (n=wakaba@EM114-51-38-211.pool.e-mobile.ne.jp) (Read error: 104 (Connection reset by peer))
  258. # [15:52] * Joins: wakaba (n=wakaba@EM114-51-8-12.pool.e-mobile.ne.jp)
  259. # [16:02] <gsnedders> Woah. Kinda big commits.
  260. # [16:07] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  261. # [16:09] <Philip`> gsnedders: I suggest complaining about the solution without bothering to read it first
  262. # [16:10] <gsnedders> Philip`: That means not revising for exams that start on Friday
  263. # [16:11] <Philip`> gsnedders: Exams happen every year, HTML5 is only going to happen once in the whole of human civilisation
  264. # [16:11] <Philip`> You need to get your priorities right
  265. # [16:11] <gsnedders> However, HTML 5 will still be ongoing after my exams.
  266. # [16:32] * Quits: drostie (n=hopkins@5354256F.cable.casema.nl) (Remote closed the connection)
  267. # [16:37] * Quits: zdobersek (n=zan@cpe-92-37-79-141.dynamic.amis.net) ("Leaving.")
  268. # [16:38] * Joins: zdobersek (n=zan@cpe-92-37-72-84.dynamic.amis.net)
  269. # [16:39] <jgraham> Philip`: Ah, you beat me. I have a somewhat working html5lib based implementation which allowed me to conclude that the api is easy to implement
  270. # [16:39] <jgraham> But went for a bike ride rather thank finishing it
  271. # [16:40] <Philip`> You need to get your priorities right
  272. # [16:40] <jgraham> You would have won anyway :)
  273. # [16:41] <Philip`> You could still win at producing RDF output
  274. # [16:42] <jgraham> Yeah I might do that. Or I might not bother. Who know
  275. # [16:42] <jgraham> s
  276. # [16:44] * Quits: gavin_ (n=gavin@firefox/developer/gavin) (Read error: 60 (Operation timed out))
  277. # [16:44] * Joins: gavin_ (n=gavin@firefox/developer/gavin)
  278. # [16:47] <Philip`> http://news.bbc.co.uk/1/hi/programmes/click_online/8040863.stm - "These TV sets are not equipped with full web browsers, as some sites involve lots of small writing that would be difficult to read from a distance." - someone should tell them about the abilities of modern browsers to zoom and change the text size
  279. # [16:48] <Philip`> (Sounds like more attempts at walled gardens)
  280. # [17:22] * ap|away is now known as ap
  281. # [17:24] * Joins: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  282. # [17:37] * Quits: ZombieLoffe (n=e@unaffiliated/zombieloffe)
  283. # [17:41] * Joins: wakaba_ (n=wakaba@114.51.13.216)
  284. # [17:52] * Quits: hdh (n=hdh@58.187.201.173) (Read error: 104 (Connection reset by peer))
  285. # [17:52] * Quits: shepazu (n=schepers@modemcable203.65-70-69.static.videotron.ca)
  286. # [17:54] * Quits: ZombieL (n=e@80.217.235.198)
  287. # [17:59] * Quits: wakaba (n=wakaba@EM114-51-8-12.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  288. # [18:00] * Quits: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  289. # [18:07] * Joins: sid0_ (n=sid0@unaffiliated/sid0)
  290. # [18:07] * Joins: VeXocide_ (i=vexocide@snail.stack.nl)
  291. # [18:08] * Joins: scherkus_ (n=scherkus@72.14.227.1)
  292. # [18:08] * Quits: sid0 (n=sid0@unaffiliated/sid0) (orwell.freenode.net irc.freenode.net)
  293. # [18:08] * Quits: webben (n=benh@91.85.210.172) (orwell.freenode.net irc.freenode.net)
  294. # [18:08] * Quits: broquaint (i=f17a7ae0@spc1-brig11-0-0-cust544.asfd.broadband.ntl.com) (orwell.freenode.net irc.freenode.net)
  295. # [18:08] * Quits: danbri_ (n=danbri@unaffiliated/danbri) (orwell.freenode.net irc.freenode.net)
  296. # [18:08] * Quits: scherkus (n=scherkus@72.14.227.1) (orwell.freenode.net irc.freenode.net)
  297. # [18:08] * Quits: onar (n=onar@17.226.20.255) (orwell.freenode.net irc.freenode.net)
  298. # [18:08] * Quits: VeXocide (i=vexocide@snail.stack.nl) (orwell.freenode.net irc.freenode.net)
  299. # [18:11] * Joins: webben (n=benh@91.85.210.172)
  300. # [18:12] * Joins: broquaint (i=1fcb6f28@spc1-brig11-0-0-cust544.asfd.broadband.ntl.com)
  301. # [18:13] * Quits: ap (n=ap@194.154.88.40)
  302. # [18:14] * Joins: ap (n=ap@194.154.88.40)
  303. # [18:15] <jgraham> """If there is exactly one element whose corresponding item is item and that has as one of its property names the string "about"""". Does that mean (there is one element whose corresponding item is item) and (the corresponding item has a property called about)"
  304. # [18:16] * Joins: danbri (n=danbri@85.144.208.21)
  305. # [18:16] <jgraham> or (of the elements whose corresponding item is item, there is exactly one called about)
  306. # [18:17] <jgraham> s/called/with a property called/
  307. # [18:17] * Joins: onar (n=onar@17.226.20.255)
  308. # [18:17] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  309. # [18:18] * Philip` wonders if jgraham is implementing the same thing he's implementing
  310. # [18:20] * Quits: ray (i=ray@2001:41c8:1:54da:0:0:0:1337) (Read error: 60 (Operation timed out))
  311. # [18:21] <jgraham> Philip`: Possibly.
  312. # [18:22] <Philip`> I hope you're implementing it in your Python version
  313. # [18:22] * Quits: hendry (n=hendry@webvm.net) (Read error: 110 (Connection timed out))
  314. # [18:23] <jgraham> Philip`: Indeed
  315. # [18:23] <jgraham> Although the RDF stuff is much more tedious than the whole rest of the microdata section, so I am tempted to stop and just implement the frontend
  316. # [18:24] <jgraham> (where by "much more tedious" I mean "I can't be bothered to work out the anser to the question above")
  317. # [18:25] <jgraham> (or implement any of the url functions)
  318. # [18:25] <jgraham> (although those are really needed anyway)
  319. # [18:33] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  320. # [18:36] * Joins: dglazkov_ (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  321. # [18:36] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  322. # [18:45] <gsnedders> 8:24 from Southampton Central to Stirling by train, with a 45 minute stop-over in London. Yay :\
  323. # [18:46] * Joins: shepazu (n=schepers@d-132-204-220-5.res.umontreal.ca)
  324. # [18:48] <gsnedders> Or I could fly Southampton to Edinburgh, then go on by train, which would save me a bit of time but would add hassle…
  325. # [18:52] * Quits: shepazu (n=schepers@d-132-204-220-5.res.umontreal.ca)
  326. # [18:57] * Quits: dglazkov_ (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  327. # [19:15] * Joins: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  328. # [19:24] * Joins: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  329. # [19:27] * Joins: KevinMarks (n=KevinMar@c-71-202-163-211.hsd1.ca.comcast.net)
  330. # [19:34] * Quits: KevinMarks (n=KevinMar@c-71-202-163-211.hsd1.ca.comcast.net) ("The computer fell asleep")
  331. # [19:35] <gsnedders> jgraham: you still around?
  332. # [19:36] <gsnedders> Anyone else who knows physics: you around?
  333. # [19:36] <gsnedders> Ah, Wikipedia helps.
  334. # [19:36] <jgraham> gsnedders: Yes
  335. # [19:36] <gsnedders> (i.e., nvm)
  336. # [19:36] <gsnedders> (Though I may still need help at some other time)
  337. # [19:38] * Quits: myakura (n=myakura@p3087-ipbf6705marunouchi.tokyo.ocn.ne.jp) ("Leaving...")
  338. # [19:48] <gsnedders> Anyone got any sane way of remembering which way around the ± is for the Doppler effect (i.e., within equations like f = f_s(\frac{v}{v±v_s}))?
  339. # [19:49] * gsnedders should probably conclude he can work this out by thinking about it.
  340. # [19:54] <gsnedders> Peh. The
  341. # [19:54] <gsnedders> So if the source and observer and getting closer, f must increase, and then it can be worked out from that.
  342. # [19:56] * Quits: ROBOd (n=robod@89.122.216.38) (Remote closed the connection)
  343. # [19:56] <gsnedders> Is that right?
  344. # [20:00] <jgraham> gsnedders: Yeah, things comping toward you go high pitched. If your answer doesn't give that you did it wrong
  345. # [20:00] <gsnedders> From Wikipedia: "Craig Bohren pointed out in 1991 that some physics textbooks erroneously state that the observed frequency increases as the object approaches an observer and then decreases only as the object passes the observer." — Huh?
  346. # [20:06] * Joins: sid0 (n=sid0@unaffiliated/sid0)
  347. # [20:07] <jgraham> gsnedders: They're saying that the frequency doesn't get higher and higher as the object approaches you
  348. # [20:09] <gsnedders> OK, that's basically what I concluded after staring at that for five minutes.
  349. # [20:09] <jgraham> In unrelated news, I hate easy_install and whatever they call the braindead system it runs on
  350. # [20:11] <Philip`> You should be thankful that they didn't call it ezinstall
  351. # [20:11] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  352. # [20:11] * Joins: drostie (n=hopkins@5354256F.cable.casema.nl)
  353. # [20:12] <jgraham> Why the fuck is it trying to extract archives to my web server directory?
  354. # [20:14] * jgraham notices Shelly's email from earlier
  355. # [20:18] * VeXocide_ is now known as VeXocide
  356. # [20:24] * Quits: sid0_ (n=sid0@unaffiliated/sid0) (Read error: 110 (Connection timed out))
  357. # [20:30] * Joins: virtuelv (n=virtuelv@084202133045.customer.alfanett.no)
  358. # [20:32] * Joins: hdh (n=hdh@118.71.97.22)
  359. # [20:34] * Joins: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  360. # [20:38] * Quits: weinig|zZz (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  361. # [20:40] * Joins: mlpug (n=mlpug@a91-156-60-235.elisa-laajakaista.fi)
  362. # [20:59] * Joins: ray (i=ray@the.ug)
  363. # [21:02] * Quits: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Read error: 110 (Connection timed out))
  364. # [21:11] * Quits: ray (i=ray@the.ug) (Remote closed the connection)
  365. # [21:31] <Hixie> jgraham: is that sentence in the rdf section clearer now?
  366. # [21:34] * Joins: weinig (n=weinig@nat/apple/x-5d16ecde3b454783)
  367. # [21:35] <Hixie> Philip`: to resolve URLs, just use the DOM attributes, the browser will then do it for you
  368. # [21:36] * Joins: wakaba (n=wakaba@EM114-51-130-66.pool.e-mobile.ne.jp)
  369. # [21:36] <jgraham> Hixie: I don't understand why there must only be a single element with item item
  370. # [21:37] <Hixie> then it's still not clear, hold on let me fix it more
  371. # [21:38] <Hixie> regenning, look in a few seconds
  372. # [21:38] <jgraham> OK
  373. # [21:38] * Quits: ap (n=ap@194.154.88.40)
  374. # [21:38] <jgraham> (I assume that the actul condition is that for each item there is a single value of a property called about, right?)
  375. # [21:39] <Hixie> right
  376. # [21:39] <Hixie> regenned
  377. # [21:40] <jgraham> Yes, that makes sense now
  378. # [21:40] * Quits: wakaba_ (n=wakaba@114.51.13.216) (Read error: 145 (Connection timed out))
  379. # [21:40] <jgraham> Thanks
  380. # [21:40] <Hixie> cool
  381. # [21:40] <Hixie> i'm very confused by shelley's e-mails
  382. # [21:41] <Hixie> was she wanting me to stop working on the use cases while she redid them?
  383. # [21:43] <takkaria> Hixie: I like the microdata draft, seems like it's far more understandable than RDFa
  384. # [21:43] <Hixie> sweet
  385. # [21:43] <Hixie> i've gotten far more positive feedback (mostly off-list or on IRC) than I expected
  386. # [21:43] <Hixie> and virtuall no negative feedback so far
  387. # [21:43] <gsnedders> Hixie: It sucks.
  388. # [21:44] <Philip`> It's easy to make something more understandable than RDFa; the problem is to make it sufficiently expressive to handle enough of what people want to do with it
  389. # [21:44] <gsnedders> (Because it's too long for me to have time to look at now.)
  390. # [21:44] <gsnedders> (See, I do actually have a reason!)
  391. # [21:44] <Hixie> gsnedders: dude it's actually surprisingly short
  392. # [21:44] <Hixie> gsnedders: there's even an incomplete intro section now too
  393. # [21:45] <gsnedders> Hixie: OK, the diff was long :P
  394. # [21:45] <gsnedders> The fact it renumbered half the TOC didn't helop
  395. # [21:45] <gsnedders> *help
  396. # [21:45] <Hixie> Philip`: yeah... it handles all the use cases i listed (i checked by making examples for most of them), but i'm sure there are things people didn't mention that will be harder
  397. # [21:45] <Philip`> gsnedders: Read the new section rather than the diff
  398. # [21:45] <Hixie> gsnedders: oh you want to look at the /source diff not the /index diff
  399. # [21:45] <Hixie> gsnedders: and the diff included all kinds of random stuff
  400. # [21:45] <Hixie> gsnedders: e.g. new interfaces and stuff
  401. # [21:45] <Hixie> gsnedders: which you don't need to read to get the microdata stiff
  402. # [21:45] <Hixie> stuff
  403. # [21:45] <gsnedders> Hixie: I know. But the email includes both, and /index is always first :P
  404. # [21:46] * gsnedders goes back to question 11 of the 2004 exam paper
  405. # [21:46] <takkaria> I wonder how hard it would be to transplant hcard into the microdata thing
  406. # [21:46] <Philip`> I suppose an obvious complaint is that people who've already put a lot of work into defining RDF-based vocabularies would have to start over again defining a whole new naming system for the vocabulary
  407. # [21:46] <Hixie> gsnedders: hah
  408. # [21:47] <Hixie> takkaria: surprisingly easy, that's next on my list of things to mail about :-)
  409. # [21:47] <Philip`> (and it'd be nice to have a stronger mapping between them)
  410. # [21:47] <Hixie> Philip`: nah, they can use uris with this
  411. # [21:47] <jgraham> http://james.html5.org/microdata/
  412. # [21:47] <jgraham> Work in progress, if it gives the right result it is pure serendipity
  413. # [21:48] <Hixie> man you guys rock
  414. # [21:48] <Philip`> jgraham: Charset is wrong on test page
  415. # [21:48] <Hixie> it's barely been 12 hours and you've already made two separate implementations
  416. # [21:49] <Philip`> jgraham: JSON output needs indentation
  417. # [21:50] * Philip` almost implemented RDF output too, but discovered it was not trivial to generate N3 when there's blank nodes, and gave up and ate biscuits instead
  418. # [21:50] * Quits: maikmerten (n=maikmert@U3882.u.pppool.de) (Remote closed the connection)
  419. # [21:50] <Hixie> it's not that hard is it? you just do _:nodeN where N is a globally increasing number per blank node
  420. # [21:51] <Hixie> basically each time you make a blank node you call it _:nodeN and then pretend it's not blank
  421. # [21:51] <Philip`> That's ugly
  422. # [21:51] <gsnedders> Hixie: See, it's all work and no µdata :P
  423. # [21:51] <gsnedders> s/µdata/play/
  424. # [21:52] <jgraham> Philip`: Fixed the pretty printing thing
  425. # [21:52] <Hixie> Philip`: it's rdf baby
  426. # [21:52] <jgraham> Oh, I think I fixed the other thing too but I'm not sure
  427. # [21:52] <Philip`> I wanted to do it like '<> custom:band [ custom:name "Jazz Band"; custom:size "12" ]'
  428. # [21:52] <Philip`> (I think that's possibly the right syntax)
  429. # [21:53] <jgraham> I got part of the way through doing the RDF thing at which point it became obvious that RDF was going to be more work than the whole microdata section so far
  430. # [21:54] <jgraham> So I stopped
  431. # [21:54] <gsnedders> rdflib++
  432. # [21:54] <Philip`> I suppose I need to generate a graph and then serialise it, rather than printing out a line each time I find a property
  433. # [21:54] * gsnedders just tells Philip` to stop implementing RDF himself, as it isn't nice to implement
  434. # [21:54] <gsnedders> Also, see #swig
  435. # [21:54] * jgraham was hoping it would work to make a list of triples and have something that took a list of triples and printed N3
  436. # [21:55] <jgraham> But maybe RDFLib is the way forward
  437. # [21:55] <Philip`> gsnedders: I'm not implementing RDF, I'm just implementing something that output text that happens to be a subset of RDF
  438. # [21:56] <jgraham> Implementing all the URL munging stuff is still a massive pain though
  439. # [21:56] <jgraham> (which I need anyway)
  440. # [21:56] <jgraham> (so I can't blame on RDF)
  441. # [21:56] <Hixie> URL munging stuff?
  442. # [21:57] <gsnedders> Hixie: For less favourable comments, see #swig :P
  443. # [21:57] <Hixie> is that archived anywhere?
  444. # [21:58] <gsnedders> Hixie: It is, but logs appear to be down
  445. # [21:58] <gsnedders> http://swig.xmlhack.com/ is the URL
  446. # [21:58] <gsnedders> no idea if it'll come back up
  447. # [21:58] <Hixie> can you paste us any feedback then? :-)
  448. # [21:59] <gsnedders> Hixie: That's effort :P
  449. # [21:59] <Philip`> jgraham: I took the approach of ignoring any URL stuff that wasn't trivial, because I was trying to make a rough proof-of-concept to see how the thing worked, rather than making an actual proper implementation :-)
  450. # [21:59] <Hixie> -_-
  451. # [21:59] <gsnedders> Hixie: I can, if you help me wit physics! :P
  452. # [21:59] <Hixie> objects with mass attract each other
  453. # [21:59] <Philip`> What about objects without mass?
  454. # [21:59] <Hixie> everything else is complicated
  455. # [21:59] <gsnedders> Hixie: I need more complex help :P
  456. # [22:00] <Hixie> Philip`: they go at the speed of light so from their perspective time doesn't move so they can't do anything
  457. # [22:00] <Philip`> gsnedders: You need to specify your problem in a more complex way than "help me wit[h] physics" if you want more complex help :-p
  458. # [22:00] <gsnedders> Hixie: http://pastebin.com/m332bac12
  459. # [22:01] * Joins: ROBOd (n=robod@89.122.216.38)
  460. # [22:01] <gsnedders> "Calculate the time for the wave to travel between these points (at x = 3.0m and x = 4.0m)" where we have a transverse wave given by y = 8.0 sin(12t-0.50x)
  461. # [22:01] <Hixie> gsnedders: let me know if they have any actual feedback :-)
  462. # [22:02] <Hixie> correct me if i'm wrong but that wave doesn't move
  463. # [22:02] <Philip`> It does if t does, surely
  464. # [22:02] <Hixie> since it has a constant amplitude
  465. # [22:02] * Joins: dglazkov_ (n=dglazkov@72.14.224.1)
  466. # [22:02] <Hixie> no, that just changes the phase of the wave
  467. # [22:02] <Hixie> the wave itself doesn't move
  468. # [22:03] <gsnedders> Well, the answer is 0.04°s.
  469. # [22:03] <gsnedders> But how do you get there? :P
  470. # [22:03] <Philip`> That's just being pedantic :-p
  471. # [22:03] <Hixie> it's not pedanticism, it's physics!
  472. # [22:03] <gsnedders> But that is true :P
  473. # [22:03] <Hixie> if you have waves in water, and you have a buoy on that water, it just bobs up and down
  474. # [22:03] <Philip`> I assume the idea is to calculate how long it takes for the peaks to 'travel', or something
  475. # [22:03] <gsnedders> It doesn't help me get me to the answer.
  476. # [22:03] <Hixie> it doesn't go tearing down the wave like a surfer headed to the beach
  477. # [22:03] <Philip`> because it couldn't mean anything else
  478. # [22:04] <Hixie> sounds like it's asking the wavelength then
  479. # [22:04] <Hixie> or equivalently the frequency
  480. # [22:04] * Joins: dglazkov__ (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  481. # [22:04] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  482. # [22:05] <Hixie> which of course you can link using LF = c (wavelength * frequency = propagation speed)
  483. # [22:05] <Hixie> er
  484. # [22:05] <Hixie> phase speed
  485. # [22:05] <Hixie> not propagation speed
  486. # [22:05] <Philip`> I guess you simply want sin(12*t1 - 0.5*3) = sin(12*t2 - 0.5*4), so 12*dt = 0.5 and dt=1/24 sec ( = 0.042ish)
  487. # [22:07] * Quits: zdobersek (n=zan@cpe-92-37-72-84.dynamic.amis.net) ("Leaving.")
  488. # [22:07] <Philip`> kind of skipping all the ideas about phase and sin not being invertable, because they make life complex
  489. # [22:07] <Philip`> *invertible
  490. # [22:08] * Quits: mlpug (n=mlpug@a91-156-60-235.elisa-laajakaista.fi) (Remote closed the connection)
  491. # [22:09] * Quits: roc (n=roc@121-72-178-31.dsl.telstraclear.net)
  492. # [22:10] <Philip`> (Perhaps it's more precise to state that the phase is 12t-0.5x and you want the phases to be equal at the two xs, rather than unjustifiedly asserting that the sins are equal)
  493. # [22:10] <gsnedders> Hixie: LF?
  494. # [22:10] <Hixie> lambda * f
  495. # [22:10] <gsnedders> Ah
  496. # [22:11] * gsnedders is probably meant to do this from the phase difference, seeming the first part of this subquestion was working that out
  497. # [22:12] * Quits: dglazkov_ (n=dglazkov@72.14.224.1) (Read error: 60 (Operation timed out))
  498. # [22:13] * Quits: dglazkov__ (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  499. # [22:13] <gsnedders> Actually, can it not be done more simply through v = f*lamba and v = s/t?
  500. # [22:14] * Joins: ray (i=ray@the.ug)
  501. # [22:17] <Philip`> gsnedders: Why do you doubt that it could be?
  502. # [22:17] <gsnedders> Philip`: That seems so much simpler than what you and Hixie were saying :P
  503. # [22:20] <Philip`> gsnedders: How is it simpler than saying 12*t1-0.5*3 = 12*t2-0.5*4? :-)
  504. # [22:21] * gsnedders shrugs
  505. # [22:22] <jgraham> Hixie: converting relative urls to absolute urls
  506. # [22:24] * Quits: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu) ("KVIrc 3.4.0 Virgo http://www.kvirc.net/")
  507. # [22:27] <Philip`> http://philip.html5.org/demos/microdata/demo.html - now with ugly buggy RDF output
  508. # [22:29] <Philip`> Hixie: "property value" is defined with "If the element also has an item attribute: The value is the item created by the element."
  509. # [22:29] <Philip`> Hixie: and the JSON thing says "Let value be the property value of element. If value is an element, then get the object for the element value, ..."
  510. # [22:30] <Philip`> which seems inconsistent; the first bit would have to say "The value is the element" instead, or something
  511. # [22:34] <gsnedders> Philip`: It can't have RDF output as RDF is an abstract concept :P
  512. # [22:43] * gsnedders has an awful lot of learn before the exam
  513. # [22:57] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  514. # [23:01] <Hixie> jgraham: oh. in JS or server-side?
  515. # [23:01] <Hixie> Philip`: yeah, i'll fix that, hold on
  516. # [23:04] <Hixie> Philip`: fixed (should be regenned in a few seconds)
  517. # [23:04] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  518. # [23:05] * Philip` discovers that it's a bad idea to leave Wireshark running in the background, collecting half a million packets and storing them all in RAM
  519. # [23:05] <jgraham> Hixie: Server side
  520. # [23:05] <Hixie> jgraham: ah. good luck. :-)
  521. # [23:05] <jgraham> :(
  522. # [23:07] <Philip`> Surely there's a standard Python library for manipulating URIs?
  523. # [23:07] <jgraham> Philip`: Yes, but it's getting the right base uri to resolve against and that sort of thing
  524. # [23:08] <jgraham> Also, I think in principle to conform with html5 I might need to implement document encoding dependent stuff
  525. # [23:08] <jgraham> which is a pity since I have no idea what the document encoding was
  526. # [23:09] <jgraham> (alhough I guess I can ind out if necessary)
  527. # [23:09] <jgraham> *find
  528. # [23:09] <Philip`> Hixie: If I have <link rel="alternate alternate stylesheet stylesheet">, should *all* the tokens get removed and replaced with "alternate-stylesheet"?
  529. # [23:10] <Philip`> jgraham: Hmm, I suggest not bothering with those details :-)
  530. # [23:10] <Hixie> Philip`: yes; i'll clarify
  531. # [23:10] <jgraham> I think I will ignore the encoding-dependant stuff for now
  532. # [23:11] * gsnedders doesn't like the µdata proposal
  533. # [23:11] <gsnedders> I'll send email when I have time, with some sort of alternative proposal
  534. # [23:11] <jgraham> Hixie: In general if I have <link rel="a a b b"> should it be handled the same as <link rel="a b">
  535. # [23:12] <Hixie> yeah
  536. # [23:12] <jgraham> if a,b!=up
  537. # [23:12] <jgraham> Oh that's good because that's what I implemented
  538. # [23:13] <Philip`> Nothing in the spec says to remove duplicates, as far as I can see, but I suppose RDF defines a graph with duplicate triples to be equivalent to one with the duplicates removed
  539. # [23:13] <gsnedders> Hixie: Short version: I'd prefer something closer to RDFa than the current draft, just without the insanity of RDFa.
  540. # [23:14] <Hixie> jgraham: updated the spec -- note the rel=up removal happens before duplicate removal
  541. # [23:14] <Hixie> jgraham: and duplicate removal, as Philip` points out, only matters for alternate stylesheet links
  542. # [23:14] <Hixie> gsnedders: your feedback or #swig's?
  543. # [23:14] <gsnedders> Hixie: mine
  544. # [23:14] <Hixie> what do you think is missing?
  545. # [23:15] <gsnedders> Hixie: There's nothing missing, it just seems to be reinventing the wheel for no reason.
  546. # [23:15] <Philip`> Hixie: If it contains >1 'up', then remove *all* 'up'? (Surely it should keep one?)
  547. # [23:15] <Hixie> gsnedders: i tried to stick as closely to RDFa as possible while fixing the problems mentioned in my e-mail
  548. # [23:16] <Hixie> Philip`: i can't see how to express the semantic of rel="up up" in rdf
  549. # [23:16] <Hixie> Philip`: without a complex set of bnodes
  550. # [23:16] <gsnedders> Hixie: As I said, I'll send something more substantial later
  551. # [23:16] <Hixie> gsnedders: cool
  552. # [23:16] <Philip`> Hixie: Oh, so it's intentionally ignored instead of being made equivalent to rel="up"?
  553. # [23:16] <Hixie> Philip`: yeah
  554. # [23:16] <Philip`> I suppose that makes some kind of sense
  555. # [23:16] <jgraham> gsnedders: I like the current draft in that I can imagine actually being able to author in it without wanting to kill people and then getting everything wrong anyway
  556. # [23:17] <gsnedders> Hixie: … that'll probably end up being an entire counter-proposal that nobody will agree with (SWIG people because it isn't RDFa and people here because you didn't write it :P)
  557. # [23:17] <Hixie> gsnedders: if you come up with something better, i'll agree with it :-)
  558. # [23:18] <Hixie> gsnedders: one of the difficult parts of designing the microdata syntax was getting the DOM API right
  559. # [23:18] <Hixie> still not sure i have it quite spot on
  560. # [23:18] <gsnedders> Hixie: See, I don't care about the DOM API :P
  561. # [23:18] <jgraham> gsnedders: So if you are going to write a counter-proposal please don't add lots of URIs and ways of marking up graphs of data
  562. # [23:18] <jgraham> gsnedders: Because they make everything too complicated
  563. # [23:18] <gsnedders> jgraham: How do we do anything related to RDF without doing the latter?
  564. # [23:19] <Hixie> what's RDF got to do with anything
  565. # [23:19] <jgraham> gsnedders: Like the current proposal?
  566. # [23:19] <Hixie> very few of these use cases involved having to do RDF
  567. # [23:19] <Hixie> and those that did are handled adequately by the RDF conversion section as far as I can tell
  568. # [23:19] <jgraham> gsnedders: I would much prefer a solution that hits the 80/20 point now and gets used than one that hits the 99/1 point now bu doesn't get used
  569. # [23:20] * gsnedders does find it odd that the proponents of RDF have always given specific use-cases for what they want to do, and not use-cases for generic semantics basically
  570. # [23:20] <gsnedders> s/basically.
  571. # [23:20] <gsnedders> s#.#//#
  572. # [23:20] <jgraham> Especially if the current solution can be extended to do more of the 20 later
  573. # [23:21] * Quits: virtuelv (n=virtuelv@084202133045.customer.alfanett.no) ("Ex-Chat")
  574. # [23:21] <Hixie> gsnedders: as far as i can tell, they only do the latter :-)
  575. # [23:21] <Hixie> (with a few exceptions)
  576. # [23:22] <Hixie> (like Manu)
  577. # [23:22] <gsnedders> Hixie: No, they say, "we want RDF", they don't give use-cases for wanting generic semantics
  578. # [23:22] <Hixie> (and some of the people on Shelley's blog)
  579. # [23:22] <Hixie> gsnedders: oh, right, yes
  580. # [23:22] <Hixie> i see what you mean
  581. # [23:22] <gsnedders> Hixie: If they want RDF and you ask for use-cases, I'd expect them to give use-cases for generic semantics, not for specific uses of these generic semantics
  582. # [23:23] <Hixie> yeah
  583. # [23:23] <Hixie> i have heard basically no reason for "generic semantics" as you put it
  584. # [23:23] <gsnedders> Generic semantics isn't a very good term…
  585. # [23:23] <gsnedders> Extensible semantics?
  586. # [23:23] <Hixie> microdata is extensible :-)
  587. # [23:23] <gsnedders> Needless to say, you know what I mean :P
  588. # [23:26] * gsnedders is unlikely to have time to really write any proposal until after at least his physics exam (in just under three weeks)
  589. # [23:26] * Philip` wonders why his router vanishes at 22:13, and doesn't come back until 07:14, and has done this for the past few days
  590. # [23:27] <Philip`> Hixie: You could make rel="up up" equivalent to rel="up-up" (and similar for "up up up" etc), so that it doesn't lose data
  591. # [23:27] * Quits: mpilgrim (n=mark@96.10.240.189) (Read error: 148 (No route to host))
  592. # [23:29] * Quits: Maurice (i=copyman@5ED548D4.cable.ziggo.nl) ("Disconnected...")
  593. # [23:32] * Quits: akamike (n=mikerobi@92.3.35.15)
  594. # [23:33] <Hixie> Philip`: *shrug*
  595. # [23:33] <Hixie> Philip`: not really the right semantic. and i don't want to make rel="up-up" equivalent. And what do you do with rel="up-up up"...
  596. # [23:34] <Hixie> really the right thing is to have a bnode
  597. # [23:34] <Hixie> <> <xhv:up> <_:a> . <_:a> <xhv:up> (href) .
  598. # [23:34] <Philip`> You do the same thing you do with rel="alternate-stylesheet stylesheet"
  599. # [23:34] <Hixie> true
  600. # [23:35] <Hixie> and with rel="http://www.w3.org/.../vocab#stylesheet"
  601. # [23:35] <Hixie> sigh
  602. # [23:57] * Quits: archtech (n=stanv@83.228.56.37)
  603. # Session Close: Mon May 11 00:00:00 2009

The end :)