IETF Logo Mail Archive

Re: [apps-discuss] [rest-discuss] Re: Feedback on draft-wilde-profile-link-00

Erik Wilde <dret@berkeley.edu> Thu, 12 April 2012 05:19 UTC

Return-Path: <dret@berkeley.edu>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3959B21F85A1 for <apps-discuss@ietfa.amsl.com>; Wed, 11 Apr 2012 22:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 LDdwBhoV2B7P for <apps-discuss@ietfa.amsl.com>; Wed, 11 Apr 2012 22:19:35 -0700 (PDT)
Received: from cm03fe.IST.Berkeley.EDU (cm03fe.IST.Berkeley.EDU [169.229.218.144]) by ietfa.amsl.com (Postfix) with ESMTP id 9070021F85A0 for <apps-discuss@ietf.org>; Wed, 11 Apr 2012 22:19:35 -0700 (PDT)
Received: from 108-67-66-127.lightspeed.sntcca.sbcglobal.net ([108.67.66.127] helo=[192.168.1.64]) by cm03fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1SICRK-00027H-Cr; Wed, 11 Apr 2012 22:19:28 -0700
Message-ID: <4F8665E4.9050303@berkeley.edu>
Date: Wed, 11 Apr 2012 22:19:32 -0700
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Jan Algermissen <jan.algermissen@nordsc.com>
References: <04FC3F79-93B5-4F86-82B2-42029138E202@mnot.net> <4F7F416C.3050400@berkeley.edu> <FFA388B3-F4D9-47AB-81EF-0761200438FB@mnot.net> <624F8E5E-7997-4716-AE84-78B30F7D2E38@nordsc.com>
In-Reply-To: <624F8E5E-7997-4716-AE84-78B30F7D2E38@nordsc.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, REST Discuss <rest-discuss@yahoogroups.com>
Subject: Re: [apps-discuss] [rest-discuss] Re: Feedback on draft-wilde-profile-link-00
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Apr 2012 05:19:36 -0000

hello jan.

On 2012-04-10 11:58 , Jan Algermissen wrote:
> Likewise, what does that check for atompub capabilities buy you? The reason you check for them is that you assume they are there in the first place. If that check fails .... then what? You are in exactly the same situation as when you POST you atom entry right away and see what happens.

the idea is to be able to check for the profile URI to see whether a 
feed i have discovered supports atompub or not. if it does, i might show 
an "upload" feature in a UI that otherwise i would not show. without the 
feed advertising its capabilities, i cannot know, and i certainly don't 
want to create a fake post to test whether atompub is supported or not.

if all operations in atompub were exposed via links, it would be a 
different story in this particular case, but they are not, so a profile 
URI would be one way to go. and it's just one example and not the whole 
'profile' story.

cheers,

dret.

-- 
erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
            | UC Berkeley  -  School of Information (ISchool) |
            | http://dret.net/netdret http://twitter.com/dret |

v2.23.0 | Report a Bug | By Email