Drew McLellan wrote:
It's the fn=n optimisation ... from my notes it seems that it was
created around the same time as a.include.
So if the fn=n optimisation is being used, does that existing spec deny
the ability to include other n properties? And if not, what wqould the
code look like?
On 4/22/07, Andy Mabbett [EMAIL PROTECTED] wrote:
I'm not clear on the relationship between n and fn in hCard. I have
some markup:
TD class=n
SPAN class=honorific-prefixThe Rt Hon/SPANnbsp;
nbsp;
SPAN class=fnTony Blair/SPAN
nbsp;
SPAN
Can someone please confirm that hAtom can still work, even doing an
abbreviation styling fix for IE such as this:
http://www.sovavsiti.cz/css/abbr.html ?
Just want to make sure I haven't broken anything by implementing this..
Thanks
Lawrence
--
Lawrence Meckan
Absalom Media
Mob: (04) 1047
Keith Grennan wrote:
Supported formats:
* hCard
* hGrant
hGrant is not a microformat. hGrant *is* reusable semantic markup
(POSH by another name).
On this page:
http://hgrants.org/index.php?title=Tutorial
you refer to hGrant as a microformat. This is incorrect. Please read
the wiki
On Thu, Apr 26, 2007 at 02:59:30PM +0100, Jeremy Keith wrote:
Keith Grennan wrote:
Supported formats:
* hCard
* hGrant
hGrant is not a microformat. hGrant *is* reusable semantic markup
(POSH by another name).
Good to know. I'll update my documentation.
On this page:
In message [EMAIL PROTECTED], Jeremy
Keith [EMAIL PROTECTED] writes
Keith Grennan wrote:
Supported formats:
* hGrant
hGrant is not a microformat. hGrant *is* reusable semantic markup
(POSH by another name).
That's a point-of view, but not a definitive fact. Who says it's not a
microformat?
Scott Reynen wrote:
On Apr 26, 2007, at 5:54 PM, Dr. Ernie Prabhakar wrote:
I realize you may not like that distinction, and we may or may not
have any ability to enforce that, but I think it is only reasonable
for us to attempt to enforce community standards, if only through peer
pressure.
