Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt

Kingsley Idehen <kidehen@openlinksw.com> Fri, 21 December 2012 22:30 UTC

Return-Path: <kidehen@openlinksw.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC3821F84F5 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 14:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.488
X-Spam-Level:
X-Spam-Status: No, score=-1.488 tagged_above=-999 required=5 tests=[AWL=1.111, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiEv28LEVhtC for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 14:30:38 -0800 (PST)
Received: from mail.openlinksw.com (mail.openlinksw.com [63.119.36.38]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD7C21F84E2 for <webfinger@ietf.org>; Fri, 21 Dec 2012 14:30:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=openlinksw.com; s=x; h=Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=g2zfTscK/J96wMF4ogaCPH+xITsjrDIF/C/UlutjJzY=; b=dj8v2md/Be6sS1fdT46M0INVqYKIrtGEe/WGwSUMvlCZC5YdJCkiQegxLqdH6wmjV8+O6g338nCG5Sw/3wVVnes9ZgCzbNno/z4dw4VTSdXvZkir/GqAbjixdInXaHfl;
Received: from kidehen.vpn ([10.100.2.3] helo=Macintosh-96.local) by mail.openlinksw.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.74) (envelope-from <kidehen@openlinksw.com>) id 1TmB6z-0003kW-Pc for webfinger@ietf.org; Fri, 21 Dec 2012 17:30:38 -0500
Message-ID: <50D4E30C.8050003@openlinksw.com>
Date: Fri, 21 Dec 2012 17:30:36 -0500
From: Kingsley Idehen <kidehen@openlinksw.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: webfinger@ietf.org
References: <20121221172032.28253.90788.idtracker@ietfa.amsl.com> <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com> <50D4CFEF.9030701@openlinksw.com> <CAHBU6isW1tZ4Jjmw+MFjhcuRMpwx8UsiK5QRWk_wf2cVDy1PsA@mail.gmail.com> <F36F9C20-2A5E-4EE0-89DD-AFC61A431832@ve7jtb.com>
In-Reply-To: <F36F9C20-2A5E-4EE0-89DD-AFC61A431832@ve7jtb.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms020001090309010907080502"
Subject: Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 22:30:39 -0000

On 12/21/12 5:06 PM, John Bradley wrote:
> Tim is correct.
>
> The URI or IRI is an identifier for a resource.
>
> Where it gets slightly grey is with the acct: scheme.  However I think 
> that the scheme is still identifying an account as the resource, even 
> if there is no default derefrencing.
>
> I think I understand Kingsley wanting to make the transitive link form 
> a identifier for a resource to having that resource denote a abstract 
> object.
>
> However I think that is best left to philosophers and the W3C.
>
> I think the current text is fine.

acct: and http: scheme URIs are both being used to denote something (an 
entity in a discourse realm). These identifiers are also associated with 
resources that bear information about their referents. Using "denote" 
helps clarify what's going on.

You have a Name that resolves to Data. Thereby have two identifiers that 
resolve to the same Data. One route by Name and the other by Location 
(Address). Thus, a URI can dually identify a real world entity while 
also doing the same for a resource that bears data describing said entity.

My suggestion is motivated by a desire to reuse breakthroughs that have 
solved similar problems elsewhere.

Links:

1. http://bit.ly/UXZEYV -- a live demonstration of Web-Scale verifiable 
identity and protected resource access controls (puts these matters into 
practical context)

-- 

Regards,

Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web: http://www.openlinksw.com
Personal Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca handle: @kidehen
Google+ Profile: https://plus.google.com/112399767740508618350/about
LinkedIn Profile: http://www.linkedin.com/in/kidehen