/irc-logs / freenode / #microformats / 2009-04-30 / end

Options:

  1. # Session Start: Thu Apr 30 00:00:01 2009
  2. # Session Ident: #microformats
  3. # [00:05] * Joins: singpolyma (n=singpoly@node-4543.tor.pppoe.execulink.com)
  4. # [00:07] * Quits: eaton (n=eaton@drupal.org/user/16496/view)
  5. # [00:27] * Quits: singpolyma (n=singpoly@node-4543.tor.pppoe.execulink.com) ("Lost terminal")
  6. # [00:38] * Quits: ajturner (n=ajturner@209.155.228.129)
  7. # [01:06] * Quits: georgebrock (n=georgebr@cpc1-wilm1-0-0-cust850.bagu.cable.ntl.com)
  8. # [01:17] * Quits: @benward (n=benward@nat/yahoo/x-7b9b0483cea346d6) (Read error: 110 (Connection timed out))
  9. # [01:23] <mfbot> Tantek edited value-class-pattern "/* Parsing date and time concatenation */ add special case parsing for certain elements (abbr, area, img)" (+340) http://is.gd/vt4L
  10. # [01:30] <mfbot> Tantek edited value-class-pattern "/* Parsing date and time concatenation */ simplify/remove a level of indentation for better chunking and readability" (-40) http://is.gd/vt8Z
  11. # [01:36] * Quits: Broady (n=broady@unaffiliated/broady) (Read error: 113 (No route to host))
  12. # [01:36] <mfbot> Tantek edited value-class-pattern "/* Parsing value from a title attribute */ move /p in example to balance start tag, clarify that value does not always use inner-text (e.g. particular tags like abbr, area, img)" (+5) http://is.gd/vtcZ
  13. # [02:07] <mfbot> Tantek edited value-class-pattern "/* Basic Parsing */ note special handling of abbr, area, img elements (as before, from [[hcard-parsing]]))" (+284) http://is.gd/vttr
  14. # [02:26] * Quits: leahculver (n=leahculv@204.9.180.30)
  15. # [02:37] * Quits: memload (n=jamesjef@82.37.24.167) (Client Quit)
  16. # [02:41] <mfbot> Tantek edited value-class-pattern "simplify and make consistent basic parsing and date time concatenation parsing" (-28) http://is.gd/vtL9
  17. # [02:47] * Joins: shigeta (n=shigeta@124.32.114.226)
  18. # [02:52] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 110 (Connection timed out))
  19. # [02:55] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
  20. # [02:58] * Quits: @dglazkov (n=dglazkov@nat/google/x-f9597d0ce3f03fd6) (Read error: 110 (Connection timed out))
  21. # [03:13] <mfbot> Tantek edited value-class-pattern "/* Parsing date and time concatenation */ add more details for consideration of parsing am/pm suffix in a separate time value, add reference to Wikipedia article on the 12 hour clock" (+186) http://is.gd/vu1O
  22. # [03:13] * Joins: Broady (n=broady@unaffiliated/broady)
  23. # [03:14] * Quits: @tantek (n=tantek@64.1.214.211)
  24. # [03:24] * Quits: azazul (n=azazul@zelli-kojas.lanet.lv) ("Leaving")
  25. # [04:02] * Joins: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  26. # [04:15] * Joins: benward (n=benward@98.210.154.133)
  27. # [04:15] * ChanServ sets mode: +o benward
  28. # [05:04] * Quits: @benward (n=benward@98.210.154.133) ("Shutdown")
  29. # [05:07] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  30. # [05:07] * ChanServ sets mode: +o dglazkov
  31. # [05:41] * Joins: shigeta_ (n=shigeta@124.32.114.226)
  32. # [05:42] * Joins: petercoulton (n=petercou@5ac0c364.bb.sky.com)
  33. # [06:01] * Quits: shigeta (n=shigeta@124.32.114.226) (Read error: 110 (Connection timed out))
  34. # [06:47] * Quits: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  35. # [07:12] * Joins: besbes (n=besbes@91-115-183-160.adsl.highway.telekom.at)
  36. # [07:17] * Quits: @dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  37. # [07:22] * Joins: BenWard (n=benward@32.152.92.67)
  38. # [07:22] * ChanServ sets mode: +o BenWard
  39. # [07:24] * Quits: @BenWard (n=benward@32.152.92.67) (Client Quit)
  40. # [07:44] * Quits: besbes (n=besbes@91-115-183-160.adsl.highway.telekom.at)
  41. # [08:07] * Joins: besbes (n=besbes@91-115-183-160.adsl.highway.telekom.at)
  42. # [08:10] * Joins: georgebrock (n=georgebr@cpc1-wilm1-0-0-cust850.bagu.cable.ntl.com)
  43. # [08:11] * Quits: petercoulton (n=petercou@5ac0c364.bb.sky.com) ("Leaving")
  44. # [08:17] * Joins: petercoulton (n=petercou@5ac0c364.bb.sky.com)
  45. # [08:55] * Joins: georgebrock_ (n=georgebr@cpc1-wilm1-0-0-cust850.bagu.cable.ntl.com)
  46. # [08:55] * Quits: georgebrock (n=georgebr@cpc1-wilm1-0-0-cust850.bagu.cable.ntl.com) (Read error: 54 (Connection reset by peer))
  47. # [09:16] * Quits: csarven (n=csarven@modemcable150.182-202-24.mc.videotron.ca) ("Leaving.")
  48. # [09:16] * Quits: besbes (n=besbes@91-115-183-160.adsl.highway.telekom.at)
  49. # [09:36] * Joins: besbes (n=besbes@mercury.mminf.univie.ac.at)
  50. # [09:49] * Quits: georgebrock_ (n=georgebr@cpc1-wilm1-0-0-cust850.bagu.cable.ntl.com)
  51. # [10:02] * Joins: georgebrock (n=georgebr@host81-158-242-88.range81-158.btcentralplus.com)
  52. # [10:05] * Joins: tobyink (n=tai@77.89.160.246)
  53. # [10:08] * Quits: gsnedders (n=gsnedder@86.136.52.180) (Remote closed the connection)
  54. # [10:13] * Joins: gsnedders (n=gsnedder@host86-136-52-180.range86-136.btcentralplus.com)
  55. # [10:41] * Joins: MrTopf (n=cs@p5B3965B4.dip.t-dialin.net)
  56. # [10:55] * Quits: Broady (n=broady@unaffiliated/broady) (Read error: 110 (Connection timed out))
  57. # [10:57] * Joins: emrojo (n=emrojo@163.117.139.34)
  58. # [11:04] * Quits: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com) ("Leaving.")
  59. # [11:32] * Joins: besbes_ (n=besbes@falkenstein.mminf.univie.ac.at)
  60. # [11:37] * Joins: Broady (n=broady@unaffiliated/broady)
  61. # [11:42] * Joins: Prometheus (n=promethe@unaffiliated/prometheus)
  62. # [11:43] * Joins: ntoll (n=ntoll@85.210.101.94)
  63. # [11:48] * Quits: besbes (n=besbes@mercury.mminf.univie.ac.at) (Read error: 110 (Connection timed out))
  64. # [11:59] * Quits: georgebrock (n=georgebr@host81-158-242-88.range81-158.btcentralplus.com)
  65. # [12:16] * Joins: besbes (n=besbes@mercury.mminf.univie.ac.at)
  66. # [12:23] * Quits: besbes_ (n=besbes@falkenstein.mminf.univie.ac.at) (Read error: 60 (Operation timed out))
  67. # [12:25] * Quits: Politoed (i=Sholsest@a83-132-177-9.cpe.netcabo.pt) (Read error: 104 (Connection reset by peer))
  68. # [12:27] * Joins: georgebrock (n=georgebr@host81-158-242-88.range81-158.btcentralplus.com)
  69. # [12:28] * Quits: georgebrock (n=georgebr@host81-158-242-88.range81-158.btcentralplus.com) (Client Quit)
  70. # [12:30] * Joins: georgebrock (n=georgebr@host81-158-242-88.range81-158.btcentralplus.com)
  71. # [12:50] * Quits: gsnedders (n=gsnedder@host86-136-52-180.range86-136.btcentralplus.com) (Remote closed the connection)
  72. # [13:06] * Quits: Prometheus (n=promethe@unaffiliated/prometheus) (Read error: 54 (Connection reset by peer))
  73. # [13:11] * Joins: eaton (n=eaton@drupal.org/user/16496/view)
  74. # [13:17] * Quits: eaton (n=eaton@drupal.org/user/16496/view)
  75. # [13:21] * Joins: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com)
  76. # [13:34] * Joins: _fil_ (n=fil@217.24.84.10)
  77. # [13:35] * Joins: Prometheus (n=promethe@unaffiliated/prometheus)
  78. # [13:37] <mfbot> ThomasLoertsch edited hrecipe "/* ingredient */ typo correction" (+2) http://is.gd/vzSz
  79. # [13:49] * Joins: eaton (n=eaton@drupal.org/user/16496/view)
  80. # [13:58] * Quits: eaton (n=eaton@drupal.org/user/16496/view)
  81. # [14:10] * Joins: besbes_ (n=besbes@securewlan-239-151.pns.univie.ac.at)
  82. # [14:16] * Quits: besbes (n=besbes@mercury.mminf.univie.ac.at) (Read error: 110 (Connection timed out))
  83. # [14:20] * Quits: shigeta_ (n=shigeta@124.32.114.226) ("Leaving...")
  84. # [14:40] * Joins: ajturner (n=ajturner@209.155.228.129)
  85. # [14:56] * Quits: georgebrock (n=georgebr@host81-158-242-88.range81-158.btcentralplus.com)
  86. # [14:57] * Joins: memload (n=jamesjef@82.37.24.167)
  87. # [15:31] * Quits: besbes_ (n=besbes@securewlan-239-151.pns.univie.ac.at)
  88. # [15:36] * Quits: Prometheus (n=promethe@unaffiliated/prometheus) ("⏏")
  89. # [15:42] * Joins: besbes (n=besbes@falkenstein.mminf.univie.ac.at)
  90. # [15:45] * Joins: besbes_ (n=besbes@vpn-119.pri.univie.ac.at)
  91. # [15:46] * Quits: ntoll (n=ntoll@85.210.101.94) ("this is not a quit message")
  92. # [15:48] * Joins: besbes__ (n=besbes@falkenstein.mminf.univie.ac.at)
  93. # [15:53] * Joins: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  94. # [15:54] * Quits: besbes_ (n=besbes@vpn-119.pri.univie.ac.at) (Read error: 60 (Operation timed out))
  95. # [16:03] * Quits: besbes (n=besbes@falkenstein.mminf.univie.ac.at) (Read error: 110 (Connection timed out))
  96. # [16:21] * Quits: petercoulton (n=petercou@5ac0c364.bb.sky.com) ("Leaving")
  97. # [16:47] * Joins: dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  98. # [16:47] * ChanServ sets mode: +o dglazkov
  99. # [16:55] * Joins: cgriego (n=cgriego@out-02.hotels.com)
  100. # [17:02] * Quits: @dglazkov (n=dglazkov@c-98-207-88-44.hsd1.ca.comcast.net)
  101. # [17:03] * Joins: gsnedders (n=gsnedder@host86-136-52-180.range86-136.btcentralplus.com)
  102. # [17:21] * Joins: besbes (n=besbes@131.130.33.118)
  103. # [17:26] * Quits: besbes (n=besbes@131.130.33.118) (Remote closed the connection)
  104. # [17:26] * Joins: besbes (n=besbes@vpn-118.pri.univie.ac.at)
  105. # [17:27] * Quits: besbes (n=besbes@vpn-118.pri.univie.ac.at) (Remote closed the connection)
  106. # [17:28] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  107. # [17:28] * ChanServ sets mode: +o tantek
  108. # [17:28] * Joins: Prometheus (n=promethe@unaffiliated/prometheus)
  109. # [17:33] * Joins: dglazkov (n=dglazkov@nat/google/x-dd5d2d69cd4b946c)
  110. # [17:33] * ChanServ sets mode: +o dglazkov
  111. # [17:40] * Quits: besbes__ (n=besbes@falkenstein.mminf.univie.ac.at) (Read error: 110 (Connection timed out))
  112. # [17:41] <mfbot> Tantek edited value-class-pattern "/* Parsing date and time concatenation */ link fix" (+0) http://is.gd/vDbn
  113. # [17:47] * Joins: singpolyma (n=singpoly@node-6457.tor.pppoe.execulink.com)
  114. # [18:00] * Quits: levitation[A] (n=levitati@rubiin.physic.ut.ee) (Remote closed the connection)
  115. # [18:09] * Quits: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  116. # [18:11] * Joins: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  117. # [18:24] * Joins: petercoulton (n=petercou@5ac0c364.bb.sky.com)
  118. # [18:26] * Quits: Prometheus (n=promethe@unaffiliated/prometheus) ("⏏")
  119. # [18:27] * Joins: to__ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  120. # [18:29] * Joins: levitation[A] (n=levitati@rubiin.physic.ut.ee)
  121. # [18:35] * Quits: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr) (Connection timed out)
  122. # [18:36] * Quits: tobyink (n=tai@77.89.160.246) ("Leaving.")
  123. # [18:50] * Joins: jonrohan (n=jrohan@208.82.18.93)
  124. # [18:55] * Joins: leahculver (n=leahculv@204.9.180.30)
  125. # [18:57] * Quits: singpolyma (n=singpoly@node-6457.tor.pppoe.execulink.com) ("Lost terminal")
  126. # [19:02] * Quits: MrTopf (n=cs@p5B3965B4.dip.t-dialin.net)
  127. # [19:08] * Quits: petercoulton (n=petercou@5ac0c364.bb.sky.com) ("Leaving")
  128. # [19:08] * Joins: petercoulton (n=petercou@5ac0c364.bb.sky.com)
  129. # [19:22] * Joins: Hey_neken (n=kaxero@215.Red-213-96-129.staticIP.rima-tde.net)
  130. # [19:41] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) (Read error: 54 (Connection reset by peer))
  131. # [19:42] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
  132. # [19:42] * ChanServ sets mode: +o tantek
  133. # [19:48] * Parts: emrojo (n=emrojo@163.117.139.34)
  134. # [19:53] * Joins: eaton (n=eaton@drupal.org/user/16496/view)
  135. # [20:04] * Quits: eaton (n=eaton@drupal.org/user/16496/view)
  136. # [20:15] * Parts: jonrohan (n=jrohan@208.82.18.93)
  137. # [20:31] * Joins: singpolyma (n=singpoly@node-6457.tor.pppoe.execulink.com)
  138. # [20:33] <mfbot> Tantek edited value-class-pattern "allow HH of 24 per ISO8601" (+0) http://is.gd/vFpK
  139. # [20:43] * Joins: csarven (n=csarven@modemcable150.182-202-24.mc.videotron.ca)
  140. # [20:44] * Quits: ramsey (n=ramsey@unaffiliated/ramsey) (Read error: 110 (Connection timed out))
  141. # [20:51] * Quits: csarven (n=csarven@modemcable150.182-202-24.mc.videotron.ca) ("Leaving.")
  142. # [20:54] * Quits: singpolyma (n=singpoly@node-6457.tor.pppoe.execulink.com) ("Lost terminal")
  143. # [21:16] <mfbot> Tantek edited html5 "added requests for examples and parsing details for HTML5 (if any are needed)" (+430) http://is.gd/vFXG
  144. # [21:18] * Joins: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  145. # [21:21] * Joins: ramsey (n=ramsey@unaffiliated/ramsey)
  146. # [21:24] * Quits: to__ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr) (Success)
  147. # [21:41] <mfbot> Tantek edited licensing-formats "fix link" (+131) http://is.gd/vGfG
  148. # [21:41] <mfbot> Tantek edited licensing-formats "Reverted edits by [[Special:Contributions/Tantek|Tantek]] ([[User talk:Tantek|Talk]]) to last version by [[User:Mike Linksvayer|Mike Linksvayer]]" (-131) http://is.gd/vGgb
  149. # [21:43] <mfbot> Tantek edited licensing-formats "actually fix link, and add a related section cross-linking to related pages" (+113) http://is.gd/vGh8
  150. # [21:43] <mfbot> Tantek edited licensing-examples "added see also section" (+111) http://is.gd/vGhz
  151. # [21:44] <mfbot> Tantek edited licensing-brainstorming "added see also section" (+112) http://is.gd/vGi6
  152. # [21:46] * Joins: singpolyma (n=singpoly@node-6457.tor.pppoe.execulink.com)
  153. # [21:48] <mfbot> Tantek edited licensing "group/simplify use case hypotheses to "What" and "How to attribute"." (+141) http://is.gd/vGku
  154. # [21:49] <@tantek> Hixie, I've simplified what I see are reasonable and desirable use cases for a licensing microformat to two things: 1. *What* is being licensed, and 2. *How to attribute* (if necessary). I think that if a licensing microformat solved those two, then there wouldn't be a need for ccREL.
  155. # [21:49] <@tantek> See http://microformats.org/wiki/licensing#Usecases_hypothesis for details of that 1 and 2.
  156. # [21:51] <Hixie> seems like a link to a license would be good too
  157. # [21:51] <Hixie> :-)
  158. # [21:52] <@tantek> yes, amazing how we can forget the obvious :)
  159. # [21:54] <Hixie> would be nice to have an algorithm somewhere that, given an HTML DOM, defines how you get a list of URL-license pairs (along with whatever other information is there)
  160. # [21:55] <Hixie> one of the problems with microformats in general is that there isn't a clear way to distinguish where a microformat starts, e.g. "fn" and "vcard" appear the same to someone who doesn't know the hCard microformat
  161. # [21:55] <mfbot> Tantek edited licensing "/* Usecases hypothesis */ added obvious "what is the license" use case hypothesis - thanks Hixie" (+215) http://is.gd/vGpp
  162. # [21:55] <Hixie> this is both a pedagogical issue (noticing where the format starts and ends isn't clear, especially with lots of "css clases" around to muddle the issue)
  163. # [21:56] <@tantek> Hixie, the clear way to distinguish where a microformat starts is the root class name. http://microformats.org/wiki/hcard-parsing#root_class_name
  164. # [21:57] <Hixie> and a more practical issue for people who want to take pages and hand them off to an inference engine (e.g. wolfram alpha) or expose the data to an API (e.g. searchmonkey)
  165. # [21:57] * Joins: benward (n=benward@65.164.123.28)
  166. # [21:57] * ChanServ sets mode: +o benward
  167. # [21:57] <Hixie> right, there's no way to know without knowing the format, that's what i mean
  168. # [21:59] <@tantek> ah ok - what you're really asking (without knowing you were asking) is, given a URL to an XMDP (which is how microformats are defined, similar to DTDs defining your HTML), how do you know what is the root class name?
  169. # [22:01] <Hixie> no, because i don't think anyone in practice will actually provide XMDPs
  170. # [22:01] <@tantek> how is that any different from anyone in practice providing DTDs?
  171. # [22:02] <Hixie> it's not -- you have to know the HTML spec to parse text/html. Which is a problem, and is why people use XML for a lot of things.
  172. # [22:05] <@tantek> but that's ok because the crowd that uses XML for a lot of things is also very particular about including DTDs, thus can use XHTML in that way, and also be very particular about including XMDPs.
  173. # [22:05] <Hixie> searchmonkey is a counter-example to that
  174. # [22:06] <@tantek> is searchmonkey indexing random XML?
  175. # [22:06] <Hixie> searchmonkey intends to expose arbitrary vocabularies that people come up with, including those microformats that might be invented later, but it can't parse them if it doesn't know about them
  176. # [22:06] <@tantek> so searchmonkey provides incentive for inclusion of XMDP URLs then
  177. # [22:07] <@tantek> because searchmonkey can simply read those XMDPs and discover new microformats in that fashion
  178. # [22:07] <@tantek> new poshformats for that matter
  179. # [22:07] <Hixie> the idea is that it would expose information on pages that don't have any relationship with the person who wants to expose the data
  180. # [22:07] <@tantek> as anyone can write an XMDP that defines the classes and ids they are using
  181. # [22:07] <Hixie> e.g. how it can expose hCard on sites today
  182. # [22:07] <Hixie> those sites don't expose XMDP
  183. # [22:07] <@tantek> sure
  184. # [22:08] <Hixie> anyway, DTDs are an anti-pattern that i'm pretty sure we don't want to replicate here :-)
  185. # [22:08] <Hixie> especially after we got rid of them for HTML
  186. # [22:08] <@tantek> then they might as well just index all classes and IDs
  187. # [22:08] <Hixie> sure but how do they know which classes and IDs are "root" classes and IDS?
  188. # [22:09] <@tantek> there have been proposals to include that in the microformats themselves
  189. # [22:09] <@tantek> without the need for XMDP
  190. # [22:10] <@tantek> BTW I don't see DTDs as much as an anti-pattern as a threshold to meet to answer the "URI extensibility" crowd's questions/issues, since that crowd seems happy with DTDs, all you need is something "just as good".
  191. # [22:11] <@tantek> Hixie, the problem of indicating the root class is also one that overlaps with indicating when a parser has encountered another piece of microformatted information that it shouldn't be looking inside for properties for some microformat higher up in the parse tree.
  192. # [22:12] <@tantek> there is some thinking on that here: http://microformats.org/wiki/mfo
  193. # [22:13] <@tantek> anyway, solutions proposed to date (e.g. RDFa) are generally considered too fragile (authors/developers won't maintain them) to be worthy of pursuing
  194. # [22:13] <@tantek> I'd rather say, there is no solution now, than offer a solution which is expectedly fragile and due to induce/cause data loss in the future.
  195. # [22:15] <@tantek> however, it all you're looking to do is *experiment* with a format (say in a specific vertical area perhaps not significantly published on the web in order to merit a microformat), then random XML, or RDFa etc. may make sense
  196. # [22:15] <@tantek> but even in those cases, I encourage people to do what web designers have been doing for years - just use semantic class names of your own
  197. # [22:15] <@tantek> or the larger practice of semantic HTML
  198. # [22:15] <@tantek> http://microformats.org/wiki/posh
  199. # [22:16] <@tantek> btw, speaking of anti-patterns
  200. # [22:17] <@tantek> the whole notion of wanting to "expose arbitrary vocabularies" is fairly fundamentally flawed, or rather, will only result in Babel.
  201. # [22:25] <mfbot> Tantek edited xmdp-brainstorming "/* root class name identification */ added inline alternative possibility" (+1301) http://is.gd/vGLh
  202. # [22:28] * Joins: thomasknoll (n=thomaskn@173.11.69.17)
  203. # [22:31] <Hixie> tantek: i don't really care about that crowd as you put it, i'm more worried about things like people wanting to mark up their family history and have searchmonkey then expose it, without them having to get Yahoo! to implement their custom little set of class values
  204. # [22:33] <Hixie> tantek: i don't see why my dad shouldn't be able to mark up his family history pages in a way that he can then extract data from in a consistent manner using tools
  205. # [22:33] <Hixie> tantek: we already have the tower of babel "problem" with class names in general
  206. # [22:42] * Quits: singpolyma (n=singpoly@node-6457.tor.pppoe.execulink.com) ("Lost terminal")
  207. # [22:43] * Joins: to__ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  208. # [22:49] * Quits: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr) (Read error: 110 (Connection timed out))
  209. # [22:53] <Hixie> incidentally what is "hreview-aggregate"? i see it on http://www.tripadvisor.com/Hotel_Review-g155032-d185642-Reviews-La_Maison_Pierre_du_Calvet-Montreal_Quebec.html
  210. # [22:53] <Hixie> but it doesn't seem to be on the hreview wiki page
  211. # [22:54] <Hixie> oh, found it on http://microformats.org/wiki/aggregate-microformat-template-brainstorming
  212. # [22:55] <Hixie> not so hypothetical i guess
  213. # [23:06] <@tantek> hReview aggregate is a microformat being pursued by a bunch of folks, some of them at Google
  214. # [23:06] <Hixie> cool
  215. # [23:07] <@tantek> interesting, I didn't realize sites were trying it out in the wild yet
  216. # [23:08] <@tantek> regarding family history / genealogy, there's the "just use hCard + XFN" answer, and then there's more here: http://microformats.org/wiki/genealogy
  217. # [23:09] <Hixie> and for marklin model trains, is there a microformat for that too?
  218. # [23:09] <Hixie> microformats aren't going to cover everything people want
  219. # [23:09] <Hixie> which is fine
  220. # [23:09] <@tantek> precisely, and that's by design!
  221. # [23:09] <@tantek> http://microformats.org/wiki/microformats#microformats_are_not
  222. # [23:09] <@tantek> since inception
  223. # [23:09] <Hixie> but that doesn't mean that small groups of people aren't going to want to do the same kind of thing with their own pages in small groups
  224. # [23:10] <Hixie> e.g. a bunch of students in a class writing content that the professor aggregates
  225. # [23:10] <Hixie> (university of mary does this with blogs iirc)
  226. # [23:10] <Hixie> right now it's not clear how to write a generic tool to handle arbitrary vocabularies
  227. # [23:11] <@tantek> Hixie, there is a larger problem which is that small groups of people are rarely going to have the necessary experience/skills to actually produce a good data format
  228. # [23:11] <@tantek> including vocabulary
  229. # [23:11] <Hixie> it doesn't have to be good
  230. # [23:11] <Hixie> it just have to be good enough to work for them
  231. # [23:11] <@tantek> so it is inevitable that there will be a bunch of one-off experimental short term vocabularies
  232. # [23:11] <@tantek> sure, for those folks, they can "just use XML" as it has been used to date
  233. # [23:11] <Hixie> i don't think that's reasonable
  234. # [23:12] <Hixie> they have html content, why can't they annotate it like the big boys?
  235. # [23:12] <@tantek> see above - it takes "big boys" with necessary experience/skills to actually produce a good data format
  236. # [23:14] <@tantek> alternatively they can do what web designers have been doing before microformats even existed
  237. # [23:14] <@tantek> just use semantic class names and posh in general http://microformats.org/wiki/posh
  238. # [23:14] <@tantek> perhaps even create their own poshformats if they really want to try to start creating a "format" per se: http://microformats.org/wiki/poshformats
  239. # [23:15] <@tantek> there are entire disciplines dedicated to this kind of thing, like Information Architecture
  240. # [23:16] <@tantek> it is actually much more unresasonable to expect that small groups of people are going to be able to create something which actually takes some amount of expertise (in known and studied fields) to create
  241. # [23:17] <Hixie> i think it's unreasonable to say that a small group of people can't use generic tools to annotate their markup
  242. # [23:18] <Hixie> for that matter, i think it's unreasonable to require that every microformat has to have its own dedicated parser that knows about all the class names to get the data into a reusable and exposable data structure
  243. # [23:18] <Hixie> even text/html's parser doesn't know about all the tags in html. :-)
  244. # [23:18] <Hixie> and that's a pretty screwed up language :-)
  245. # [23:19] * Joins: azazul (n=azazul@zelli-kojas.lanet.lv)
  246. # [23:19] <@tantek> it's the very act of annotation, in any meaningful sense (using a vocabulary etc) that's the hard part
  247. # [23:20] <@tantek> it's not unreasonable to say that, just as it's not unreasonable to say that a small groups of people can't use generic tools to build an airplane
  248. # [23:20] <Hixie> but they can
  249. # [23:21] <@tantek> not without being skilled
  250. # [23:21] <Hixie> you can totally use generic CAD programs and CNC lathes and so forth
  251. # [23:21] <Hixie> i've done it myself
  252. # [23:21] <Hixie> and i'm hardly skilled
  253. # [23:21] <@tantek> you might be able to build something that looks like an airplane, but it won't actually fly
  254. # [23:21] <Hixie> sure, but they can still use the tools
  255. # [23:22] <@tantek> similarly, groups may be able to build something to looks like decent annotations, but it won't actually work to share data
  256. # [23:22] <Hixie> it doesn't need to work on a large scale, it only has to be good enough for their own needs
  257. # [23:23] <@tantek> right, the airplane they build won't go short distances, across town even, nevermind large scales like across continents
  258. # [23:23] <Hixie> tell that to the FIRST robotics teams
  259. # [23:23] <@tantek> it's not that much different than saying they can't write code just for their own needs too
  260. # [23:24] <Hixie> every year, kids around the world build robots using generic tools that work very well
  261. # [23:24] <Hixie> and getting basic annotation-like stuff working on a limited basis isn't anywhere near as complex as building a robot
  262. # [23:24] <@tantek> it might be more complex/difficult actually
  263. # [23:24] <@tantek> because with annotation, the tests are all abstract, data etc.
  264. # [23:25] <@tantek> whereas with a robot, physics gives you good feedback at every step as to whether you're making a mistake or making progress
  265. # [23:26] <Hixie> if you have a specific goal in mind, e.g. aggregating a bunch of documents, then testing is easy.
  266. # [23:26] <Hixie> and that's the kind of thing we're talking about here.
  267. # [23:26] <Hixie> specific concrete goals that need minor annotation support, and the ability to use generic tools to achieve the results
  268. # [23:27] <@tantek> sure, and you might say RDF has been trying to solve that problem for 15+ years
  269. # [23:27] <Hixie> RDF fails to solve that problem on so many levels it's not even worth discussing here
  270. # [23:27] <@tantek> that's not the point
  271. # [23:28] <Hixie> then what's the point? one group failed so we must give up?
  272. # [23:28] <@tantek> the people who set out with the goal of creating generic tools for annotation have followed that path
  273. # [23:28] <@tantek> not necessarily give up, but perhaps solve simpler problems first
  274. # [23:28] <@tantek> learn from solving those simpler problems, perhaps with hardcoded vocabularies, parsers etc.
  275. # [23:28] <Hixie> i believe the problem i'm describing is orders of magnitude simpler than the problems the RDF community set out to solve
  276. # [23:29] <@tantek> and *maybe* we might have sufficient wisdom some day to actually produce a solution to the generic tools problem
  277. # [23:29] <@tantek> Hixie, it doesn't sound like it
  278. # [23:29] <Hixie> either you underestimate the kind of problems they want to solve, or you overestimate my ambition :-)
  279. # [23:30] <@tantek> your scoping of annotation by groups and using "generic tools" matches the RDF community
  280. # [23:31] <Hixie> so does my using english :-)
  281. # [23:31] <@tantek> in the case of English, so does microformats http://microformats.org/wiki/en-US
  282. # [23:32] <Hixie> my point is that just because there are similarities doesn't mean the same problem is being solved. That, if anything, is the mistake many RDF proponents make a lot.
  283. # [23:32] <@tantek> sure, I tend to agree with that statement
  284. # [23:33] <@tantek> however, if two things resemble each other, it's important to point out why it's different
  285. # [23:33] <@tantek> otherwise you fall prey to the "quacks like a duck" problem
  286. # [23:34] <Hixie> ok, things rdf attempts to solve that i have no interest in solving: a generic data model that can describe anything; preventing name clashes; defining schemas; ability to reason or perform inference based on the data; ability to translate from one vocabulary to another
  287. # [23:35] <@tantek> and arbitrary annotation, small groups, generic tools are all very much "smells like RDF", or before RDF, smells like "knowledge representation" an already well trudged field of AI
  288. # [23:35] <Hixie> it also smells of xml and json
  289. # [23:35] <Hixie> and sgml
  290. # [23:35] <@tantek> RDF itself has had (still has) difficulty distinguishing itself from KR
  291. # [23:36] <@tantek> http://en.wikipedia.org/wiki/Knowledge_representation
  292. # [23:37] <@tantek> "ability to reason or perform inference based on the data; ability to translate from one vocabulary to another" are more OWL than RDF
  293. # [23:38] <@tantek> generic data model sounds like arbitrary annotations
  294. # [23:38] <@tantek> (vice versa)
  295. # [23:39] <@tantek> "defining schemas" is not that different from "defining vocabularies" especially if you start to add things like, what's the root, etc.
  296. # [23:39] <@tantek> that just leaves "preventing name clashes" - so what you've described then is just RDF without namespaces
  297. # [23:46] <Hixie> i disagree with most of that but the key one is that i don't think we should define what the root is in a definition of a vocabulary
  298. # [23:46] <Hixie> i think it needs to be syntacticaly self-evident
  299. # [23:47] <@tantek> interesting
  300. # [23:47] * Joins: to_ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr)
  301. # [23:49] <@tantek> we have found cases where it was useful to alter the definition of what was a root after the fact, and without problems
  302. # [23:49] <@tantek> e.g. in hCard the root is the class name "vcard"
  303. # [23:49] <@tantek> however we found use cases for separate/lone addresses and geo coordinates
  304. # [23:50] <@tantek> and thus defined the "adr" and "geo" microformats as proper subsets of hCard with those two respective class names as roots
  305. # [23:50] <Hixie> yeah i was looking at adr in particular recently
  306. # [23:50] <@tantek> thus, I would offer that experience to date shows that it might not be desirable to require that the root is syntactically self-evident.
  307. # [23:50] <Hixie> and wondering whether if we did add some way to indicate a "root" of some kind, it might make sense to have a way to indicate that a root is still part of another object as well
  308. # [23:52] <@tantek> I believe we approached an isomorphic problem from a different direction, that is, it can be useful to be able to know that a contained microformat's properties should not affect the container - thus mfo http://microformats.org/wiki/mfo
  309. # [23:53] <@tantek> and this has been based upon the experience of developing hAtom and hAudio
  310. # [23:53] <@tantek> again - as before - reasoning from experience rather than just a priori needs
  311. # [23:54] * Quits: to__ (n=abernier@AAubervilliers-551-1-53-8.w86-212.abo.wanadoo.fr) (Connection timed out)
  312. # Session Close: Fri May 01 00:00:00 2009

The end :)