Re: [link-relations] NEW RELATION: collection

mike amundsen <mamund@yahoo.com> Wed, 10 August 2011 03:55 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 6DFDE21F8A96 for <link-relations@ietfa.amsl.com>; Tue, 9 Aug 2011 20:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.342
X-Spam-Level:
X-Spam-Status: No, score=-0.342 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, FORGED_YAHOO_RCVD=2.297, J_CHICKENPOX_43=0.6, 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 akfiWtD8AFwD for <link-relations@ietfa.amsl.com>; Tue, 9 Aug 2011 20:55:04 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 99CEF21F8A95 for <link-relations@ietf.org>; Tue, 9 Aug 2011 20:55:04 -0700 (PDT)
Received: by fxe6 with SMTP id 6so680557fxe.31 for <link-relations@ietf.org>; Tue, 09 Aug 2011 20:55:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.54.90 with SMTP id p26mr10568342fag.44.1312948534440; Tue, 09 Aug 2011 20:55:34 -0700 (PDT)
Sender: mca@amundsen.com
Received: by 10.223.107.19 with HTTP; Tue, 9 Aug 2011 20:55:34 -0700 (PDT)
In-Reply-To: <4E41FD54.4070907@gmail.com>
References: <CAPW_8m676cCQEHN=_XE_E4k_7zF=MBNE7O6Cvy1+BLwp9fG8MA@mail.gmail.com> <4E3CF493.9010007@gmx.de> <CAPW_8m44aMqgFJ7nf3trD=r_LTNPYnQjGp31YMfrGGeX1bqC=A@mail.gmail.com> <4E3CFA65.3090300@gmx.de> <CAPW_8m5AyZsxSg2FBsNCQ7WyyS0ghZpQZ0jeAc=yQ92=qmH-jw@mail.gmail.com> <4E3CFE8A.1070103@gmail.com> <CAPW_8m4M0S0BS37OPCkCD1BPUwL7gMYM7jP5qxr3B=vnxW7HVg@mail.gmail.com> <4E3D0C54.7070209@gmx.de> <CABzDd=4be+7aQ65aH1Msgusn0RTcqGnfQrUdH1X160cgL0eQMg@mail.gmail.com> <CAPW_8m5yQEMO0Mw7=6b1vaLdUqSWKNEq6VG6THJ6YWorEqYOZw@mail.gmail.com> <4E3E93EF.8050800@gmx.de> <CAPW_8m5GzQACSueOU+XJ2XvnEfSY3wnWWF5rs-F5Hsa=6QB0dQ@mail.gmail.com> <4E41FD54.4070907@gmail.com>
Date: Tue, 09 Aug 2011 23:55:34 -0400
X-Google-Sender-Auth: VgY4gjp4o7lSSxwgPadMQtpRZsc
Message-ID: <CAPW_8m6RVjqp_a1bG5GZgOW636JnKWUUOPppqDRH4b1npb+ZQA@mail.gmail.com>
From: mike amundsen <mamund@yahoo.com>
To: Mykyta Yevstifeyev <evnikita2@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: link-relations@ietf.org
Subject: Re: [link-relations] NEW RELATION: collection
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: Wed, 10 Aug 2011 03:55:05 -0000

Mykyta:

Ok, will do.

One procedural Q. I will be submitting both the TXT and the XML file.
I assume the file names should be:
draft-amundsen-item-and-collection-link-relations-00.txt
draft-amundsen-item-and-collection-link-relations-00.xml

IOW, i supply the "00" and i supply the file extension.

thanks.

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


#RESTFest 2011 - Aug 18-20
http://restfest.org



On Tue, Aug 9, 2011 at 23:39, Mykyta Yevstifeyev <evnikita2@gmail.com> wrote:
> Mike,
>
> Please upload this draft with <https://datatracker.ietf.org/submit/> to
> allow further comments.
>
> Mykyta
>
> 10.08.2011 6:21, mike amundsen wrote:
>>
>> I've updated my pre-draft I-D for 'collection' and 'item' Link Relation
>> Types:
>> http://amundsen.com/media-types/files/item-and-collection/
>>
>> per suggestions from Mykyta&  Julian:
>> - added opening sentence in Abstract and Introduction that refers to
>> RFC5988
>> - added a reference to the existing media types (OpenSearch, Maze+XML,
>> and Collection+JSON) in the Introduction
>> - dropped the 2119 section
>> - removed the JSON examples and replaced them w/ Link Header examples;
>> cleaned up the examples a bit, too.
>> - modified Security and I18N w/ references to appropriate sections in 5988
>> - modified the IANA Considerations section "Reference" item per Julian
>> (is this what you meant?)
>>
>> Julian:
>> regarding the existing "up" link-rel-type and the proposed
>> "collection" link-rel-type...
>> I note the def for "up" (in 5988) refers to a "hierarchy" which I mean
>> to avoid in the case of "collection." IOW, i think "collection" can be
>> used not only for navigating hierarchies (if that is what is needed),
>> but also to navigate filtered sets or groups that are not in a
>> hierarchy.
>>
>> Thanks again for the feedback. I look forward to additional remarks.
>>
>> mca
>> http://amundsen.com/blog/
>> http://twitter.com@mamund
>> http://mamund.com/foaf.rdf#me
>>
>>
>> #RESTFest 2011 - Aug 18-20
>> http://restfest.org
>>
>>
>>
>> On Sun, Aug 7, 2011 at 09:32, Julian Reschke<julian.reschke@gmx.de>
>>  wrote:
>>>
>>> On 2011-08-07 04:09, mike amundsen wrote:
>>>>
>>>> I've posted a "pre-draft" version of the I-D here:
>>>> http://amundsen.com/media-types/files/item-and-collection/
>>>>
>>>> I would appreciate any advice, pointers, suggestions on improving this
>>>> before I post the first submission to the IETF.
>>>> ...
>>>
>>> OK. Looks good so far.
>>>
>>> A general question: what's the relation between "up" and "collection"? Do
>>> you see "up" as a special case in that it mentions document hierarchies?
>>>
>>> Editorial:
>>>
>>> - as Mykyta noted: no need for Section 2 if you don't need the keywords
>>>
>>> - the examples use a JSON vocabulary without saying what it is; you may
>>> want
>>> to reference "your" media types
>>>
>>> - alternatively or additionally, add Link header field examples
>>>
>>> - IANA considerations: replace "this document" with a reference to the
>>> actual section
>>>
>>> - I18N: just point to RFC 5988, Section 8.
>>>
>>>> I am currently at a loss as to what to include for the Security
>>>> Considerations section. I've posted some suggestions/questions within
>>>> this draft; feel free to point me in the proper direction.
>>>
>>> As Mykyta said: cite RFC 5988 and then think about additional issues.
>>>
>>>>    Consideration for links that cross admin boundaries?
>>>>    Infected Sites?
>>>>    Pointing to malicious content?
>>>
>>> ...and maybe link loops. Not sure what can be said; all of these seem to
>>> generic to any kind of following hyperlinks.
>>>
>>>> As soon as I clean up this version, I'll post it to the tracker
>>>> (another first for me<g>).
>>>> ...
>>>
>>> Best regards, Julian
>>>
>
>