Options:
- # Session Start: Tue Sep 01 00:00:00 2009
- # Session Ident: #microformats
- # [00:05] * Parts: BillCriswell (n=Bill@66.240.28.254)
- # [00:08] <JonathanMalek_> ok, those moves are done, and the link to the hatom-geo discussion is in place.
- # [00:11] <@tantek> awesome
- # [00:11] <JonathanMalek_> hoping the proposal makes it clear what we're trying to do: examples will be even better
- # [00:12] <JonathanMalek_> we're getting a lot of questions (and some serious misunderstanding, including from Google) regarding the concept of inheriting from hatom
- # [00:13] <@tantek> inheritance in general has always caused lots of questions and misunderstanding
- # [00:13] <@tantek> it's one of the biggest design flaws of OOP
- # [00:13] <JonathanMalek_> I think for the most part
- # [00:14] <JonathanMalek_> people just miss the concept that we're reusing hAtom
- # [00:14] <@tantek> re-use good. inheritance bad.
- # [00:14] <JonathanMalek_> and are asking questions like, "why only 5 fields for news?"
- # [00:14] <JonathanMalek_> "Because we don't want to retype the hatom spec" is not a good answer yet :)
- # [00:14] <@tantek> sounds like a good way to start /wiki/news-faq :)
- # [00:14] <JonathanMalek_> absolutely right
- # [00:15] <@tantek> JonathanMalek - it also might be better to consider defining a news item/addition which is a special kind of hAtom entry or addition - rather than discussing news as inheriting or subclassing hAtom
- # [00:15] <JonathanMalek_> hmmm
- # [00:15] <JonathanMalek_> struggled with that idea early on
- # [00:15] <@tantek> note that hReview is reviews about items, and those items used to just have a name (fn), photo, url
- # [00:15] <@tantek> and grew to include an hCard instead
- # [00:16] <@tantek> and an hCalendar vevent instead
- # [00:16] <@tantek> and similarly people can now composite hMedia to do reviews of media items
- # [00:16] <@tantek> etc.
- # [00:16] <@tantek> this kind of re-use, composition, works MUCH better in practice with human data (documents) than *any* form of programming language inheritance
- # [00:16] <JonathanMalek_> completely agreed
- # [00:17] <JonathanMalek_> we're depending heavily on that idea
- # [00:18] * Quits: ajturner (n=ajturner@209.155.228.129)
- # [00:19] <JonathanMalek_> for instance, AP classification systems do entity extraction, subject, geo and event identification. Rather than describing those as parts of a news story, authors/publishers are free to mark those up however they see fit. The simplest is a rel-tag, the more thorough (and interesting) would be hCard or hCalendar.
- # [00:23] <JonathanMalek_> composing news stories using a range of tools, from simplest to the kind of change that impacts your authoring system.
- # [00:23] <JonathanMalek_> on your statement: "a special kind of hAtom entry", I think that's exactly what we're doing.
- # [00:24] <JonathanMalek_> though maybe I need to understand that point a bit better--my thought is that, using DavidJanes' suggestion, "hentry [some-other-root]" as the right way to express "specialized" instances of hatom.
- # [00:25] <JonathanMalek_> Benefit to parsers and authors alike--if you can't parse or produce the specialization, you can still benefit by parsing/emitting hentry.
- # [00:26] <csarven> I think Comments may be another good example for specialized hAtom.. It is not fully sorted out yet though
- # [00:27] <@tantek> JonathanMalek - I agree that's what you're conceptually doing with the news work, but I think the documentation does not currently reflect that viewpoint / positioning - and could be updated to improve that.
- # [00:27] <@tantek> csarven - comments could also be marked up as hReview
- # [00:27] <@tantek> as a comment is often feedback/review of a post
- # [00:27] <@tantek> now a *time ordered list* of comments could *also* be marked up as hAtom
- # [00:28] <csarven> Could stretch it even to hCalendar I suppose
- # [00:30] <JonathanMalek_> tantek: will look at the docs to express that clearer. It's become fairly obvious that the intent to define a root class "hnews" that *will not* parse without including "hentry" is not an immediately graspable concept. I would have thought that class="hnews hentry" would be immediately clear as to objective, but that's not the case.
- # [00:33] <@tantek> csarven - no, not hCalendar, because they're not "events" in the human event sense
- # [00:34] <csarven> I realise that. It is a stretch
- # [00:34] <@tantek> JonathanMalek, maybe class="hentry hnews" may be better understood (though it is semantically identically)
- # [00:34] <@tantek> csarven - it's worse than a stretch, it's a dilutionary abuse
- # [00:34] <@tantek> we made the mistake of doing this with issues on the wiki
- # [00:34] <@tantek> the template used to use hCalendar
- # [00:35] <JonathanMalek_> I'll make sure the examples use that--that's a great clarification
- # [00:35] <@tantek> but that made little sense, both semantically, and practically
- # [00:35] <@tantek> nobody views issues in a calendar program!
- # [00:35] <@tantek> it's nonsensical
- # [00:35] <@tantek> JonathanMalek, for similar examples see hCalendar e.g. "location vcard", and hReview, e.g. "item vevent"
- # [00:36] <JonathanMalek_> "hentry [specialized-root]" while only playing with order and nothing else, just makes it clearer
- # [00:36] <csarven> What about microblogging notices? Would you see them as events?
- # [00:37] <@tantek> activity stream type stuff? no
- # [00:37] <@tantek> hCalendar events are for *human* events, not machine events
- # [00:37] <@tantek> machine events are essentially *anything* that has a timestamp
- # [00:37] <@tantek> in the context of human calendars, that's not useful
- # [00:40] * Joins: madness (n=mng@ip70-176-92-111.ph.ph.cox.net)
- # [00:41] <csarven> Must sleep. Later all
- # [00:42] <@tantek> later csarven!
- # [00:42] <csarven> Thanks
- # [00:43] <csarven> I've been having an on/off internal debate with myself about using hCalendar in StatusNet (formerly aka Laconica updates. Good that I've put that off :)
- # [00:44] <@tantek> thanks csarven
- # [00:44] <@tantek> StatusNet definitely hAtom :)
- # [00:45] <csarven> Bye
- # [00:45] * Quits: csarven (n=csarven@53563002.cable.casema.nl) ("Leaving.")
- # [00:56] * Quits: Hey_neken (n=kaxero@215.Red-213-96-129.staticIP.rima-tde.net) (Remote closed the connection)
- # [00:56] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [00:58] * Joins: thuddwhirr (n=wolthuis@mimezine.com)
- # [01:05] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [01:05] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [01:16] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [01:16] * Joins: mcdave (n=mcdave@cm-83-97-164-135.telecable.es)
- # [01:19] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [01:26] * Quits: mcdave (n=mcdave@cm-83-97-164-135.telecable.es)
- # [01:26] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [01:27] * Joins: mcdave (n=mcdave@cm-83-97-164-135.telecable.es)
- # [01:30] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [01:37] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [01:44] * Quits: memload_ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk) (Read error: 110 (Connection timed out))
- # [01:53] * Quits: mcdave (n=mcdave@cm-83-97-164-135.telecable.es)
- # [01:53] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [02:07] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [02:11] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [02:13] * Quits: @dglazkov (n=dglazkov@nat/google/x-zgpwbfcdchpcqfky)
- # [02:19] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [02:20] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [02:24] * Quits: knmurphy (n=knmurphy@209.20.67.137) ("Coyote finally caught me")
- # [02:24] * Joins: knmurphy (n=knmurphy@209.20.67.137)
- # [02:27] * Quits: @tantek (n=tantek@67.180.202.79) (Read error: 145 (Connection timed out))
- # [02:31] * Quits: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com) ("Leaving.")
- # [02:32] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [02:35] * Quits: leahculver (n=leahculv@204.9.180.30)
- # [02:35] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 54 (Connection reset by peer))
- # [02:42] * Joins: singpolyma (n=singpoly@node-533.tor.pppoe.execulink.com)
- # [02:44] * Joins: tantek (n=tantek@67.180.202.79)
- # [02:44] * ChanServ sets mode: +o tantek
- # [02:45] * Joins: pjkix (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net)
- # [02:45] * Quits: pjkix (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net) (Client Quit)
- # [02:46] * Joins: pjkix (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net)
- # [02:53] * Joins: shigeta (n=shigeta@sakkgw2.sixapart.jp)
- # [03:00] * Quits: knmurphy (n=knmurphy@209.20.67.137) ("Coyote finally caught me")
- # [03:14] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [03:14] * ChanServ sets mode: +o dglazkov
- # [03:16] * Joins: dglazkov_ (n=dglazkov@72.14.224.1)
- # [03:16] * ChanServ sets mode: +o dglazkov_
- # [03:20] * Quits: madness (n=mng@ip70-176-92-111.ph.ph.cox.net)
- # [03:23] <benward_> Would appreciate thoughts on using category to indicate the languages supported by a product (or person): http://microformats.org/wiki/category-brainstorming
- # [03:23] * benward_ is now known as benward
- # [03:23] * ChanServ sets mode: +o benward
- # [03:24] <@tantek> benward - there shouldn't be a need for it
- # [03:24] <@tantek> in the case of content, "lang" handles it
- # [03:25] <@tantek> in the case of a link to content in another language, a rel="alternate" hreflang=".." handles it
- # [03:25] <@benward> OK, here's our use case:
- # [03:25] * Quits: @dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net) (Read error: 60 (Operation timed out))
- # [03:25] * dglazkov_ is now known as dglazkov
- # [03:25] <@tantek> so if e.g. an hReview is published in multiple languages
- # [03:26] <@benward> We have the Yahoo Application Platform.
- # [03:26] <@tantek> "consumable" as it were
- # [03:26] <@tantek> then links to those instances should be marked up with hreflang="..." rel="alternate"
- # [03:26] <@benward> So we have a directory of applications you can run on Yahoo (each app is a product -> hProduct)
- # [03:26] <@tantek> (per HTML4.01)
- # [03:27] <@benward> Each hProduct describes the app, and the properties of it.
- # [03:27] <@tantek> benward - best to document those real world examples on a "language-examples" page
- # [03:27] <@benward> The available/supported languages in question are some of those properties
- # [03:28] <@tantek> but what does that even mean? "available/supported" languages
- # [03:28] <@tantek> need links to real world examples to better understand
- # [03:28] <@benward> As in, an app may support English, French and German.
- # [03:28] <@tantek> what of the app? the UI? the content model?
- # [03:28] <@benward> As documented o the category-brainstorming page: An app can be localized into multiple languages.
- # [03:28] <@benward> The UI
- # [03:28] <@tantek> so this is *localizations* then
- # [03:29] <@tantek> for apps that may be localized in a number of different languages
- # [03:29] <@tantek> start localization-examples to document this
- # [03:29] <@tantek> I don't think jumping to "category-brainstorming" is the right thing to do here
- # [03:30] <@tantek> better to proceed with localization-examples, localization-formats, and then localization-brainstorming
- # [03:30] <@tantek> because you're coming up with a way of marking up the localization(s) that is/are being expressed
- # [03:30] <@tantek> and "category" is only one possible solution
- # [03:30] <@tantek> whereas I'd expect a category-brainstorming page to be about brainstorming how to markup a category
- # [03:32] * Quits: pjkix (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net) (Read error: 104 (Connection reset by peer))
- # [03:33] * Joins: pjkix (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net)
- # [03:33] <@benward> Hmm. It's not a microformat for the app itself. It's about describing the app — which is already within the context of hProduct. Will add additional documentation.
- # [03:34] <@tantek> microformats are always about text content describing something
- # [03:34] <@tantek> sometimes the text content *is* the something, e.g. hAtom, hReview
- # [03:34] <@tantek> but often it is *about* something, e.g. hCard, hCalenar
- # [03:34] <@tantek> hCalendar even
- # [03:35] <@tantek> thus the distinction you make, not for the app itself, but for describing the app - is not a useful/relevant distinction - as the same reasoning will apply in both cases.
- # [03:35] <@tantek> localization as an aspect of hProduct may make sense yes
- # [03:35] <@tantek> thus perhaps add localization examples within that context to product-examples
- # [03:35] <@tantek> etc.
- # [03:36] <@benward> k
- # [03:37] <@tantek> benward - is this an example of the kind of thing you are talking about?
- # [03:37] <@tantek> http://www.mozilla.com/en-US/firefox/all.html
- # [03:37] <@tantek> product downloads listed by localization
- # [03:37] * Joins: madness (n=mng@ip70-176-92-111.ph.ph.cox.net)
- # [03:37] <@tantek> note the heading text "Fully *Localized* Versions"
- # [03:37] <@tantek> :)
- # [03:38] <@benward> In so far as it's a page for a single product that lists languages, yes. But in this context, there's no concept of a per-language download link.
- # [03:38] * Quits: factoryjoe (n=factoryj@c-67-169-94-222.hsd1.ca.comcast.net)
- # [03:38] <@tantek> need URL for what you mean by "this context"
- # [03:38] <@benward> Don't have one yet. Internal.
- # [03:38] <@tantek> then it doesn't deserve a microformat - we've been down that road before
- # [03:39] <@benward> OK, http://apps.yahoo.com/-yqRaUQ7k/
- # [03:39] <@tantek> no public examples of content to be marked up, not important enough (80/20) to merit a microformat
- # [03:39] <@benward> Imagine that underneath the text description is some text that says ‘Supported Languages: English, Français, Deutsch’
- # [03:41] <@benward> Anyway. I'll expand document/examples when I can
- # [03:41] <@tantek> but again - that's ambiguous
- # [03:41] <@tantek> "Supported Languages" could mean UI or content or both
- # [03:41] <@tantek> if it's UI - it's *localization*
- # [03:42] <@tantek> if it's content - it's *internationalization*
- # [03:42] <@tantek> in either case is it "language" is imprecise/ambiguous
- # [03:43] <@benward> Supported Languages, in the context or advertizing an application, means localization.
- # [03:44] <@benward> It refers explicitly to a user preference for the language in which content (that is, page content, which includes YAP UI) will be displayed where available
- # [03:44] <@tantek> I understand the desire to mark this up with POSH (or even just plain categories/tagging), but I don't see what problem is being solved per se
- # [03:45] <@tantek> i.e. what data sharing does this enable that has an actual use case
- # [03:45] <@tantek> (and just "publishing" is not a use case, that's an example useful for research, but not for a problem statement)
- # [03:46] <@benward> That's somewhat fair. It would allow search engines to only display applications available in a certain language. Which this being Open Social, there's cross-network interop going to happen for apps like these.
- # [03:47] <@tantek> that's a much better problem / use-case statement
- # [03:47] <@benward> But yes, likelihood is that our ship date will involve POSH in the initial version anyway, just through production reality. But I'm keen to have documentation iteration here and in the open as early as possible, obviosuly
- # [03:47] <@benward> Anyway, gotta run home
- # [03:47] <@benward> Back online later.
- # [03:48] <@tantek> k
- # [04:04] * Joins: knmurphy (n=knmurphy@209.20.67.137)
- # [04:05] * Quits: knmurphy (n=knmurphy@209.20.67.137) (Client Quit)
- # [04:05] * Joins: knmurphy (n=knmurphy@209.20.67.137)
- # [04:05] * Quits: @benward (n=benward@nat/yahoo/x-ccdlzbovgwhwiwib) (Read error: 110 (Connection timed out))
- # [04:08] * Joins: dglazkov_ (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [04:08] * ChanServ sets mode: +o dglazkov_
- # [04:10] * Quits: @dglazkov_ (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net) (Client Quit)
- # [04:12] * Quits: KevinMarks (n=KevinMar@157.22.22.46) ("The computer fell asleep")
- # [04:15] * Joins: shigeta_ (n=shigeta@sakkgw2.sixapart.jp)
- # [04:17] * Quits: knmurphy (n=knmurphy@209.20.67.137) ("Coyote finally caught me")
- # [04:17] * Joins: knmurphy (n=knmurphy@209.20.67.137)
- # [04:22] * Quits: shigeta_ (n=shigeta@sakkgw2.sixapart.jp) (Read error: 60 (Operation timed out))
- # [04:25] * Joins: dglazkov_ (n=dglazkov@67.188.3.204)
- # [04:25] * ChanServ sets mode: +o dglazkov_
- # [04:26] * Quits: @dglazkov (n=dglazkov@72.14.224.1) (Read error: 110 (Connection timed out))
- # [04:26] * dglazkov_ is now known as dglazkov
- # [04:26] * Joins: dglazkov_ (n=dglazkov@72.14.224.1)
- # [04:26] * ChanServ sets mode: +o dglazkov_
- # [04:30] * Quits: shigeta (n=shigeta@sakkgw2.sixapart.jp) (Read error: 110 (Connection timed out))
- # [04:34] * Quits: @dglazkov (n=dglazkov@67.188.3.204) (Read error: 145 (Connection timed out))
- # [04:34] * dglazkov_ is now known as dglazkov
- # [04:35] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (leguin.freenode.net irc.freenode.net)
- # [04:35] * Quits: JonathanMalek (n=Jonathan@24.23.63.49) (leguin.freenode.net irc.freenode.net)
- # [04:35] * Quits: chuck (n=charlie@yourwiki/staff/charlie) (leguin.freenode.net irc.freenode.net)
- # [04:37] * Joins: shigeta (n=shigeta@sakkgw2.sixapart.jp)
- # [04:41] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
- # [04:41] * Joins: JonathanMalek (n=Jonathan@24.23.63.49)
- # [04:41] * Joins: chuck (n=charlie@yourwiki/staff/charlie)
- # [04:50] * Quits: @dglazkov (n=dglazkov@72.14.224.1)
- # [04:54] * Quits: @tantek (n=tantek@67.180.202.79)
- # [05:16] * Quits: aux (n=aux@c-76-112-237-28.hsd1.mi.comcast.net) (Read error: 110 (Connection timed out))
- # [05:19] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [05:19] * ChanServ sets mode: +o dglazkov
- # [05:20] * Joins: leahculver (n=leahculv@c-67-180-197-78.hsd1.ca.comcast.net)
- # [05:26] * Joins: aux (n=aux@c-76-112-237-28.hsd1.mi.comcast.net)
- # [05:29] * Quits: leahculver (n=leahculv@c-67-180-197-78.hsd1.ca.comcast.net)
- # [05:32] * Joins: dglazkov_ (n=dglazkov@72.14.224.1)
- # [05:32] * ChanServ sets mode: +o dglazkov_
- # [05:35] * Quits: @dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net) (Read error: 60 (Operation timed out))
- # [05:35] * dglazkov_ is now known as dglazkov
- # [05:46] * Joins: BobJonkman (n=BobJonkm@206.248.137.186)
- # [05:57] * Quits: singpolyma (n=singpoly@node-533.tor.pppoe.execulink.com) ("Lost terminal")
- # [06:01] * Joins: tantek (n=tantek@c-76-126-175-28.hsd1.ca.comcast.net)
- # [06:01] * ChanServ sets mode: +o tantek
- # [06:09] * Joins: benward (n=benward@98.210.154.133)
- # [06:09] * ChanServ sets mode: +o benward
- # [06:28] * Joins: tantekc (n=tantek@70.36.139.128)
- # [06:45] * Quits: @tantek (n=tantek@c-76-126-175-28.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
- # [06:54] * Joins: dglazkov_ (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [06:54] * ChanServ sets mode: +o dglazkov_
- # [07:02] * Quits: @dglazkov (n=dglazkov@72.14.224.1) (Read error: 60 (Operation timed out))
- # [07:02] * dglazkov_ is now known as dglazkov
- # [07:03] * Joins: besbes (n=besbes@188-23-186-133.adsl.highway.telekom.at)
- # [07:18] * Quits: @dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [07:19] * Joins: leahculver (n=leahculv@c-67-180-197-78.hsd1.ca.comcast.net)
- # [07:21] * Quits: BobJonkman (n=BobJonkm@206.248.137.186) (Read error: 131 (Connection reset by peer))
- # [07:31] * Joins: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com)
- # [07:53] * Joins: Upgrayedd (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net)
- # [07:53] * Quits: Upgrayedd (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net) (Client Quit)
- # [07:59] * Quits: Danny_B (n=Danny_B@wikimedia/Danny-B.) (Nick collision from services.)
- # [07:59] * Joins: Danny_B (n=Danny_B@wikimedia/Danny-B.)
- # [08:13] * Quits: pjkix (n=pjkix@c-67-169-92-224.hsd1.ca.comcast.net) (Read error: 110 (Connection timed out))
- # [08:14] * Joins: pesla (n=retep@procurios.xs4all.nl)
- # [08:27] * Quits: besbes (n=besbes@188-23-186-133.adsl.highway.telekom.at)
- # [08:34] * Quits: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com) ("Leaving.")
- # [08:49] * Joins: besbes (n=besbes@mercury.mminf.univie.ac.at)
- # [09:08] * Joins: KevinMarks (n=KevinMar@c-67-164-14-96.hsd1.ca.comcast.net)
- # [09:23] * Quits: besbes (n=besbes@mercury.mminf.univie.ac.at) (Read error: 110 (Connection timed out))
- # [09:34] * Joins: mcdave (n=mcdave@cm-83-97-166-34.telecable.es)
- # [09:36] * Quits: leahculver (n=leahculv@c-67-180-197-78.hsd1.ca.comcast.net)
- # [10:13] * Quits: knmurphy (n=knmurphy@209.20.67.137) (Read error: 60 (Operation timed out))
- # [10:13] * Joins: knmurphy (n=knmurphy@209.20.67.137)
- # [10:15] * Joins: emrojo (n=emrojo@163.117.139.228)
- # [10:50] * Joins: SunWuKung (n=tenshiku@S0106000d93cb5211.vc.shawcable.net)
- # [10:51] * Quits: SunWuKung (n=tenshiku@S0106000d93cb5211.vc.shawcable.net) (Remote closed the connection)
- # [10:53] * Joins: veeliam (n=veeliam@193.52.24.66)
- # [10:56] * Joins: MrTopf (n=cs@p5B396142.dip.t-dialin.net)
- # [11:03] * Joins: to__ (n=to_@AAubervilliers-551-1-166-202.w92-141.abo.wanadoo.fr)
- # [11:03] * Quits: to_ (n=to_@AAubervilliers-551-1-166-202.w92-141.abo.wanadoo.fr) (Read error: 60 (Operation timed out))
- # [11:03] * to__ is now known as to_
- # [11:05] * Joins: Phae (n=phaeness@gateb.thls.bbc.co.uk)
- # [11:05] * ChanServ sets mode: +o Phae
- # [11:07] * Joins: adactio (n=adactio@host86-156-238-27.range86-156.btcentralplus.com)
- # [11:07] * ChanServ sets mode: +o adactio
- # [11:18] * Joins: besbes (n=besbes@mercury.mminf.univie.ac.at)
- # [11:21] * Quits: veeliam (n=veeliam@193.52.24.66)
- # [11:39] * Quits: @benward (n=benward@98.210.154.133) (Read error: 110 (Connection timed out))
- # [11:48] * Joins: uf-wiki-visitor (i=c3abb632@gateway/web/freenode/x-xympxbwbocruoggz)
- # [11:50] * Quits: uf-wiki-visitor (i=c3abb632@gateway/web/freenode/x-xympxbwbocruoggz) (Client Quit)
- # [11:56] * Joins: seengee (n=chatzill@195.171.182.50)
- # [11:57] <seengee> hi all, anyone familiar with google's implementation of microformats for their "rich snippets" ?
- # [11:58] <seengee> especially interested in their rich snippets testing tool - http://www.google.com/webmasters/tools/richsnippets - which appears to not be following the relevant standards
- # [12:01] * Joins: veeliam (n=veeliam@193.52.24.66)
- # [12:01] <@adactio> seengee: It does have some issues. People have been giving feedback to the Google guys on the list so hopefully it will get updated soon.
- # [12:08] <seengee> what i'm unsure of at the moment is whether the preview I am seeing is actually accurate to how my results will be shown because how its misinterpreting - for example - dtreviewed means that a user will see a timestamp instead of a nicely formatted date
- # [12:08] <seengee> thanks btw
- # [12:26] <seengee> adactio: which list are these issues being reported on? would be interested to make some additions
- # [12:29] <@adactio> seengee: you can find the emails in the list archive (check for activity in the past few days).
- # [12:32] <seengee> adactio: thanks, i'll have a read through
- # [12:34] <seengee> one other thing while i'm in here - is it possible to prevent accidental class clashes within a microformat, i can understand why namespacing is not used but especially when enhancing legacy code its not always possible to update css and html
- # [12:44] * Quits: veeliam (n=veeliam@193.52.24.66)
- # [12:45] * Joins: gsnedders (n=gsnedder@p54BEB4FE.dip0.t-ipconnect.de)
- # [12:48] * Quits: tantekc (n=tantek@70.36.139.128)
- # [12:51] <@adactio> seengee: the root class (e.g. vcard, vevent) effectively acts like a name space. Clashes can't occur with a class of, say, "url" inside an hcard and a class of "url" elsewhere on the same page.
- # [12:58] <seengee> adactio: the problem we have seen is in using hproduct for example, we are using classes nested within the hproduct container that make semantic sense being called what they are called but are storing data that is not suitable for the microformat. this clash seems unavoidable to me
- # [12:59] * Joins: csarven (n=csarven@53563002.cable.casema.nl)
- # [13:00] <@adactio> seengee: but where's the problem? You can use your own class names and the microformats class names.
- # [13:01] <seengee> adaction: an example of this is a class "availability" which stores a system configurable label that represents what that specific site wants to call availability, we cannot rename the class and , although nested within the container , it is not storing data that the mircoformat would expect
- # [13:02] <seengee> adactio: an example of this is a class "availability" which stores a system configurable label that represents what that specific site wants to call availability, we cannot rename the class and , although nested within the container , it is not storing data that the mircoformat would expect
- # [13:03] <@adactio> seengee: but why is that a problem>
- # [13:03] <@adactio> ?
- # [13:04] <@adactio> Are you saying that what you call availability matches to a different class name in the microformat?
- # [13:05] <seengee> adactio: because the microformat parser thinks that the phrase stored within that class is a reference to the item's availability which it isnt, its just the label representing Availability
- # [13:05] <@adactio> ah, I see.
- # [13:06] <@adactio> I must admit, I don't know much about hproduct. It's a draft microformat so it could well be that the class names end up changing.
- # [13:09] <seengee> I would assume though that this issue would exist within other microformats too, its not inconceivable that a class within a microformat container could need to be ignored by the parser, or is it?
- # [13:13] <@adactio> seengee: I think it's pretty unlikely but I guess it's certainly possible.
- # [13:15] <seengee> adactio: i guess this is only going to be an issue with legacy code but this is the bread and butter for a lot of developers and it would be a shame if there were potential barriers to adoption for these people
- # [13:16] <@adactio> seengee: I would agree but I think it's an edge case. Yours is the first instance I've heard.
- # [13:17] <seengee> adactio: my mum always said i was "unique"
- # [13:17] <@adactio> :-)
- # [13:20] <seengee> as much as it is an edge case, would you say there's any value in me pursuing this?
- # [14:03] * Joins: tobyink (n=tai@77.89.160.246)
- # [14:06] * Quits: shigeta (n=shigeta@sakkgw2.sixapart.jp) ("Leaving...")
- # [14:12] * Quits: seengee (n=chatzill@195.171.182.50) ("ChatZilla 0.9.85 [Firefox 3.5.2/20090729225027]")
- # [14:54] * Joins: ajturner (n=ajturner@209.155.228.129)
- # [15:00] * Quits: gsnedders (n=gsnedder@p54BEB4FE.dip0.t-ipconnect.de)
- # [15:02] * Quits: mcdave (n=mcdave@cm-83-97-166-34.telecable.es)
- # [15:10] * Joins: veeliam (n=veeliam@conference/drupalcon/x-zuwqwpnwfdpihnsu)
- # [15:29] * Joins: mcdave (n=mcdave@cm-83-97-164-135.telecable.es)
- # [15:51] * Quits: Amorphous (i=jan@unaffiliated/amorphous) (Read error: 110 (Connection timed out))
- # [15:52] * Joins: singpolyma (n=singpoly@node-533.tor.pppoe.execulink.com)
- # [15:54] * Joins: Amorphous (i=jan@unaffiliated/amorphous)
- # [15:57] * Joins: gsnedders (n=gsnedder@p54BE9AE8.dip0.t-ipconnect.de)
- # [16:07] * Joins: inarru (n=inarru@cpc3-acto1-0-0-cust676.4-2.cable.virginmedia.com)
- # [16:07] * Quits: inarru (n=inarru@cpc3-acto1-0-0-cust676.4-2.cable.virginmedia.com) (Client Quit)
- # [16:10] * Joins: inarru (n=inarru@cpc3-acto1-0-0-cust676.4-2.cable.virginmedia.com)
- # [16:13] * Quits: emrojo (n=emrojo@163.117.139.228) (Remote closed the connection)
- # [16:13] * Joins: emrojo (n=emrojo@163.117.139.228)
- # [16:24] * Joins: dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [16:24] * ChanServ sets mode: +o dglazkov
- # [16:26] * Joins: shigeta (n=shigeta@50.29.100.220.dy.bbexcite.jp)
- # [16:37] * Quits: KevinMarks (n=KevinMar@c-67-164-14-96.hsd1.ca.comcast.net) ("The computer fell asleep")
- # [16:37] * Joins: KevinMarks (n=KevinMar@c-67-164-14-96.hsd1.ca.comcast.net)
- # [16:39] * Quits: gsnedders (n=gsnedder@p54BE9AE8.dip0.t-ipconnect.de)
- # [16:44] * Quits: csarven (n=csarven@53563002.cable.casema.nl) ("Leaving.")
- # [16:44] * Quits: KevinMarks (n=KevinMar@c-67-164-14-96.hsd1.ca.comcast.net) (Read error: 60 (Operation timed out))
- # [16:47] * Quits: @dglazkov (n=dglazkov@c-67-188-0-62.hsd1.ca.comcast.net)
- # [16:57] * Joins: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [17:03] * Quits: singpolyma (n=singpoly@node-533.tor.pppoe.execulink.com) (Remote closed the connection)
- # [17:03] * Joins: singpolyma (n=singpoly@node-533.tor.pppoe.execulink.com)
- # [17:09] * Joins: dglazkov (n=dglazkov@nat/google/x-tijlaoxdxncjmqum)
- # [17:09] * ChanServ sets mode: +o dglazkov
- # [17:11] * Parts: veeliam (n=veeliam@conference/drupalcon/x-zuwqwpnwfdpihnsu)
- # [17:24] * Joins: gsnedders (n=gsnedder@p54BE857A.dip0.t-ipconnect.de)
- # [17:30] * Quits: pesla (n=retep@procurios.xs4all.nl) ("( www.nnscript.com :: NoNameScript 4.21 :: www.esnation.com )")
- # [17:40] * Quits: singpolyma (n=singpoly@node-533.tor.pppoe.execulink.com) ("Lost terminal")
- # [17:46] <@adactio> Quick question for anyone...
- # [17:47] <@adactio> Are "fuzzy" dates valid in hResume?
- # [17:47] <@adactio> e.g. 2009-09 rather than 2009-09-01
- # [17:47] <@adactio> for work history/experience?
- # [17:48] <gsnedders> It uses hCalendar, so all ISO 8601 should be fine
- # [17:48] <gsnedders> (Which I guess technically allows even 21, just giving century)
- # [17:53] * Joins: KevinMarks (n=KevinMar@157.22.22.46)
- # [17:55] * Quits: besbes (n=besbes@mercury.mminf.univie.ac.at)
- # [17:55] * Joins: leahculver (n=leahculv@c-67-180-197-78.hsd1.ca.comcast.net)
- # [18:01] * Parts: emrojo (n=emrojo@163.117.139.228)
- # [18:13] * Joins: emrojo (n=emrojo@163.117.139.228)
- # [18:20] * Quits: emrojo (n=emrojo@163.117.139.228) ("Leaving.")
- # [18:24] * Quits: @Phae (n=phaeness@gateb.thls.bbc.co.uk)
- # [18:26] * Joins: BobJonkman (n=BobJonkm@206-248-137-186.dsl.teksavvy.com)
- # [18:26] * Quits: inarru (n=inarru@cpc3-acto1-0-0-cust676.4-2.cable.virginmedia.com)
- # [18:29] <hober> although "Microformats /should/ use RFC 3339." -- /wiki/iso-8601
- # [18:29] * Joins: thomasknoll (n=thomaskn@99.13.242.166)
- # [18:39] * Joins: tantek (n=tantek@c-76-126-175-28.hsd1.ca.comcast.net)
- # [18:39] * ChanServ sets mode: +o tantek
- # [18:51] <tobyink> gsnedders, in ISO 8601 terms, the 21st century is "20".
- # [18:51] * Parts: tobyink (n=tai@77.89.160.246) ("Leaving")
- # [18:56] <gsnedders> Yeah, right, duh
- # [18:57] * Joins: tantekc (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [18:57] * gsnedders typed "20" then realized, wait, this is the 21st cent., and changed it to 21, even though he knew what ISO 8601 said (which is why he got it right before)
- # [19:07] * Quits: @tantek (n=tantek@c-76-126-175-28.hsd1.ca.comcast.net) (Read error: 60 (Operation timed out))
- # [19:22] * Quits: thomasknoll (n=thomaskn@99.13.242.166) (Read error: 145 (Connection timed out))
- # [19:29] * Quits: MrTopf (n=cs@p5B396142.dip.t-dialin.net)
- # [19:35] * Joins: JonathanMalek__ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [19:35] * Parts: @adactio (n=adactio@host86-156-238-27.range86-156.btcentralplus.com)
- # [19:39] * Quits: JonathanMalek__ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [19:42] * Joins: JonathanMalek__ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net)
- # [19:42] * Quits: JonathanMalek_ (n=Jonathan@adsl-68-127-11-22.dsl.pltn13.pacbell.net) (Read error: 104 (Connection reset by peer))
- # [19:50] * Joins: zro (n=zro@wikimedia/zro)
- # [19:56] * Joins: dwhittle (n=dwhittle@nat/yahoo/x-kfwzclvciavqviku)
- # [19:56] * Quits: gsnedders (n=gsnedder@p54BE857A.dip0.t-ipconnect.de)
- # [19:59] * Joins: yvesl (n=yves@dag94-5-88-173-206-27.fbx.proxad.net)
- # [20:02] * Joins: ajturner_ (n=ajturner@209.155.228.129)
- # [20:08] * Joins: Hey_neken (n=kaxero@215.Red-213-96-129.staticIP.rima-tde.net)
- # [20:09] * Quits: ajturner_ (n=ajturner@209.155.228.129)
- # [20:15] * Joins: TabAtkins (n=chatzill@99-35-179-251.lightspeed.hstntx.sbcglobal.net)
- # [20:20] * Quits: ajturner (n=ajturner@209.155.228.129) (Read error: 110 (Connection timed out))
- # [20:22] * Quits: KevinMarks (n=KevinMar@157.22.22.46) ("The computer fell asleep")
- # [20:32] * Joins: ajturner (n=ajturner@209.155.228.129)
- # [20:41] * Joins: besbes (n=besbes@vie-086-059-011-102.dsl.sil.at)
- # [21:06] * Quits: besbes (n=besbes@vie-086-059-011-102.dsl.sil.at) (Read error: 110 (Connection timed out))
- # [21:23] * Joins: markhuot (n=markhuot@64.3.245.34.ptr.us.xo.net)
- # [21:24] * Joins: thomasknoll (n=thomaskn@dsl081-241-091.sfo1.dsl.speakeasy.net)
- # [21:47] * tantekc is now known as tantek
- # [21:47] * ChanServ sets mode: +o tantek
- # [21:51] * Joins: gsnedders (n=gsnedder@p54BE857A.dip0.t-ipconnect.de)
- # [21:58] * Quits: dwhittle (n=dwhittle@nat/yahoo/x-kfwzclvciavqviku) ("Im gone.")
- # [22:06] * Quits: thomasknoll (n=thomaskn@dsl081-241-091.sfo1.dsl.speakeasy.net) ("Leaving.")
- # [22:09] * Quits: ajturner (n=ajturner@209.155.228.129)
- # [22:26] * Quits: shigeta (n=shigeta@50.29.100.220.dy.bbexcite.jp) (Read error: 110 (Connection timed out))
- # [22:32] * Quits: mcdave (n=mcdave@cm-83-97-164-135.telecable.es)
- # [22:33] * Joins: csarven (n=csarven@53563002.cable.casema.nl)
- # [22:48] * Quits: yvesl (n=yves@dag94-5-88-173-206-27.fbx.proxad.net) ("Ex-Chat")
- # [22:50] * Quits: @tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net)
- # [23:13] * Joins: Phae (n=phaeness@cpc2-acto9-0-0-cust364.brnt.cable.ntl.com)
- # [23:13] * ChanServ sets mode: +o Phae
- # [23:22] * Quits: zro (n=zro@wikimedia/zro) (Connection timed out)
- # [23:33] * Quits: csarven (n=csarven@53563002.cable.casema.nl) (Read error: 110 (Connection timed out))
- # [23:40] * Joins: memload (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk)
- # [23:45] * Joins: memload_ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk)
- # [23:46] * Joins: memload__ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk)
- # [23:47] * Quits: memload_ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk) (Read error: 104 (Connection reset by peer))
- # [23:47] * Joins: memload_ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk)
- # [23:48] * Joins: memload___ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk)
- # [23:48] * Joins: KevinMarks (n=KevinMar@dsl081-241-091.sfo1.dsl.speakeasy.net)
- # [23:48] * Quits: memload__ (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk) (Read error: 104 (Connection reset by peer))
- # [23:49] * Quits: memload (n=jamesjef@94-171-217-23.cable.ubr15.wolv.blueyonder.co.uk) (Connection reset by peer)
- # [23:52] * Quits: gsnedders (n=gsnedder@p54BE857A.dip0.t-ipconnect.de)
- # [23:54] * Joins: csarven1 (n=csarven@53563002.cable.casema.nl)
- # [23:55] * csarven1 is now known as csarven
- # [23:59] * Quits: madness (n=mng@ip70-176-92-111.ph.ph.cox.net)
- # Session Close: Wed Sep 02 00:00:00 2009
The end :)