Re: [webfinger] Registration of a URN for WebFinger Properties

Kingsley Idehen <> Fri, 11 October 2013 20:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A50DE21E80AA for <>; Fri, 11 Oct 2013 13:02:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id dAirB7NJfikp for <>; Fri, 11 Oct 2013 13:02:20 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9B18D21F9ACA for <>; Fri, 11 Oct 2013 13:02:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=x; h=Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=+MST+xtgzuKvrkjLRsAna/M6ByWQpz5McfW/H6Og/+Q=; b=qYa0vLDyRPauH4mBuu+KWXopvgKSkRNIL3EiR++97/X1tn06mUJeKpNrpELy8wgYqdhMq9XAVUK65fgewX1CA92H76ZbMkKelytCvYmnC+ak6THmOGGNq/NvwDA7M4cd;
Received: from dyn226.usnet.private ([]) by with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.74) (envelope-from <>) id 1VUiuc-0002ti-A7 for; Fri, 11 Oct 2013 16:02:14 -0400
Message-ID: <>
Date: Fri, 11 Oct 2013 16:02:14 -0400
From: Kingsley Idehen <>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
References: <> <em19baa0e5-7a97-44ab-874e-b084b9645052@sydney> <> <>
In-Reply-To: <>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms020509050106050502020907"
Subject: Re: [webfinger] Registration of a URN for WebFinger Properties
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 11 Oct 2013 20:02:23 -0000

On 10/11/13 1:07 PM, Paul E. Jones wrote:
> FOAF does not define a set of URI.  Rather, it's XML-based markup.  
> WebFinger uses URIs as identifiers.  I don't really care where those 
> identifiers are defined, but at present there is no standard property 
> identifer in URI form that means "name".

FOAF [1] isn't XML-based markup. It is an RDF model oriented vocabulary 
that's accessible in a variety of formats. Basically, FOAF provides 
modelling for entities and entity relationships in domains such as 
social networks.

URIs are Names.

An HTTP URI can also be used to Name (or Denote) anything, and that 
includes Relations.

An HTTP URL is a type of HTTP URI that Names (or Denotes) a Web Document.

A WebID is a type of HTTP URI that Names (or Denotes) an entity of type 
Agent (Person, Organization, Software, Machine etc..) .

Webfinger enables the use of acct: scheme URIs to Name (or Denote) 
entities of type Person (and possibly other Agent types).

Name->Address Indirection:

When I look-up an HTTP URL that denotes a Document or WebID that denotes 
an Agent my request resolves to data that describes the URI's referent.

The Webfinger protocol enables me  look-up an acct: scheme URI such that 
it resolves to data that describes the URI's referent.

Data Formats:

When I look-up an HTTP URL I more than likely get an HTML representation 
of data.
When I look-up a WebID I will get RDF model based Linked Data in formats 
such as Turtle, JSON-LD, RDFa, RDF/XML etc..
When I lookup an acct: scheme URI (via Webfinger protocol) I will get 
EAV model structured data in JRD or XRD format.

Ultimately, I think its time we all coalesce around the same thing 
(webby structured data), since the host OS (World Wide Web) already has 
all the thorny issues addressed in its core architecture :-)


2. -- HTTP URIs as Names for anything has been 
part of the Web's architecture since inception .



Kingsley Idehen	
Founder & CEO
OpenLink Software
Company Web:
Personal Weblog:
Twitter/ handle: @kidehen
Google+ Profile:
LinkedIn Profile: