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

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