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

John Bradley <ve7jtb@ve7jtb.com> Sun, 06 October 2013 14:05 UTC

Return-Path: <ve7jtb@ve7jtb.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 0034521E80C3 for <webfinger@ietfa.amsl.com>; Sun, 6 Oct 2013 07:05:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 GTgEiQitfSx7 for <webfinger@ietfa.amsl.com>; Sun, 6 Oct 2013 07:05:30 -0700 (PDT)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id AA10A21E80BD for <webfinger@ietf.org>; Sun, 6 Oct 2013 07:05:29 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id f12so6130686wgh.5 for <webfinger@ietf.org>; Sun, 06 Oct 2013 07:05:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=w/sfI8cPnXKvnQ98CiSV72p7bP+VtvjxOKZpGfZ9K48=; b=SB0V7T61Y2+BMhA4ALoN1mm4gsJIh7trYfgkkCw4fmSLP4G/FxmsmDxgrZCRntAqCZ NabxzapytrQB44CpbCqkVpgPd/qz5FCESHJt9692eR0IusLbahIJS5QuI9A8jU9HHkKk HAx/bQ7ppW8LWiBOJ3oErPoiycEKPlcnfbtsnA+uqE9ng9sfgcdvVE839amGdGRcavAm au+NmBgPxp+tPF4XiAQzSghp1fVdaO5hpALzxv8gFUgfqCTiatUHH6/b2DIXnFOVfDO8 fcpGbiMmTbaUClcH7Sn2sWqKwpRlUl+b4mELvjkpJAqi6vHSGp6KGtCn+sFJzdWnEnx+ s6Vw==
X-Gm-Message-State: ALoCoQlqW7x72jWrst3FodzrwMcslOSa6LX436I8NX3ILXZcyZoRetxYysPxVP4GGaM9cQk9JlY3
X-Received: by 10.180.198.44 with SMTP id iz12mr15328819wic.32.1381068328574; Sun, 06 Oct 2013 07:05:28 -0700 (PDT)
Received: from [192.168.0.93] ([195.99.165.34]) by mx.google.com with ESMTPSA id q5sm29666072wiz.3.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 06 Oct 2013 07:05:27 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_67BCB271-F469-45E4-91F9-81752626E3FF"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <CAKaEYh+n4LCJXevsJ_Y6dc5YnvH75kyQDXVtRV21RbTabCE=Dg@mail.gmail.com>
Date: Sun, 6 Oct 2013 15:05:25 +0100
Message-Id: <208721BC-8EB8-418B-8F71-AA4642F11208@ve7jtb.com>
References: <em8fca55dc-a3ff-4231-8218-6c2221838850@sydney> <CAKaEYh+n4LCJXevsJ_Y6dc5YnvH75kyQDXVtRV21RbTabCE=Dg@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "Paul E. Jones" <paulej@packetizer.com>, webfinger <webfinger@ietf.org>
Subject: Re: [webfinger] Registration of a URN for WebFinger Properties
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: Sun, 06 Oct 2013 14:05:42 -0000

That was my assumption as well.   There is no requirement for a URN namespace,.

Documenting the usage of the agreed http URI keys is the task that needs to undertaken by someone,


John B.


On 2013-10-06, at 2:19 PM, Melvin Carvalho <melvincarvalho@gmail.com> wrote:

> 
> 
> 
> On 5 October 2013 03:22, Paul E. Jones <paulej@packetizer.com> wrote:
> Folks,
>  
> As you know, properties (both link and subject-specific properties) are identified via a URI.  For applications that are defined outside the IETF, those organizations are able to define any URI they wish to use.  For any we might define within the IETF, however, we need something.
>  
> In anticipation of having such a need, I think we should create a document along the lines of RFC 6755 for WebFinger.  Specifically, we would define a URN sub-namespace as:
>  
>    urn:ietf:params:webfinger
>  
> One such potentially-useful subject-specific properties are "name", which would be the the subject's name intended for human consumption.  If you've queried my WebFinger server, you would know I currently advertise my name in English and Chinese.  For the "default" name, the URN might be:
>  
>    urn:ietf:params:webfinger:name
>  
> For language-specific variants, it might be:
>  
>    urn:ietf:params:webfinger:name:zh-CN
>  
> Defining the various properties and their meaning is an exercise for another day, but I hope you see the value in defining the URN sub-namespace.
> 
> Cant this be done using traditional HTTP keys.  The advantage being that they can be systematically dereferenced using http GET, rather than having to look it up in a central registry in a non machine readable way.  This is what has been going on for 10+ years, with FOAF, schema.org, open graph protocol and others.  Have I missed something?
>  
>  
> Thoughts?
>  
> Paul
>  
> 
> _______________________________________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger
> 
> 
> _______________________________________________
> webfinger mailing list
> webfinger@ietf.org
> https://www.ietf.org/mailman/listinfo/webfinger