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

Erik Wilde <dret@berkeley.edu> Thu, 12 April 2012 16:24 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 1111921F86C3 for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 09:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level:
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 7KMNFIsS6LaM for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 09:24:35 -0700 (PDT)
Received: from cm05fe.IST.Berkeley.EDU (cm05fe.IST.Berkeley.EDU [169.229.218.146]) by ietfa.amsl.com (Postfix) with ESMTP id D491B21F86C1 for <apps-discuss@ietf.org>; Thu, 12 Apr 2012 09:24:34 -0700 (PDT)
Received: from 108-67-66-127.lightspeed.sntcca.sbcglobal.net ([108.67.66.127] helo=[192.168.1.67]) by cm05fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1SIMot-0007sj-HQ; Thu, 12 Apr 2012 09:24:32 -0700
Message-ID: <4F8701B8.9020307@berkeley.edu>
Date: Thu, 12 Apr 2012 09:24:24 -0700
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
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> <4F8665E4.9050303@berkeley.edu> <5006D354-A78D-4347-A3D1-0ED840BD81ED@nordsc.com>
In-Reply-To: <5006D354-A78D-4347-A3D1-0ED840BD81ED@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 16:24:36 -0000

hello jan.

On 2012-04-12 00:12 , Jan Algermissen wrote:
> On Apr 12, 2012, at 7:19 AM, Erik Wilde wrote:
>> 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.
> Ok (though I personally would not see a profile as saying something about the resource, but about the payload)

yes, we have agreement on this. a profile (quoting from the -01 text i 
am writing now) "are additional semantics that can be used to process a 
resource  representation, such as constraints, conventions, extensions, 
or any other aspects that do not alter the basic media type semantics."

if a feed indicates it supports atompub, that extends what to expect in 
the feed, and in case of atompub, it also extends the feed's behavior. 
like i said in a response to mark, i think the line between "format 
conventions" and "behavior" is fuzzy. but i'd argue that the 'atompub 
profile' definitely would be specific for the representation (the 
atompub enabled feed), because a different representation of the 
collection resource might very well expose a different mechanism to 
provide write access to the collection.

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 |