Options:
- # Session Start: Tue Jun 30 00:00:00 2009
- # Session Ident: #microformats
- # [00:05] * Quits: gsnedders (n=gsnedder@c83-252-197-166.bredband.comhem.se)
- # [00:05] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [00:05] * ChanServ sets mode: +o tantek
- # [00:05] * Quits: ntoll (n=ntoll@88-111-137-153.dynamic.dsl.as9105.com) ("this is not a quit message")
- # [00:14] * Joins: georgebrock (n=georgebr@client-86-25-199-236.cht-bng-011.adsl.virginmedia.net)
- # [00:15] * Joins: maddiin (n=mc@unaffiliated/maddiin)
- # [00:20] * Joins: tim_hwang (n=chatzill@65.112.9.178)
- # [00:22] * Joins: gsnedders (n=gsnedder@c83-252-197-166.bredband.comhem.se)
- # [00:25] <maddiin> hey there
- # [00:29] * Joins: jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net)
- # [00:29] <maddiin> I want to use hAtom in a blog, this is what I have done right now http://paste.pocoo.org/show/Ji8j2cc2deZPNCeJPUTf/
- # [00:30] <mfbot> Tantek edited mailing-lists "document theoretical examples (explicitly label them as theoretical) rather than ignore to reduce reraising. document on a brainstorming page, where they can be (de)prioritized accordingly." (+563) http://is.gd/1irZL
- # [00:30] <maddiin> should I avoid classnames similar to the schema like entry-meta, entry-related, etc. and if so, what would you suggest?
- # [00:30] <hober> IIRC I use entry-meta like that
- # [00:31] <singpolyma> maddiin: If the classnames aren't in the schema it doesn't really matter if they're "similar"
- # [00:31] <maddiin> hober, singpolyma: thanks
- # [00:41] * Quits: gsnedders (n=gsnedder@c83-252-197-166.bredband.comhem.se)
- # [00:41] * Quits: georgebrock (n=georgebr@client-86-25-199-236.cht-bng-011.adsl.virginmedia.net)
- # [00:42] * Quits: Jon (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net) (Read error: 110 (Connection timed out))
- # [00:51] <mfbot> Tantek edited put-it-on-the-wiki "add examples of types of content to add to the wiki and where such content should go." (+2537) http://is.gd/1isXf
- # [00:51] <mfbot> Tantek created citations "redir" http://is.gd/1isZ6
- # [00:54] <mfbot> Tantek created reviews "redir" http://is.gd/1it5L
- # [00:56] <mfbot> Tantek created listing "draft" http://is.gd/1itci
- # [00:56] <mfbot> Tantek created listings "Redirecting to [[listing]]" http://is.gd/1itcT
- # [01:00] <mfbot> Tantek created recipes "redir" http://is.gd/1itpO
- # [01:01] * Joins: memload (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk)
- # [01:08] * Quits: Hey_neken (n=kaxero@215.Red-213-96-129.staticIP.rima-tde.net) (Read error: 113 (No route to host))
- # [01:09] * Joins: georgebrock (n=georgebr@client-86-25-199-236.cht-bng-011.adsl.virginmedia.net)
- # [01:11] * Quits: georgebrock (n=georgebr@client-86-25-199-236.cht-bng-011.adsl.virginmedia.net) (Client Quit)
- # [01:28] * Quits: memload (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk) (Client Quit)
- # [01:31] <@tantek> hober, your recent tweet/post mentioned the HTML Design Principles http://www.w3.org/TR/html-design-principles/, and I can't help but notice many similarities to the (priori art of the) microformats principles http://microformats.org/wiki/principles
- # [01:32] <@tantek> many of these principles individually predate microformats as well, however it is interesting that so many microformats principles were incorporated as a set into the HTML Design Principles, e.g.
- # [01:33] <@tantek> http://www.w3.org/TR/html-design-principles/#do-not-reinvent-the-wheel is essentially a negative avoidance restatement of "reuse" http://microformats.org/wiki/reuse
- # [01:34] <@tantek> http://www.w3.org/TR/html-design-principles/#pave-the-cowpaths is directly quoted from http://microformats.org/wiki/microformats, which cites Adam Rifkin's essay of the same title: http://ifindkarma.typepad.com/relax/2004/12/microformats.html
- # [01:35] <@tantek> http://www.w3.org/TR/html-design-principles/#evolution-not-revolution is nearly the same as the quote on http://microformats.org/wiki/microformats "An evolutionary revolution" - a blog post cited by Ryan King: http://theryanking.com/blog/archives/2005/04/07/an-evolutionary-revolution/
- # [01:38] * Quits: Zitter (n=danilo@93-42-153-78.ip87.fastwebnet.it) (Read error: 104 (Connection reset by peer))
- # [01:38] <@tantek> http://www.w3.org/TR/html-design-principles/#solve-real-problems - again as mentioned on http://microformats.org/wiki/microformats , the emphasis on solving *real world* problems has been part of microformats since the presentation that introduced the term "microformat" - "real world semantics" - http://www.tantek.com/presentations/2004etech/realworldsemanticspres.html
- # [01:41] <@tantek> http://www.w3.org/TR/html-design-principles/#priority-of-constituencies - (which sounds reasonable) specifically mentions to consider "authors over implementors" which microformats has specifically mentioned as being "publisher-centric in design rather than parser-centric" - http://microformats.org/wiki/principles#lowering-barriers
- # [01:43] <@tantek> http://www.w3.org/TR/html-design-principles/#avoid-needless-complexity - again a negative avoidance restatement of "start as simple as possible" as stated on the above-mentioned http://microformats.org/wiki/principles page, and expanded upon in http://microformats.org/wiki/start-simple
- # [01:45] <@tantek> much of the microformats principles noted above are barely changed from when they were published on microformats.org at its launch on 2005-06-20: http://microformats.org/about/
- # [01:45] <@tantek> which clearly predates by more than 2 years the 2007-11-26 date of http://www.w3.org/TR/2007/WD-html-design-principles-20071126/
- # [01:47] <@tantek> thus if I've kept count correctly, that's 6 out of the 16 HTML Design Principles, specifically the subsections (e.g. 2.1,2.2,2.3,2.4,2.5, 3.1 etc.) that very much appear to have originated from microformats principles
- # [01:50] <@tantek> hober, the bottom of the HTML Design Principles says "If you contributed to this document, but your name is not listed above please let the editors know so they can correct this omission." - given that many of those authors knew of the microformats principles (I remember personally discussing several of the microformats principles and merits there of with about half dozen of the editors/acknowledged contributors) - it would
- # [01:52] <@tantek> hober, does this seem reasonable to you? if so, perhaps you could suggest an effective means of letting "the editors know". thanks!
- # [01:54] * Quits: @dglazkov (n=dglazkov@nat/google/x-6eeaf0058876cab4)
- # [01:55] * Joins: dglazkov (n=dglazkov@nat/google/x-d2313608083350f3)
- # [01:55] * ChanServ sets mode: +o dglazkov
- # [01:59] * Quits: @dglazkov (n=dglazkov@nat/google/x-d2313608083350f3) (Client Quit)
- # [02:00] * Joins: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk)
- # [02:12] * Joins: dane (n=dane@c-69-181-142-171.hsd1.ca.comcast.net)
- # [02:17] <mfbot> BenWard created Template:HTML-design-principles "Draft: HTML Design Principals. We've been directly citing XHTML and XML benefits for years, which is inaccurate given that we actually operate mostly in HTML now. Proposed update to principals." http://is.gd/1ixk7
- # [02:18] <mfbot> BenWard edited semantic-xhtml "/* forms */ Fixed mis-nested textarea hierachy" (-1) http://is.gd/1ixmV
- # [02:19] <@tantek> BenWard - might I suggest both not using a template for replaced content (since we agreed that was a misuse of template) as well as avoiding calling something "HTML Design Principles" which is already overloaded? (see above in IRC)
- # [02:21] <@benward> The use of Template is valid — it gets included by reference in lots of pages, currently: {{Template:xhtml-design-principals}} — so it is a Template (it's not a something that gets cut+pasted+modifed… I guess you could cal that a stencil…)
- # [02:22] <@benward> I've created it separately again for drafting, since editing the existing template would also change the content of all referencing pages (hCard, hCalendar, etc.)
- # [02:22] <@benward> As for the naming, yes we could change that.
- # [02:22] <@tantek> what's the purpose of the (re)drafting?
- # [02:23] * Joins: shigeta (n=shigeta@sakkgw2.sixapart.jp)
- # [02:23] <@tantek> (i.e. what problems is being solved)
- # [02:23] <@benward> The existing wording advocates and emphasises benefits of XML that are simply not applied to microformats in practice
- # [02:25] <@benward> Most microformats are published in HTML. The XML part is distracting/confusing here.
- # [02:26] <@tantek> indeed - that's true now. there's a bit of historical context there.
- # [02:26] <@benward> Separately, the final design principal instructs people to put data in <abbr>, which isn't worded appropriately given the more recent research/efforts we put into abbr/accessibilty, and the value-class-pattern is also a valid alternate.
- # [02:27] <@tantek> back when that was first authored (I think I wrote it up as part of hCard IIRC on the Technorati developers wiki originally), XML was actually expected to be used to publish arbitrary visual information on the web.
- # [02:27] <@benward> Indeed.
- # [02:27] * Quits: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk) (Read error: 104 (Connection reset by peer))
- # [02:27] * Joins: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk)
- # [02:28] <@tantek> given that this template affects hCard and hCalendar and I'm already making similar updates to both deemphasize XML and change abbr references to be value-class-pattern aware, I'd much rather prefer if you captured updating Template:semantic-xhtml-design-principles as an hcard-issue and hcalendar-issue rather than just fixing the template. - it's only one of many areas that needs fixing for those two issue.
- # [02:28] <@benward> And at the time there was great evangelical effort behind XHTML over HTML, the latter being used as a term for ‘old’ tag-soup, and ‘XHTML’ a differenciator for ‘new’ semantic XHTML. The new name made it easier to differentiate good/bad new/old practice, and easier to educate.
- # [02:29] <@tantek> er, http://microformats.org/wiki/hcard-issues , http://microformats.org/wiki/hcalendar-issues
- # [02:29] <@benward> OK, can do.
- # [02:30] <@benward> I think, from a document clarify perspective, I favour all of that text being removed from the specs themselves, and just linking to the one appropriate page documenting the design principals separately.
- # [02:30] <@tantek> and yeah, agreed, the great differentiating benefits of XHTML over HTML never really materialized.
- # [02:30] <@tantek> I tend to agree with that direction, hence have been updating and fleshing out the principles on their own pages quite a bit in the past few weeks.
- # [02:31] <@tantek> e.g. http://microformats.org/wiki/principles
- # [02:31] <@tantek> http://microformats.org/wiki/start-simple
- # [02:31] <@tantek> http://microformats.org/wiki/reuse
- # [02:31] <@tantek> and http://microformats.org/wiki/naming-principles
- # [02:31] <@benward> It would be more manageable for us, and would improve the readability of /hcard and /hcalendar, letting people get to the core content sooner without diversions.
- # [02:31] <@tantek> yes, agreed
- # [02:32] <@tantek> indeed I did that some time ago for hCard
- # [02:33] <@tantek> note that hCard no longer includes that template
- # [02:33] <singpolyma> <@tantek> and yeah, agreed, the great differentiating benefits of XHTML over HTML never really materialized.
- # [02:33] <@tantek> and the related section is near the end of hCard: http://microformats.org/wiki/hcard#Notes_on_derivation_from_vCard
- # [02:33] <singpolyma> Except for the "easier to parse for scrapers" part
- # [02:33] * singpolyma <<---- scraper
- # [02:33] <@tantek> which itself links to http://microformats.org/wiki/hcard-design-methodology
- # [02:36] <@tantek> BenWard, was there some other aspect improving the readability of /wiki/hcard , letting people get to the core content sooner without diversions not related to Template:semantic-xhtml-design-principles that I missed?
- # [02:36] <@benward> tantek Erm, not in this thread no. I intend to do a review of it for you at some point though, with 1.0.1 and 1.1 in sight
- # [02:37] <@tantek> ok, cool. appreciated.
- # [02:39] * Quits: maddiin (n=mc@unaffiliated/maddiin)
- # [02:40] * Quits: tim_hwang (n=chatzill@65.112.9.178) (Read error: 110 (Connection timed out))
- # [02:41] * Quits: dwhittle (n=dwhittle@nat/yahoo/x-a812beb9866e458f) ("Im gone.")
- # [02:46] * Quits: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk) (Connection timed out)
- # [02:47] * Joins: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk)
- # [02:48] * Joins: Atamido_ (n=atamido@cpe-72-179-49-46.austin.res.rr.com)
- # [02:48] * Quits: Atamido (n=atamido@cpe-72-179-49-46.austin.res.rr.com) (Read error: 104 (Connection reset by peer))
- # [02:48] * Atamido_ is now known as Atamido
- # [03:03] * Quits: @benward (n=benward@nat/yahoo/x-879c26330e95836c) (Read error: 110 (Connection timed out))
- # [03:21] * Joins: pcwick (n=paul@173-30-110-19.client.mchsi.com)
- # [03:45] * Quits: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk) (Read error: 104 (Connection reset by peer))
- # [03:45] * Joins: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk)
- # [03:55] * Quits: pcwick (n=paul@173-30-110-19.client.mchsi.com) ("Ex-Chat")
- # [04:07] * Joins: pcwick (n=paul@173-30-110-19.client.mchsi.com)
- # [04:08] * Quits: singpolyma (n=singpoly@173-11-94-130-SFBA.hfc.comcastbusiness.net) ("Lost terminal")
- # [04:09] * Joins: dglazkov (n=dglazkov@c-69-181-143-54.hsd1.ca.comcast.net)
- # [04:09] * ChanServ sets mode: +o dglazkov
- # [04:34] * Quits: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk) (Read error: 104 (Connection reset by peer))
- # [04:35] * Joins: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk)
- # [04:39] * Quits: @dglazkov (n=dglazkov@c-69-181-143-54.hsd1.ca.comcast.net)
- # [04:46] * Quits: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk) (Read error: 104 (Connection reset by peer))
- # [04:47] * Joins: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk)
- # [04:50] * Joins: singpolyma (n=singpoly@c-76-21-5-96.hsd1.ca.comcast.net)
- # [04:53] * Joins: benward (n=benward@98.210.154.133)
- # [04:53] * ChanServ sets mode: +o benward
- # [05:00] * Joins: tim_hwang (n=chatzill@c-71-192-163-225.hsd1.nh.comcast.net)
- # [05:00] * Quits: milkmiruku (n=milk@82-41-66-19.cable.ubr09.sgyl.blueyonder.co.uk) ("www.milkmiruku.com")
- # [05:13] <hober> tantek: yes, that sounds reasonable; I'll ping maciej to that effect
- # [05:15] <hober> It's really not at all surprising that there's so much overlap--the principles that overlap are general good design principles for any technology intended for the web
- # [05:15] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [05:15] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [05:15] * ChanServ sets mode: +o tantek
- # [05:44] * Joins: dglazkov (n=dglazkov@c-69-181-143-54.hsd1.ca.comcast.net)
- # [05:44] * ChanServ sets mode: +o dglazkov
- # [05:49] * Joins: besbes (n=besbes@188-23-191-68.adsl.highway.telekom.at)
- # [06:07] * Quits: besbes__ (n=besbes@91-115-190-222.adsl.highway.telekom.at) (Read error: 110 (Connection timed out))
- # [06:13] * Joins: shigeta_ (n=shigeta@sakkgw2.sixapart.jp)
- # [06:29] * Quits: shigeta (n=shigeta@sakkgw2.sixapart.jp) (Read error: 110 (Connection timed out))
- # [06:55] * Quits: tim_hwang (n=chatzill@c-71-192-163-225.hsd1.nh.comcast.net) (Remote closed the connection)
- # [06:56] * Quits: RobotDeathSquad_ (n=RobotDea@c-71-237-177-242.hsd1.or.comcast.net)
- # [07:00] * Quits: BobJonkman (n=BobJonkm@206.248.137.186) (Read error: 110 (Connection timed out))
- # [07:02] * Joins: RobotDeathSquad (n=RobotDea@c-71-237-177-242.hsd1.or.comcast.net)
- # [07:04] * Quits: @dglazkov (n=dglazkov@c-69-181-143-54.hsd1.ca.comcast.net)
- # [07:09] * Quits: singpolyma (n=singpoly@c-76-21-5-96.hsd1.ca.comcast.net) ("Lost terminal")
- # [07:36] * Joins: singpolyma (n=singpoly@c-76-21-5-96.hsd1.ca.comcast.net)
- # [07:53] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [07:57] * Quits: csarven (n=csarven@24.202.182.150) ("Leaving.")
- # [08:07] * Joins: benward_ (n=benward@nat/yahoo/x-3e22cde9ba51b366)
- # [08:09] * Quits: @benward (n=benward@98.210.154.133) (Read error: 110 (Connection timed out))
- # [08:38] * Joins: pesla (n=retep@procurios.xs4all.nl)
- # [08:51] * Quits: besbes (n=besbes@188-23-191-68.adsl.highway.telekom.at)
- # [09:12] * Quits: singpolyma (n=singpoly@c-76-21-5-96.hsd1.ca.comcast.net) ("Lost terminal")
- # [09:13] * Joins: singpolyma (n=singpoly@c-76-21-5-96.hsd1.ca.comcast.net)
- # [09:13] * Quits: singpolyma (n=singpoly@c-76-21-5-96.hsd1.ca.comcast.net) (Client Quit)
- # [09:17] * Joins: besbes (n=besbes@mercury.mminf.univie.ac.at)
- # [09:19] * Joins: gsnedders (n=gsnedder@c83-252-197-166.bredband.comhem.se)
- # [09:27] * Quits: gsnedders (n=gsnedder@c83-252-197-166.bredband.comhem.se)
- # [09:34] * Quits: pcwick (n=paul@173-30-110-19.client.mchsi.com) ("Ex-Chat")
- # [10:01] * Joins: ebel (n=rory@unaffiliated/ebel)
- # [10:06] * Joins: tobyink (n=tai@77.89.160.246)
- # [11:07] * Joins: besbes_ (n=besbes@securewlan-238-146.pns.univie.ac.at)
- # [11:17] * Quits: besbes (n=besbes@mercury.mminf.univie.ac.at) (Read error: 110 (Connection timed out))
- # [11:25] <mfbot> ThomasLoertsch edited hrecipe "/* Field details */ typos..." (+36) http://is.gd/1iXix
- # [11:30] <mfbot> ThomasLoertsch edited hrecipe "/* Schema */ removed references to reused microformats" (-284) http://is.gd/1iXvu
- # [11:31] <mfbot> ThomasLoertsch edited hrecipe "/* duration */ " (+42) http://is.gd/1iXxq
- # [11:58] * Quits: CaptSolo (i=captsolo@kaste.lv) (Read error: 110 (Connection timed out))
- # [12:18] * Quits: besbes_ (n=besbes@securewlan-238-146.pns.univie.ac.at)
- # [12:24] * Joins: MrTopf (n=cs@81.187.73.203)
- # [12:25] <mfbot> ThomasLoertsch edited hrecipe "/* author */ " (+0) http://is.gd/1iZJF
- # [12:30] * Quits: MrTopf (n=cs@81.187.73.203) (Read error: 113 (No route to host))
- # [12:39] * Joins: MrTopf (n=cs@81.187.73.203)
- # [12:40] * Quits: benward_ (n=benward@nat/yahoo/x-3e22cde9ba51b366) ("Sleep")
- # [12:41] * Quits: MrTopf (n=cs@81.187.73.203) (Read error: 54 (Connection reset by peer))
- # [12:42] * Joins: MrTopf (n=cs@81.187.73.203)
- # [12:45] * Joins: besbes (n=besbes@131.130.33.44)
- # [13:05] * Quits: MrTopf (n=cs@81.187.73.203)
- # [13:12] * Joins: MrTopf (n=cs@81.187.73.203)
- # [13:16] * Quits: besbes (n=besbes@131.130.33.44) (Read error: 110 (Connection timed out))
- # [13:21] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 110 (Connection timed out))
- # [13:24] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
- # [13:27] * Joins: Phae (n=phaeness@gateb.mh.bbc.co.uk)
- # [13:27] * ChanServ sets mode: +o Phae
- # [13:33] * Joins: HerrTopf (n=cs@81.187.73.203)
- # [13:33] * Quits: MrTopf (n=cs@81.187.73.203) (Read error: 54 (Connection reset by peer))
- # [13:45] * HerrTopf is now known as MrTopf
- # [13:48] * Quits: dane (n=dane@c-69-181-142-171.hsd1.ca.comcast.net)
- # [13:49] * Quits: emrojo (n=emrojo@dummyhost12.it.uc3m.es) (Read error: 60 (Operation timed out))
- # [13:50] * Joins: emrojo (n=emrojo@163.117.139.228)
- # [14:03] * Joins: georgebrock (n=georgebr@86.25.199.236)
- # [14:05] * Quits: MrTopf (n=cs@81.187.73.203)
- # [14:09] * Quits: jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net) (Connection timed out)
- # [14:37] * Joins: besbes (n=besbes@securewlan-237-014.pns.univie.ac.at)
- # [14:48] * Joins: Atamido_ (n=atamido@cpe-72-179-49-46.austin.res.rr.com)
- # [14:48] * Quits: Atamido (n=atamido@cpe-72-179-49-46.austin.res.rr.com) (Read error: 104 (Connection reset by peer))
- # [14:48] * Atamido_ is now known as Atamido
- # [14:49] * Quits: besbes (n=besbes@securewlan-237-014.pns.univie.ac.at) (Read error: 60 (Operation timed out))
- # [14:54] * Joins: besbes (n=besbes@securewlan-237-014.pns.univie.ac.at)
- # [15:22] * Joins: MrTopf (n=cs@81.187.73.203)
- # [15:25] * Quits: MrTopf (n=cs@81.187.73.203) (Connection reset by peer)
- # [15:33] * Quits: besbes (n=besbes@securewlan-237-014.pns.univie.ac.at)
- # [15:44] * Quits: shigeta_ (n=shigeta@sakkgw2.sixapart.jp) ("Leaving...")
- # [15:49] * Joins: besbes (n=besbes@131.130.33.44)
- # [16:28] * Quits: azazul` (n=azazul@zelli-kojas.lanet.lv) (Read error: 54 (Connection reset by peer))
- # [16:28] * Joins: azazul` (n=azazul@zelli-kojas.lanet.lv)
- # [16:34] <mfbot> ThomasLoertsch edited hrecipe "/* Examples */ a lot of details changed and updated" (+577) http://is.gd/1jaVL
- # [16:36] * Joins: tim_hwang (n=chatzill@71.192.163.225)
- # [16:36] <mfbot> ThomasLoertsch edited hrecipe "/* nutrition */ typo" (+1) http://is.gd/1jb2P
- # [16:47] * Joins: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com)
- # [17:09] * Joins: tomlurge (n=tl@fwhide.guj.de)
- # [17:10] <tomlurge> hi! is this the correct way to encode a duration according to hAudio: <abbr class="duration" title="PT1H30M">90 min</abbr> ?
- # [17:12] <mfbot> ThomasLoertsch edited hrecipe "/* duration */ changed the reference from hCalender to hAudio" (+270) http://is.gd/1jcDz
- # [17:18] <mfbot> ThomasLoertsch edited hrecipe "/* duration */ " (-1) http://is.gd/1jcRm
- # [17:18] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [17:18] * ChanServ sets mode: +o tantek
- # [17:22] <tobyink> tomlurge: PT1H30M - yes.
- # [17:22] <tobyink> Though PT90M is also acceptable.
- # [17:23] <tobyink> Or even PT5400S.
- # [17:23] <tomlurge> oh, that's great!
- # [17:24] <tobyink> ISO 8601explicitly allows duration units to "overflow", and I don't think anyone's made an attempt at creating a subset of it such that each duration has a single canonical representation.
- # [17:24] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [17:24] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [17:24] * ChanServ sets mode: +o tantek
- # [17:25] <tomlurge> you know so much... :-)
- # [17:25] <tobyink> I wrote an ISO 8601 parser for Swignition. There's probably bugs in it, but it mostly works.
- # [17:26] <tomlurge> i wonder what made me reuse "type" and "value" from hCard for hRecipe. hCard is such a mess...
- # [17:27] <@tantek> tomlurge - what aspects of hCard do you find "a mess"?
- # [17:28] <tomlurge> hrecipe says: "The element MAY include the fields value and type following the conventions outlined in hCard." now i'm struggling to find those conventions...
- # [17:29] <@tantek> http://microformats.org/wiki/hcard#Value_excerpting
- # [17:29] <@tantek> and http://microformats.org/wiki/hcard#type_subproperty_values
- # [17:29] <@tantek> both found by search the hCard TOC for "value" and "type" respectively
- # [17:30] <@tantek> Certainly let me know if you have suggestions for better findability.
- # [17:31] <tomlurge> yes, i found it by search too. but first i tried browsing the page, then i tried the TOC, then the element list
- # [17:31] <tomlurge> it would be nice to have a description for everey element, ordered by element name, with all the appropriate (non-trivial) information about each element
- # [17:32] <tomlurge> like e.g. hRecipe :-)
- # [17:32] <@tantek> by "element" you mean "property" right?
- # [17:32] <tomlurge> yes
- # [17:32] <@tantek> like hReview :) http://microformats.org/wiki/hreview#Format
- # [17:33] <tomlurge> even better :-)
- # [17:34] <@tantek> microformats spec conventions definitely evolved with subsequent specs, in particular with specs that introduced new vocabulary (e.g. hReview)
- # [17:35] <tomlurge> i just imagined a poor idealistic user trying to follow all the links i carelessly added for best practices. i'm trying to inline the appropriate parts now and just realized how hard that is
- # [17:35] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) (Read error: 54 (Connection reset by peer))
- # [17:35] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [17:35] * ChanServ sets mode: +o tantek
- # [17:38] * Joins: dglazkov (n=dglazkov@nat/google/x-7162b9e2eed0e1bb)
- # [17:38] * ChanServ sets mode: +o dglazkov
- # [17:44] <mfbot> Tantek edited to-do "hCard 1.0.1 property descriptions, include any non-trivial details, next step, draft hCard 1.0.1 from hCard 1.0, incorporating resolved issues, similarly for hCalendar" (+905) http://is.gd/1je1W
- # [17:45] <@tantek> Thanks tomlurge, I've added this asnt: pecific to-do item for hCard 1.0.1 so that it is not forgotten.
- # [17:45] <tomlurge> you're welcome ;-)
- # [17:46] <tomlurge> native speakers, please: does the following make sense: "The element {{must}} follow the conventions outlined in [[hCard]]. Using only text will fulfill these requirements just fine." ?
- # [17:47] <@tantek> tomlurge - the convention for "element" vs. "property" is that "element" is used *only* for HTML elements, e.g. <a>, <span>, <div>
- # [17:47] <@tantek> whereas microformats use "property"
- # [17:47] <@tantek> I hope that helps
- # [17:48] <tomlurge> ah... okay. but i meant the second sentence
- # [17:48] <tomlurge> (btw: hReview uses "field")
- # [17:49] * Joins: singpolyma (n=singpoly@173-11-94-130-SFBA.hfc.comcastbusiness.net)
- # [17:49] <tobyink> possibly - "Using only text will fulfill these requirements just fine." -> "Plain text fulfils these requirements."
- # [17:50] <@tantek> tomlurge - yes that's a good point, no need to use a second term there in hReview - and I can very much respect that use of a second term may add confusion to non-native speakers
- # [17:51] <tomlurge> i'm looking for a phrase with the connotation: "in most cases you won't need anything more than plain text and therefor you don't have to bother with that messy hCard spec. just use plain text only, right?!"
- # [17:53] <tomlurge> okay, i'll go with tobyink
- # [17:53] <mfbot> ThomasLoertsch edited hrecipe "/* fn */ modified reference to hCard" (+40) http://is.gd/1jesW
- # [17:54] <@tantek> tomlurge, unless otherwise specified, a property is just text.
- # [17:55] <@tantek> e.g. - again, take a look at hReview
- # [17:56] <tomlurge> but a little note may safe the innocent goodintentioned implementor a painful search.... it's just a convenience :-)
- # [17:57] <@tantek> tomlurge - I disagree - stating "fulfils these requirements" over and over will add clutter and crowd out the key information which is just "text"
- # [17:57] <@tantek> it's not convenience - it actually adds "mess" as you put it
- # [17:58] <tomlurge> maybe you're right. but let me try first
- # [18:04] * Quits: pesla (n=retep@procurios.xs4all.nl) ("( www.nnscript.com :: NoNameScript 4.21 :: www.esnation.com )")
- # [18:06] <mfbot> Tantek edited hreview "replace use of "field" by "property" when the spec means property, reduce confusion by reducing the number of terms that are used to mean the same thing, remove a note which contradicted scope" (-32) http://is.gd/1jeX0
- # [18:07] <@tantek> tomlurge - per your point, I've removed the unnecessary use of the term "field" from hReview, and used the term "property" consistently - I would appreciate it if you could check it as a non-native en-speaker to see if that helps. http://microformats.org/wiki/hreview
- # [18:07] <tomlurge> i'm just doing the same for hRecipe
- # [18:09] <mfbot> ThomasLoertsch edited hreview "/* property details */ typo" (+0) http://is.gd/1jf6z
- # [18:10] <tomlurge> tantek: looks good to me
- # [18:13] * Quits: ebel (n=rory@unaffiliated/ebel) ("me goes home")
- # [18:13] <mfbot> Tantek edited hreview "move design principles just before References - most readers will not need to re-analyze how it was designed, and listing the properties sooner helps spec readability." (+172) http://is.gd/1jfhM
- # [18:13] <@tantek> thanks tomlurge
- # [18:15] <mfbot> ThomasLoertsch edited hrecipe "changed "element" and "field" to "property" (where appropriate)" (+96) http://is.gd/1jfms
- # [18:16] <mfbot> Tantek edited hreview "remove explicit TOC (auto-placement works fine), moved acknowledgments to end near references to move property list to sooner in the document" (-11) http://is.gd/1jfqa
- # [18:17] <mfbot> ThomasLoertsch edited hrecipe "/* ingredient */ arg" (+2) http://is.gd/1jfqQ
- # [18:25] <mfbot> ThomasLoertsch edited hrecipe "/* photo */ removed superfluous link to hCard" (-34) http://is.gd/1jfLP
- # [18:29] <mfbot> ThomasLoertsch edited hrecipe "/* summary */ added: Plain text fulfills these requirements." (+40) http://is.gd/1jfSg
- # [18:31] * Quits: tim_hwang (n=chatzill@71.192.163.225) (Read error: 110 (Connection timed out))
- # [18:34] <tomlurge> tobyink, tantek: does the following make sense and is correct??? "* The contents of the element {{may}} be a plain text string which any conforming parser should interpret as "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hAtom]].
- # [18:35] <tomlurge> (about "author")
- # [18:35] <tobyink> Seems sensible to me.
- # [18:37] <tomlurge> great! thanks
- # [18:39] <mfbot> ThomasLoertsch edited hrecipe "/* author */ added default type "vcard fn"" (+117) http://is.gd/1jgim
- # [18:44] * Joins: MrTopf (n=cs@81.187.73.203)
- # [18:44] <@tantek> tomlurge - the author conventions in hAtom have some issues right now, e.g. with improper use of the HTML <address> element
- # [18:44] <@tantek> (yes this has been captured in hatom-issues )
- # [18:44] <tomlurge> aha. any better idea?
- # [18:45] <@tantek> using the term "author" is good in this case for vocabulary reuse
- # [18:45] <@tantek> however, we should avoid propagating a known issue from hAtom
- # [18:46] <tomlurge> what if i link to hCard directly?
- # [18:46] <@tantek> yes that would be better
- # [18:47] <tomlurge> ok, np
- # [18:47] <@tantek> better to define it as either a text string meaning the author's name, or a nested hCard providing the author's name (as fn) and any other details (such as URL)
- # [18:47] <@tantek> also - I recommend omitting any text about "conforming parser" from the property definitions.
- # [18:47] <@tantek> the property definitions should be written for authors/publishers
- # [18:48] <@tantek> for parsers/programmers - it is better to create a separate "Parsing" section later
- # [18:48] <@tantek> that specifies any parsing details
- # [18:49] <@tantek> (btw re: "author", hReview's "reviewer" needs similar fixes as well) http://microformats.org/wiki/hreview#Property_details
- # [18:49] <tomlurge> but they should know *why* they can omit *what*. and therfor they have to know about parsers. but i'll try to make it sound less frightening
- # [18:49] * Quits: @Phae (n=phaeness@gateb.mh.bbc.co.uk)
- # [18:50] <@tantek> tomlurge - authors/publishers really don't want to know about parsers
- # [18:50] <@tantek> it's just confusing
- # [18:50] <@tantek> for them - it is just extra text that they have to wade through
- # [18:50] <@tantek> better to group the parsing details in a separate section
- # [18:51] <tomlurge> k
- # [18:56] * Parts: emrojo (n=emrojo@163.117.139.228)
- # [18:59] * Quits: tobyink (n=tai@77.89.160.246) ("Leaving.")
- # [19:00] <mfbot> ThomasLoertsch edited hrecipe "/* published */ deleted reference to hAtom. refering to datetime-design-pattern is good enough and easier to comprehend" (+40) http://is.gd/1jhfL
- # [19:01] * Joins: Jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net)
- # [19:02] <tomlurge> tantek: how about this: "* The contents of the element {{may}} be a plain text string in which case it defaults to a "vcard fn". Anything more elaborate {{must}} follow the conventions outlined in [[hCard]]. "
- # [19:04] <mfbot> ThomasLoertsch edited hrecipe "/* author */ switched from hAtom to hCard, removed parsing note" (-17) http://is.gd/1jhso
- # [19:04] * Quits: Jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net) (Read error: 54 (Connection reset by peer))
- # [19:06] * Joins: Jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net)
- # [19:07] <mfbot> ThomasLoertsch edited hrecipe "/* Property details */ "author" is now inherited from vCard" (-3) http://is.gd/1jhBJ
- # [19:08] <mfbot> ThomasLoertsch edited hrecipe "/* Property details */ " (+2) http://is.gd/1jhEO
- # [19:11] <mfbot> ThomasLoertsch edited hrecipe "/* Parser Processing Notes */ author defaults to "vcard fn"" (+93) http://is.gd/1jhNk
- # [19:14] * Quits: MrTopf (n=cs@81.187.73.203) (Read error: 113 (No route to host))
- # [19:18] <mfbot> ThomasLoertsch edited hrecipe "/* ingredient */ added example for type and value" (+105) http://is.gd/1ji9J
- # [19:23] <mfbot> ThomasLoertsch edited hrecipe "added some spacing between chapters" (+4) http://is.gd/1jinN
- # [19:24] * Quits: tomlurge (n=tl@fwhide.guj.de)
- # [19:35] * Joins: trammell (n=trammell@64-71-7-198.static.wiline.com)
- # [19:37] * Quits: Jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net) (Read error: 104 (Connection reset by peer))
- # [19:38] <trammell> Good morning, all! Does anyone know if/how Google looks at VoteLinks?
- # [19:39] * Joins: Jonbo (n=Jonbo123@adsl-068-209-082-227.sip.bhm.bellsouth.net)
- # [19:41] <@tantek> welcome trammell!
- # [19:41] * Joins: KevinMarks (n=Snak@c-67-164-14-96.hsd1.ca.comcast.net)
- # [19:41] <trammell> thanks, tantek :-)
- # [19:41] <@tantek> hi KevinMarks. trammell has a question about Google and VoteLinks.
- # [19:41] <trammell> hiya, kevin!
- # [19:42] <KevinMarks> hi
- # [19:42] <KevinMarks> OK
- # [19:42] <KevinMarks> whats the question?
- # [19:42] <trammell> Does Google give any credence to VoteLinks?
- # [19:43] <mfbot> Tantek edited hrecipe "/* Copyright */ fix typo, reference microformats wiki copyrights explicitly" (+6) http://is.gd/1jjjw
- # [19:43] <KevinMarks> not that I know of - Pagerank can't handle negative links
- # [19:43] <trammell> hmmm...
- # [19:43] <@tantek> but does Google treat "vote-against" like "rel-nofollow" ?
- # [19:43] <KevinMarks> google treats normal links as +1 vote and nofollow ones as 0 vote
- # [19:44] <trammell> noindex and nofollow seem like such a nuclear option. i'd like to be able to qualify a link and not hide things from spiders.
- # [19:44] <@tantek> then does Google treat "vote-abstain" as 0 vote also?
- # [19:44] <KevinMarks> not sure - matt cutts would know
- # [19:44] <@tantek> nofollow is a poorly named rel
- # [19:44] <KevinMarks> I don't think so
- # [19:44] <@tantek> it doesn't actually mean "don't follow"
- # [19:44] <@tantek> it just means, don't give any weight to this link
- # [19:45] * Joins: tim_hwang (n=chatzill@65.112.8.177)
- # [19:45] <@tantek> so crawlers may still spider through "rel-nofollow" links
- # [19:45] <trammell> ah
- # [19:45] <@tantek> yeah
- # [19:45] <hober> tantek: I talked to maciej yesterday; he's amenable to crediting the microformats principles in the html design principles document.
- # [19:45] <hober> I'll let you know when that change goes in, if I notice it. Or you can follow along here: http://dev.w3.org/cvsweb/html5/html-design-principles/
- # [19:45] <@tantek> hober, very much appreciated
- # [19:45] <hober> np
- # [19:46] * Joins: gsnedders (n=gsnedder@c83-252-204-248.bredband.comhem.se)
- # [19:46] <trammell> that makes a bit of difference, but having a trinary option like votelinks feels like a better solution.
- # [19:47] <KevinMarks> yes, that was the original idea
- # [19:47] <@tantek> btw - regarding the naming issue of rel-nofollow: http://microformats.org/wiki/rel-nofollow#open_issues
- # [19:48] <trammell> that's exactly what i was looking for, tantek. thanks!
- # [19:48] <@tantek> which reminds me - KevinMarks, mind adding yourself to: http://microformats.org/wiki/rel-nofollow#Copyright
- # [19:48] <@tantek> ?
- # [19:49] <KevinMarks> oops, sorry, thought i had
- # [19:49] <mfbot> Kevin Marks edited rel-nofollow "/* Copyright */ make mine PD" (+164) http://is.gd/1jjCK
- # [19:50] <@tantek> naming is a difficult thing - it's not uncommon for naming errors to occur in formats/specs
- # [19:50] <@tantek> trammell - for more on naming, see http://microformats.org/wiki/naming-principles
- # [19:50] <KevinMarks> gtg
- # [19:51] * Quits: KevinMarks (n=Snak@c-67-164-14-96.hsd1.ca.comcast.net) (Remote closed the connection)
- # [19:51] <trammell> thanks, kevin!
- # [20:04] <hober> There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton
- # [20:11] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [20:11] * Joins: tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [20:11] * ChanServ sets mode: +o tantek
- # [20:12] <@tantek> hober - do you have a citation for that quote?
- # [20:13] * Joins: ebel (n=rory@unaffiliated/ebel)
- # [20:14] <@tantek> (URL)
- # [20:18] <@tantek> there is no wikipedia page for Phil Karlton nor is there any mention in Wikiquote: http://en.wikiquote.org/wiki/Special:Search/Phil_Karlton
- # [20:18] <@tantek> also, I think Knuth would beg to differ that "there are only two hard things in Computer Science".
- # [20:24] * Joins: CaptSolo (i=captsolo@kaste.lv)
- # [20:35] * Joins: tomlurge (n=tl@c189088.adsl.hansenet.de)
- # [20:37] <@tantek> tomlurge I made a small fix/update to the copyright section in hRecipe - looks like there may have been a copy/paste typo from hAudio
- # [20:38] <tomlurge> tantek: thanks. that's very well possible. i found more than one months after editing it ...
- # [20:47] * Quits: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com) ("Leaving.")
- # [20:51] <@tantek> sf folks - since we just had the 4th bday party last Friday - none of us usual organizers has proposed a dinner for tonight (yet). if there is interest however, we can certainly make it happen.
- # [20:54] * Parts: tomlurge (n=tl@c189088.adsl.hansenet.de)
- # [20:56] * Quits: tim_hwang (n=chatzill@65.112.8.177) (Read error: 110 (Connection timed out))
- # [21:02] * Joins: dglazkov_ (n=dglazkov@72.14.224.1)
- # [21:02] * Joins: benward (n=benward@nat/yahoo/x-dee63fb87aef9eff)
- # [21:02] * ChanServ sets mode: +o benward
- # [21:02] * Joins: tim_hwang (n=chatzill@65.112.8.177)
- # [21:07] * Joins: dglazkov__ (n=dglazkov@nat/google/x-dac19dd0bb6f1b85)
- # [21:07] * Joins: dwhittle (n=dwhittle@nat/yahoo/x-c28e3cb26583eca7)
- # [21:07] * Quits: @dglazkov (n=dglazkov@nat/google/x-7162b9e2eed0e1bb) (Read error: 104 (Connection reset by peer))
- # [21:24] * Quits: dglazkov_ (n=dglazkov@72.14.224.1) (Read error: 110 (Connection timed out))
- # [21:35] * Joins: dane (n=dane@c-69-181-142-171.hsd1.ca.comcast.net)
- # [21:37] * Quits: dwhittle (n=dwhittle@nat/yahoo/x-c28e3cb26583eca7) ("Im gone.")
- # [21:37] * dglazkov__ is now known as dglazkov
- # [21:37] * ChanServ sets mode: +o dglazkov
- # [22:10] <hober> tantek: the oldest reference I can find is from January 2000: http://lists.xml.org/archives/xml-dev/200001/msg00170.html
- # [22:11] <hober> I suppose http://mailman.ic.ac.uk/pipermail/xml-dev/2000-January/018394.html is more canonical a link for that message
- # [22:19] * hober emailed Tim to see if there's an older, linkable reference
- # [22:30] <hober> make that January 1999 (again tbray quoting pk): http://mailman.ic.ac.uk/pipermail/xml-dev/1999-January/008389.html
- # [22:31] * Joins: dglazkov_ (n=dglazkov@nat/google/x-03b43da4fe19c6cd)
- # [22:32] * Quits: @dglazkov (n=dglazkov@nat/google/x-dac19dd0bb6f1b85) (Read error: 60 (Operation timed out))
- # [22:54] * Joins: ntoll (n=ntoll@88-111-137-153.dynamic.dsl.as9105.com)
- # [22:54] * Quits: singpolyma (n=singpoly@173-11-94-130-SFBA.hfc.comcastbusiness.net) ("Lost terminal")
- # [22:55] * Joins: singpolyma (n=singpoly@173-11-94-130-SFBA.hfc.comcastbusiness.net)
- # [23:02] * Quits: dglazkov_ (n=dglazkov@nat/google/x-03b43da4fe19c6cd)
- # [23:03] <@tantek> benward - I noticed that hReview had that problem you mentioned with the semantic-xhtml-design-principles being at the front of the spec - fixed now. see if this look better / gets to the point sooner from your perspective: http://microformats.org/wiki/hreview
- # [23:03] <@benward> Ah, yes, that's much better to have it at the end of the document. Nice :)
- # [23:05] * Joins: dglazkov (n=dglazkov@nat/google/x-74b845582e8fafab)
- # [23:05] * ChanServ sets mode: +o dglazkov
- # [23:07] <@tantek> tomlurge (editor of hRecipe) and I had a bit of a good editors conversation back and forth earlier today, and it was clear that many issues in the format/order of hRecipe came from other drafts (notably hAudio/hAtom/hReview) - so while he fixed hRecipe, I fixed hReview respectively. I'm thinking of writing up a few of the editors lessons learned into an "editors-guide".
- # [23:07] <@benward> That would be a good document to have
- # [23:09] * Quits: singpolyma (n=singpoly@173-11-94-130-SFBA.hfc.comcastbusiness.net) (Nick collision from services.)
- # [23:09] * Joins: singpolyma (n=singpoly@173-11-94-130-SFBA.hfc.comcastbusiness.net)
- # [23:25] <mfbot> Tantek edited to-do "/* update specification section organization */ note goal, process vaguely worded statements into next-actions, note hCard improvements, add editors-guide task" (+437) http://is.gd/1jrW6
- # [23:28] * Quits: trammell (n=trammell@64-71-7-198.static.wiline.com) (Read error: 104 (Connection reset by peer))
- # [23:30] * Joins: trammell (n=trammell@64-71-7-198.static.wiline.com)
- # [23:39] * Quits: gsnedders (n=gsnedder@c83-252-204-248.bredband.comhem.se) (Remote closed the connection)
- # [23:41] * Joins: gsnedders (n=gsnedder@c83-252-204-248.bredband.comhem.se)
- # [23:42] * Quits: tim_hwang (n=chatzill@65.112.8.177) (Read error: 60 (Operation timed out))
- # Session Close: Wed Jul 01 00:00:00 2009
The end :)