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

Options:

  1. # Session Start: Mon May 11 00:00:00 2009
  2. # Session Ident: #whatwg
  3. # [00:09] * Joins: akamike (n=mikerobi@92.3.35.15)
  4. # [00:10] * Joins: csarven (n=csarven@modemcable150.182-202-24.mc.videotron.ca)
  5. # [00:10] * Quits: sid0 (n=sid0@unaffiliated/sid0) (Read error: 110 (Connection timed out))
  6. # [00:16] * Quits: akamike (n=mikerobi@92.3.35.15)
  7. # [00:20] * Joins: taf2 (n=taf2@c-68-49-245-59.hsd1.dc.comcast.net)
  8. # [00:21] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  9. # [00:21] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  10. # [00:24] * Joins: dglazkov_ (n=dglazkov@72.14.224.1)
  11. # [00:26] * Joins: Rik` (n=Rik@pha75-2-81-57-187-57.fbx.proxad.net)
  12. # [00:43] * Joins: doublec (n=doublec@202.0.36.64)
  13. # [00:44] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  14. # [00:44] * Joins: shepazu (n=schepers@modemcable003.225-21-96.mc.videotron.ca)
  15. # [00:58] * Quits: dglazkov_ (n=dglazkov@72.14.224.1)
  16. # [00:58] * Joins: nessy (n=nessy@124-171-63-74.dyn.iinet.net.au)
  17. # [01:10] * Joins: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com)
  18. # [01:14] * Quits: shepazu (n=schepers@modemcable003.225-21-96.mc.videotron.ca) (Read error: 104 (Connection reset by peer))
  19. # [01:15] * Joins: shepazu (n=schepers@modemcable003.225-21-96.mc.videotron.ca)
  20. # [01:16] * Joins: olliej (n=oliver@76.14.74.242)
  21. # [01:22] * Joins: akamike (n=mikerobi@92.3.35.15)
  22. # [01:26] * Quits: webben (n=benh@91.85.210.172) (Read error: 110 (Connection timed out))
  23. # [01:38] * Quits: drostie (n=hopkins@5354256F.cable.casema.nl) (Remote closed the connection)
  24. # [01:40] * Quits: karlcow (n=karl@nerval.la-grange.net) ("This computer has gone to sleep")
  25. # [01:50] * Joins: roc (n=roc@202.0.36.64)
  26. # [01:55] * Quits: heycam (n=cam@203-217-72-53.dyn.iinet.net.au) ("bye")
  27. # [01:58] * Quits: taf2 (n=taf2@c-68-49-245-59.hsd1.dc.comcast.net)
  28. # [01:59] * Quits: shepazu (n=schepers@modemcable003.225-21-96.mc.videotron.ca)
  29. # [02:01] * Joins: erlehmann (n=erlehman@86.59.25.121)
  30. # [02:10] * Parts: erlehmann (n=erlehman@86.59.25.121)
  31. # [02:14] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  32. # [02:15] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net) (Client Quit)
  33. # [02:15] <takkaria> things I don't get: people saying that html5:property conflicts with rdfa:property
  34. # [02:15] <takkaria> it explicitly doesn't afaics
  35. # [02:15] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  36. # [02:16] <Hixie> takkaria: if anyone can think of a better attribute name, i'm happy to change it, just to avoid the argument
  37. # [02:16] <Hixie> takkaria: but i agree that it's a bit weird for the rdfa guys to be complaining that html5 conflicts with their future plans
  38. # [02:16] <Hixie> it's just like when i complained that rdfa conflicted with our future plans :-)
  39. # [02:19] <takkaria> I mean, I get that RDFa people want to use RDFa
  40. # [02:20] <takkaria> but you can tell RDFa:property and html5:property apart using strchr(content, ":")
  41. # [02:20] * takkaria shrugs and goes off to do other things
  42. # [02:21] * Quits: akamike (n=mikerobi@92.3.35.15)
  43. # [02:22] <Hixie> takkaria: RDFa property is not in their own namespace
  44. # [02:22] <Hixie> oh, i misunderstood
  45. # [02:23] <Hixie> takkaria: they're saying they want to add new features that remove that distinction
  46. # [02:23] * Joins: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  47. # [02:33] * Joins: erlehmann (n=erlehman@86.59.25.121)
  48. # [02:37] * Quits: weinig (n=weinig@nat/apple/x-5d16ecde3b454783)
  49. # [02:42] * Quits: hdh (n=hdh@118.71.97.22) (Read error: 110 (Connection timed out))
  50. # [02:48] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 104 (Connection reset by peer))
  51. # [02:54] * Joins: taf2 (n=taf2@c-68-49-245-59.hsd1.dc.comcast.net)
  52. # [03:00] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  53. # [03:02] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  54. # [03:05] * Joins: heycam (n=cam@zot.infotech.monash.edu.au)
  55. # [03:14] * Quits: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  56. # [03:14] * Joins: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  57. # [03:22] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  58. # [03:28] * Joins: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  59. # [03:41] * Joins: wakaba_ (n=wakaba@EM114-51-157-163.pool.e-mobile.ne.jp)
  60. # [03:53] * Joins: ojan (n=ojan@203.39.247.241)
  61. # [03:54] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  62. # [03:55] * Quits: wakaba (n=wakaba@EM114-51-130-66.pool.e-mobile.ne.jp) (Read error: 104 (Connection reset by peer))
  63. # [04:32] * Joins: karlcow (n=karl@nerval.la-grange.net)
  64. # [04:42] * Quits: taf2 (n=taf2@c-68-49-245-59.hsd1.dc.comcast.net)
  65. # [04:59] * Joins: shepazu (n=schepers@modemcable203.65-70-69.static.videotron.ca)
  66. # [05:20] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  67. # [05:42] * Quits: olliej (n=oliver@76.14.74.242)
  68. # [05:43] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  69. # [05:43] * Joins: olliej (n=oliver@76.14.74.242)
  70. # [05:43] * Joins: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  71. # [05:55] * Quits: karlcow (n=karl@nerval.la-grange.net) ("This computer has gone to sleep")
  72. # [05:55] * Joins: slightlyoff (n=slightly@204.14.154.244)
  73. # [05:56] * Quits: slightlyoff (n=slightly@204.14.154.244) (Remote closed the connection)
  74. # [06:22] * Joins: harig (n=opera@59.90.71.35)
  75. # [06:43] * Joins: karlcow (n=karl@nerval.la-grange.net)
  76. # [06:55] * Quits: roc (n=roc@202.0.36.64)
  77. # [06:55] * Joins: roc (n=roc@202.0.36.64)
  78. # [07:00] * Quits: csarven (n=csarven@modemcable150.182-202-24.mc.videotron.ca) ("Leaving.")
  79. # [07:02] * Joins: ojan_ (n=ojan@203.39.247.241)
  80. # [07:03] * Quits: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  81. # [07:05] * Joins: hdh (n=hdh@118.71.97.22)
  82. # [07:06] * Quits: ojan (n=ojan@203.39.247.241) (Read error: 60 (Operation timed out))
  83. # [07:16] * Joins: sid0 (n=sid0@unaffiliated/sid0)
  84. # [07:17] * Joins: dimich (n=dimich@c-98-203-230-54.hsd1.wa.comcast.net)
  85. # [07:28] * Quits: ojan_ (n=ojan@203.39.247.241)
  86. # [07:34] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  87. # [07:44] * Quits: doublec (n=doublec@202.0.36.64) (Read error: 110 (Connection timed out))
  88. # [07:50] * Joins: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  89. # [07:56] * Joins: pesla (n=retep@procurios.xs4all.nl)
  90. # [08:01] * Quits: roc (n=roc@202.0.36.64)
  91. # [08:02] <MikeSmith> what does the spec say about a case where a form has two controls with the same name?
  92. # [08:03] <MikeSmith> as far as I can see, it does not disallow a form to have multiple name instances
  93. # [08:04] <MikeSmith> parts of a form to have the same name
  94. # [08:04] * Quits: onar_ (n=onar@c-98-234-65-251.hsd1.ca.comcast.net)
  95. # [08:07] <MikeSmith> ah, ignore me
  96. # [08:08] <MikeSmith> I realize there are of course cases where certain controls need to have the same name
  97. # [08:10] * Joins: weinig_ (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  98. # [08:11] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
  99. # [08:12] * weinig_ is now known as weinig
  100. # [08:15] * Joins: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  101. # [08:17] * Joins: ojan (n=ojan@203.39.247.241)
  102. # [08:26] <erlehmann> MikeSmith, i think name is obsolete?
  103. # [08:27] * Quits: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au) ("Tomorrow to fresh woods, and pastures new.")
  104. # [08:30] * Joins: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  105. # [08:30] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  106. # [08:30] * Quits: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au) (Remote closed the connection)
  107. # [08:34] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  108. # [08:36] * Quits: dimich (n=dimich@c-98-203-230-54.hsd1.wa.comcast.net)
  109. # [08:36] * Joins: KevinMarks (n=KevinMar@c-71-202-163-211.hsd1.ca.comcast.net)
  110. # [08:37] * Joins: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  111. # [08:39] * Joins: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl)
  112. # [08:41] * Joins: dimich (n=dimich@c-98-203-230-54.hsd1.wa.comcast.net)
  113. # [08:44] * Joins: maikmerten (n=merten@ls5dhcp196.cs.uni-dortmund.de)
  114. # [08:46] * Quits: dimich (n=dimich@c-98-203-230-54.hsd1.wa.comcast.net)
  115. # [08:49] * Quits: hdh (n=hdh@118.71.97.22) (Remote closed the connection)
  116. # [08:53] <MikeSmith> erlehmann: I was meaning to refer to the name attribute on various form controls
  117. # [08:58] * Parts: erlehmann (n=erlehman@86.59.25.121)
  118. # [09:05] * Joins: philipj (n=philipj@pat.se.opera.com)
  119. # [09:08] * Quits: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  120. # [09:23] * Quits: olliej (n=oliver@76.14.74.242)
  121. # [09:25] <Philip`> Hixie: You're not allowed to rename property now, there's already two legacy implementations!
  122. # [09:26] <Hixie> hah
  123. # [09:27] * Philip` can't think of any names other than "key"
  124. # [09:28] <zcorpan_> Hixie: the microdata solution and the <dl> example gives more reason to introduce <di> (you duplicate the <dt> content in <dd><meta>)
  125. # [09:28] * Quits: weinig (n=weinig@c-67-180-35-124.hsd1.ca.comcast.net)
  126. # [09:29] <Hixie> zcorpan_: yeah, i did notice that this made <di> have a reason for being
  127. # [09:29] <Hixie> was hoping no-one else would notice too :-P
  128. # [09:29] * zcorpan_ replies :)
  129. # [09:36] * Quits: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au) (Read error: 104 (Connection reset by peer))
  130. # [09:45] <zcorpan_> Hixie: will <link rel="alternate stylesheet" ...> and <link rel="alternate-stylesheet"> produce the same RDF output?
  131. # [09:46] <zcorpan_> s/">/" ...>/
  132. # [09:46] * Joins: wakaba (n=wakaba@EM114-51-29-42.pool.e-mobile.ne.jp)
  133. # [09:47] <zcorpan_> <p property="com.damowmow.desc">Siamese color-point.
  134. # [09:47] <zcorpan_> <img property="com.damowmow.img" alt="" src="/images/erwin.jpeg">
  135. # [09:47] <zcorpan_> Hixie: was the img intended to be a child of the p?
  136. # [09:53] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  137. # [09:57] <zcorpan_> Philip`: item=" " generates two types in your impl (both empty string)
  138. # [10:01] * Quits: heycam (n=cam@zot.infotech.monash.edu.au) ("bye")
  139. # [10:03] * Quits: wakaba_ (n=wakaba@EM114-51-157-163.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  140. # [10:03] * Quits: deltab (n=deltab@82-36-30-34.cable.ubr02.smal.blueyonder.co.uk) (Read error: 110 (Connection timed out))
  141. # [10:04] * Joins: deltab (n=deltab@82-36-30-34.cable.ubr02.smal.blueyonder.co.uk)
  142. # [10:04] * Quits: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com) (Read error: 110 (Connection timed out))
  143. # [10:05] <Philip`> zcorpan_: Possibly fixed now
  144. # [10:06] * Quits: webben_ (n=benh@dip5-fw.corp.ukl.yahoo.com) (Read error: 104 (Connection reset by peer))
  145. # [10:06] * Joins: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  146. # [10:07] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  147. # [10:07] <Hixie> zcorpan_: yes, they'll produce the same output.
  148. # [10:07] <jgraham> Ah so, unsurprisingly, "I cannot live with" has become a magic phrase
  149. # [10:07] <Hixie> zcorpan_: not sure what to do about it. (so will <link rel="http://..../#alternate-stylesheet">)
  150. # [10:08] <zcorpan_> Hixie: (true)
  151. # [10:09] <zcorpan_> maybe it's not a problem
  152. # [10:09] <Hixie> i think it is
  153. # [10:09] <zcorpan_> Philip`: yep, cool
  154. # [10:09] <Hixie> but i don't know what to do about it
  155. # [10:09] <Hixie> short of making those explicitly non-conforming, but even then
  156. # [10:10] <zcorpan_> can you produce a URL that cannot be produced otherwise?
  157. # [10:10] <Hixie> not as far as i can tell
  158. # [10:10] <zcorpan_> #alternate stylesheet
  159. # [10:10] <zcorpan_> with a space :)
  160. # [10:12] <Philip`> #ALTERNATE-STYLESHEET
  161. # [10:12] <Hixie> zcorpan_: heh
  162. # [10:12] <Hixie> Philip`: you can still do that as a url, right?
  163. # [10:13] <Philip`> Hixie: No, because they're lowercased first
  164. # [10:13] <Philip`> (I think)
  165. # [10:13] * Joins: erlehmann (n=erlehman@86.59.25.121)
  166. # [10:14] <Hixie> Philip`: urls are? that's a problem if so
  167. # [10:14] <Hixie> i don't intend urls to be lowercased
  168. # [10:15] <Philip`> "split the value of the element's rel attribute on spaces, obtaining list of tokens. Convert each token in list of tokens to lowercase."
  169. # [10:15] <jgraham> Hixie: BTW, as a general comment it is rather confusing when the spec uses "lowercase" to mean "ascii only lowercase"
  170. # [10:15] <jgraham> (I know it is defined and there is alink and everything, but it is still confusing)
  171. # [10:16] <Hixie> jgraham: file a bug, i can change that terminology easily enough
  172. # [10:16] * Philip` wonders if he's badly confused about things
  173. # [10:16] <Philip`> Hixie: As far as I can see, rel="http://..." will never produce any triples at all
  174. # [10:17] <Philip`> (because there's only "For each token token in list of tokens that contains neither a U+003A COLON character (:) nor a U+002E FULL STOP character (.), generate the following triple:")
  175. # [10:17] * zcorpan_ just noticed that Philip`'s impl didn't generate a triple for urls
  176. # [10:18] * Philip` notes that his implementation does not attempt to be perfectly correct
  177. # [10:18] <Philip`> (but if there are things that are easy to fix then I can fix them)
  178. # [10:19] * Quits: harig (n=opera@59.90.71.35) (Read error: 104 (Connection reset by peer))
  179. # [10:19] <Hixie> Philip`: oh right, for rel="" it's only values, i forgot
  180. # [10:19] <Hixie> Philip`: ok, will use uppercase
  181. # [10:27] * zcorpan_ updates html5-elements
  182. # [10:27] <Hixie> Philip`: done
  183. # [10:33] * zcorpan_ notes that the order is different in the Amanda examples, in Philip`'s impl
  184. # [10:36] <jgraham> zcorpan_: Order of hat?
  185. # [10:37] <jgraham> Argh. "what"
  186. # [10:37] <zcorpan_> jgraham: the "band" and "name" properties
  187. # [10:37] <zcorpan_> "In this example, the outer item represents a person, and the inner one represents a band:"
  188. # [10:37] <zcorpan_> and "This example is the same as the previous one, but all the properties are separated from their items:"
  189. # [10:38] <zcorpan_> Hixie: you could either move the second div to below the name paragraph or clarify that the order of the properties will be different
  190. # [10:38] <Philip`> Properties have no order
  191. # [10:38] <Philip`> (in the JSON version, at least)
  192. # [10:38] <jgraham> What Philip` said
  193. # [10:39] <zcorpan_> ok
  194. # [10:39] <Philip`> The output order is just an irrelevant artifact of the JS Object implementation and of the JSON serialiser
  195. # [10:39] <jgraham> At least I hope that is true because if if is, it's much easier to come up with nice API design
  196. # [10:40] * Joins: heycam (n=cam@203-217-72-53.dyn.iinet.net.au)
  197. # [10:40] <jgraham> And if it's not, my implementation is wrong :)
  198. # [10:41] <zcorpan_> the order of attributes in html is also supposed to be irrelevant, but browsers still have to represent them in the source order to plugins for web compat
  199. # [10:42] <zcorpan_> iirc
  200. # [10:42] <jgraham> zcorpan_: Right. But hopefully this case is different
  201. # [10:43] <Philip`> Hixie: The first example in the spec using 'getItem' looks a little broken
  202. # [10:43] <Philip`> (at least in the multipage version)
  203. # [10:43] <zcorpan_> it's only different until people start to rely on the order of a popular implementation
  204. # [10:43] <Philip`> because it does "i < something" instead of "i &lt; something"
  205. # [10:44] <Philip`> If all implementations implement it in the way the spec describes, they'll give the same order for the same input
  206. # [10:44] <Philip`> so there's no problem
  207. # [10:44] * Joins: mat_t (n=mattomas@nat/canonical/x-62a6a02782e07464)
  208. # [10:44] <Philip`> (and it doesn't matter that different inputs give different orders)
  209. # [10:44] <jgraham> Actually I think I would prefer it if the DOM APIs were unordered
  210. # [10:44] * jgraham hadn't really looked at those
  211. # [10:45] <Philip`> (and since the order is an implementation detail (though one that may be constrained by compatibility concerns), it can be ignored in the introduction section)
  212. # [10:45] <Philip`> jgraham: You don't want to allow enumeration of properties?
  213. # [10:45] <zcorpan_> Philip`: it's a problem for implementations that assume that the order is irrelevant and do optimzations that will change the order
  214. # [10:46] <jgraham> Philip`: Yeah, not sure what to do about enumeration
  215. # [10:46] <jgraham> But having IndexGetter seems bad
  216. # [10:47] <jgraham> Since that just encourages people to rely on order
  217. # [10:47] <Philip`> Having IndexGetter seems good, because it's a useful feature
  218. # [10:47] <Philip`> and the spec could just require implementations to sort properties alphabetically, or whatever
  219. # [10:47] <jgraham> (enumeration seems very useful and as along as it is clearly stated that the order is arbitary, maybe it's not a problem)
  220. # [10:48] <jgraham> Philip`: Why?
  221. # [10:48] <jgraham> (is IndexGetter useful?)
  222. # [10:48] <Philip`> jgraham: Um, because I failed to understand what IndexGetter is
  223. # [10:48] <zcorpan_> Philip`: sorting alphabetically would have worked but is too late for html attributes
  224. # [10:48] <Philip`> and I was just thinking of enumeration
  225. # [10:48] <Hixie> the collections are ordered in tree order
  226. # [10:48] <zcorpan_> Philip`: still not too late for microdata :)
  227. # [10:49] <Hixie> zcorpan_: not sure what you mean about the divs earlier
  228. # [10:49] <jgraham> Hixie: Enforcing ordering is bad if you want to back the implementation with a hash table
  229. # [10:49] <zcorpan_> Hixie: <div subject="amanda" property="band" item id="jazzband"></div> starts the "band" property before seeing the "name" property
  230. # [10:49] <zcorpan_> Hixie: so the order is different from the previous example
  231. # [10:50] <Hixie> jgraham: collections are already ordered in the rest of the platform, so it won't need new code as far as i can tell
  232. # [10:50] <Hixie> zcorpan_: hm, yeah, might be best to not have that change
  233. # [10:50] <Hixie> Philip`: uppercased and fixed < issue
  234. # [10:50] <jgraham> Hixie: But this is something that non-browsers are likely to implement
  235. # [10:51] <jgraham> So having a requirement to be ordered also burdens them
  236. # [10:51] <Philip`> Interoperability between non-browsers seems unimportant
  237. # [10:51] <Hixie> jgraham: the dom api? i doubt it. why would they use that api? it's got all kinds of weird JSisms
  238. # [10:51] <Philip`> since the problem is just when two browsers run one script that makes assumptions that are only valid in one
  239. # [10:52] <Philip`> whereas it seems unlikely anyone will run the same code on two non-browser implementations and expect them to be identical
  240. # [10:52] * Joins: webben (n=benh@nat/yahoo/x-d4770dbb3271a1e5)
  241. # [10:52] <jgraham> Hixie: I guess if it only applies to the DOM API then I can't really object. I don't want people to have the general idea that items are ordered collections of name:value pairs
  242. # [10:53] <jgraham> s/I/I just/
  243. # [10:57] * Joins: roc (n=roc@121-72-178-31.dsl.telstraclear.net)
  244. # [10:59] <Hixie> jgraham: maybe we should define some other api for other languages or something to prevent people from trying to implement it outside the dom
  245. # [10:59] <Hixie> jgraham: or maybe if html5lib gets an api for it and we publicise that, people will try to duplicate that one and it won't be an issue
  246. # [11:00] <Hixie> jgraham: i'm happy to put something in the spec if you think it'd help
  247. # [11:00] <jgraham> Hixie: Not worth worrying about at this point, I guess
  248. # [11:01] <Hixie> k
  249. # [11:01] * zcorpan_ wonders whether the microdata solution will get bad press because of its name cf predefined class names vs microformats before
  250. # [11:04] <Hixie> I'm happy to rename it if anyone has a better idea
  251. # [11:04] <Hixie> i wasn't really intending to call it "microdata", that's just what it is
  252. # [11:06] <zcorpan_> HRDF?
  253. # [11:06] <zcorpan_> i.e. Hixie-RDF
  254. # [11:07] * Joins: drostie (n=hopkins@wlan-145-94-168-221.wlan.tudelft.nl)
  255. # [11:07] <Hixie> heh
  256. # [11:07] <Hixie> it's not RDF per se
  257. # [11:08] <Hixie> any more than it is JSON or whatever
  258. # [11:08] <zcorpan_> that doesn't really matter :)
  259. # [11:09] <Hixie> it matters a little!
  260. # [11:09] <jgraham> FWIWW microdata seems like a totally fine name to me
  261. # [11:10] * Quits: ojan (n=ojan@203.39.247.241)
  262. # [11:11] <Philip`> I don't understand why it's micro
  263. # [11:11] <Hixie> tiny bits of data
  264. # [11:11] * zcorpan_ wonders whether document.items and element.item will clash with web pages' scripts
  265. # [11:11] <Hixie> zcorpan_: :-/ hope not, hard to know ahead of time though
  266. # [11:11] <Philip`> Hixie: But it could be big bits of data, and lots of them
  267. # [11:12] <Hixie> Philip`: they can't really be that big, while still being useful.
  268. # [11:12] <Hixie> granted there could be many
  269. # [11:12] <Hixie> not sure how that stops them being small though :-)
  270. # [11:12] <Philip`> I suppose the most prominent feature is that it's data embedded into the markup, but a term like "embedded data" doesn't sound great to me
  271. # [11:12] <zcorpan_> <html item>
  272. # [11:13] <Philip`> Hixie: Any data could be viewed as a collection of lots of small bits of data, so that's hardly unique to the microdata proposal :-)
  273. # [11:13] <zcorpan_> i think it's primary feature is that it's easily extractable data while ignoring other content
  274. # [11:14] <zcorpan_> so maybe "Easily Extractable Data" (EED)
  275. # [11:14] <Philip`> zcorpan_: If that was the primary feature, you could use <script type="text/json">easily extractable data in JSON form</script> which would be much easier
  276. # [11:14] <Philip`> It's more significant that it's mixed up with the markup
  277. # [11:14] <zcorpan_> Philip`: "Embeeded Easily Extractable Data" (EEED)
  278. # [11:15] <zcorpan_> s/e/d//
  279. # [11:15] <zcorpan_> er
  280. # [11:15] <zcorpan_> s#/##
  281. # [11:15] * Parts: erlehmann (n=erlehman@86.59.25.121)
  282. # [11:15] <Hixie> zcorpan_: i don't like naming things in a way that presumes that a design criteria was successfully met ("easily")
  283. # [11:16] <Philip`> Call it Embedded Data With A Related Dom api, or Edward for short
  284. # [11:16] <Hixie> zcorpan_: because too often i have seen technologies called something like that only to have failed at that goal, and it just makes them easy targets for jokes :-)
  285. # [11:16] <Hixie> Philip`: heh
  286. # [11:16] <zcorpan_> Edward is a good name :)
  287. # [11:17] <zcorpan_> though the data-* stuff is also embedded data with a dom api
  288. # [11:18] <Philip`> Web Data
  289. # [11:18] * Joins: archtech (n=stanv@83.228.56.37)
  290. # [11:22] * Joins: ROBOd (n=robod@89.122.216.38)
  291. # [11:22] * Quits: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl) ("Disconnected...")
  292. # [11:23] <Philip`> Semantic Web 2.0
  293. # [11:24] <Philip`> By the way, implementing the RDF/N3 output thing made me dislike prefixes, because I couldn't work out what prefixes to use
  294. # [11:24] <Philip`> Searching for http://purl.org/dc/terms/ suggested that people use a random mixture of dcterms:, dct: and dc:
  295. # [11:25] <Philip`> and I don't like having to make uneducated choices between such things
  296. # [11:25] <zcorpan_> Philip`: randomize which prefix to use
  297. # [11:25] <Hixie> prefixes are a disaster. When I'm forced to use them I intentionally mint new ones like "a", "b", "c", etc.
  298. # [11:25] <Hixie> to prevent people from thinking they have special meanings.
  299. # [11:27] <jgraham> I think I will implement rdf output using rdflib (assuming I can work out how to use it). Hopefully that will give me magic random prefixes
  300. # [11:30] * zcorpan_ wonders whether form controls with microdata was considered
  301. # [11:31] <Philip`> I guess the conflict is between the viewpoint in which prefixes are just a syntactic shortcut (and so you can use whichever prefix you fancy, and there's no need to standardise them or have any conventions or design them carefully), and the viewpoint in which they're critical to human understanding of the data (since people think of them as being names with a colon in the middle, and try to use consistent meaningful prefixes, etc)
  302. # [11:31] * Joins: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl)
  303. # [11:31] <Philip`> It'd be fine if it was all one way, or all the other way
  304. # [11:33] <zcorpan_> Hixie: <input type=image src=foo property=bar>
  305. # [11:33] <Philip`> (e.g. if humans thought at that level of abstraction, or if humans never had to look at prefixes at all; or (the other way) if the prefixes really were just part of the name and were standardised etc)
  306. # [11:33] <Hixie> zcorpan_: <input> always uses the textContent
  307. # [11:33] <Hixie> zcorpan_: there were no use cases that needed form controls to be usefully linked into the microdata system
  308. # [11:34] <zcorpan_> i'm sure someone can mint a use case for that :)
  309. # [11:34] <Philip`> That could be a nice way of submitting structured data to a server
  310. # [11:35] * Joins: wakaba_ (n=wakaba@EM114-51-162-132.pool.e-mobile.ne.jp)
  311. # [11:35] <Hixie> not really
  312. # [11:35] <Philip`> without having to come up with unique names for every single input control in your page, and reconstructing that back into a tree structure on the server
  313. # [11:35] <Hixie> user input rarely maps directly to structured data schemas
  314. # [11:36] <Philip`> (particularly if the form controls are generated automatically, like in repetition templates)
  315. # [11:50] * Quits: wakaba (n=wakaba@EM114-51-29-42.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  316. # [11:56] * Joins: pauld (n=pauld@194.102.13.6)
  317. # [11:58] <zcorpan_> Hixie: maybe you could solve the naming/RDFa conflict debate and solve the potential Web script incompatibility problem by prefixing all relevant attributes with something
  318. # [12:01] <Hixie> any ideas?
  319. # [12:01] <zcorpan_> data- is taken :P
  320. # [12:02] <Hixie> indeed
  321. # [12:02] <zcorpan_> though data-* isn't much used yet so could be redesigned
  322. # [12:02] <zcorpan_> not that there's anything wrong with data-*
  323. # [12:04] <zcorpan_> "rdf"
  324. # [12:05] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  325. # [12:05] <zcorpan_> <div rdfitem><span rdfproperty="name">, document.rdfItems, element.rdfContent etc
  326. # [12:05] * jgraham wonders if that is supposed to be a serious suggestion
  327. # [12:05] <Hixie> as noted before, this doesn't really have any more to do with rdf than json or anything else :-)
  328. # [12:06] <jgraham> Because it seems like a really bad idea :)
  329. # [12:06] <zcorpan_> Hixie: as noted before, that only matters a little
  330. # [12:06] <zcorpan_> jgraham: why is it bad?
  331. # [12:06] <Hixie> zcorpan_: :-P
  332. # [12:07] <jgraham> If you really want prefixes it should be really short like md-property
  333. # [12:07] <Philip`> Prefix all the names with µ
  334. # [12:07] <Hixie> it matters enough, imho
  335. # [12:07] <Hixie> Philip`: html attributes have to be ascii
  336. # [12:07] <zcorpan_> "md-" could work
  337. # [12:07] <Hixie> Philip`: (to make hsivonen happy)
  338. # [12:07] <zcorpan_> though it's no shorter than "rdf" :)
  339. # [12:07] <Hixie> md- is ugly
  340. # [12:08] <jgraham> zcorpan_: Because this isn't a generic RDF serialisation and all dong things that irritate the RDF people even more will not help anyone
  341. # [12:08] <Philip`> Hixie: Prefix them with org.whatwg.microdata-
  342. # [12:08] <Hixie> hah
  343. # [12:08] <jgraham> Plus it is silly to put rdf on a pedestal
  344. # [12:08] <Philip`> jgraham: "and all dong things"?
  345. # [12:09] * Philip` 's error-correcting parser fails
  346. # [12:09] <jgraham> Philip`: s/all dong/doing/
  347. # [12:09] <Philip`> Ah
  348. # [12:09] <jgraham> I guess I started a different clause
  349. # [12:09] <jgraham> Hixie: md- is indeed ugly but anything longer than about 2-3 characters is irritating
  350. # [12:10] <Hixie> 0 characters works for me :-)
  351. # [12:10] * jgraham would prefer no prefix, really
  352. # [12:10] * zcorpan_ is slightly scared about web compat
  353. # [12:10] * Joins: doublec (n=doublec@118-93-168-138.dsl.dyn.ihug.co.nz)
  354. # [12:10] <zcorpan_> cf formaction=""
  355. # [12:11] <Philip`> zcorpan_: Unintentional uses of the attributes won't cause UAs to misbehave
  356. # [12:11] <zcorpan_> Philip`: i guess
  357. # [12:11] <Hixie> zcorpan_: let's address it when it's a problem
  358. # [12:11] * Joins: virtuelv (n=virtuelv@213.236.208.247)
  359. # [12:12] <jgraham> It seems really unlikely that anyone is using the attributes in just the way needed to produce spurious microdata
  360. # [12:12] <zcorpan_> but it might make it hard to use on existing pages that already have <div id="item"> or something
  361. # [12:12] <Philip`> (http://philip.html5.org/data/attr-count-pages-dotbot.txt suggests most of the attributes aren't used too frequently
  362. # [12:13] <Philip`> )
  363. # [12:13] <zcorpan_> Philip`: the concern is about scripts having document.items matching <div id="items"> etc
  364. # [12:14] <Philip`> Oh, okay
  365. # [12:14] <zcorpan_> so implementing the dom api might make existing pages to stop working
  366. # [12:15] * Quits: mat_t (n=mattomas@nat/canonical/x-62a6a02782e07464) ("Leaving")
  367. # [12:20] <Hixie> we can always make id=items overwrite .items
  368. # [12:25] <Philip`> id="items" is about the 1209th most common value
  369. # [12:26] <Philip`> (on 355 out of ~425K pages)
  370. # [12:30] * Quits: virtuelv (n=virtuelv@213.236.208.247) (Read error: 113 (No route to host))
  371. # [12:32] <Hixie> ok, intro section at http://www.whatwg.org/specs/web-apps/current-work/#microdata is written
  372. # [12:33] <Hixie> it doesn't cover everything, and i'll add more examples later
  373. # [12:33] <Hixie> but it covers the basics
  374. # [12:36] <Philip`> "favorite-color" - urgh :-(
  375. # [12:38] <Philip`> "A valid reversed DNS identifier is a string that consists of a series of IDNA labels in reverse order (i.e. starting with the top-level domain), the prefix of which, when reversed and converted to ASCII, corresponds to a registered domain."
  376. # [12:38] <Philip`> but e.g. org.example.name is unlikely to correspond (directly) to a registered domain
  377. # [12:39] <Philip`> (since it'd be silly to register a subdomain for every single property you ever use)
  378. # [12:39] <Philip`> Oh
  379. # [12:39] <Philip`> I might have missed the bit saying "prefix"
  380. # [12:39] <Philip`> Seems a confusing definition since it's not at all clear what the prefix of "org.example.name" is
  381. # [12:40] <Philip`> "Types are identified in three ways:" - I only count two
  382. # [12:48] <Hixie> all the lists of ways you can identify things have "predefined types" commented out
  383. # [12:48] <Hixie> will fill that in later this week (maybe tomorrow)
  384. # [12:49] <Hixie> not sure how to fix the reversed dns identifier definition to be easier to understand
  385. # [12:49] * Joins: Hish (n=chatzill@mail2.n-e-s.de)
  386. # [12:49] <Hixie> bet time now
  387. # [12:49] <Hixie> nn
  388. # [12:50] <Hish> hi. is there a special tag which would help me to display page numbers, date, author, or filename on each page? can I use header/footer for this or is there something else? thanks.
  389. # [12:52] <zcorpan_> Hish: you mean when printed?
  390. # [12:54] <Hish> zcorpan_: yes
  391. # [12:56] <zcorpan_> Hish: i think you can do it with css but browser support is probably flaky
  392. # [12:57] <zcorpan_> Hish: position:fixed will repeat things on every page but might not be suitable for proper page headers
  393. # [12:57] <zcorpan_> Hish: see printed media, generated content and css3
  394. # [12:58] <jgraham> You might b e able to get it working using Prince
  395. # [12:58] <Hish> zcorpan_: thx. so the bottomline is that this is CSS related and there are no special tags for this.
  396. # [12:58] <Hish> Prince???
  397. # [12:59] <zcorpan_> Prince is a piece of software that is used to generate the PDF version of the html5 spec
  398. # [12:59] <zcorpan_> supports this kind of stuff
  399. # [13:00] * Quits: drostie (n=hopkins@wlan-145-94-168-221.wlan.tudelft.nl) (Remote closed the connection)
  400. # [13:00] <jgraham> Generally it's a HTML+CSS -> PDF converter
  401. # [13:01] * sid0 is now known as sid0|brb
  402. # [13:02] <Hish> is it a proposal or an already working piece of code?
  403. # [13:02] <zcorpan_> the latter
  404. # [13:02] <Hish> sorry. forget it. didn't read your last comment, zcorpan_
  405. # [13:03] <Hish> do you have a url?
  406. # [13:03] * sid0|brb is now known as sid0
  407. # [13:05] <jgraham> http://www.princexml.com/
  408. # [13:07] * Quits: danbri (n=danbri@unaffiliated/danbri)
  409. # [13:18] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  410. # [13:21] * Joins: harig (n=opera@59.90.71.35)
  411. # [13:25] * Quits: webben (n=benh@nat/yahoo/x-d4770dbb3271a1e5) (Read error: 110 (Connection timed out))
  412. # [13:53] <zcorpan_> Hixie: "This example creates a big list with a nested list for each item on the page, each with of all the property names used in that item./p>" markup typo
  413. # [13:53] * Joins: Lachy (n=Lachlan@121.217.132.251)
  414. # [13:54] * Joins: drostie (n=hopkins@wlan-145-94-168-206.wlan.tudelft.nl)
  415. # [13:54] <zcorpan_> a markup error that a validator wouldn't catch :(
  416. # [13:55] <zcorpan_> nor a spell-checker, presumably
  417. # [13:55] <Philip`> But you'd catch it when reading the page
  418. # [13:56] <zcorpan_> Philip`: after having done markup validation, you'd expect you would have caught all markup errors
  419. # [13:59] <zcorpan_> maybe a validator could issue a warning if there was a ">" before an implied tag, or similar
  420. # [13:59] <jgraham> zcorpan_: Your expectation would be wrong, however
  421. # [13:59] <zcorpan_> clearly
  422. # [14:00] <zcorpan_> i'd like to know if it's possible to make it right a bit more often, though
  423. # [14:00] * jgraham wonders ho "kind" means something like "property"
  424. # [14:00] <jgraham> *how
  425. # [14:01] * Philip` looks for synonyms
  426. # [14:01] <Philip`> We could replace it with the "realestate" attribute
  427. # [14:02] <Philip`> Since we already have a "subject" attribute, property could be renamed to "predicate"
  428. # [14:03] <jgraham> Philip`: Noooooooooooooooooooo
  429. # [14:04] <Philip`> Since the attribute is determining how the value is related to the item, it could be called "rel"
  430. # [14:04] <jgraham> Tip 1 for writing a usable markup language: don't use natural language words that most native speakers of the natural langauge don't understand
  431. # [14:05] <jgraham> as part of the language
  432. # [14:07] <Philip`> Everyone should know what predicates are! You can't even do higher-order logic without them
  433. # [14:07] <jgraham> Oh noes!
  434. # [14:07] <jgraham> As gsnedders would say]
  435. # [14:09] * Joins: taf2 (n=taf2@38.99.201.242)
  436. # [14:10] <zcorpan_> Philip`: your impl doesn't generate a triple for the <title>
  437. # [14:12] <Philip`> zcorpan_: See line 186 or thereabouts
  438. # [14:12] <Philip`> // TODO: title
  439. # [14:13] * Joins: myakura (n=myakura@p3087-ipbf6705marunouchi.tokyo.ocn.ne.jp)
  440. # [14:14] * zcorpan_ notes that RDF uses title.textContent while document.title uses just the <title>s child text nodes
  441. # [14:14] * Joins: webben (n=benh@nat/yahoo/x-659ba78708484358)
  442. # [14:19] <Philip`> zcorpan_: (Added title)
  443. # [14:19] * Quits: pauld (n=pauld@194.102.13.6)
  444. # [14:20] * Joins: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  445. # [14:21] <zcorpan_> Philip`: i get <> dct:title "HTML 5 microdata demo" . regardless of what i write as input
  446. # [14:22] <Philip`> zcorpan_: That's because that's the first title element on the page
  447. # [14:22] <zcorpan_> Philip`: maybe you could use an iframe?
  448. # [14:23] <Philip`> zcorpan_: Then I'd have to figure out how to make jQuery give me elements from within that iframe instead of the current document
  449. # [14:24] <zcorpan_> Philip`: you could replace title[0] with title[1]
  450. # [14:25] <Philip`> zcorpan_: I'd prefer to be implementing what the spec says, so any bugs are in the demo setup rather than in the parser code
  451. # [14:28] * Joins: hendry (n=hendry@webvm.net)
  452. # [14:29] <zcorpan_> Philip`: btw http://simon.html5.org/tools/js/innerhtml-viewer/getInnerHTML.js has an ascii-lowercase function
  453. # [14:34] <jgraham> function toAsciiLowerCase(input) {return input.replace(/[A-Z]/g, function(char) {return char.toLowerCase()})}
  454. # [14:36] <Philip`> Hmph, '_:n2 c:org.w3.name "HTML5" .' isn't valid because it's not a proper QName
  455. # [14:37] <Philip`> or something like that
  456. # [14:37] <Philip`> http://www.rdfabout.com/demo/validator/ complains "Invalid token" so I assume it's right and I'm wrong
  457. # [14:39] * Quits: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Success)
  458. # [14:40] * jgraham wwonders how he got spidermonkey to fill up empty array elements with characters
  459. # [14:40] <jgraham> doing something like ["a", "b"].concat(["c",,"d"])
  460. # [14:41] * Joins: pauld (n=pauld@194.102.13.6)
  461. # [14:49] <Philip`> N3 output should now be correcter
  462. # [14:50] <Philip`> and conciser
  463. # [14:50] <Philip`> except for the bits that had to become verboser in order to be correcter
  464. # [14:54] * Joins: aja (n=aja@70.230.182.121)
  465. # [14:55] <zcorpan_> c:org.w3.name is not a proper QName?
  466. # [14:56] <Philip`> It's not a proper "QName or something like that", where the "something" is (([A-Z_a-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿‌-‍⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�𐀀-󯿿][\-0-9A-Z_a-z·À-ÖØ-öø-ͽͿ-῿‌-‍‿-⁀⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�𐀀-󯿿]*)?:)?[A-Z_a-zÀ-ÖØ-öø-˿Ͱ-ͽͿ-῿‌-‍⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�𐀀-󯿿][\-0-9A-Z_a-z·À-ÖØ-öø-ͽͿ-῿‌-‍‿-⁀⁰-↏Ⰰ-⿯、-퟿豈-﷏ﷰ-�𐀀-󯿿]*
  467. # [14:56] <Philip`> according to http://www.w3.org/2000/10/swap/grammar/n3-report.html
  468. # [14:57] <zcorpan_> so no dots
  469. # [14:57] <aja> is audio element still around? wondered why it wasn't in microdata additions like img, object, video, & a are
  470. # [14:58] <zcorpan_> it's still around
  471. # [14:58] * aja thought so
  472. # [14:58] <Philip`> zcorpan_: Lots of dots, but not "." in particular
  473. # [14:59] <Philip`> aja: Sounds like an oversight
  474. # [14:59] <jgraham> aja: Seems like it makes as much sense as <video> so probably an omisssion
  475. # [14:59] <jgraham> accidential omission
  476. # [14:59] <aja> can someone pls mention to Hixie......not gonna online rest of day
  477. # [15:00] <aja> be online, that is
  478. # [15:00] <Philip`> aja: You could email it somewhere
  479. # [15:00] <Philip`> but I guess Hixie will read the IRC logs anyway
  480. # [15:01] <aja> k...will f/u if i dont see an update.....later all
  481. # [15:01] * Quits: aja (n=aja@70.230.182.121) ("Ex-Chat")
  482. # [15:02] <zcorpan_> Philip`: maybe you should not use any prefixes to prevent such bugs?
  483. # [15:02] <Philip`> zcorpan_: That would make it unnecessarily hard to read
  484. # [15:04] <Philip`> Also, I don't care much about bugs - readability is more useful
  485. # [15:09] <Philip`> "<[object Object]> c:about _:n0 ." - hmm
  486. # [15:11] * Quits: Lachy (n=Lachlan@121.217.132.251) (Read error: 104 (Connection reset by peer))
  487. # [15:14] * Joins: pmuellr (n=pmuellr@nat/ibm/x-c58245e31f7d09e2)
  488. # [15:19] * Joins: Lachy (n=Lachlan@121.217.132.251)
  489. # [15:23] * Joins: davidb (n=davidb@bas4-toronto06-1279277172.dsl.bell.ca)
  490. # [15:30] * Joins: danbri (n=danbri@130.37.26.77)
  491. # [15:36] * Joins: doublec_ (n=doublec@118-92-139-120.dsl.dyn.ihug.co.nz)
  492. # [15:37] * Quits: doublec_ (n=doublec@118-92-139-120.dsl.dyn.ihug.co.nz) (Client Quit)
  493. # [15:37] * Quits: danbri (n=danbri@unaffiliated/danbri)
  494. # [15:38] <Philip`> It's confusing that <span item><span item><span property=foo>bar</span></span></span> generates no properties
  495. # [15:38] * Quits: doublec (n=doublec@118-93-168-138.dsl.dyn.ihug.co.nz) (Read error: 110 (Connection timed out))
  496. # [15:41] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) ("Ex-Chat")
  497. # [15:41] * Joins: aroben (n=aroben@unaffiliated/aroben)
  498. # [15:47] * Philip` sees http://chatlogs.planetrdf.com/swig/2009-05-11.html#T10-27-03 has a few more HTML5-related comments
  499. # [15:49] * Quits: maikmerten (n=merten@ls5dhcp196.cs.uni-dortmund.de) (Remote closed the connection)
  500. # [15:54] * Joins: mlpug (n=mlpug@a91-156-60-235.elisa-laajakaista.fi)
  501. # [15:55] * Joins: virtuelv (n=virtuelv@pat-tdc.opera.com)
  502. # [15:59] <jgraham> Twitter really, really sucks for, well, as far as I can tell, for pretty much everything. But in particular for all the myriad types of communication where reasoned argument is needed
  503. # [15:59] <fearphage> jgraham: for instance?
  504. # [16:01] <gavin> fearphage: you two should continue this discussion on twitter
  505. # [16:01] * Joins: danbri (n=danbri@dyn77.roaming.few.vu.nl)
  506. # [16:01] <fearphage> you may have a point
  507. # [16:04] <jgraham> fearphage: Ironically it is hard to explain on IRC for rather similar reasons. But look e.g. at rubys's titter page and then try to follow any of the threads backward
  508. # [16:05] <jgraham> *twitter
  509. # [16:06] <jgraham> And wonder if the medium is not distorting the message in a rahter harmful way, by allowing people to be irrational by enforced brevity
  510. # [16:06] <jgraham> So that reasoned argument being replaced by pithy one-liners is the norm
  511. # [16:06] <jgraham> and is totally expected and so unremarkable
  512. # [16:08] * Quits: danbri (n=danbri@unaffiliated/danbri)
  513. # [16:09] * Quits: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com) (Read error: 104 (Connection reset by peer))
  514. # [16:09] <fearphage> jgraham: that's twitter's ui failing really. it should show threaded views of conversations
  515. # [16:09] * Joins: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  516. # [16:10] * Joins: maikmerten (n=merten@vp-c-67.cs.uni-dortmund.de)
  517. # [16:10] * Joins: mstange (n=markus@buntes215.wohnheim.uni-kl.de)
  518. # [16:11] <zcorpan_> and not have a silly 140 char limit
  519. # [16:11] <Philip`> It doesn't have a silly 140 char limit - it has a sensible 140 char limit
  520. # [16:12] <Philip`> If it didn't have that limit then it would be a blog, and everyone has a blog already so there wouldn't be any point in it
  521. # [16:12] * Joins: danbri (n=danbri@dyn77.roaming.few.vu.nl)
  522. # [16:14] <jgraham> Philip`: Indeed. But the 140 character limit is both the distinguishing design feature and the reason it sucks
  523. # [16:14] <jgraham> Well that and the UI
  524. # [16:15] <jgraham> But the UI problem is a distant decond
  525. # [16:15] <jgraham> second
  526. # [16:15] <zcorpan_> if it sucks so much, you could come up with a competing alternative and make people switch and earn lots of money
  527. # [16:16] <jgraham> zcorpan_: I don't deny that people like it. But people like taking heroin but that sucks too
  528. # [16:16] <jgraham> So I don't know what to do
  529. # [16:16] <jgraham> Apart from maybe to ignore it
  530. # [16:17] <zcorpan_> jgraham: give up and take heroin, then twitter about it
  531. # [16:22] <zcorpan_> would maybe be nice to be able to give RDF/XML or n3 as input and convert it to html5 microdata
  532. # [16:23] <Philip`> Is that possible?
  533. # [16:24] <zcorpan_> maybe not losslessly
  534. # [16:24] <Philip`> And: Is that possible in general, or only in very limited situations e.g. where all the predicates are the xhtml/custom namespace?
  535. # [16:25] <jgraham> Why is that useful?
  536. # [16:25] <zcorpan_> didn't say it would be useful, only maybe nice
  537. # [16:26] <zcorpan_> e.g. if you're familiar with microdata syntax but not rdf
  538. # [16:27] <Philip`> <meta item id="n0"> <meta subject="n0" property="about" content="http://subject/"> <meta subject="n0" property="http://predicate/" content="value">
  539. # [16:27] <Philip`> Would that work?
  540. # [16:27] <Philip`> as a general way to encode (non-nested) triples
  541. # [16:28] <Philip`> It seems useful to be able to write data using existing RDF vocabularies, so you can easily reuse all the work that's gone into defining them
  542. # [16:29] * Quits: roc (n=roc@121-72-178-31.dsl.telstraclear.net) (Read error: 110 (Connection timed out))
  543. # [16:31] <zcorpan_> how many are subscribed to www-archive?
  544. # [16:31] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  545. # [16:31] <Philip`> How many read it via web archives?
  546. # [16:31] <Philip`> (since that mode of usage is the reason for the group's existence, after all)
  547. # [16:32] <Philip`> Oh, hmm, content="http://..." won't work because that's not an absolute URL
  548. # [16:34] <Philip`> Actually... Is it?
  549. # [16:34] <Philip`> "If name is not an absolute URL, ..." - how can it ever be an absolute URL? It's always just a string token
  550. # [16:36] <Philip`> I can't tell whether (absolute) URLs are meant to be a type distinct from strings, or whether they're just any string that happens to resolve into itself with no errors when you use the URL resolution algorithm
  551. # [16:37] * Joins: roc (n=roc@121-72-168-226.dsl.telstraclear.net)
  552. # [16:37] * jgraham thought the latter
  553. # [16:38] <Philip`> I assumed the former, but I guess it must be the latter, but then I have no idea whether <span property=foo>http://google.com/</span> should be an RDF resource (<http://google.com/> in N3) or still just a string ("http://google.com/")
  554. # [16:39] <jgraham> I guess a string
  555. # [16:39] <jgraham> But clarity would be nice
  556. # [16:39] <Philip`> It makes sense to me that any content in href/src/etc should be a resource, whereas any other content should just be a string
  557. # [16:39] <jgraham> That's what I assume
  558. # [16:39] <Philip`> If you make it a string then you lose the whole graphiness of RDF, which would be silly
  559. # [16:39] <Philip`> Wait
  560. # [16:39] <Philip`> No you don't, I'm confused again
  561. # [16:40] * jgraham doesn't know
  562. # [16:40] <Philip`> I'm sure the <span>http:// ought to be a string, because anything else is crazy
  563. # [16:40] <jgraham> But it makes sense that if you want to make a link to another resource you have to say <a href="http://my.other.resource">
  564. # [16:40] <Philip`> but property="http://..." ought to be a URL, because anything else is crazy
  565. # [16:41] <Philip`> and href="http://..." ought to be a URL, because anything else is crazy
  566. # [16:41] <jgraham> Yes
  567. # [16:41] <Philip`> so the spec must be wrong because it uses the same terminology for property and for values
  568. # [16:42] * jgraham wishes the spec called values "values" rather than "property values"
  569. # [16:43] <jgraham> Philip`: Does it? Where
  570. # [16:43] <jgraham> ?
  571. # [16:45] * Joins: csarven (n=csarven@modemcable106.33-81-70.mc.videotron.ca)
  572. # [16:50] <Philip`> <meta item id="n0"> <link subject="n0" property="about" href="http://subject/"> <link subject="n0" property="http://predicate/" href="http://value/"> <meta subject="n0" property="http://predicate/" content="value"> should work, I think
  573. # [16:50] <Philip`> (though not in my implementation)
  574. # [16:51] <Philip`> jgraham: Um...
  575. # [16:51] <jgraham> Hmm, so it is necessary to keep tabs on where a property came from to determine if it is a url or a string that looks like a URL
  576. # [16:51] <Philip`> jgraham: I'm still just being confused
  577. # [16:51] <jgraham> I have a bug there too, then
  578. # [16:52] <jgraham> Philip`: This only really applies to the RDF serialization, right?
  579. # [16:52] <jgraham> The json serialization seems to have data loss...
  580. # [16:52] <Philip`> In order to produce RDF output (but not JSON), concept-property-value needs to remember whether it returns a URL or a string (which may or may not look like a URL)
  581. # [16:52] <Philip`> and then you use <...> or "..." depending on which it is
  582. # [16:53] <Philip`> but for 'type' and 'name' you just have a string and look to see whether it looks sufficiently like an absolute URL to be treated like one
  583. # [16:53] <jgraham> Philip`: Is that a spec quote?
  584. # [16:54] <Philip`> function looks_like_an_absolute_url(str) { return str.match(/^(([a-zA-Z][0-9a-zA-Z+\-\.]*:)\/{0,2}[0-9a-zA-Z;\/?:@&=+$\.\-_!~*'()%]+)?(#[0-9a-zA-Z;\/?:@&=+$\.\-_!~*'()%]+)?$/); }
  585. # [16:54] <Philip`> That'll do for me, I guess
  586. # [16:54] <Philip`> jgraham: Is what a spec quote?
  587. # [16:54] <jgraham> "In order to produce RDF output..."
  588. # [16:55] <Philip`> jgraham: Regardless of your answer, my answer is no
  589. # [16:55] <Philip`> The spec doesn't say anything about this for the RDF output, because it ignores types entirely
  590. # [16:55] <jgraham> OK, so the spec is wrong here
  591. # [16:55] <jgraham> In some sense
  592. # [16:56] <jgraham> s/wrong/incomplete/
  593. # [16:56] <Philip`> unless you implicitly read some typing in the bits where it says "the value is an absolute URL"
  594. # [16:56] <Philip`> (which I do, because that's sensible)
  595. # [16:56] <jgraham> (yeha, I did that too)
  596. # [16:57] <Philip`> So, anyway, the spec should clarify that, but otherwise it seems like it's capable of representing arbitrary subject/predicate/object triples as long as you ignore all the extra bits like types and languages
  597. # [16:57] <Philip`> so you could do an RDF-to-text/html converter
  598. # [16:58] * jgraham isn't sure about types and names as urls
  599. # [16:59] <jgraham> Oh wait. I think it's OK
  600. # [16:59] <jgraham> I'm being silly
  601. # [16:59] <jgraham> Probably
  602. # [17:00] <zcorpan_> how does RDF/XML distinguish between URLs and strings?
  603. # [17:00] <jgraham> So: Any type or name that looks like a URL is a URL. Any value that somes from a URLish place is a URL but any value that comes from text is text
  604. # [17:01] * Quits: drostie (n=hopkins@wlan-145-94-168-206.wlan.tudelft.nl) (Remote closed the connection)
  605. # [17:04] * Quits: danbri (n=danbri@unaffiliated/danbri)
  606. # [17:04] * Quits: Maurice (n=ano@a80-101-46-164.adsl.xs4all.nl) ("Disconnected...")
  607. # [17:05] <Philip`> zcorpan_: <predicate rdf:resource="object"/> vs <predicate>object</predicate>
  608. # [17:06] <Philip`> zcorpan_: according to '<#n1> <#n2> <#n3> . <#n4> <#n5> "#n6" .' in http://www.rdfabout.com/demo/validator/
  609. # [17:09] * Quits: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  610. # [17:09] * Quits: ROBOd (n=robod@89.122.216.38) (Remote closed the connection)
  611. # [17:09] * Quits: nessy (n=nessy@124-171-63-74.dyn.iinet.net.au) ("This computer has gone to sleep")
  612. # [17:09] <zcorpan_> Philip`: ok
  613. # [17:10] * Joins: danbri (n=danbri@dyn77.roaming.few.vu.nl)
  614. # [17:10] * Joins: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  615. # [17:11] <zcorpan_> The underlying triples
  616. # [17:11] <zcorpan_> :n1 :n2 :n3 .
  617. # [17:11] <zcorpan_> :n4 :n5 "#n6" .
  618. # [17:12] <Philip`> (In N3, the empty prefix is <#>)
  619. # [17:12] <Philip`> (by default)
  620. # [17:12] * Quits: virtuelv (n=virtuelv@pat-tdc.opera.com) (Read error: 110 (Connection timed out))
  621. # [17:14] * Quits: mstange (n=markus@buntes215.wohnheim.uni-kl.de) (Read error: 104 (Connection reset by peer))
  622. # [17:14] * Quits: gmiernicki (n=gmiernic@unaffiliated/gmiernicki) (Remote closed the connection)
  623. # [17:23] * Joins: wakaba (n=wakaba@EM114-51-150-168.pool.e-mobile.ne.jp)
  624. # [17:23] * Quits: sid0 (n=sid0@unaffiliated/sid0) (Read error: 110 (Connection timed out))
  625. # [17:25] * Quits: myakura (n=myakura@p3087-ipbf6705marunouchi.tokyo.ocn.ne.jp) ("Leaving...")
  626. # [17:26] * Joins: ROBOd (n=robod@89.122.216.38)
  627. # [17:31] * Quits: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Read error: 110 (Connection timed out))
  628. # [17:32] * Joins: dglazkov (n=dglazkov@nat/google/x-754e2e3c23effa42)
  629. # [17:36] * Joins: cgriego (n=cgriego@12.14.172.51)
  630. # [17:36] * Joins: hdh (n=hdh@118.71.99.185)
  631. # [17:41] * Quits: wakaba_ (n=wakaba@EM114-51-162-132.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  632. # [17:45] <zcorpan_> will someone send email about the url vs string issue?
  633. # [17:45] * Parts: harig (n=opera@59.90.71.35)
  634. # [17:47] * Quits: maikmerten (n=merten@vp-c-67.cs.uni-dortmund.de) (Remote closed the connection)
  635. # [17:49] <jgraham> I will if no one else does, but not before I have had a serious attempt at implementing that part of the spec
  636. # [17:49] <jgraham> Which might be this evening but is more likely not to be
  637. # [17:51] * gsnedders should probably buy Lightroom at academic prices before he leaves school
  638. # [17:51] <jgraham> gsnedders: You can still do that at university you realise?
  639. # [17:52] <gsnedders> jgraham: But if I'm not going to uni for a year, I then couldn't do it for a year :P
  640. # [17:52] <Philip`> You could ask somebody still in school/university to buy it for you
  641. # [17:52] <csarven> Is there a document somewhere that outlines XML Namespaces as helpful (as opposed to http://wiki.whatwg.org/wiki/Namespace_confusion ) ? Thought it'd be good to have data for both extreme cases, unless, of course, if Namespaces is 100% confusing and useless for all developers.
  642. # [17:53] <Philip`> csarven: Namespaces helpful? That's blasphemy!
  643. # [17:53] <jgraham> csarven: You may have come to the wrong place :)
  644. # [17:53] <csarven> Unless I'm mistaking, the existing approach is hardly scientific. :)
  645. # [17:54] * Philip` is not aware of documents listing the benefits of namespaces over other approaches, but assumes there must be some somewhere
  646. # [17:54] <jgraham> (But I guess the TAG will have something about how they are wonderful somewhere)
  647. # [17:54] <csarven> s/mistaking/mistaken
  648. # [17:55] <jgraham> csarven: If I didn't have to go, I would probably argue with that statement :)
  649. # [17:56] * Joins: mat_t (n=mattomas@nat/canonical/x-22f9946cdeea64ce)
  650. # [17:57] <Philip`> I guess the obvious advantages are that they make it possible to create unambiguous globally-unique names (using the DNS infrastructure to avoid conflicts between independent groups), that can be dereferenced to find related information about their meaning, and that can be expressed concisely in XML syntax in a way that's easy to read and write by hand but can still express arbitrarily complex arrangements of namespaced data
  651. # [17:57] <Philip`> Also, colons are cute
  652. # [17:58] * zcorpan_ finds http://mailman.ic.ac.uk/pipermail/xml-dev/1999-January/008189.html
  653. # [18:00] * Joins: onar_ (n=onar@17.244.69.220)
  654. # [18:00] <Philip`> That's, um, a lot of syntax
  655. # [18:01] <Philip`> <?xml:begin-ns name="D" urn="http://www.daisoft.com/schema-D"?><D:baz></D:baz><?xml:end-ns name="D"?>
  656. # [18:01] <Philip`> vs <D:baz xmlns:D="http://www.daisoft.com/schema-D"></D:baz>
  657. # [18:02] * Joins: pesla\work (n=retep@procurios.xs4all.nl)
  658. # [18:02] <Philip`> XML Namespaces could have been much worse than it is :-)
  659. # [18:02] * Joins: Maurice (i=copyman@5ED548D4.cable.ziggo.nl)
  660. # [18:03] <csarven> Would I get yelled at if I started a Wiki page on 'Namespaces' which covers both pros and cons?
  661. # [18:03] <Philip`> Not at all
  662. # [18:06] <gsnedders> csarven: I think the current page is more to avoid making the same points over and over again about the conventional wisdom
  663. # [18:07] * Quits: pesla (n=retep@procurios.xs4all.nl) (Read error: 60 (Operation timed out))
  664. # [18:08] * Quits: mat_t (n=mattomas@nat/canonical/x-22f9946cdeea64ce) ("Leaving")
  665. # [18:10] * Quits: shepazu (n=schepers@modemcable203.65-70-69.static.videotron.ca)
  666. # [18:11] * Joins: drostie (n=hopkins@5354256F.cable.casema.nl)
  667. # [18:12] <csarven> gsnedders Is the decision for HTML5 based on http://wiki.whatwg.org/wiki/Namespace_confusion ? i.e., a subset of views on XML Namespaces
  668. # [18:13] <gsnedders> csarven: No
  669. # [18:14] * Quits: KevinMarks (n=KevinMar@c-71-202-163-211.hsd1.ca.comcast.net) ("The computer fell asleep")
  670. # [18:14] * Joins: billmason (n=billmaso@ip246.unival.com)
  671. # [18:14] * Quits: danbri (n=danbri@unaffiliated/danbri)
  672. # [18:14] <Philip`> There are non-confusion-related issues with Namespaces in text/html, like the inconsistency between text/html parsers and XML parsers when names contain colons, that make it less desirable too
  673. # [18:15] <csarven> That's good. So, how was the decision made? Is there more evidence supporting the disadvantages of NS than advantages?
  674. # [18:15] <csarven> I'm just curious about the data gathered for both cases
  675. # [18:17] * zcorpan_ wonders which decision is being discussed
  676. # [18:17] <csarven> Pardon me if I'm repeating/rehashing something which has been discussed, I don't wish to take people's time with this. Kindly point me to a URI which answers such questions.
  677. # [18:17] * Quits: pauld (n=pauld@194.102.13.6)
  678. # [18:22] * Joins: sid0 (n=sid0@unaffiliated/sid0)
  679. # [18:28] * Philip` updates his RDF output to be much less wrong
  680. # [18:28] * Joins: ap (n=ap@194.154.88.37)
  681. # [18:32] * Quits: sid0 (n=sid0@unaffiliated/sid0) (Read error: 60 (Operation timed out))
  682. # [18:38] <Philip`> csarven: I don't think there's a URI giving the rationale
  683. # [18:38] <zcorpan_> Philip`: "_:n2 a <http://www.w3.org/1999/xhtml/custom#org.w3.spec> ." - what's the "a"?
  684. # [18:39] <Philip`> zcorpan_: Shorthand for <http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
  685. # [18:39] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  686. # [18:39] <zcorpan_> ah
  687. # [18:39] <Philip`> Maybe rdf:type would be less confusing
  688. # [18:40] * aroben is now known as aroben|lunch
  689. # [18:40] <Philip`> but I'm assuming it was added to N3 (and Turtle) because they wanted it to be used
  690. # [18:40] * Joins: olliej (n=oliver@76.14.74.242)
  691. # [18:41] * Quits: jwalden (n=waldo@24.6.168.212) ("ChatZilla 0.9.82.1-rdmsoft [XULRunner 1.8.0.9/2006120508]")
  692. # [18:42] <zcorpan_> are there more magic identifiers in n3?
  693. # [18:42] * Joins: sid0 (n=sid0@unaffiliated/sid0)
  694. # [18:43] <Philip`> http://www.w3.org/DesignIssues/Notation3.html
  695. # [18:44] * Quits: pesla\work (n=retep@procurios.xs4all.nl) ("( www.nnscript.com :: NoNameScript 4.21 :: www.esnation.com )")
  696. # [18:44] <Philip`> but http://www.dajobe.org/2004/01/turtle/ (sort of a subset of N3) only has 'a' and not the others
  697. # [18:45] * Philip` hopes those are the most proper specifications
  698. # [18:45] * Joins: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  699. # [18:46] * Quits: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Read error: 110 (Connection timed out))
  700. # [18:46] <Philip`> csarven: When you say "decision", which one do you mean? (The decision to use full URIs / reverse domain labels instead of CURIEs for the microdata property attribute?)
  701. # [18:46] <zcorpan_> n3 is more complicated than i had thought
  702. # [18:49] * zcorpan_ stops reading and goes on to do something different
  703. # [18:51] <csarven> Philip` Moreso where WHATWG stands with NS and how was that decision made i.e., based on which data? I'm only aware of http://wiki.whatwg.org/wiki/Namespace_confusion
  704. # [18:52] <takkaria> namespaces aren't an end in themselves, though, they're an implementation detail for certain use cases
  705. # [18:52] <takkaria> namespaces are explicitly used, e.g. for SVG and MathML content, the spec says those elements go in the right namespace
  706. # [18:53] * Quits: olliej (n=oliver@76.14.74.242)
  707. # [18:53] <Philip`> csarven: I don't think the WHATWG has a specific standing on Namespaces - sometimes they're considered to be appropriate, sometimes other solutions are considered to be better
  708. # [18:56] * Joins: weinig (n=weinig@17.246.16.191)
  709. # [18:57] * Quits: philipj (n=philipj@pat.se.opera.com) (Read error: 110 (Connection timed out))
  710. # [18:59] * Joins: riven` (n=colin@53525B67.cable.casema.nl)
  711. # [19:03] * Joins: riven`` (n=colin@53525B67.cable.casema.nl)
  712. # [19:03] * Quits: riven (n=colin@53525B67.cable.casema.nl) (Read error: 60 (Operation timed out))
  713. # [19:05] * riven`` is now known as riven
  714. # [19:05] * Joins: danbri (n=danbri@s5590d015.adsl.wanadoo.nl)
  715. # [19:07] <csarven> takkaria Philip` Thanks.
  716. # [19:10] <Philip`> (However, I have heard rumours that XML Namespaces cause babies to grow horns and were the cause of World War 2, so to stay safe I think we should avoid them)
  717. # [19:12] * Joins: sid0_ (n=sid0@unaffiliated/sid0)
  718. # [19:14] * Quits: csarven (n=csarven@modemcable106.33-81-70.mc.videotron.ca) ("Leaving.")
  719. # [19:15] * Joins: csarven (n=csarven@modemcable106.33-81-70.mc.videotron.ca)
  720. # [19:16] * gsnedders rather dislikes uni of Edi for re-inventing email for the sake of applicants
  721. # [19:17] <Philip`> Maybe they didn't re-invent email, but invented it before it had actually been invented, and then stuck with their legacy system
  722. # [19:17] * Quits: riven` (n=colin@53525B67.cable.casema.nl) (Connection timed out)
  723. # [19:21] * Joins: wakaba_ (n=wakaba@EM114-51-1-2.pool.e-mobile.ne.jp)
  724. # [19:22] * aroben|lunch is now known as aroben
  725. # [19:24] * Joins: dave_levin (n=dave_lev@72.14.227.1)
  726. # [19:25] * Joins: franksalim (n=frank@adsl-75-61-86-233.dsl.pltn13.sbcglobal.net)
  727. # [19:30] * Quits: sid0 (n=sid0@unaffiliated/sid0) (Read error: 110 (Connection timed out))
  728. # [19:34] * Joins: ZombieLoffe (n=e@unaffiliated/zombieloffe)
  729. # [19:35] * Joins: jwalden (n=waldo@corp-241.mountainview.mozilla.com)
  730. # [19:36] * Quits: wakaba (n=wakaba@EM114-51-150-168.pool.e-mobile.ne.jp) (Read error: 110 (Connection timed out))
  731. # [19:37] * Quits: sid0_ (n=sid0@unaffiliated/sid0) (Read error: 110 (Connection timed out))
  732. # [19:46] * Joins: blooberry (n=brian@c-76-126-110-8.hsd1.ca.comcast.net)
  733. # [19:47] * Joins: maikmerten (n=maikmert@BAE1dfb.bae.pppool.de)
  734. # [19:47] * Quits: hdh (n=hdh@118.71.99.185) (Remote closed the connection)
  735. # [19:50] * Joins: sid0 (n=sid0@unaffiliated/sid0)
  736. # [19:51] * Joins: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com)
  737. # [19:52] * Quits: webben (n=benh@nat/yahoo/x-659ba78708484358) (Read error: 110 (Connection timed out))
  738. # [19:56] * Quits: dolske (n=dolske@firefox/developer/dolske)
  739. # [19:59] * Joins: dimich (n=dimich@72.14.227.1)
  740. # [20:00] <Philip`> Hmm, the serialised JSON output can be O(2^n) in size compared to the markup
  741. # [20:00] <Philip`> <meta item id="n0"> <meta subject="n0" property="a b" item id="n1"> <meta subject="n1" property="a b" item id="n2"> <meta subject="n2" property="a b" item id="n3"> <meta subject="n3" property="p" content="x"> etc
  742. # [20:04] * Joins: olliej (n=oliver@17.203.15.172)
  743. # [20:04] * Parts: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  744. # [20:06] * Joins: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  745. # [20:08] * Quits: onar_ (n=onar@17.244.69.220)
  746. # [20:17] * Joins: mpilgrim_ (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  747. # [20:18] * Quits: sid0 (n=sid0@unaffiliated/sid0) (Read error: 54 (Connection reset by peer))
  748. # [20:21] * Joins: onar_ (n=onar@17.244.69.220)
  749. # [20:21] * Joins: dolske (n=dolske@corp-241.mountainview.mozilla.com)
  750. # [20:23] * Joins: zcorpan (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  751. # [20:24] * Quits: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se) (Read error: 110 (Connection timed out))
  752. # [20:32] * Quits: ap (n=ap@194.154.88.37)
  753. # [20:33] * Joins: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net)
  754. # [20:39] * Quits: zcorpan (n=zcorpan@c83-252-196-43.bredband.comhem.se) (Read error: 110 (Connection timed out))
  755. # [20:40] * Joins: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  756. # [20:41] * Quits: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Read error: 110 (Connection timed out))
  757. # [20:58] * Quits: dolske (n=dolske@firefox/developer/dolske)
  758. # [21:04] * Joins: dbaron_ (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net)
  759. # [21:05] * Quits: dbaron_ (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net) (Client Quit)
  760. # [21:05] * Joins: sid0 (n=sid0@unaffiliated/sid0)
  761. # [21:05] * Joins: dbaron_ (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net)
  762. # [21:06] * Quits: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com)
  763. # [21:07] * Joins: dolske (n=dolske@corp-241.mountainview.mozilla.com)
  764. # [21:08] * Quits: dbaron (n=dbaron@c-98-234-51-190.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
  765. # [21:09] <tantek> Philip - the "space separated set" feature of profile, class, rel (and property in the example you gave) attributes is quite powerful, and helps with more succinct expression of semantics.
  766. # [21:10] <tantek> I think it's a consequence of content-centric design rather than syntax-centric (or even model-centric) design.
  767. # [21:11] <Hish> hi. can anybody enlighten me regarding footnotes (http://www.whatwg.org/specs/web-apps/current-work/multipage/text-level-semantics.html#footnotes)? I understand the three approaches but when it comes to editing a document with long footnotes, then doing copy/paste the part with the <a href> link won't change the footnode content. any ideas?
  768. # [21:12] * Quits: onar_ (n=onar@17.244.69.220)
  769. # [21:13] * jgraham wonders if anyone who has used rdflib is around and if so wheher they could point him to some simple instructions for creating a graph and serializing it
  770. # [21:14] <jgraham> Preferbly one that, unlike the officil documentation, doesn't require me to already understand the api
  771. # [21:15] * Joins: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com)
  772. # [21:15] * Joins: zcorpan (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  773. # [21:26] * Joins: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se)
  774. # [21:26] * Joins: webben (n=benh@91.85.210.172)
  775. # [21:28] * Quits: zcorpan_ (n=zcorpan@c83-252-196-43.bredband.comhem.se) (Client Quit)
  776. # [21:31] * Quits: zcorpan (n=zcorpan@c83-252-196-43.bredband.comhem.se) (Read error: 60 (Operation timed out))
  777. # [21:36] * Quits: mpilgrim_ (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com) (Read error: 110 (Connection timed out))
  778. # [21:40] <Philip`> jgraham: Read the source code - it's Python so it must be easy to read
  779. # [21:41] <Philip`> tantek: It would just be nice if it was possible to parse a page without being vulnerable to DOS attacks :-)
  780. # [21:44] * Quits: mlpug (n=mlpug@a91-156-60-235.elisa-laajakaista.fi) (Remote closed the connection)
  781. # [21:46] <jgraham> Philip`: Not sure that reading the source will allow me to trivially work out how all the design elements are expected to fit together (which is basically the problem)
  782. # [21:46] <jgraham> Also: I just read the xml:base spec and oh boy do the authors hate conformance criteria
  783. # [21:46] <Philip`> jgraham: Maybe the source code contains comments giving high-level documentation of how all the design elements are expected to fit together
  784. # [21:47] <Philip`> although if it does, they'll probably be three years out of date and have no correspondence to the current code, and those comments won't exist anyway
  785. # [21:47] <Philip`> so maybe that's not the best plan
  786. # [21:48] * Quits: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com) (Remote closed the connection)
  787. # [21:48] * Philip` decides that in general it's impossible to serialise microdata as N3 without explicit blank nodes
  788. # [21:48] * Joins: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com)
  789. # [21:48] <Philip`> (even if you use the [...] syntax whenever possible)
  790. # [21:49] <Philip`> because it's possible to have two predicates using the same blank node, but impossible to represent that non-explicitly, as far as I can tell
  791. # [21:54] * Joins: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  792. # [21:59] * Joins: jacobolus (i=8cf77223@gateway/web/ajax/mibbit.com/x-f40645463b3bac91)
  793. # [22:00] * Joins: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu)
  794. # [22:04] * Quits: pauld (n=pauld@host81-158-125-194.range81-158.btcentralplus.com)
  795. # [22:07] * Quits: maikmerten (n=maikmert@BAE1dfb.bae.pppool.de) (Remote closed the connection)
  796. # [22:12] * Quits: csarven (n=csarven@modemcable106.33-81-70.mc.videotron.ca) ("Leaving.")
  797. # [22:13] * Quits: pmuellr (n=pmuellr@nat/ibm/x-c58245e31f7d09e2)
  798. # [22:13] <krijnh> http://www.grauw.nl/blog/entry/513
  799. # [22:14] * Quits: zalan (n=kvirc@catv-89-132-200-147.catv.broadband.hu) (Read error: 110 (Connection timed out))
  800. # [22:16] <Dashiva> So the only conceivable reason to remove namespaces is to spite RDFa, obviously
  801. # [22:17] <gsnedders> Duh.
  802. # [22:18] <jgraham> Philip`: Given there are no docstrings anywhere, I have doubts about the number of comments in the code
  803. # [22:20] <jgraham> Hmm that is the same comment that Laurens posted at simonwillison.net. Unrelatedly, my comment there seems to have become trapped in the moderation queue. Or maybe it is a write only queue
  804. # [22:26] * Joins: weinig_ (n=weinig@nat/apple/x-81d66e17f87d77e1)
  805. # [22:27] * Quits: roc (n=roc@121-72-168-226.dsl.telstraclear.net)
  806. # [22:33] <jgraham> Does the html 5 definition of absolute url make any sense?
  807. # [22:33] * Quits: jwalden (n=waldo@corp-241.mountainview.mozilla.com) ("->S")
  808. # [22:33] * Quits: ZombieLoffe (n=e@unaffiliated/zombieloffe)
  809. # [22:34] * Quits: dolske (n=dolske@firefox/developer/dolske)
  810. # [22:34] <jgraham> An absolute url is one that resolves to itself
  811. # [22:34] <jgraham> But resolving a url requires something to resolve it against which is not specified
  812. # [22:35] * Joins: dolske (n=dolske@corp-241.mountainview.mozilla.com)
  813. # [22:36] * Joins: hdh (n=hdh@118.71.99.185)
  814. # [22:39] <Philip`> jgraham: An absolute URL doesn't need anything to resolve it against
  815. # [22:39] <Dashiva> Would namespaces be less of a mess if tutorials used random strings for prefixes?
  816. # [22:40] <Philip`> Dashiva: No
  817. # [22:41] * Quits: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) (Read error: 104 (Connection reset by peer))
  818. # [22:41] * Quits: dolske (n=dolske@firefox/developer/dolske)
  819. # [22:41] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  820. # [22:42] * Quits: weinig (n=weinig@17.246.16.191) (Read error: 110 (Connection timed out))
  821. # [22:43] <jgraham> Philip`: Right but the algorithm doesn't allow for that
  822. # [22:43] <Dashiva> "And the copy and paste thing is less relevant than you all seem to imply. First of all, it would take no more than ten minutes to ensure people understand what example foaf: means."
  823. # [22:43] <Dashiva> Oh boy
  824. # [22:44] <jgraham> Dashiva: What are you quoting?
  825. # [22:44] * Quits: ROBOd (n=robod@89.122.216.38) ("http://www.robodesign.ro")
  826. # [22:45] <Dashiva> Fifth comment on http://realtech.burningbird.net/semantic-web/semantic-web-issues-and-practices/holding-on-html5
  827. # [22:45] <Dashiva> Also interesting that RDFa chooses to ignore part of the CURIE spec
  828. # [22:52] <Philip`> Which part is that?
  829. # [22:54] * Joins: dolske (n=dolske@corp-241.mountainview.mozilla.com)
  830. # [23:01] * Joins: jwalden (n=waldo@corp-241.mountainview.mozilla.com)
  831. # [23:02] <Dashiva> Philip`: Without prefix
  832. # [23:07] * Quits: olliej (n=oliver@17.203.15.172) (Read error: 110 (Connection timed out))
  833. # [23:07] * Quits: zalan_ (n=kvirc@catv-89-132-200-147.catv.broadband.hu) ("KVIrc 3.4.0 Virgo http://www.kvirc.net/")
  834. # [23:08] * Quits: Maurice (i=copyman@5ED548D4.cable.ziggo.nl) ("Disconnected...")
  835. # [23:09] * Quits: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au) ("Tomorrow to fresh woods, and pastures new.")
  836. # [23:09] * Joins: MikeSmith (n=MikeSmit@60-240-249-107.tpgi.com.au)
  837. # [23:09] * Quits: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com)
  838. # [23:17] * Joins: aroben_ (n=aroben@unaffiliated/aroben)
  839. # [23:20] * Quits: aroben (n=aroben@unaffiliated/aroben) (Read error: 110 (Connection timed out))
  840. # [23:34] * Quits: Lachy (n=Lachlan@121.217.132.251) ("This computer has gone to sleep")
  841. # [23:34] * Quits: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com) (Read error: 54 (Connection reset by peer))
  842. # [23:34] * Joins: mpilgrim (n=mark@rrcs-96-10-240-189.midsouth.biz.rr.com)
  843. # [23:35] * Joins: weinig (n=weinig@17.246.16.191)
  844. # [23:48] * aroben_ is now known as aroben
  845. # [23:50] * Parts: billmason (n=billmaso@ip246.unival.com)
  846. # [23:51] * Joins: bgalbraith (n=bgalbrai@corp-241.mountainview.mozilla.com)
  847. # [23:51] * Quits: weinig_ (n=weinig@nat/apple/x-81d66e17f87d77e1) (Read error: 110 (Connection timed out))
  848. # [23:54] * Quits: dave_levin (n=dave_lev@72.14.227.1)
  849. # [23:54] * Quits: jacobolus (i=8cf77223@gateway/web/ajax/mibbit.com/x-f40645463b3bac91) ("http://www.mibbit.com ajax IRC Client")
  850. # Session Close: Tue May 12 00:00:00 2009

The end :)