In message [EMAIL PROTECTED], Guillaume Lebleu
[EMAIL PROTECTED] writes
not least because the alternative:
foo class=fnPink Floyd/foo
would be optimised (sic) to have a given name of Pink and a family
name of Floyd.
I don't disagree that groups/bands should be considered
On 7/2/08 00:13, Guillaume Lebleu [EMAIL PROTECTED] wrote:
I don't disagree that groups/bands should be considered organisations.
This takes me back several months (June 2007) to a thread about whether both
music:groups and music:artists_singular should be marked up as
organisations:
The change made recently, to the hCard spec:
http://microformats.org/wiki?title=hcard-parsingdiff=nextoldid=25563
affects not only hCard but also other microformats; it has implications
for both current parsers and published microformats, but seems to have
been made without prior notification
On Thu, February 7, 2008 09:55, Michael Smethurst wrote:
This takes me back several months (June 2007) to a thread about whether
both music:groups and music:artists_singular should be marked up as
organisations:
http://www.mail-archive.com/microformats-discuss@microformats.org/msg07887.html
On Thu, 2008-02-07 at 09:55 +, Michael Smethurst wrote:
Agreed. The problem also arises with artists like Eminem, Madonna,
Prince.
How is fn optimisation supposed to work here?
As we find a lot in music your above examples are people and
Organizations. How it appears, I would guess is how
Can someone please enlighten me as to the correct values for this type link
above?
It depends on the implementation but basically you want to link to
another page and say that it is also you, using rel=me. The easiest
way to get your xfn links links detected by Googles Social Graph API is
to
Thom Shannon wrote:
perhaps there was prior discussion and agreement that was just a long
time ago? Have you searched the archives or asked Tantek directly?
Here's the IRC log regarding the change to the wiki:
http://rbach.priv.at/Microformats/IRC/2008-02-07#T010220
I agree with the change -
On Thu, February 7, 2008 15:37, Scott Reynen wrote:
On Feb 7, 2008, at 4:59 AM, Andy Mabbett wrote:
If it's just a generic contact that you know nothing about, I'd say
just use fn, as adding org is potentially incorrect information. But if
you know it's a music act, I think it makes sense
I've been thinking about how to create a standard structure to format
a post within a publishing system and I was looking for a microformat
and was wondering if the hentry as used on posts on microformats.org
is a proposed spec and if there are any other examples? Would this be
important in
Q1. yes
Q2. yes
Q3. don't know
Here's the spec:
http://microformats.org/wiki/hatom
Regards, etc...
On Feb 7, 2008 12:43 PM, Brandon Richards [EMAIL PROTECTED] wrote:
I've been thinking about how to create a standard structure to format
a post within a publishing system and I was looking for a
On 2/7/08 7:14 AM, Thom Shannon [EMAIL PROTECTED] wrote:
perhaps there was prior discussion and agreement that was just a long
time ago? Have you searched the archives or asked Tantek directly?
Yes, this is from a long time ago, may even predate microformats.org.
It's not a change except in
On Thu, February 7, 2008 14:33, Michael Smethurst wrote:
At the time Scott Reynen suggested:
snip
If it's just a generic contact that you know nothing about, I'd say
just use fn, as adding org is potentially incorrect information. But
if you know it's a music act, I think it makes sense to
On 7/2/08 11:59, Andy Mabbett [EMAIL PROTECTED] wrote:
On Thu, February 7, 2008 09:55, Michael Smethurst wrote:
This takes me back several months (June 2007) to a thread about whether
both music:groups and music:artists_singular should be marked up as
organisations:
Brandon wrote:
and was wondering if the hentry as used on posts on microformats.org
is a proposed spec and if there are any other examples? Would this be
http://microformats.org/wiki/hatom
--
Edward O'Connor
[EMAIL PROTECTED]
Ense petit placidam sub libertate quietem.
On Feb 7, 2008, at 11:08 AM, Manu Sporny wrote:
It invalidates the need for mfo in hcard, doesn't it?
If it were applied to the rest of Microformats, it would invalidate
the
need for mfo entirely.
Not exactly. As hober said in IRC:
# [02:17:12] hober just to quickly clarify, the
The hCard spec says:
http://microformats.org/wiki/hcard#Property_Notes
The 'n' property is OPTIONAL if any implied 'n' optimization
rules are in effect.
suggesting that it is mandatory otherwise, while the cheatsheet:
In message [EMAIL PROTECTED], Tantek Çelik
[EMAIL PROTECTED] writes
On 2/7/08 7:14 AM, Thom Shannon [EMAIL PROTECTED] wrote:
perhaps there was prior discussion and agreement that was just a long
time ago? Have you searched the archives or asked Tantek directly?
Yes, this is from a long
On Feb 7, 2008, at 1:19 PM, Rickards, Julian (NDM) wrote:
Hi:
I have multiple hCards on one page
(http://www.mndm.gov.on.ca/mndm/mines/lands/pro/contact_e.asp
blocked::http://www.mndm.gov.on.ca/mndm/mines/lands/pro/
contact_e.asp
). I created a unique ID for each div class=vcard so that the
On 2/7/08 10:08 AM, Manu Sporny [EMAIL PROTECTED] wrote:
It invalidates the need for mfo in hcard, doesn't it?
If it were applied to the rest of Microformats, it would invalidate the
need for mfo entirely.
This is one of the reasons mfo has not progressed much further than the
examples given
Ok so hatom, but I suppose what I'm missing is the multiple pages of
content that belong to the same entry. For portability sake, how do
the other pages of content get linked or associated without having to
actually include all of the content within one page? Sorry this just
isn't clear to me.
*
Hi:
I have multiple hCards on one page
(http://www.mndm.gov.on.ca/mndm/mines/lands/pro/contact_e.asp
blocked::http://www.mndm.gov.on.ca/mndm/mines/lands/pro/contact_e.asp
). I created a unique ID for each div class=vcard so that the link
beside each one
On Feb 7, 2008, at 4:59 AM, Andy Mabbett wrote:
If it's just a generic contact that you know nothing about, I'd say
just
use fn, as adding org is potentially incorrect information. But if
you
know it's a music act, I think it makes sense to consider even an
individual performer's name to be
Since hAudio is still much more of a new microformat in development rather
than a current microformat that people are simply asking about how to use,
please keep discussions about it on the microformats-new list.
Thanks,
Tantek
___
perhaps there was prior discussion and agreement that was just a long
time ago? Have you searched the archives or asked Tantek directly?
Andy Mabbett wrote:
The change made recently, to the hCard spec:
http://microformats.org/wiki?title=hcard-parsingdiff=nextoldid=25563
affects not only
Andy Mabbett wrote:
In message [EMAIL PROTECTED], Guillaume Lebleu
[EMAIL PROTECTED] writes
not least because the alternative:
foo class=fnPink Floyd/foo
would be optimised (sic) to have a given name of Pink and a family
name of Floyd.
I don't disagree that groups/bands should be
In message
[EMAIL PROTECTED], Brandon
Richards [EMAIL PROTECTED] writes
I've been thinking about how to create a standard structure to format a
post within a publishing system and I was looking for a microformat
That would be hAtom:
http://microformats.org/wiki/hatom
though you seem to
In message [EMAIL PROTECTED], Scott
Reynen [EMAIL PROTECTED] writes
On the topic of whether this should have had wider discussion, I
thought it was well established long ago that the properties of an
AGENT hCard are not inherited by the container hCard, so I don't see
anything really
In message [EMAIL PROTECTED], Manu Sporny
[EMAIL PROTECTED] writes
Thom Shannon wrote:
perhaps there was prior discussion and agreement that was just a long
time ago? Have you searched the archives or asked Tantek directly?
Here's the IRC log regarding the change to the wiki:
On Thu, February 7, 2008 15:46, Guillaume Lebleu wrote:
Sorry if I misinterpreted: I'm not a native english speaker.
Doesn't not least because [reason] means that [reason] is not the
least reason, i.e. a strong one?
Literally, yes, but in colloquial use it can mean not the weakest, but
far
On Feb 7, 2008, at 3:03 PM, Andy Mabbett wrote:
On the topic of whether this should have had wider discussion, I
thought it was well established long ago that the properties of an
AGENT hCard are not inherited by the container hCard, so I don't
see anything really changing here.
The
On 7/2/08 15:30, Andy Mabbett [EMAIL PROTECTED] wrote:
On Thu, February 7, 2008 14:33, Michael Smethurst wrote:
Not sure I follow. The hcard wiki page says nickname optimisation
happens when FN and ORG are not the same, and the value of the FN
property is exactly one word. What would:
In message [EMAIL PROTECTED], Scott
Reynen [EMAIL PROTECTED] writes
On Feb 7, 2008, at 3:03 PM, Andy Mabbett wrote:
On the topic of whether this should have had wider discussion, I
thought it was well established long ago that the properties of an
AGENT hCard are not inherited by the container
On Feb 7, 2008, at 1:47 PM, Brandon Richards wrote:
For portability sake, how do
the other pages of content get linked or associated without having to
actually include all of the content within one page?
rel=next and rel=prev [1] can be used to describe these kind of
relationships between
On Feb 7, 2008, at 5:11 PM, Andy Mabbett wrote:
added:
Similarly, parsers should treat nested [[hCalendar]],
[[hReview]], [[hResume]] [[xFolk]] in the same way, properties
inside them {{must}} only apply to the nested microformat, not
to the containing microformat.
This would be a lot more clearer if you showed an example on the web.
Regards, etc...
On Feb 7, 2008 3:47 PM, Brandon Richards [EMAIL PROTECTED] wrote:
Ok so hatom, but I suppose what I'm missing is the multiple pages of
content that belong to the same entry. For portability sake, how do
the
35 matches
Mail list logo
