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

"Paul E. Jones" <paulej@packetizer.com> Thu, 10 October 2013 23:41 UTC

Return-Path: <paulej@packetizer.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 9136F11E8193 for <webfinger@ietfa.amsl.com>; Thu, 10 Oct 2013 16:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.957
X-Spam-Level:
X-Spam-Status: No, score=-1.957 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6]
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 m0kMtVa1dDGX for <webfinger@ietfa.amsl.com>; Thu, 10 Oct 2013 16:41:03 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 45CB211E8162 for <webfinger@ietf.org>; Thu, 10 Oct 2013 16:41:02 -0700 (PDT)
Received: from [192.168.1.20] (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r9ANf0hV011934 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 10 Oct 2013 19:41:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1381448461; bh=XEcSGIlcbXDTu6LGcBaPFExhxGTqW2mTybwNK2EO9qw=; h=From:To:Subject:Cc:Date:Content-Type:In-Reply-To:Message-Id: Mime-Version:Reply-To; b=Bwzr/+2TsFQOrPYzM6NW8tjZpp1fEZw5U2kH07SqQTa942St35uhXN9loPqKMegTl heqh7bX96vK+GExW8lqlkN/qAhKZMlGCH1x+qjX6sq3Qn0TCNJAw1DuM6zGHJ66ri8 gz4A9QrhkAHO2r5R2hUWF7HwHasTqG7XC/E2ilP8=
From: "Paul E. Jones" <paulej@packetizer.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Date: Thu, 10 Oct 2013 23:41:13 +0000
Content-Type: multipart/alternative; boundary="------=_MB602F051C-ECA7-4A5D-955A-433ED7945EC7"
In-Reply-To: <CAKaEYhJEvfiPT-5zTjnVXSpyGxYnpOO5gB0wvjgcHB6u6Fq6RQ@mail.gmail.com>
Message-Id: <em19baa0e5-7a97-44ab-874e-b084b9645052@sydney>
Mime-Version: 1.0
User-Agent: eM_Client/5.0.18661.0
Cc: webfinger <webfinger@ietf.org>, Will Norris <will@willnorris.com>
Subject: Re: [webfinger] Registration of a URN for WebFinger Properties
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
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: Thu, 10 Oct 2013 23:41:07 -0000

Melvin,
>>There are also properties, and I've not seen any described formally 
>>anywhere.  I've defined a ones I find useful:
>>http://www.packetizer.com/webfinger/properties.html
>
>Regarding name, just from the top of my head (I didnt include PoCo, 
>OpenSocial, PIM, DOAP, but you could search for them)
>
>http://xmlns.com/foaf/spec/#term_name
>https://schema.org/name
>http://graph.facebook.com/schema/user#name
>http://www.w3.org/TR/vcard-rdf/#d4e1731
>
>Remember that link relations predate webfinger by over 5 years.  It's 
>often better to reuse than to reinvent.
I agree, though none of these are designed for use in WebFinger.  So, I 
created my own.  You can't point to something 5 years old and declare 
I'm reproducing it because there is some syntax scribbling that has the 
word "name" associated with it.

What I defined in the link above for "name", for example, is somewhere 
between foaf:name and the one related to vcard.  WebFinger has a 
registry for identifiers now.  It would be good to see that get 
populated with useful items, though I would not recommend putting 
everything one might possibly put into a vcard in there.  If a vcard is 
essential, the vcard link relation should be published in a WF JRD and a 
client query that.  However, there are basic things like "name" that are 
very useful, such as when you log into a web site and that site would 
like to display your avatar and name.  The avatar already has a defined 
LR value under webfinger.org.  The person's name does not have a defined 
property identifier anywhere, except the one I specified under 
packetizer.com.

Paul