On Feb 7, 2007, at 2:56 PM, David Janes wrote:
On 2/7/07, Ryan King [EMAIL PROTECTED] wrote:
On Feb 7, 2007, at 12:50 PM, David Janes wrote:
On 2/7/07, Ryan King [EMAIL PROTECTED] wrote:
Yes there are several problems:
1. XFN applies to whole pages. This means that you can't
reliably put
On 2/8/07, Ryan King [EMAIL PROTECTED] wrote:
Nothing special is needed at /blog/contact/.
-ryan
But that's the authoritative hCard. What's the algorithm (or
heuristic) that I follow if I'm a parser looking at the blog at
microformats.org, see your partial hCard and try to find your
On 2/8/07, Ben Ward [EMAIL PROTECTED] wrote:
On 8 Feb 2007, at 19:02, David Janes wrote:
On 2/8/07, Ryan King [EMAIL PROTECTED] wrote:
Nothing special is needed at /blog/contact/.
-ryan
But that's the authoritative hCard. […]
Sorry if this sounds pedantic, I'm not trying to be.
On Feb 8, 2007, at 11:02 AM, David Janes wrote:
On 2/8/07, Ryan King [EMAIL PROTECTED] wrote:
Nothing special is needed at /blog/contact/.
But that's the authoritative hCard. What's the algorithm (or
heuristic) that I follow if I'm a parser looking at the blog at
microformats.org, see your
On Feb 8, 2007, at 12:00 PM, David Janes wrote:
On 2/8/07, Ben Ward [EMAIL PROTECTED] wrote:
On 8 Feb 2007, at 19:02, David Janes wrote:
On 2/8/07, Ryan King [EMAIL PROTECTED] wrote:
Nothing special is needed at /blog/contact/.
-ryan
But that's the authoritative hCard. […]
Sorry if
Sorry, I'm way behind on this thread. I wish I weren't but there's
nothing I can do about that now...
On Jan 29, 2007, at 5:50 PM, John Allsopp wrote:
Ben,
For my money, John Allsopp's idea to reuse rel=bookmark self [1]
makes most sense. As well as being gorgeously consistent with
On Jan 30, 2007, at 2:28 PM, John Allsopp wrote:
Chris,
(all the following simply thoughts in the spirit of brainstorming,
rather than any particular argument in favour of my original
suggestion)
I pretty much came up with a very similar proposal for handling this
issue, though from the
On Jan 30, 2007, at 4:06 PM, Ben Ward wrote:
Chris Messina:
div class=vcard id=vcard
addressa href=http://factoryjoe.com/blog/hcard/#hcard;
class=fn
url rel=me selfChris Messina/a/address
div class=orgCitizen Agency/a
...
/div
John Allsopp:
The definition of the self attribute value
On 2/7/07, Ryan King [EMAIL PROTECTED] wrote:
Yes there are several problems:
1. XFN applies to whole pages. This means that you can't reliably put
different people's hCards on the same page and do this.
2. We have prior art that is being ignored. Publishers are already
using a class=url uid
On Feb 7, 2007, at 12:50 PM, David Janes wrote:
On 2/7/07, Ryan King [EMAIL PROTECTED] wrote:
Yes there are several problems:
1. XFN applies to whole pages. This means that you can't reliably put
different people's hCards on the same page and do this.
2. We have prior art that is being
On 2/7/07, Ryan King [EMAIL PROTECTED] wrote:
On Feb 7, 2007, at 12:50 PM, David Janes wrote:
On 2/7/07, Ryan King [EMAIL PROTECTED] wrote:
Yes there are several problems:
1. XFN applies to whole pages. This means that you can't reliably put
different people's hCards on the same page and
In message [EMAIL PROTECTED], John
Allsopp [EMAIL PROTECTED] writes
When rel-license is inside an hReview, it is taken to be associated
with the review, rather than the larger fragment it would otherwise
be associated with (e.g. post or page)
I wonder whether that makes sense more generally -
On 31/01/07, Ben Ward [EMAIL PROTECTED] wrote:
Chris Messina:
div class=vcard id=vcard
addressa href=http://factoryjoe.com/blog/hcard/#hcard; class=fn
url rel=me selfChris Messina/a/address
div class=orgCitizen Agency/a
...
/div
John Allsopp:
The definition of the self attribute
On Jan 31, 2007, at 3:46 AM, Frances Berriman wrote:
On 31/01/07, Ben Ward [EMAIL PROTECTED] wrote:
Chris Messina:
div class=vcard id=vcard
addressa href=http://factoryjoe.com/blog/hcard/#hcard;
class=fn
url rel=me selfChris Messina/a/address
div class=orgCitizen Agency/a
...
/div
On 31 Jan 2007, at 12:08, Colin Barrett wrote:
Can I get a clearer idea of what exactly is people are +1-ing? I +1
@rel=self me, but am not willing to give my vote yet on using
address, as it's not entirely clear if we're talking about
mandating it, recommending it, etc. FWIW I'm not
On Jan 31, 2007, at 4:34 AM, Ben Ward wrote:
On 31 Jan 2007, at 12:08, Colin Barrett wrote:
Can I get a clearer idea of what exactly is people are +1-ing? I +1
@rel=self me, but am not willing to give my vote yet on using
address, as it's not entirely clear if we're talking about
+1
On 1/31/07, Colin Barrett [EMAIL PROTECTED] wrote:
On Jan 31, 2007, at 4:34 AM, Ben Ward wrote:
On 31 Jan 2007, at 12:08, Colin Barrett wrote:
Can I get a clearer idea of what exactly is people are +1-ing? I +1
@rel=self me, but am not willing to give my vote yet on using
address, as
On 1/31/07, Ben Ward [EMAIL PROTECTED] wrote:
We are voting only on the use of @rel=me self to reference an
authoritative hCard that parsers should follow.
e.g.
div class=vcard
a class=fn url href=http://ben-ward.co.uk/about; rel=me
selfBen Ward/a
/div
Just to be 100% pedantically clear:
On Jan 31, 2007, at 9:49 AM, Ara Pehlivanian wrote:
Just to stir the pot a little, and maybe it's a good idea to consider
authenticity in the whole discussion of authoritative cards. What
guarantees that when someone creates an hCard and puts rel=me self
that they are giving the correct URL and
On 1/31/07, Ryan Cannon [EMAIL PROTECTED] wrote:
I'm getting into this late, but isn't the entire concept behind
rel=me?
rel=me links *must* be symmetric in order to create a distributed
verification system?. It's definition is A link to yourself at a
different URL[1]. According to the spec,
On 31 Jan 2007, at 16:15, Ryan Cannon wrote:
It's definition is A link to yourself at a
different URL[1].
Correct. Which is still valid in the rel=me self case.
According to the spec, rel=self me is invalid *unless*
you do not include the XFN profile on your Web site.
Sorry, I've got
On 1/31/07, Ben Ward [EMAIL PROTECTED] wrote:
On 31 Jan 2007, at 16:15, Ryan Cannon wrote:
It's definition is A link to yourself at a
different URL[1].
Correct. Which is still valid in the rel=me self case.
According to the spec, rel=self me is invalid *unless*
you do not include the XFN
On 31 Jan 2007, at 17:24, Ara Pehlivanian wrote:
Ben,
Don't you think he has a point though? If you think of it, rel=me
could suffice in that it refers to yourself at another URL (in line
with the idea of an authoritative hCard) and once you get there and
read that hCard and discover that it
I'm trying to catch up, but I'm finding it a bit difficult. The
problem with rel=me is that it's merely an alternative version, and
not authoritative or canonical, right? Why is rel=me self desirable
though? Were there any other alternatives considered?
Thanks,
Ben West
On 1/31/07, David
On 1/31/07, Ben Ward [EMAIL PROTECTED] wrote:
The authoratitive hcard will also contain @rel=me. Firstly, to
fulfil XFN it must link back to the linking resource and as a full
hCard it will still contain URLs with @rel=me pointing to the other
sites I own.
Hang on, linking /back/ to the
On Jan 31, 2007, at 12:15 PM, Ben Ward wrote:
According to the spec, rel=self me is invalid *unless*
you do not include the XFN profile on your Web site.
Sorry, I've got muddled here. According to which spec? Are you
referring to the “Exclusive of all other XFN values” part of the
@rel=me spec
On Jan 31, 2007, at 9:47 AM, Ben Ward wrote:
My understanding therefore, is that @rel=me indicates that it is the
same person. @rel=self indicates that it is the same hcard.
Therefore the absolute authoritative hcard we speak of may (I expect
will) contain other links with @rel=me but will
Just chiming in my two pence here:
Rather than something like @rel=me self, would a better idea not be
to look at including some kind of way of authenticating the source
such as a MicroID hash?
This has already been discussed on the MicroId list along the lines of this:
@rel=me
There is quite a lot of interest in this topic. With all the voices,
it's becoming quite difficult to keep track of what we're talking
about, and who thinks what.
I've added this issue to the hcard-issues page.
http://microformats.org/wiki/hcard-issues#Canonical.2FAuthoritative_Hcard
I would
Well, I certainly am coming to the party late.
I actually started a post on this topic over a week ago -- and
absentmindedly hadn't checked on this list first before posting and
therefore published without the benefit of this discussion (I can hear
Tantek chiding me) but nonetheless, as the
Chris,
(all the following simply thoughts in the spirit of brainstorming,
rather than any particular argument in favour of my original suggestion)
I pretty much came up with a very similar proposal for handling this
issue, though from the standpoint of XFN-links, and I think that
John's
Chris Messina:
div class=vcard id=vcard
addressa href=http://factoryjoe.com/blog/hcard/#hcard; class=fn
url rel=me selfChris Messina/a/address
div class=orgCitizen Agency/a
...
/div
John Allsopp:
The definition of the self attribute value in Atom is self: the
feed itself. The term the
+1 from me.
On 1/30/07, Ben Ward [EMAIL PROTECTED] wrote:
Chris Messina:
div class=vcard id=vcard
addressa href=http://factoryjoe.com/blog/hcard/#hcard; class=fn
url rel=me selfChris Messina/a/address
div class=orgCitizen Agency/a
...
/div
John Allsopp:
The definition of the self
On 24 Jan 2007, at 14:51, Ara Pehlivanian wrote:
Just a shot in the dark here, but couldn't the a class=url ... be
assumed to be pointing to the hCard owner's site where it could be
further assumed that the authoritative hCard would reside? What's
more, if the href in the a class=url...
Ben,
For my money, John Allsopp's idea to reuse rel=bookmark self [1]
makes most sense. As well as being gorgeously consistent with other
existing microformats, it's also a completely graceful addition to
existing hCards.
thanks ;-)
There's a lot of goodness to reuse from other ufs, for
On Jan 23, 2007, at 8:46 PM, Joe Andrieu wrote:
Tantek Ç elik wrote
None of those examples given are actually canonical
sources, they're merely citations and quotations of sources
(for which we have existing HTML semantics for: cite q
cite blockquote cite. The semantic of canonicality is not
My concern about this is that many publishers (myself included) try
to avoid linking a page to itself due to usability concerns, e.g. I
just clicked on that link and didn't go anywhere. This site is broken.
Just a shot in the dark here, but couldn't the a class=url ... be
assumed to be
In message [EMAIL PROTECTED], Joe Andrieu
[EMAIL PROTECTED] writes
A few two major things happen when you do this:
1. You enable an hCard author to semantically declare this hCard as
definitive
2. You could provide a link from a refering hCard to the authoritative
hCard for discovery of
38 matches
Mail list logo
