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

Kingsley Idehen <kidehen@openlinksw.com> Fri, 21 December 2012 22:22 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 2C40921F85AB for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 14:22:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.348
X-Spam-Level:
X-Spam-Status: No, score=-1.348 tagged_above=-999 required=5 tests=[AWL=1.250, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 GXdig7rGv5wj for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 14:22:46 -0800 (PST)
Received: from mail.openlinksw.com (mail.openlinksw.com [63.119.36.38]) by ietfa.amsl.com (Postfix) with ESMTP id 0C74C21F859D for <webfinger@ietf.org>; Fri, 21 Dec 2012 14:22:45 -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:CC:To:MIME-Version:From:Date:Message-ID; bh=NvmWu6pKsIaSljAu02BddQK8ofcAVFmehDfCdLr38Cg=; b=bs++e+50gf1xd9FetXuybV1UTo+rILiYSA5NWZpoWpCUP23Wuv+iy3Lre/DEhLYIRfyHacCQE5/RcqZEyQ/c48sLFdkKZmw+h4fnJu2ILHDJCKhFgDT7qFh5XbRxAEC3;
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 1TmAzM-00037c-61; Fri, 21 Dec 2012 17:22:44 -0500
Message-ID: <50D4E132.6070407@openlinksw.com>
Date: Fri, 21 Dec 2012 17:22:42 -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: Tim Bray <tbray@textuality.com>
References: <20121221172032.28253.90788.idtracker@ietfa.amsl.com> <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com> <50D4CFEF.9030701@openlinksw.com> <CAHBU6isW1tZ4Jjmw+MFjhcuRMpwx8UsiK5QRWk_wf2cVDy1PsA@mail.gmail.com>
In-Reply-To: <CAHBU6isW1tZ4Jjmw+MFjhcuRMpwx8UsiK5QRWk_wf2cVDy1PsA@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms080900070603050508080702"
Cc: "Paul E. Jones" <paulej@packetizer.com>, webfinger@googlegroups.com, webfinger@ietf.org
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:22:48 -0000

On 12/21/12 4:38 PM, Tim Bray wrote:
> No. The I in URI stands for Identifier. URIs identify resources, 
> that's what they're for. -T

I know the "I" stands for "Identifier" but these "Identifiers" are being 
used to "denote" entities (things), in this context.

This subtle tweak has also been adopted in the Semantic Web discourse 
realm (note latest RDF specs [1]) as a mechanism for adding clarity to 
the function or URIs.

Links:

1. http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-concepts/index.html -- 
see how denotation with regards to the function of URIs .

Kingsley
>
> On Fri, Dec 21, 2012 at 1:09 PM, Kingsley Idehen 
> <kidehen@openlinksw.com <mailto:kidehen@openlinksw.com>> wrote:
>
>
>     Could this:
>
>      WebFinger is used to discover information about people or other
>        entities on the Internet that are identified by a URI [6] or
>     IRI [7]
>        using standard Hypertext Transfer Protocol (HTTP) [2] methods
>     over a
>        secure transport [14].
>
>     become:
>
>      WebFinger is used to discover information about people or other
>        entities on the Internet that are *denoted* by a URI [6] or IRI
>     [7]. Actual information retrieval uses
>        standard Hypertext Transfer Protocol (HTTP) [2] methods over a
>        secure transport [14].
>
>     -- 
>
>     Regards,
>
>     Kingsley Idehen
>     Founder & CEO
>     OpenLink Software
>     Company Web: http://www.openlinksw.com
>     Personal Weblog: http://www.openlinksw.com/blog/~kidehen
>     <http://www.openlinksw.com/blog/%7Ekidehen>
>     Twitter/Identi.ca handle: @kidehen
>     Google+ Profile: https://plus.google.com/112399767740508618350/about
>     LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>
>
>
>     _______________________________________________
>     webfinger mailing list
>     webfinger@ietf.org <mailto:webfinger@ietf.org>
>     https://www.ietf.org/mailman/listinfo/webfinger
>
>
>
>
> _______________________________________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger


-- 

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