IRC Log for #microformats on 2005-12-28
Timestamps are in UTC.
- [00:10:43] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Read error: 104 (Connection reset by peer))
- [00:10:48] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [01:11:18] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [01:14:28] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [01:22:15] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [01:23:32] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [01:33:47] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [01:34:16] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [01:46:57] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [01:48:12] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [01:59:37] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [02:00:52] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [02:08:35] * rtomayko (n=rtomayko@cpe-24-166-51-26.neo.res.rr.com) Quit (Read error: 110 (Connection timed out))
- [02:09:52] * fuzzyBSc (n=fuzzy@c210-49-72-91.rochd2.qld.optusnet.com.au) has joined #microformats
- [02:13:10] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [02:13:50] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [02:29:58] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [02:30:29] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [02:37:29] * lies (n=tim@mail.del.icio.us) Quit (Read error: 110 (Connection timed out))
- [02:48:24] <fuzzyBSc>
tantek: re your email: class=summary in hAtom currently means "content summary", and is a distinct atom element to both content and title elements. This would seem to be another clash.
- [02:51:06] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [02:51:23] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [02:54:55] <fuzzyBSc>
Morning, Atamido :)
- [03:14:58] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [03:16:02] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [03:36:04] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [03:36:25] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [03:55:52] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Excess Flood)
- [03:56:32] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [04:08:04] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Remote closed the connection)
- [04:23:40] * tantek (n=tantek@dsl092-187-246.sfo1.dsl.speakeasy.net) Quit ()
- [04:48:04] * factoryjoe (n=cmessina@c-69-181-81-22.hsd1.ca.comcast.net) Quit ()
- [05:08:19] * factoryjoe (n=cmessina@c-69-181-81-22.hsd1.ca.comcast.net) has joined #microformats
- [05:42:27] * bergie (n=bergie@cs78242134.pp.htv.fi) has joined #microformats
- [05:48:25] <Frederic>
hello
- [05:58:07] * rtomayko (n=rtomayko@cpe-24-166-51-26.neo.res.rr.com) has joined #microformats
- [06:22:53] * bergie (n=bergie@cs78242134.pp.htv.fi) Quit ()
- [06:39:27] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [06:50:28] * factoryjoe (n=cmessina@c-69-181-81-22.hsd1.ca.comcast.net) Quit ()
- [07:06:01] * tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) has joined #microformats
- [07:06:01] * ChanServ sets mode +o tantek
- [07:40:37] <fuzzyBSc>
Morning, Frederic
- [08:21:20] <fuzzyBSc>
Atamido: How badly out of date is <http://microformats.org/wiki/existing-classes>?
- [08:25:03] * factoryjoe (n=cmessina@dsl092-013-089.sfo1.dsl.speakeasy.net) has joined #microformats
- [09:36:37] <tantek>
fuzzyBSc, perhaps check the history tab on that page
- [10:25:33] * rtomayko (n=rtomayko@cpe-24-166-51-26.neo.res.rr.com) Quit (Connection timed out)
- [10:56:08] * factoryjoe (n=cmessina@dsl092-013-089.sfo1.dsl.speakeasy.net) Quit ()
- [11:09:25] * valmont (n=chrishol@men75-2-82-66-215-76.fbx.proxad.net) has joined #microformats
- [11:20:33] * bergie (n=bergie@host-43.253.lasipalatsi.fi) has joined #microformats
- [11:48:47] * bergie (n=bergie@host-43.253.lasipalatsi.fi) Quit ()
- [12:00:18] * tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) Quit ()
- [12:03:28] * bergie (n=bergie@b-062-197-172-250.lohjanpuhelin.fi) has joined #microformats
- [12:20:51] * tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) has joined #microformats
- [12:20:51] * ChanServ sets mode +o tantek
- [12:26:52] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Read error: 104 (Connection reset by peer))
- [12:26:57] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [12:34:19] * RobertBachmann (n=RobertBa@N123P025.adsl.highway.telekom.at) has joined #microformats
- [12:34:31] <RobertBachmann>
greetings
- [12:38:28] <RobertBachmann>
fuzzyBSc: I've tried to change hAtom2Atom.xsl to do it's job without exslt:node-set but it didn't work. Althought exslt is not supported by every XSLT engines, most popular XSLT engines provide some kind of node-set() function. Have you done any changes to hAtom2Atom.xsl?
- [13:00:53] * bergie (n=bergie@b-062-197-172-250.lohjanpuhelin.fi) Quit (Read error: 110 (Connection timed out))
- [13:07:31] * bkdelong_ (n=bkdelong@h-67-102-164-116.cmbrmaor.covad.net) has joined #microformats
- [13:11:07] * bkdelong_ is now known as bkdelong
- [13:26:34] <mfbot>
[[hreview]] M http://microformats.org/wiki?title=hreview&diff=0&oldid=3613 * Tantek * (+0)
- [13:30:34] <fuzzyBSc>
Robert: Yes, I haven't been able to come up with a solution that supports both opacity and disambiguation but doesn't use node-set.
- [13:30:55] <fuzzyBSc>
I haven't made any changes since the patch I sent your way that uses the exsl:node-set function.
- [13:32:27] <fuzzyBSc>
tantek: Atamido wrote on microformats-discuss that the existing-classes wiki page was out of date. My question was really, "in what way?" rather than "when was it last updated?".
- [13:36:58] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Read error: 104 (Connection reset by peer))
- [13:37:03] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [13:41:39] * danja (i=DannyAye@host90-220.pool80104.interbusiness.it) has joined #microformats
- [14:12:21] * dglazkov (n=dglazkov@adsl-065-081-081-030.sip.bhm.bellsouth.net) has joined #microformats
- [14:15:50] <RobertBachmann>
fuzzyBSc: I've installed lost of XSLT enginges (MSXSL, libxslt, saxon, xt, xalan-j, 4xslt, oracle xdk). I'm currently trying to get xmldiff (http://www.logilab.org/projects/xmldiff) working.
- [14:37:42] * danja (i=DannyAye@host90-220.pool80104.interbusiness.it) Quit (Read error: 110 (Connection timed out))
- [14:41:12] <fuzzyBSc>
Robert: Do you think trying to work without a node-set implementation is advisable based on this experience?
- [14:42:38] <RobertBachmann>
No.
- [14:43:06] <fuzzyBSc>
tantek: Do you have any thoughts on how title should be handled in hAtom? Presumably the hCard specification is pretty much set in concrete, now.
- [14:43:49] <fuzzyBSc>
tantek: It is interesting to me that it seems parts of hReview could be superceeded by hAtom elements (reviewer -> author, for example) also. Could hReview be subject to change at this late stage?
- [14:44:56] <fuzzyBSc>
Robert: My understanding is that xslt 2.0 will not require node-set. A variable can effectively be a document without any extra handling. Unfortunately, it is less widely implemented than exslt at this stage :-/
- [14:45:10] * bergie (n=bergie@cs78242134.pp.htv.fi) has joined #microformats
- [14:49:33] <RobertBachmann>
xsltproc/libxslt, saxon, xt, 4xslt, support exslt:node-set() out of the box. MSXSL and Oracle XDK have a function with the same name and functionality but in an other namespace. So using node-set is not a problem.
- [14:50:35] * danja (i=DannyAye@host192-217.pool80104.interbusiness.it) has joined #microformats
- [15:25:21] <Atamido>
fuzzyBSc: I wrote the existing classes page, but haven't finished it yet. There are a lot of missing classes, so it really needs to be updated. :p
- [15:32:02] <fuzzyBSc>
Ahh :)
- [16:06:39] <RobertBachmann>
fuzzyBSc: I've got xmldiff working. seems to be quite handy for running the tests.
- [16:37:23] * bergie (n=bergie@cs78242134.pp.htv.fi) Quit ()
- [16:47:25] <tantek>
fuzzyBSc, hReview has actually gotten built into a number of tools, so we'll probably want to avoid cosmetic changes like renaming properties
- [16:47:47] <tantek>
also, note that *reviewer* is a very specific semantic
- [16:48:12] <tantek>
moreso than author
- [16:48:29] <tantek>
that being said, yes, there are changes we are looking into for hReview
- [16:48:46] <tantek>
and they've been discussed on the hReview feedback page so far http://microformats.org/wiki/hreview-feedback
- [16:49:08] * tantek sets mode +o RobertBachmann
- [16:51:52] <fuzzyBSc>
So long as the "of" part of author is clear it should be semantically equivalent, I would have thought. "author of this review" and "reviewer" are probably equivalent. The installed base argument is always compelling, though.
- [16:52:59] <fuzzyBSc>
In fact, the hAtom terminology permits the conept of a "contributor to the review" which adds extra semantics that may be useful.
- [16:53:31] <fuzzyBSc>
The review and the blog entry spaces overlap a fair bit.
- [16:54:10] <tantek>
yes, in many ways, blog posts and reviews tend to overlap
- [16:55:22] <tantek>
but i've actually noticed that most reviews in blog posts tend to be only *part* of the blog post, not the whole thing
- [16:58:09] * fuzzyBSc nods
- [16:58:35] <fuzzyBSc>
I was just thinking that. I often see reviews for the last five movies someone has seen popping up on planets.
- [16:58:56] <tantek>
right, people often put multiple reviews in one blog post
- [16:59:43] <fuzzyBSc>
The hAtom specification for blog entries also seems a lot more structured. There is a clear separation of an opaque "content" and other hAtom elements. Nothing in the content is parsed (at least, not first time around).
- [17:11:01] <tantek>
the problem of opacity is one that we've been barely dodging for a while now
- [17:11:24] <tantek>
i'm actually very glad that hAtom has raised a concrete/practical example of requiring opacity
- [17:11:42] <tantek>
as we've actually discussed it informally since around this past June
- [17:12:06] <tantek>
specifically, the possibility of having a one-class-name microformat that was used to indicate opacity
- [17:12:16] <tantek>
call it "mfo" for short
- [17:12:55] <tantek>
you could use this on *any* root microformat element as a way of ensuring that wherever it happened to be embedded, anything parsing the stuff "above" it, wouldn't accidentally find something inside it
- [17:13:50] <tantek>
e.g. you might put a <span class="vcard mfo"> deep inside a <span class="vevent">, and not want the categories/tags of the hCard accidentally parsed into the hCalendar event
- [17:14:18] <fuzzyBSc>
I think the problem crops up whenever you have a container within a container.
- [17:14:48] <fuzzyBSc>
You are defining a new context in which to understand the elemental classes and rel values, and that context is distinct from any containing context.
- [17:16:15] <fuzzyBSc>
Whenever you have <span class="entry"> <span class="vcard">...</span> </span> you may want to ignore the vcard content in the entry parsing. I guess it only really matters when there is overlapping vocabulary.
- [17:16:49] <fuzzyBSc>
"author" doesn't just mean "author". It means "author of the container I live in".
- [17:17:58] <fuzzyBSc>
Unless there is an explicit way for the full assertion to be made contexts have to be careful about nesting within one another. A common term like mfo (or even "context", "microformat"?) would avoid forward-compatability problems of defining new containers.
- [17:18:44] <Atamido>
I am working on an example traditional forum layout using the hAtom, so my questions will come from there.
- [17:19:15] <tantek>
right
- [17:19:39] <tantek>
so far the problem has been avoided because any compound use of microformats would presumably support earlier microformats
- [17:19:59] <tantek>
e.g. an hCalendar parser would want to parse hCards explicitly, and thus could treat class="vcard" as a signal of "opacity"
- [17:20:10] <tantek>
but forward-compatibility is exactly the problem
- [17:21:15] <tantek>
when we come up with hFoobar which has a summary property for example, you should be able to embed an hFoobar into an hCalendar event, or an hReview, safely without having the hFoobar summary be treated as a summary for the event or review.
- [17:22:02] <tantek>
in many ways, it's like saying "this thing here is an object, a layer of abstraction, and thus anything inside it should be treated as its properties, not as properties of the container"
- [17:22:30] <tantek>
i think we have enough of a need now to start at least an examples page, documenting real world examples we are coming up with which present this problem
- [17:23:05] <tantek>
then we can start a *-formats page, documenting various terms that previous formats have given to opaque containers, like "object", "container", etc.
- [17:24:09] <tantek>
lacking any better name to call this concept, a few of us have been informally using "mfo" just as a working name for the purposes of discussion. we'd rather pick an actual classname which represented previous effort in this area though, based on what we come up with during the research phase.
- [17:24:19] <fuzzyBSc>
Maybe the class name should just be "u" to indicate microformat :)
- [17:24:19] <fuzzyBSc>
Something like class="u vcard", class="u hcalendar", class="u feed", etc.
- [17:24:39] <fuzzyBSc>
If you see that class name while parsing and understand the class, just use it. If you don't, treat it as opaque.
- [17:26:19] <tantek>
or perhaps "uf"?
- [17:26:36] <tantek>
nonetheless, we should start with some wiki pages to document examples and formats
- [17:26:43] <tantek>
we can worry about the name later :)
- [17:26:49] <fuzzyBSc>
:)
- [17:27:18] <tantek>
fuzzyBsc, Atamido, would you guys like to start the wiki pages for this?
- [17:27:23] <fuzzyBSc>
One thing to consider before getting in too deep is that this may be a uf-specific problem. There may be less out there by way of example than you're used to.
- [17:28:00] <tantek>
yes, these will be examples of real world use cases that need it
- [17:28:15] <tantek>
rather than the traditional examples of real world use cases that demonstrate it
- [17:28:26] <tantek>
it's a subtle distinction, and one that should be documented in the page
- [17:28:31] * fuzzyBSc nods. Ok.
- [17:29:06] <tantek>
so the best ways i have found to think about this concept is as a layer of abstraction, or a wrapper, or a container
- [17:29:19] * edsu (n=esummers@66.187.134.52) has joined #microformats
- [17:29:49] <tantek>
but all those don't seem to convey the meaning precisely either
- [17:30:13] <tantek>
thus, lacking a better name, would anyone be opposed to using "mfo-" as the name of the concept for purpose of discussion?
- [17:30:34] <tantek>
like I said, I have no particular desire to use "mfo" as the class name, and am confident that as a result of the discussion/analysis we will come up with a better name
- [17:30:57] <tantek>
if there are no objections to mfo- then I will go ahead and create mfo-examples, mfo-formats
- [17:31:14] <fuzzyBSc>
No objections, here.
- [17:31:45] <fuzzyBSc>
Is that an acronym for anything? :)
- [17:31:55] <tantek>
microformats opacity
- [17:31:57] <fuzzyBSc>
Microformat opaque?
- [17:31:59] <fuzzyBSc>
Ok :)
- [17:32:04] <tantek>
or microformat object
- [17:32:13] <tantek>
deliberately left unspecified :)
- [17:32:19] <fuzzyBSc>
It works from a few angles, then :)
- [17:34:57] <fuzzyBSc>
I'll just finish my train of thought and I'll have a look at what I can do. I'm migrating my blog to a vanity domain, or conducting stage one at least.
- [17:39:50] <Hixie>
regarding opacity, one would hope that there are few enough microformats that name clashes can simply be avoided by design...
- [17:40:32] <mfbot>
[[mfo-examples]] N http://microformats.org/wiki/mfo-examples * Tantek * (+2171)
- [17:40:43] <mfbot>
[[mfo-examples]] M http://microformats.org/wiki?title=mfo-examples&diff=0&oldid=3614 * Tantek * (-1) Contributors -
- [17:41:04] <tantek>
Hixie, yes, that was certainly my thought from the beginning
- [17:41:18] <tantek>
and the reason why I have held back on bringing this up as something we should bother with
- [17:41:25] <tantek>
but clearly others have run into the same problem
- [17:41:39] <tantek>
and now there are real examples with real content
- [17:42:09] <tantek>
which IMHO is the necessary prerequisite before considering an explicit microformat
- [17:42:31] <tantek>
but yes, in general the idea is to keep the number of total microformats to a very small number
- [17:42:32] <Hixie>
too many microformats ;-)
- [17:42:42] <Hixie>
time to start culling ;-)
- [17:43:07] <tantek>
there are good arguments being made for microformats for resumes, listings (e.g. classifieds), and recipes for example
- [17:43:30] <RobertBachmann>
fuzzyBSc: found a bug in hAtom2Atom.xsl
- [17:43:32] <tantek>
also, an "abstraction" microformat feels fairly harmless, as it is only one class name
- [17:43:42] <Hixie>
slippery slope :-)
- [17:43:48] <Hixie>
what are the arguments for resumes?
- [17:44:14] <tantek>
many people publish their resumes online, and presumably want them found and parsed properly
- [17:44:18] <tantek>
as well as
- [17:44:24] <tantek>
there are now resume aggregators out there
- [17:44:27] <tantek>
er, search engines
- [17:44:30] <tantek>
e.g. SimplyHired
- [17:44:36] <tantek>
which would like to see this as well
- [17:44:47] * Hixie thought most resumes were in MS Word format
- [17:44:48] <tantek>
thus there is practical publisher and indexer demand
- [17:45:00] <tantek>
i.e. SimplyHired came to me and asked for this
- [17:45:14] <tantek>
most resumes on the web tend to be HTML
- [17:45:22] <Hixie>
well yeah, people are always asking for things
- [17:45:38] <Hixie>
the mapping vendors are asking the svgwg for mapping-specific features
- [17:45:42] <Hixie>
the key is to say no :-P
- [17:45:43] <tantek>
Atamido, fuzzyBSc, I have created http://microformats.org/wiki/mfo-examples please contribute your thoughts and build on what is there
- [17:45:57] <tantek>
Hixie, you're right, the key is to in general say no
- [17:46:11] <tantek>
and the microformats community has certainly said no far more often than yes
- [17:46:29] <Hixie>
in the case of microformats it's less of an issue since it doesn't require anything of other UAs, at least
- [17:46:30] <tantek>
though sometimes you have to first do some research before you can concretely determine the "no"
- [17:46:35] <Hixie>
yup
- [17:46:41] <tantek>
but that research is still useful
- [17:46:46] <tantek>
as often the same requests come in multiple times
- [17:46:54] <tantek>
and having that backing can be useful
- [17:46:59] <RobertBachmann>
fuzzyBSc: The XHTML nodes inside of <summary> and <content> must be enclosed by <div xmlns="http://www.w3.org/1999/xhtml">. The current code might generate different results.
- [17:47:20] <tantek>
or perhaps the same request comes in but with new evidence/justification, and can demonstrated that it is new by pointing to the research and adding it
- [17:47:31] <tantek>
one must assume that one does not always get things right the first time
- [17:47:46] <tantek>
or rather, that a better theory/hypothesis can always be proposed
- [17:47:50] <tantek>
per the scientific method
- [17:48:11] <Hixie>
theory and hypothesis mean quite different things in science, but sure
- [17:50:04] <fuzzyBSc>
Robert: I think it will produce the correct results. The xhtml namespace is used in the xsl, so namespace declarations should be inserted by the processor at appropriate places...
- [17:50:22] * Hixie finds a witch in the SVG Tiny 1.2 spec
- [17:50:30] <Hixie>
(section 7.11, first sentence)
- [17:51:25] <fuzzyBSc>
Hrmm.. I might not be able to get at this until tomorrow.
- [17:52:40] <tantek>
Hixie, agreed
- [17:53:09] <tantek>
both are iterated, that's my point
- [17:53:43] <RobertBachmann>
fuzzyBSc: The problem isn't the namespace the current code would transform <p class="summary"> to <p xmlns="http://www.w3.org/1999/xhtml" class="summary"> but Atom specifies that it must be <div xmlns="http://www.w3.org/1999/xhtml">. I'm currently working on a patch. Should be fixed within the next 10 minutes.
- [18:00:46] <fuzzyBSc>
Ahh.. ok.
- [18:01:29] <mfbot>
[[cite-brainstorming]] http://microformats.org/wiki?title=cite-brainstorming&diff=0&oldid=3615 * Tim White * (+436) Types and Roles -
- [18:06:34] <RobertBachmann>
fuzzyBSc: fixed & mailed
- [18:09:37] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Remote closed the connection)
- [18:10:54] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [18:11:13] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Client Quit)
- [18:11:35] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [18:11:36] <fuzzyBSc>
Robert: Applied :)
- [18:12:53] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Client Quit)
- [18:12:59] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [18:13:08] <RobertBachmann>
fuzzyBSc: by the way: xmldiff works great the only problem it chockes on titles.output (because it isn't well-formed).
- [18:20:44] <fuzzyBSc>
Ahh... the multiple feeds.
- [18:21:13] <fuzzyBSc>
Anyway, I had better be off. I'll try to get something useful done tomorrow :)
- [18:21:17] * fuzzyBSc (n=fuzzy@c210-49-72-91.rochd2.qld.optusnet.com.au) has left #microformats
- [18:51:01] * tantek (n=tantek@adsl-63-195-114-133.dsl.snfc21.pacbell.net) Quit ()
- [19:22:33] * hober (n=ted@rrcs-67-52-157-90.west.biz.rr.com) has joined #microformats
- [19:22:42] * t1m (n=t1m@pool-151-199-47-177.bos.east.verizon.net) Quit (Read error: 110 (Connection timed out))
- [19:35:19] * tantek (n=tantek@dsl092-187-246.sfo1.dsl.speakeasy.net) has joined #microformats
- [19:35:19] * ChanServ sets mode +o tantek
- [19:54:08] * valmont (n=chrishol@pdpc/supporter/silver/valmont) Quit (Read error: 110 (Connection timed out))
- [19:55:58] * hober (n=ted@rrcs-67-52-157-90.west.biz.rr.com) Quit ("nil")
- [19:56:39] * factoryjoe (n=cmessina@c-69-181-81-22.hsd1.ca.comcast.net) has joined #microformats
- [20:00:49] <Atamido>
tantek: Would it be overkill to include a class name to indicate that the element is a container element whose contents should not be parsed in relation to the parent's contents?
- [20:01:39] <Atamido>
Like <div class="hatom mfo"><div class="vcard mfo">
- [20:02:36] <Atamido>
Hmm, that seems borked if you use <div class="hatom mfo"><div class="vcard author mfo">
- [20:36:01] * hober (n=ted@rrcs-67-52-157-90.west.biz.rr.com) has joined #microformats
- [20:45:08] * RobertBachmann (n=RobertBa@N123P025.adsl.highway.telekom.at) Quit (Read error: 110 (Connection timed out))
- [20:49:43] <Atamido>
http://files.commo.de/md-lite/mdforum/topic-combined-2.html
- [21:25:10] * bergie (n=bergie@cs78242134.pp.htv.fi) has joined #microformats
- [21:39:20] <tantek>
Atamido, re: your question, see the mfo-examples page where this is discussed
- [21:50:12] <Atamido>
tantek: I don't think I was paying attention the first time I read that.
- [21:50:41] <Atamido>
However, what about my example page where an element is both the vcard and the author?
- [21:59:50] <tantek>
yes that is ok, because you are stating that the author property is essentially an entire hCard and must be parsed as such
- [22:03:07] <Frederic>
Hello tantek
- [22:10:45] * hlb (i=hlb@CCCA.NCTU.edu.tw) Quit (Read error: 104 (Connection reset by peer))
- [22:10:51] * hlb (i=hlb@CCCA.NCTU.edu.tw) has joined #microformats
- [22:21:10] * t1m (n=t1m@pool-151-199-47-177.bos.east.verizon.net) has joined #microformats
- [22:21:54] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit (Remote closed the connection)
- [22:25:03] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [22:25:37] <mfbot>
[[cite-examples]] http://microformats.org/wiki?title=cite-examples&diff=0&oldid=3616 * Tim White * (+3933) Example Citation Formats -
- [22:25:48] * dglazkov (n=dglazkov@adsl-065-081-081-030.sip.bhm.bellsouth.net) Quit ()
- [22:26:50] <Atamido>
mfbot: help
- [22:31:01] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) Quit ("Chatzilla 0.9.69 [Firefox 1.5/2005111116]")
- [22:35:44] <mfbot>
[[citations in the wild]] N http://microformats.org/wiki/citations_in_the_wild * Tim White * (+27338)
- [22:37:02] * Atamido (n=atamido@user-0ccsqt9.cable.mindspring.com) has joined #microformats
- [22:39:28] * danja (i=DannyAye@host192-217.pool80104.interbusiness.it) Quit ("Ciao!")
- [22:40:37] * rtomayko (n=rtomayko@cpe-24-166-51-26.neo.res.rr.com) has joined #microformats
- [23:04:09] * bergie (n=bergie@cs78242134.pp.htv.fi) Quit ()
- [23:24:38] * mburns (n=burns@c-24-22-50-182.hsd1.or.comcast.net) has joined #microformats
- [23:56:40] * edsu (n=esummers@66.187.134.52) Quit ("leaving")
These logs were automatically created by mflogbot on
chat.freenode.net
using a modified version of the Java IRC LogBot.
See http://microformats.org/wiki/mflogbot for more information.