What I interpreted from Chris' words was that contact and me was the
only values _needed_ to achieve contact list portability. Not that the
rest should be dropped altogether.
I learned that from now on, I should always include the value contact,
on top of all other values. XFN exists for more
Hi Folks,
Below is a proposal. The proposal is based on the following assertion.
ASSERTION
An expression of a relationship is useful only if you know who is the
source and who is the target of the relationship.
EXAMPLE
??? is friends with ??? is not useful.
But Alice is friends with
On 19 Mar 2008, at 12:36, Costello, Roger L. wrote:
Hi Folks,
Below is a proposal. The proposal is based on the following
assertion.
ASSERTION
An expression of a relationship is useful only if you know who is the
source and who is the target of the relationship.
I agree there are
1. If XFN is used on a web page then that web page MUST contain an
hCard of the person that represents the source of the relationship.
MUST is pretty abhorrent to me. I use rel=me on my blog, which
is also my OpenID URI, which is a very strong way of my attaching
my OpenID to my flickr,
Thanks Dan. Excellent points.
Okay, then let's revise it from Mandatory to Best Practice.
The Best Practice may be simply stated as such:
If you use XFN in your web page then it is Best Practice
to incorporate an hCard in the web page which identifies the
source of the
On Mar 19, 2008, at 6:36 AM, Costello, Roger L. wrote:
1. If XFN is used on a web page then that web page MUST contain an
hCard of the person that represents the source of the relationship.
2. There MUST be a mechanism that connects the XFN to the hCard that
represents the source individual.
Thanks Paul. Excellent comments.
I too am a big fan of separation of concerns. However, if there is
no way for a robot application to determine in some automated way who
is friends with xxx then the separation of concerns buys me nothing.
a URI is a great way to identify someone:
André Luís wrote:
What I interpreted from Chris' words was that contact and me was the
only values _needed_ to achieve contact list portability. Not that the
rest should be dropped altogether.
There isn't really any other way to interpret what he wrote:
If you use Google’s new Social
Hi Roger!
I too am a big fan of separation of concerns. However, if there is
no way for a robot application to determine in some automated way who
is friends with xxx then the separation of concerns buys me nothing.
So it might be nice if Flickr pointed to profile pages,
which publish
Costello, Roger L. wrote:
But Alice is friends with Bob is useful.
^ ^ ^
| | |
source relationship target
I think that maybe Alice and Bob are plotting something. They keep sending
all these encrypted e-mails to each other. Eve and I will
Hi Folks,
My mind has really latched on to the term that Scott Reynen used in his
last message:
XFNetwork
Nice!
In a nutshell, what's needed is a way to connect the XFNetwork to an
Identity Network.
/Roger
___
microformats-discuss mailing
The address element is a valid and semantic way of claiming
ownership/authorship of a document, I use it on my blog, and my accounts
link to my blog claiming it's me.
A url is a valid and important piece of someones identity, it's not ???
is friends with ??? it's http://x is friends with
Just as an example of where URLs are more than enough, here's a way you
could use Googles Social Graph API.
Bob signs up to new fangled social n etwork, he's prompted for a profile
address to find if any of his friends are already on here.
NewFangled asks Google for his relationships, G
On Mar 19, 2008, at 10:02 AM, Costello, Roger L. wrote:
1. All people in an XFNetwork MUST be identified via
hCard somewhere within the network.
How about allowing the parties involved in an XFN-relationship be
identified by either hCard or a FOAF document or an OpenID? (I must
confess
I'm in the process of adding 'rel=license' in the relevant places on
blip.tv, a video-sharing site, and I've run squarely into the 'open issue'
raised by Evan on 2006-04-07 (in the wiki). Namely, there's no obvious way
to specify that the license applies to a content element on a page - a
picture,
Angus McIntyre wrote:
I seem to remember one of the microformats has a poorly-understood
algorithm for determining the scope of a declaration; could this be
reapplied here?
The problem lies deeper than rel-license. The rel attribute in (X)
HTML is able to specify a specific element within a
Then how do you specify the license for different elements of the page?
Perhaps making your video embeds an iframe that contains the
embed/object and its own rel-license would be the best set of hoops to
jump through.
This is where RDFa starts to shine. I don't think there's a good way
in
Hey Angus,
On Wed, Mar 19, 2008 at 8:32 PM, Angus McIntyre [EMAIL PROTECTED] wrote:
I'm in the process of adding 'rel=license' in the relevant places on
blip.tv, a video-sharing site, and I've run squarely into the 'open issue'
raised by Evan on 2006-04-07 (in the wiki). Namely, there's no
On Mar 18, 2008, at 9:18 AM, Costello, Roger L. wrote:
Chris Messina wrote[1]: ... you'll find that, by and large, the
majority of XFN links on the web are using either rel-contact or
rel-me.
I have been looking at various social networks for the last week, and
Chris' statement is consistent
This is not a big problem, its mostly solved with [1]
-ryan
1. http://microformats.org/wiki/representative-hcard
On Mar 18, 2008, at 5:31 AM, Costello, Roger L. wrote:
Hi Folks,
Flickr uses XFN. Here is a sample Flickr page that uses XFN:
http://www.flickr.com/people/tantek/
At the
Thom Shannon wrote:
It turns out no one else is on NewFangled yet, but NewFangled stores
the URLs that Bob lays a claim to, his flickr and twitter pages
(stored as a hash!).
What's the collision rate when hypothetical implementations are
unnecessarily hashed? ~D
Wow. A spec just like Aphrodite, born fully an adult.
On Wed, Mar 19, 2008 at 8:11 PM, Ryan King [EMAIL PROTECTED] wrote:
This is not a big problem, its mostly solved with [1]
-ryan
1. http://microformats.org/wiki/representative-hcard
On Mar 18, 2008, at 5:31 AM, Costello, Roger L.
Is the problem that the page contains multiple video elements? If so
using hAtom to define them as separate entries may help clarify this,
especially in conjunction with rel-enclosure.
On Wed, Mar 19, 2008 at 4:40 PM, Charles Iliya Krempeaux
[EMAIL PROTECTED] wrote:
Hey Angus,
On Wed, Mar
Hello list,
Is anybody aware of implementation or research on the topic of microformat
usage for automation of user input? It is obvious that attaching microformat to
said HTML form fields makes it possible for automation software to provide
known values for them, without user interaction.
David,
Wow. A spec just like Aphrodite, born fully an adult.
p class=pedantryI think you mean the goddess Athena ;-)/p
john
John Allsopp
style master :: css editor :: http://westciv.com/style_master
about me :: http://johnfallsopp.com
Web Directions Conferences :: http://webdirections.org
Hi Victor,
Is anybody aware of implementation or research on the topic of
microformat usage for automation of user input? It is obvious that
attaching microformat to said HTML form fields makes it possible for
automation software to provide known values for them, without user
On Wed, Mar 19, 2008 at 11:28 PM, John Allsopp [EMAIL PROTECTED] wrote:
Wow. A spec just like Aphrodite, born fully an adult.
p class=pedantryI think you mean the goddess Athena ;-)/p
gonna have to take that westciv domain away if you're not
careful :-) :-)
27 matches
Mail list logo
