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
Precedence: list
Reply-To: "Paul E. Jones" <paulej@packetizer.com>

--------=_MB602F051C-ECA7-4A5D-955A-433ED7945EC7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8

Melvin,
>>There are also properties, and I've not seen any described formally=20
>>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,=20
>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=20
>often better to reuse than to reinvent.
I agree, though none of these are designed for use in WebFinger.  So, I=20
created my own.  You can't point to something 5 years old and declare=20
I'm reproducing it because there is some syntax scribbling that has the=20
word "name" associated with it.

What I defined in the link above for "name", for example, is somewhere=20
between foaf:name and the one related to vcard.  WebFinger has a=20
registry for identifiers now.  It would be good to see that get=20
populated with useful items, though I would not recommend putting=20
everything one might possibly put into a vcard in there.  If a vcard is=20
essential, the vcard link relation should be published in a WF JRD and a=
=20
client query that.  However, there are basic things like "name" that are=
=20
very useful, such as when you log into a web site and that site would=20
like to display your avatar and name.  The avatar already has a defined=20
LR value under webfinger.org.  The person's name does not have a defined=
=20
property identifier anywhere, except the one I specified under=20
packetizer.com.

Paul

--------=_MB602F051C-ECA7-4A5D-955A-433ED7945EC7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=utf-8

<HTML><HEAD>
<STYLE id=3DeMClientCss>blockquote.cite { margin-left: 5px; margin-right:=
 0px; padding-left: 10px; padding-right:0px; border-left: 1px solid #000000=
 }
.plain pre, .plain tt { font-family: monospace; font-size: 100%; font-weigh=
t: normal; font-style: normal; }
body {font-family: Calibri;font-size: 11pt;}
.plain pre, .plain tt {font-family: Calibri;font-size: 11pt;}
</STYLE>

<STYLE></STYLE>
</HEAD>
<BODY scroll=3Dauto class>
<DIV>Melvin,</DIV>
<BLOCKQUOTE class=3Dcite cite=3DCAKaEYhJEvfiPT-5zTjnVXSpyGxYnpOO5gB0wvjgcHB=
6u6Fq6RQ@mail.gmail.com type=3D"cite">
<DIV id=3D51d18880cb9541a1bc43787562335d42>
<DIV dir=3Dltr>
<DIV class=3Dgmail_extra>
<DIV class=3Dgmail_quote>
<BLOCKQUOTE class=3Dgmail_quote style=3D"PADDING-LEFT: 1ex; MARGIN: 0px =
0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV>There are also properties, and I've not seen any described formally=
 anywhere.&nbsp; I've defined a ones I find useful:</DIV>
<DIV><A href=3D"http://www.packetizer.com/webfinger/properties.html">http:/=
/www.packetizer.com/webfinger/properties.html</A></DIV></DIV></BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>Regarding name, just from the top of my head (I didnt include PoCo,=
 OpenSocial, PIM, DOAP, but you could search for them)<BR></DIV>
<DIV><BR><A href=3D"http://xmlns.com/foaf/spec/#term_name">http://xmlns.com=
/foaf/spec/#term_name</A><BR><A href=3D"https://schema.org/name">https://sc=
hema.org/name</A><BR><A href=3D"http://graph.facebook.com/schema/user#name"=
>http://graph.facebook.com/schema/user#name</A><BR><A href=3D"http://www.w3=
.org/TR/vcard-rdf/#d4e1731">http://www.w3.org/TR/vcard-rdf/#d4e1731</A><BR>=
<BR></DIV>
<DIV>Remember that link relations predate webfinger by over 5 years.&nbsp;=
 It's often better to reuse than to reinvent.</DIV></DIV></DIV></DIV></DIV>=
</BLOCKQUOTE>
<DIV>I agree, though none of these are designed for use in WebFinger.&nbsp;=
 So, I created my own.&nbsp; You can't point to something&nbsp;5 years old=
 and declare I'm reproducing it because there is some syntax scribbling =
that has the word "name" associated with it.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What I defined in the link above for "name", for example, is somewhere=
 between foaf:name and the one related to vcard.&nbsp; WebFinger has a regi=
stry for identifiers now.&nbsp; 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.&nbsp; If a vcard is essential,=
 the vcard link relation should be published in a WF JRD and a client query=
 that.&nbsp; However, there are basic things like "name" that are very usef=
ul, such as when you log into a web site and that site would like to displa=
y your&nbsp;avatar and name.&nbsp; The avatar already has a defined LR valu=
e under webfinger.org.&nbsp; The person's name does not have a defined prop=
erty identifier anywhere, except the one I specified under packetizer.com.<=
/DIV>
<DIV>&nbsp;</DIV>
<DIV>Paul</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>
--------=_MB602F051C-ECA7-4A5D-955A-433ED7945EC7--