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

Goix Laurent Walter <laurentwalter.goix@telecomitalia.it> Wed, 14 March 2012 11:19 UTC

Return-Path: <laurentwalter.goix@telecomitalia.it>
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 3ECF421F86EB for <apps-discuss@ietfa.amsl.com>; Wed, 14 Mar 2012 04:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.039
X-Spam-Level:
X-Spam-Status: No, score=-0.039 tagged_above=-999 required=5 tests=[AWL=-1.180, BAYES_20=-0.74, EXTRA_MPART_TYPE=1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 kyAH+ehpQbph for <apps-discuss@ietfa.amsl.com>; Wed, 14 Mar 2012 04:19:26 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 2D2D321F8636 for <apps-discuss@ietf.org>; Wed, 14 Mar 2012 04:19:26 -0700 (PDT)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 14 Mar 2012 12:19:13 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Wed, 14 Mar 2012 12:19:12 +0100
From: Goix Laurent Walter <laurentwalter.goix@telecomitalia.it>
To: "Paul E. Jones" <paulej@packetizer.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "webfinger@googlegroups.com" <webfinger@googlegroups.com>
Date: Wed, 14 Mar 2012 12:19:11 +0100
Thread-Topic: [apps-discuss] Webfinger: acct "link relation"
Thread-Index: Ac0BpQFPzAZiU0kpTmqy3YhO+8RyEwALlNNg
Message-ID: <A09A9E0A4B9C654E8672D1DC003633AE52EDA3023D@GRFMBX704BA020.griffon.local>
References: <05d001cd01a7$3cbb0c70$b6312550$@packetizer.com>
In-Reply-To: <05d001cd01a7$3cbb0c70$b6312550$@packetizer.com>
Accept-Language: en-US
Content-Language: it-IT
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
Content-Type: multipart/related; boundary="_004_A09A9E0A4B9C654E8672D1DC003633AE52EDA3023DGRFMBX704BA02_"; type="multipart/alternative"
MIME-Version: 1.0
Subject: [apps-discuss] R: 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 11:19:29 -0000

Well, generalizing could be a more flexible approach. Especially if uri schemes evolve over time to identify users (could be http, tel, etc). I guess the semantics here is o refer to yet another identity of that individual.

"seealso" may fit, although it is quite vague semantically and do not specifically ensure that the specific resource is actually the same individual but another account.

The "related" relation link (defined in atom [1] ) may also fit and has more or less the same meaning whilst being already formally assigned.
In alternative one could borrow from xfn concepts [2] and use "me" to clearly state that this resource is another pointer to "myself"...

Just my 2 cents to stimulate the discussion here
walter

[1] http://tools.ietf.org/html/rfc4287#section-4.2.7.2
[2] http://gmpg.org/xfn/11
Da: apps-discuss-bounces@ietf.org [mailto:apps-discuss-bounces@ietf.org] Per conto di Paul E. Jones
Inviato: mercoledì 14 marzo 2012 6.57
A: apps-discuss@ietf.org; webfinger@googlegroups.com
Oggetto: [apps-discuss] Webfinger: acct "link relation"

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.

Your thoughts?

Paul



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks.

[cid:00000000000000000000000000000003@TI.Disclaimer]Rispetta l'ambiente. Non stampare questa mail se non è necessario.