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

"Paul E. Jones" <> Fri, 11 October 2013 17:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0984A21E81B9 for <>; Fri, 11 Oct 2013 10:07:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.963
X-Spam-Status: No, score=-1.963 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id puiks4C971n6 for <>; Fri, 11 Oct 2013 10:07:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 97D9121E8137 for <>; Fri, 11 Oct 2013 10:07:04 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) by (8.14.5/8.14.5) with ESMTP id r9BH6x9h021063 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 11 Oct 2013 13:06:59 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=dublin; t=1381511220; bh=JXfYuLleGtSr8t7HVMWRDZBQbQUJcP6SfazmlLicZkg=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type; b=p+N7WQjl1oyhM0ZEG/lVDf1cTGsyiQmKIg2mfgiGDxgWRBYW6i3N3rFrlguxwjCBu QA9OubrAK73sOXCfpsP7+v9+2gXST8B1jVfHjxHMgPBB95//2yPepme2nQovfkZjXD o901jQOWHi1OOIpaACZcUSkPHF04UXf1A4RaIDmw=
Message-ID: <>
Date: Fri, 11 Oct 2013 13:07:12 -0400
From: "Paul E. Jones" <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Melvin Carvalho <>
References: <> <em19baa0e5-7a97-44ab-874e-b084b9645052@sydney> <>
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------050809040609080805030607"
Cc: webfinger <>, Will Norris <>
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 17:07:10 -0000


See comments below:

On 10/11/2013 11:01 AM, Melvin Carvalho wrote:
>     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 <>. The person's name does
>     not have a defined property identifier anywhere, except the one I
>     specified under <>.
> Ah I see what you've done, you've added some internationalization, ie 
> one URI for each language?  Apart from that are there any differences 
> to FOAF (by the way FOAF already has standards for internationalization)
> Wouldnt this lead to potentially dozens of new URIs, per term, for 
> example, for a different one for every language supported?

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".

Using the URI fragment to indicate the language does introduce a number 
of distinct URIs, but having the language tag would need to be 
/somewhere/ if we want to allow the language to be specified as part of 
the property.  Unlike XML, we do not have additional attributes we can 
apply.  Arguably, we do not need to specify the language and we allow a 
user to advertise just a single name.  However, I've found it beneficial 
to allow people to advertise names in at least two different character 
sets.  I can't read Chinese, Japanese, or Korean, for example, so 
allowing a western alphabet is helpful to be used in parallel with the 
native alphabet is nice.