MIME-Version: 1.0
In-Reply-To: <087c01ce951a$e32da1f0$a988e5d0$@packetizer.com>
References: <087c01ce951a$e32da1f0$a988e5d0$@packetizer.com>
Date: Sat, 17 Aug 2013 20:12:11 +0200
Message-ID: <CAKaEYh+i38utNp=ML3Qnut2OeoKPRPKhpquUOx5UUqp1Y+Pyiw@mail.gmail.com>
From: Melvin Carvalho <melvincarvalho@gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Content-Type: multipart/alternative; boundary=089e013d1b9c62dd4604e428a548
Cc: webfinger <webfinger@ietf.org>
Subject: Re: [webfinger] New WebFinger Draft posted
Precedence: list

--089e013d1b9c62dd4604e428a548
Content-Type: text/plain; charset=ISO-8859-1

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
> 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
>

--089e013d1b9c62dd4604e428a548
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 9 August 2013 18:09, Paul E. Jones <span dir=3D"ltr">&lt;<a href=
=3D"mailto:paulej@packetizer.com" target=3D"_blank">paulej@packetizer.com</=
a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">Folks,<br>
<br>
As we&#39;re trying to bring the WebFinger spec to a close, we published a =
new<br>
version -17 with some changes the WG might want to consider.<br>
<br>
Draft is:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-17" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-17</a=
><br>
<br>
Those changes are:<br>
<br>
- Section 2, added a new last paragraph to explain what URI syntax we use i=
n<br>
WebFinger<br>
- Corrected error in section 3.2 (&quot;Host:&quot; line in example and quo=
tes around<br>
&quot;3.2&quot;)<br>
- We remove the words &quot;absolute URI&quot; since it&#39;s really redund=
ant<br>
- Added &quot;query target&quot; to 4.5 for clarity<br>
- Introduced a new section 8 that describes &quot;WebFinger&quot; applicati=
ons. =A0This<br>
is a major new addition.<br>
- Added a new section 10.3 and 10.4 to address registration of link relatio=
n<br>
types and properties. =A0Link relations types already have a registry and w=
e<br>
refer to existing procedures. =A0WebFinger properties did not have a regist=
ry,<br>
so we define one, primarily for the purpose of helping people avoid creatin=
g<br>
redundant definitions.<br>
<br>
If you have any questions or comments, please feel free to post to the list=
.<br></blockquote><div><br>[[<br><pre class=3D"">   The order of elements i=
n the &quot;links&quot; array indicates an order of
   preference.  Thus, if there are two or more link relations having the
   same &quot;rel&quot; value, the first link relation would indicate the u=
ser&#39;s
   preferred link.<br></pre>]]<br>=A0<br></div><div>Maybe remove this altog=
ether, as I am unsure it can be guaranteed.<br><br></div><div>Case 1: Let&#=
39;s say I have a list of friends, how am I to determine as a server the pr=
eferred friends?=A0 How am I to determine as a client whether the friends a=
re ordered or not?<br>
<br></div><div>Case 2: Say I mash up data from two sources, how do I then o=
rder the combined list?<br></div><div><br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">

<br>
<br>
Paul<br>
<br>
<br>
_______________________________________________<br>
webfinger mailing list<br>
<a href=3D"mailto:webfinger@ietf.org">webfinger@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/webfinger" target=3D"_blan=
k">https://www.ietf.org/mailman/listinfo/webfinger</a><br>
</blockquote></div><br></div></div>

--089e013d1b9c62dd4604e428a548--