Re: [apps-discuss] Webfinger: acct "link relation"

["Paul E. Jones" <[e-mail]>]

Melvin,

 

I, too, like the idea of introducing "seealo" that would have wider
applicability.  For example, consider this page:

http://www.techabulary.com/h/h323/

 

The bottom of this page refers the reader to several other resources for
additional information.  I think having "seealso" generally available as a
web link relation would allow a web site to suggest related reading material
and the browser could offer up that list via a consistent user interface for
the user.

 

Now, should we document "seealso" in the Webfinger draft or should that be
in its own draft?

 

Paul

 

From: [e-mail] [mailto:[e-mail]] On
Behalf Of Melvin Carvalho
Sent: Wednesday, March 14, 2012 6:08 AM
To: [e-mail]
Cc: [e-mail]
Subject: Re: Webfinger: acct "link relation"

 

 

On 14 March 2012 06:56, Paul E. Jones <[e-mail]> wrote:

Folks,

 

In the latest Webfinger draft, we introduced a "acct" link relation named
"acct" (see Section 6).  The intent with that link relation was to allow for
one to inform a webfinger client that a user's account information may be
retrieved elsewhere.  I believe this will be important, since a user might
have more than one account and this might serve as a means of associating
them.  Certainly, it would be a way of retrieving information from those
other accounts automatically.

 

Perhaps calling the new link relation "acct" is too restrictive, though.  If
one used Webfinger to query other kinds of information other than a user's
account, there may still be a need/desire to refer the Webfinger client to
other resources.

 

What do you think about changing this section such that the link relation is
renamed to "seealso"?  This would still be useful when querying an acct URI,
but would also be useful when querying any URI since it  is more generic.

 

Do note that "seealso" would be different than the "alternate" link
relation.  It would not refer to alternative information, but would refer to
supplemental information.  In practice, the supplemental information may be
the more informative since the bulk of the information related to a user
might be held under a different account.


seeAlso already exists as an "extended relation type"

http://www.w3.org/TR/2000/CR-rdf-schema-20000327/#s2.3.4

Seems like a good choice.  In fact, timbl uses it in his profile:

$ rapper -g http://www.w3.org/People/Berners-Lee/card | grep seeAlso

<http://www.w3.org/People/Berners-Lee/card#i> 
    <http://www.w3.org/2000/01/rdf-schema#seeAlso>
<http://dig.csail.mit.edu/2008/webdav/timbl/foaf.rdf> .
 
sameas is also similar

<http://www.w3.org/People/Berners-Lee/card#i> 
    <http://www.w3.org/2002/07/owl#sameAs> <http://identi.ca/user/45563> .

 

 

Your thoughts?

 

Paul