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

Erik Wilde <dret@berkeley.edu> Thu, 12 April 2012 16:39 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 4340D21F86AF for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 09:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 XwskcZStIt6F for <apps-discuss@ietfa.amsl.com>; Thu, 12 Apr 2012 09:39:39 -0700 (PDT)
Received: from cm01fe.IST.Berkeley.EDU (cm01fe.IST.Berkeley.EDU [169.229.218.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0FD2D21F86A7 for <apps-discuss@ietf.org>; Thu, 12 Apr 2012 09:39:39 -0700 (PDT)
Received: from 108-67-66-127.lightspeed.sntcca.sbcglobal.net ([108.67.66.127] helo=[192.168.1.67]) by cm01fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1SIN3S-000835-6I; Thu, 12 Apr 2012 09:39:36 -0700
Message-ID: <4F87053F.2080203@berkeley.edu>
Date: Thu, 12 Apr 2012 09:39:27 -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: Julian Reschke <julian.reschke@gmx.de>
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> <4F86F99A.3070601@gmx.de> <4F86FD73.2010708@berkeley.edu> <4F86FE6E.40801@gmx.de>
In-Reply-To: <4F86FE6E.40801@gmx.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, Jan Algermissen <jan.algermissen@nordsc.com>, REST Discuss <rest-discuss@yahoogroups.com>, "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
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:39:40 -0000

hello julian.

On 2012-04-12 09:10 , Julian Reschke wrote:
> It seems you are using "profile" in a very different way then it was
> used in HTML4; is this really a good idea?

i certainly do not intend to use it in a different way, because like 
you, i do not think that would be a good idea. my current definition is 
that "a profile 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."

my understanding of HTML's profile was always like this. quoting from 
http://www.w3.org/TR/html4/struct/global.html#profiles :

"User agents may be able to recognize the name (without actually 
retrieving the profile) and perform some activity based on known 
conventions for that profile. For instance, search engines could provide 
an interface for searching through catalogs of HTML documents, where 
these documents all use the same profile for representing catalog entries."

mark also noted that he regards a profile mostly as saying something 
about a representation's content, such as a metadata profile in HTML, 
saying that the web page uses dublin core. but even when you look at the 
dublin core HTML profile (http://dublincore.org/documents/dcq-html/), it 
also defines conventions about links 
(http://dublincore.org/documents/dcq-html/#sect-2-4), and not just about 
non-link data. which is the point i was trying to make saying that the 
line between "format extensions" and "links" is fuzzy: essentially, a 
link *is* a format extension, only one that extends beyond the current 
resource.

i am not sure i was able to fully address your concerns, so if you still 
think i am "redefining" what 'profile' is supposed to do, could you be a 
bit more specific why you think that's the case, and how you'd like to 
see it done?

thanks a lot and 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 |