OK, so this

<span class="fn">ChattingChuck</span>

would produce a blank N, but the implied nickname rule would kick in to produce nickname:ChattingChuck?

If so, then the remaining question is: Is this useful enough to mark up as an hcard? There's not much you can do with the nickname without more context except display it.


brian suda wrote:

Actually, the ONLY property that is mandatory is FN (and the root class
of vcard). The N property can be extracted from an FN (when possible).
So in the example you would need:

<li class="vcard"><span class="fn nickname">ChattingChuck</span></li>

There is also an implied-nickname rule that if a FN is only one word
long it is used. So class="nickname" is redundant.

In this case since there is no explicit N, and since the FN does not
meet the implied N rule, the N value in the final output will be N:;;;;;
(blank)

-brian


Chris Messina wrote:
I think in order to validate, you need to supply at least the 'n'
value, even if the screenname is not the actual "name":

<li class="vcard"><span class="n nickname">ChattingChuck</span></li>

On the other hand, I don't know if you *should* mark up those
fragments as hcards given the 'n' requirement... I think it's good to
be semantic to the last drop, but I think Tantek's advice on this
issue would help: how little data can substantiate hcard markup?

Chris

On 5/23/06, John Panzer <[EMAIL PROTECTED]> wrote:
All,

I have a use case for displaying lists of people (readers of a blog)
which seems reasonable to mark up using XOXO and hCard.  However, in at
least some of the cases the only piece of information I have about a
user is their login ID, which is an AOL/AIM 'screen name'.  Is this a
reasonable minimal hCard markup for these cases?

<li class="vcard"><span class="nickname">ChattingChuck</span></li>

Two questions here: (1) is "nickname" the right way to say this and (2)
is this sufficient to be a reasonable if minimal hCard?


Thanks,
John Panzer
_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss

_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss


_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss

_______________________________________________
microformats-discuss mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-discuss

Reply via email to