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 381DB21F9929 for ; Sat, 17 Aug 2013 11:40:32 -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 L+5E0L+WcmW5 for ; Sat, 17 Aug 2013 11:40:31 -0700 (PDT) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id B878021F96EF for ; Sat, 17 Aug 2013 11:40:30 -0700 (PDT) Received: by mail-la0-f54.google.com with SMTP id ea20so2392378lab.13 for ; Sat, 17 Aug 2013 11:40:29 -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=z5Hexxyior31difRgyAc1+xsd/TagN8s9CS3u/DKvHU=; b=RtThz3hNnVAoi6UuzsDix5P5gFR2MR8xA8kvaq1aDDi9KTgXd7/FA8iUpD+GP7J/Gx p0+H9lR6160Of1aKJ+0NQW0iVcEFd2ZKGasQEw8Vy1KufCIccnFRvQPoPHVVWOlI1NPO lihoXRm9hX29A2laNCM/23d/dLFbn1MkcN0HVn2mCEVCUtg5chb53tkvPKZ0DSyXCAh5 GdOqMakZgs2P4jns93V0uXN4DeAAb2xd3PeQvA/8LcrFTWbBRw98LqPneegjy5YpAEow crLI50QDzWeNTlYTSzHWKAzGE3kpfW2z3muD8fzquCS4bey/hzs1AWwH3TNfqlV9r6Ag 5wfg== MIME-Version: 1.0 X-Received: by 10.112.87.68 with SMTP id v4mr3755619lbz.2.1376764829611; Sat, 17 Aug 2013 11:40:29 -0700 (PDT) Received: by 10.112.159.233 with HTTP; Sat, 17 Aug 2013 11:40:29 -0700 (PDT) In-Reply-To: References: <087c01ce951a$e32da1f0$a988e5d0$@packetizer.com> Date: Sat, 17 Aug 2013 20:40:29 +0200 Message-ID: From: Melvin Carvalho To: "Paul E. Jones" Content-Type: multipart/alternative; boundary=001a11341b069bbefc04e4290aff Cc: webfinger Subject: Re: [webfinger] New WebFinger Draft posted 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: Sat, 17 Aug 2013 18:40:32 -0000 --001a11341b069bbefc04e4290aff Content-Type: text/plain; charset=ISO-8859-1 On 17 August 2013 20:32, Paul E. Jones wrote: > Melvin, > > We have been asked about this before. If we leave it in, it meets the > needs of some. I admit there might be cases where it's hard to control > order, but if it matters, there is at least a way. > > In my own implementation, I assign an integer value to each entry and sort > on that. > > I have no strong objection either way, but I do think it's good to have > for those who care. > I understand the trade offs. However, I can see that this is useful in many cases, particularly this would work well for openid, but other use cases, eg to have a friends list, for something like a federated social web, would then be perhaps impractical with JRD (not the end of the world, though) > Paul > > > ------------------------------ > *From:* Melvin Carvalho > *Sent:* Sat Aug 17 14:12:11 EDT 2013 > *To:* "Paul E. Jones" > *Cc:* webfinger > *Subject:* Re: [webfinger] New WebFinger Draft posted > > > > > On 9 August 2013 18:09, Paul E. Jones wrote: > >> Folks, >> >> As we're trying to bring the WebFinger spec to a close, we published a new >> version -17 with some changes the WG might want to consider. >> >> Draft is: >> http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-17 >> >> Those changes are: >> >> - Section 2, added a new last paragraph to explain what URI syntax we use >> in >> WebFinger >> - Corrected error in section 3.2 ("Host:" line in example and quotes >> around >> "3.2") >> - We remove the words "absolute URI" since it's really redundant >> - Added "query target" to 4.5 for clarity >> - Introduced a new section 8 that describes "WebFinger" applications. >> This >> is a major new addition. >> - Added a new section 10.3 and 10.4 to address registration of link >> relation >> types and properties. Link relations types already have a registry and we >> refer to existing procedures. WebFinger properties did not have a >> registry, >> so we define one, primarily for the purpose of helping people avoid >> creating >> redundant definitions. >> >> If you have any questions or comments, please feel free to post to the >> list. >> > > [[ > > The order of elements in the "links" array indicates an order of > preference. Thus, if there are two or more link relations having the > same "rel" value, the first link relation would indicate the user's > preferred link. > > ]] > > Maybe remove this altogether, as I am unsure it can be guaranteed. > > Case 1: Let's say I have a list of friends, how am I to determine as a > server the preferred friends? How am I to determine as a client whether > the friends are ordered or not? > > Case 2: Say I mash up data from two sources, how do I then order the > combined list? > > >> >> Paul >> >> >> _______________________________________________ >> webfinger mailing list >> webfinger@ietf.org >> https://www.ietf.org/mailman/listinfo/webfinger >> > > --001a11341b069bbefc04e4290aff Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On 17 August 2013 20:32, Paul E. Jones <paulej@packetizer.com<= /a>> wrote:

Melvin,

We have been asked about this before. If we leave it in, it = meets the needs of some. I admit there might be cases where it's hard t= o control order, but if it matters, there is at least a way.

In my own implementation, I assign an integer value to each = entry and sort on that.

I have no strong objection either way, but I do think it'= ;s good to have for those who care.


I understand the trade offs.=A0 However, I can see that this is useful i= n many cases, particularly this would work well for openid, but other use c= ases, eg to have a friends list, for something like a federated social web,= would then be perhaps impractical with JRD (not the end of the world, thou= gh)

Paul



From: Melvin Carvalho <melvincarvalho@gmail.com>
Sent: Sat Aug 17 14:12:11 EDT 2013
To: "Paul E. Jones" <paulej@packetizer.com>
Cc: webfinger <webfinger@ietf.org>
Subject: Re: [webfinger] New WebFinger Draft posted




On 9 August 2013 18:09, Paul E. Jones <paulej@packetizer.com> wrote:
Folks,

As we're trying to bring the WebFinger spec to a close, we published a = new
version -17 with some changes the WG might want to consider.

Draft is:
http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-17

Those changes are:

- Section 2, added a new last paragraph to explain what URI syntax we use i= n
WebFinger
- Corrected error in section 3.2 ("Host:" line in example and quo= tes around
"3.2")
- We remove the words "absolute URI" since it's really redund= ant
- Added "query target" to 4.5 for clarity
- Introduced a new section 8 that describes "WebFinger" applicati= ons. =A0This
is a major new addition.
- Added a new section 10.3 and 10.4 to address registration of link relatio= n
types and properties. =A0Link relations types already have a registry and w= e
refer to existing procedures. =A0WebFinger properties did not have a regist= ry,
so we define one, primarily for the purpose of helping people avoid creatin= g
redundant definitions.

If you have any questions or comments, please feel free to post to the list= .



Paul


_______________________________________________
webfinger mailing list
webfinger@ietf.org<= /a>
https://www.ietf.org/mailman/listinfo/webfinger


--001a11341b069bbefc04e4290aff--