Return-Path: 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 6F1ED21F9808 for ; Fri, 11 Oct 2013 08:01:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_44=0.6, 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 M2e0boaf07FK for ; Fri, 11 Oct 2013 08:01:28 -0700 (PDT) Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 2250311E80E3 for ; Fri, 11 Oct 2013 08:01:27 -0700 (PDT) Received: by mail-la0-f49.google.com with SMTP id ev20so3520181lab.36 for ; Fri, 11 Oct 2013 08:01:27 -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=WkJHjxiwWNK7Uravcebvd8/cUel7nhbF+OD6QqaOgSs=; b=jaBpSOe9ksgcO2NCPtKIPAjUkV8HoQFy+GqRBE4lCM0JAMOlXETY+vRq/XN4KWP/1r YpEaWGjn3JaMUotcjxRLqGNke6V5VEnVkhi9uLiwZc3Tnj2Cuu4RlrRrhIMlXGwRDNxi ruwuEL+Sawtpk1ED7iNAgwBzOKXb4cgAmxWAGH4DYoEiGHBiIBPF3Bp0UKIP3UDTGyan TtxnldGnS3yDpvUtLjneZZtOeMvVrRU20sNLF48pyZlWSkLahc4riGoxEjfGyui3v4lK dyLuIpuOSYIiV6OKf7Ou4wNBKrLwdgJXCrXkc2jxFpbvWOIZyu28txoC84TnKrvqDAwn lJPg== MIME-Version: 1.0 X-Received: by 10.152.29.201 with SMTP id m9mr16793016lah.6.1381503686902; Fri, 11 Oct 2013 08:01:26 -0700 (PDT) Received: by 10.112.159.233 with HTTP; Fri, 11 Oct 2013 08:01:26 -0700 (PDT) In-Reply-To: References: Date: Fri, 11 Oct 2013 17:01:26 +0200 Message-ID: From: Melvin Carvalho To: "Paul E. Jones" Content-Type: multipart/alternative; boundary=089e0158cb9283899604e8786410 Cc: webfinger , Will Norris 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Oct 2013 15:01:31 -0000 --089e0158cb9283899604e8786410 Content-Type: text/plain; charset=ISO-8859-1 On 11 October 2013 01:41, Paul E. Jones wrote: > Melvin, > > There are also properties, and I've not seen any described formally >> 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, > 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 > often better to reuse than to reinvent. > > 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 > webfinger.org. The person's name does not have a defined property > identifier anywhere, except the one I specified under packetizer.com. > 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? > > Paul > > --089e0158cb9283899604e8786410 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 11 October 2013 01:41, Paul E. Jones <paulej@packetizer.com= > wrote:
Melvin,
There are also properties, and I've not seen any described formall= y anywhere.=A0 I've defined a ones I find useful:

Regarding name, just from the top of my head (I didnt include PoCo, Op= enSocial, PIM, DOAP, but you could search for them)
Remember that link relations predate webfinger by over 5 years.=A0 It&= #39;s often better to reuse than to reinvent.
=
I agree, though none of these are designed for use in WebFinger.= =A0 So, I created my own.=A0 You can't point to something=A05 years old= and declare I'm reproducing it because there is some syntax scribbling= that has the word "name" associated with it.
=A0
What I defined in the link above for "name", for example, is= somewhere between foaf:name and the one related to vcard.=A0 WebFinger has= a registry for identifiers now.=A0 It would be good to see that get popula= ted with useful items, though I would not recommend putting everything one = might possibly put into a vcard in there.=A0 If a vcard is essential, the v= card link relation should be published in a WF JRD and a client query that.= =A0 However, there are basic things like "name" that are very use= ful, such as when you log into a web site and that site would like to displ= ay your=A0avatar and name.=A0 The avatar already has a defined LR value und= er webfinger.org.=A0= The person's name does not have a defined property identifier anywhere= , except the one I specified under packetizer.com.

Ah I see what you've done, you&#= 39;ve added some internationalization, ie one URI for each language?=A0 Apa= rt 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 ter= m, for example, for a different one for every language supported?
=
=A0
=A0
Paul
=A0

--089e0158cb9283899604e8786410--