Hi All,
We at Plazes are currently doing a redesign of our page and would like
to use microformats in various situations.
We already discussed some of our basic code structure with Ryan but we'd
like to get your opinions, too.
So here is a small code snippet showing an example usage of a
I believe that this is possible, given that a proposed optimization to
collapse vcard and fn into one class value (class=vcard fn) was
rejected for this very reason.
Additionally, you might consider that the more important hcard in this
case is the location instead of the discover and dispense
Maybe this would be a good time to bring up rel-vcard (and
rel-microformat in general). In particular, to do one of
a rel=vcard href=/profile/fiahless/span class=fn
nicknamefiahless/span/a
or
a class=vcard rel=vcard href=/profile/fiahless/span class=fn
nicknamefiahless/span/a
To indicate
Ooo... that's pretty cool.
How does that compare with the object-include concept?
;)
On 4/19/06, David Janes -- BlogMatrix [EMAIL PROTECTED] wrote:
Maybe this would be a good time to bring up rel-vcard (and
rel-microformat in general). In particular, to do one of
a rel=vcard
On Apr 19, 2006, at 12:49 AM, Rebecca Cox wrote:
If a number of sub-properties are specified within n, do these all
have to be included in fn?
For example, if I had something like:
-
n:
family-name: Cox
given-name: Rebecca
additional-name: Laura
Chris Messina wrote:
Ooo... that's pretty cool.
How does that compare with the object-include concept?
;)
Good question:
- object-include is data inclusion from elsewhere on a page
- rel-uF is indicating that there's a better or more canonical version
of this uF object on the other side of
On 4/18/06, Dr. Ernie Prabhakar [EMAIL PROTECTED] wrote:
I would vote of hCalendar --- this really is a full event, the
life of one person. It also would be the most natural extension of a
birthday event.
Ian Davis has a series of posts on this sort of modelling -- using
Einstein in fact --
Additionally, along the lines of authority, seems that linking to a
named anchor on the destination page would be addtionally wise:
Current page:
a class=vcard rel=contact friend vcard
href=http://beta.plazes.com/plaze/cd21e1717f61ba9cf9df9006038da172/#fiahless;span
class=fn
On Apr 19, 2006, at 10:52 AM, Tantek Çelik wrote:
Rather than attempting to shoehorn this into hCard, perhaps
citations are
the right place to think about this?
I think there is a large difference between what to do with contact
data for an acquaintance who has recently passed away and
On Apr 18, 2006, at 6:49 PM, Sam Sethi wrote:
Thanks Eran. Also lots of back reading to do ;-) But one more quick
question do you have a pointer to the topic on why hcard's are
class=vcard
and not class=hcard? In fact why the class=hx is not the standard
moniker for calender, reviews
On 4/19/06 10:59 AM, Ryan King [EMAIL PROTECTED] wrote:
On Apr 18, 2006, at 6:49 PM, Sam Sethi wrote:
Thanks Eran. Also lots of back reading to do ;-) But one more quick
question do you have a pointer to the topic on why hcard's are
class=vcard
and not class=hcard? In fact why the
On Apr 19, 2006, at 5:08 AM, David Janes -- BlogMatrix wrote:
Maybe this would be a good time to bring up rel-vcard (and rel-
microformat in general). In particular, to do one of
a rel=vcard href=/profile/fiahless/span class=fn
nicknamefiahless/span/a
or
a class=vcard rel=vcard
On Apr 19, 2006, at 10:45 AM, Tantek Çelik wrote:
...
Though you do point out that like all current popular forms of web
syndication, contacts and events have something similar to the RSS
Denial
Of Service problem.
http://weblog.philringnalda.com/2002/10/19/joels-rss-problem
Tell me about
On Apr 19, 2006, at 2:23 PM, Ryan King wrote:
That's right. The reason you can't collapse a 'vcard' class name
and its 'fn' class name is that it makes putting a 'vcard' class
name inside another one becomes ambiguous.
I've seen this explanation a few times, and I've never personally
Scott Reynen wrote:
On Apr 19, 2006, at 2:23 PM, Ryan King wrote:
That's right. The reason you can't collapse a 'vcard' class name and
its 'fn' class name is that it makes putting a 'vcard' class name
inside another one becomes ambiguous.
I've seen this explanation a few times, and I've
On Apr 19, 2006, at 12:58 PM, Scott Reynen wrote:
On Apr 19, 2006, at 2:23 PM, Ryan King wrote:
That's right. The reason you can't collapse a 'vcard' class name
and its 'fn' class name is that it makes putting a 'vcard' class
name inside another one becomes ambiguous.
I've seen this
On Apr 19, 2006, at 1:44 PM, David Janes -- BlogMatrix wrote:
Scott Reynen wrote:
On Apr 19, 2006, at 2:23 PM, Ryan King wrote:
That's right. The reason you can't collapse a 'vcard' class name
and its 'fn' class name is that it makes putting a 'vcard' class
name inside another one becomes
Ryan King wrote:
This is great place to continue this debate. The issue (as I
understand it) is that this optimization doesn't allow nested vcards:
span class=vcard fn[SPAM-DATA]/span
This would still be a problem if it were nested inside another hcard.
(remember, @class is an
Kevin Marks wrote...
Thats why you use a list:
ol
liciteChris Messina/cite qA chat is a list of
definitions./q/li
liciteKevin Marks/cite qNo, a chat is a list of
quotations./q/li
/ol
Which has a very nice default rendering.
Slap a date/time-design-pattern abbr in there and it would
Ryan King wrote:
But the relationship isn't 'vcard'. 'vcard' describes the format (or
part of the format) of the referenced resource, not the relationship
between the two.
OK, fair enough: vcard is just a word, and in particular
[top-level-uf-id] is just a word. But because we're devising
David, it appears you may have missed my email from this morning:
[uf-discuss] UID, URL, live microformats (was: Microformat auto-discovery
WAS: Plazes Microformats)
http://microformats.org/discuss/mail/microformats-discuss/2006-April/003726
.html
In short, we don't want a vocabulary explosion
On 4/19/06 1:57 PM, David Janes -- BlogMatrix [EMAIL PROTECTED]
wrote:
Ryan King wrote:
This is great place to continue this debate. The issue (as I
understand it) is that this optimization doesn't allow nested vcards:
span class=vcard fn[SPAM-DATA]/span
This would still be a problem
On Apr 19, 2006, at 2:13 PM, Scott Reynen wrote:
On Apr 19, 2006, at 3:45 PM, Ryan King wrote:
On Apr 19, 2006, at 12:58 PM, Scott Reynen wrote:
On Apr 19, 2006, at 2:23 PM, Ryan King wrote:
That's right. The reason you can't collapse a 'vcard' class name
and its 'fn' class name is that it
Ryan King wrote:
One option would be to use both. This may seem a bit convoluted, but
hopefully it can be illustrative of how microformats can be overlaid.
div class=vcard vevent
span class=fn summaryAlbert Einstein/span
(abbr class=dtstart bday title=1879-03-14March 14, 1879/ abbr -
On Apr 19, 2006, at 4:32 PM, Ryan King wrote:
div class=vcard
span class=fnTantek Çelik/span
span class=agent vcard
!-- the order is actually irrelevant here class=vcard
agent is synonymous --
span class=fnRyan King/span
/span
/div
Which hcard does the 'agent'
Hi Tantek and Atamido,
I think genealogy is more about relationships (ie marriage, parent
child, etc) than individual biographies. A genealogy microformat, to
my way of thinking, would borrow more from XFN than hCard.
To deal with life dates and other biographical information (like,
On 4/19/06, Paul Bryson [EMAIL PROTECTED] wrote:
One thing though, I use at least one chat program that has an option to
condense all contiguous messages from a single author together so that it
just displays the author once, but the timestamp of each message.
A couple of responses come to
You should also be aware of the proposed OBJECT include pattern[1].
With this you could do something like:
span class=vcard id=Person1
!-- hcard stuff here for Person1 --
/span
ol
licitePerson1/citeqQuoted Text/q/li
liciteobject data=#Person1 class=include//citeqQuoted
Text/q/li
/ol
The object
does anyone have any ideas about good ways to specify cities and countries
in hcalendar listings?
What would be the best way to do this?
I see a lot of people just putting a city or state name in the location
field but it would be nice if there was a standard way to to this.
(there can be
There is an address design pattern[1]. it is taken from the hCard
spec. So for location you could mark it up as:
abbr class=geo location adr title=34.34;-120.12span
class=localityAny Town/span, abbr class=region
title=MissouriMO/abbr abbr class=country-name title=United
States of
On 4/14/06, Ben Ward [EMAIL PROTECTED] wrote:
Since chronology is vital to describing dialogue, Kevin Marks
OL+CITE+Q|BLOCKQUOTE example works much better for me. Appealingly it
also uses the same number of HTML elements as using the DL example.
Some (very late) thoughts:
- I find the idea
On Apr 19, 2006, at 9:07 PM, Chris Messina wrote:
On 4/20/06, Atamido [EMAIL PROTECTED] wrote:
Is there any real disadvantage to using 'bday' instead of 'dtstart'?
I think Ryan's suggestion is to use both, so there's no obvious
disadvantage without knowing the intended use. By using both you
I just wanted to be sure that my simple implementation of hCard into
my personal blog's comments are accurate. Here is the syntax I
installed.
div id=vcard-1 class=comment_meta vcardcitea class=url fn
href=http://cdevroe.com;Colin D. Devroe/cite on a
href=#comment-135 title=April 19th,
On Apr 20, 2006, at 1:33 AM, Chris Messina wrote:
Looks pretty good from here. Standard practice is to use fn rather
than the more specific classes for general use where, as you pointed
out, user input is involved. I would make one change:
div id=vcard-1 class=comment_metacite class=vcarda
Is there any real disadvantage to using 'bday' instead of 'dtstart'?
I think Ryan's suggestion is to use both, so there's no obvious
disadvantage without knowing the intended use. By using both you get
secondary benefits that we might not conceive of just yet. The more
specific the
35 matches
Mail list logo
