Re: [link-relations] [apps-discuss] New Version Notification for draft-amundsen-item-and-collection-link-relations-04.txt

mike amundsen <mamund@yahoo.com> Sun, 09 October 2011 18:03 UTC

Return-Path: <mca@amundsen.com>
X-Original-To: link-relations@ietfa.amsl.com
Delivered-To: link-relations@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A7B21F8AAF; Sun, 9 Oct 2011 11:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.68
X-Spam-Level:
X-Spam-Status: No, score=-0.68 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, FORGED_YAHOO_RCVD=2.297, RCVD_IN_DNSWL_LOW=-1]
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 ozoPuKmYz-hH; Sun, 9 Oct 2011 11:03:29 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 73B4E21F88B7; Sun, 9 Oct 2011 11:03:29 -0700 (PDT)
Received: by wwf22 with SMTP id 22so5614293wwf.13 for <multiple recipients>; Sun, 09 Oct 2011 11:03:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.227.23.202 with SMTP id s10mr5146010wbb.85.1318183406842; Sun, 09 Oct 2011 11:03:26 -0700 (PDT)
Sender: mca@amundsen.com
Received: by 10.180.94.136 with HTTP; Sun, 9 Oct 2011 11:03:26 -0700 (PDT)
In-Reply-To: <47B4DDF4A432612AE8838EBF@cyrus.local>
References: <20111009165234.27400.89244.idtracker@ietfa.amsl.com> <CAPW_8m5yQpOvrKfxxO0L1x_Y4Pb6v+6syGazBUdijZYPLherjg@mail.gmail.com> <CAPW_8m4aGXPgXb9i5HRpbpNNFeV+ax7Y2i4QFoJMJ0dMN93x1A@mail.gmail.com> <47B4DDF4A432612AE8838EBF@cyrus.local>
Date: Sun, 09 Oct 2011 14:03:26 -0400
X-Google-Sender-Auth: NIGmdHzUn9h_4f2Pbj886oa0CKU
Message-ID: <CAPW_8m6giRgNa6Hhpf3pOLPW1sBbMbcfvXo4hq85YmxUKPtZLw@mail.gmail.com>
From: mike amundsen <mamund@yahoo.com>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: apps-discuss@ietf.org, link-relations@ietf.org
Subject: Re: [link-relations] [apps-discuss] New Version Notification for draft-amundsen-item-and-collection-link-relations-04.txt
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2011 18:03:30 -0000

Cyrus:

The I-D does not mandate how the link-relation type is to be used.

Authors can use these values in message bodies only if they like;
there is no requirement to use Link headers. They can create "paged"
output that emits as many (or as few) links as desired.

Basically, this does not change the number of links, just adds the
possibility of a shared understanding of the rel value used to
decorate those links.

mca
http://amundsen.com/blog/
http://twitter.com@mamund
http://mamund.com/foaf.rdf#me





On Sun, Oct 9, 2011 at 07:36, Cyrus Daboo <cyrus@daboo.name> wrote:
> Hi mike,
>
> --On October 9, 2011 1:14:26 PM -0400 mike amundsen <mamund@yahoo.com>
> wrote:
>
>> I modified the examples of include Frank Ellermann's suggestion
>> regarding Link Header reference in the text.
>>
>> http://tools.ietf.org/html/draft-amundsen-item-and-collection-link-relati
>> ons-04
>>
>> I will submit this I-D to the rfc-editor within 24 hrs. Anyone who
>> would like to volunteer as a potential reviewer, feel free to post on
>> this thread or contact me directly and I'll include your name/contact
>> info in the submission.
>>
>> Thanks to all for the assistance.
>
> Has any thought been given to scalability. I know of web applications where
> the number of "items" can be in the 1000's or more. Returning 1000+ Link
> headers seems inappropriate in that case. Perhaps what is needed is an
> "item-list" link which points to another resource where the full "item"
> listing can be retrieved in some suitable fashion?
>
> --
> Cyrus Daboo
>
>