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

Melvin Carvalho <melvincarvalho@gmail.com> Wed, 14 March 2012 10:08 UTC

Return-Path: <melvincarvalho@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC6D921F8742 for <apps-discuss@ietfa.amsl.com>; Wed, 14 Mar 2012 03:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level:
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ll9vaQLYsxyl for <apps-discuss@ietfa.amsl.com>; Wed, 14 Mar 2012 03:08:04 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 88E3321F871B for <apps-discuss@ietf.org>; Wed, 14 Mar 2012 03:08:04 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so2106619vcb.31 for <apps-discuss@ietf.org>; Wed, 14 Mar 2012 03:08:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0GO4p50/wgIYn0wuNTCsFM13EaRyVr2D7dY3az+8E8E=; b=bDzKuJvXGt4zl/+gx5M/RMnGE8iB623tEZiNQeIcF1eGiVvEy2UWs3S/mqUGsttvAq UtbC8vmAiFCqsMa/KdXQHN8DEBcMV/o8O/czGLY01sCugSJexqynB8K3CDcUXkzUJFLV 1avXUZC/bMaEAwBsu90vRYTBF9RrhbzgaGFJOxmjRohY49rZfZ+ORHUGxvnn8OpSV1MM +VXvwKvu7h0amBur3IRv4BqLAkstXG4FmYUY0MTqmuFjGexf5mmlSMupyorw7n8pRbD/ zYsSqiR9rOGxa+tWVWL7aJEm21Ez9/Szia5jxX6ScvFC0GIuv013Pa8xfZ3Ua6WSd5mq 3HDg==
MIME-Version: 1.0
Received: by 10.52.94.146 with SMTP id dc18mr1411417vdb.19.1331719683715; Wed, 14 Mar 2012 03:08:03 -0700 (PDT)
Received: by 10.52.174.70 with HTTP; Wed, 14 Mar 2012 03:08:03 -0700 (PDT)
In-Reply-To: <05d001cd01a7$3cbb0c70$b6312550$@packetizer.com>
References: <05d001cd01a7$3cbb0c70$b6312550$@packetizer.com>
Date: Wed, 14 Mar 2012 11:08:03 +0100
Message-ID: <CAKaEYhK3m2w4zxenDCKaob5uZdnvKZ_VkhU32GLb-5yMH6x-zQ@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: webfinger@googlegroups.com
Content-Type: multipart/alternative; boundary="bcaec501646fb031d704bb3126c9"
X-Mailman-Approved-At: Wed, 14 Mar 2012 08:04:45 -0700
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Webfinger: acct "link relation"
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 10:08:05 -0000

On 14 March 2012 06:56, Paul E. Jones <paulej@packetizer.com> 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****
>
> ** **
>
> ** **
>
> ** **
>