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

Melvin Carvalho <melvincarvalho@gmail.com> Sun, 06 October 2013 13:19 UTC

Return-Path: <melvincarvalho@gmail.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 6D77921F999C for <webfinger@ietfa.amsl.com>; Sun, 6 Oct 2013 06:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 segEsP35EDPM for <webfinger@ietfa.amsl.com>; Sun, 6 Oct 2013 06:19:52 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 84C4721E80AD for <webfinger@ietf.org>; Sun, 6 Oct 2013 06:19:43 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id eo20so4610725lab.6 for <webfinger@ietf.org>; Sun, 06 Oct 2013 06:19:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oudP2v2jJZp96yBA6unSnWdDo3hV73JzwIj72e3Mhu0=; b=MkmaUK0GXV/PMfIkGiqby+jsEe1MKQ1czxw8fb0u64ejwmSGVbMbr38VvwbEZTXzcH vaaGFZJTGaHeYpJcTeW/htwFyUnrngtw3wjzn5cTAgi5nHbZKb59tCgmDFNAq5b/69qN 5GWWzykVWATpx7F6VaOZojnsF4NxyEw3L4c+CbjAufgjHiN5lmKfLTQdFz7udt70EgkM U5JtyC+P6EmlT7gzZMtbcJwIsyK5JZASqg1G8kljpNjqxYoU0SS/DZonfwS1L3y3FIGr zG8PAIA5sGq7cgsjYSZTPpyPCtrzLWVBGqN0KH8r3nTZfScYdYac/hrJowJtCVehUx5L h4aw==
MIME-Version: 1.0
X-Received: by 10.112.51.101 with SMTP id j5mr20762440lbo.17.1381065582434; Sun, 06 Oct 2013 06:19:42 -0700 (PDT)
Received: by 10.112.159.233 with HTTP; Sun, 6 Oct 2013 06:19:42 -0700 (PDT)
In-Reply-To: <em8fca55dc-a3ff-4231-8218-6c2221838850@sydney>
References: <em8fca55dc-a3ff-4231-8218-6c2221838850@sydney>
Date: Sun, 6 Oct 2013 15:19:42 +0200
Message-ID: <CAKaEYh+n4LCJXevsJ_Y6dc5YnvH75kyQDXVtRV21RbTabCE=Dg@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary=001a1133646073e1b704e8126360
Cc: 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 13:19:53 -0000

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