Re: [apps-discuss] draft-wilde-profile-link-01 published

Erik Wilde <dret@berkeley.edu> Mon, 16 April 2012 05:46 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 F05D221F8739 for <apps-discuss@ietfa.amsl.com>; Sun, 15 Apr 2012 22:46:25 -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 VZ-ds0nDf6e1 for <apps-discuss@ietfa.amsl.com>; Sun, 15 Apr 2012 22:46:24 -0700 (PDT)
Received: from cm01fe.IST.Berkeley.EDU (cm01fe.IST.Berkeley.EDU [169.229.218.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB2221F8734 for <apps-discuss@ietf.org>; Sun, 15 Apr 2012 22:46:24 -0700 (PDT)
Received: from [212.234.135.180] (helo=dretair.local) 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 1SJelb-0002X4-3x; Sun, 15 Apr 2012 22:46:24 -0700
Message-ID: <4F8BB227.2050904@berkeley.edu>
Date: Mon, 16 Apr 2012 07:46:15 +0200
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: REST Discuss <rest-discuss@yahoogroups.com>, application-layer protocols <apps-discuss@ietf.org>
References: <04FC3F79-93B5-4F86-82B2-42029138E202@mnot.net> <4F7F416C.3050400@berkeley.edu> <FFA388B3-F4D9-47AB-81EF-0761200438FB@mnot.net> <4F8B2231.1090300@berkeley.edu> <A09A9E0A4B9C654E8672D1DC003633AE52EE05C2BF@GRFMBX704BA020.griffon.local>
In-Reply-To: <A09A9E0A4B9C654E8672D1DC003633AE52EE05C2BF@GRFMBX704BA020.griffon.local>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [apps-discuss] draft-wilde-profile-link-01 published
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: Mon, 16 Apr 2012 05:46:26 -0000

hello walter.

> Thanks for the update.
> Such types of link have also been widely used for years together with the webfinger specification (usually under the http://webfinger.net/rel/profile-page rel type for html profile pointers) so I would suppose it will also relate to the wf/swd discussion and that ultimately this draft becomes compatible with the discovery solution ultimately specified. It may be worth adding it as an example.

thanks for the pointer to web finger. i am sure there are quite a number 
of other formats out there using html profiles, maybe it would be 
interesting to create a small list of "well-known" profiles.

> I would also suggest to emphasize the usage on the "type" attribute together with this link rel to better characterize the type of information a client should expect. Indeed I would expect in some cases more than one of such "profile" link rel to be published within the same document, and the type may be useful for this. E.g. so far in wf the http://webfinger.net/rel/profile-page and http://microformats.org/profile/hcard (and to some extent the http://portablecontacts.net/spec/1.0#me) rel types are widely used to discriminate the expect type of "profile" format/info accessible. It would be valuable to maintain such flexibility.

while i think that the "type" idea is interesting, i am confused that 
you suggest http://microformats.org/profile/hcard as such a type. 
afaict, hCard is a specific profile and does not define a format for 
describing profiles. i would expect types to define a framework that 
could be used to define specific profiles, but maybe we have a different 
idea of what a "type" attribute could do? could you explain why you 
consider http://microformats.org/profile/hcard to be a type instead of a 
specific profile?

thanks 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 |