Atom Content Negotiation (follow-up)
Erik Wilde <dret@berkeley.edu> Sat, 30 April 2011 19:26 UTC
Return-Path: <owner-atom-syntax@mail.imc.org>
X-Original-To: ietfarch-atompub-archive@ietfa.amsl.com
Delivered-To: ietfarch-atompub-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 608F7E06A3 for <ietfarch-atompub-archive@ietfa.amsl.com>; Sat, 30 Apr 2011 12:26:11 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjanBTWKY7zR for <ietfarch-atompub-archive@ietfa.amsl.com>; Sat, 30 Apr 2011 12:26:10 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2001:4870:a30c:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6514CE0697 for <atompub-archive@ietf.org>; Sat, 30 Apr 2011 12:26:05 -0700 (PDT)
Received: from hoffman.proper.com (localhost [127.0.0.1]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p3UJKQJD078223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Apr 2011 12:20:26 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
Received: (from majordom@localhost) by hoffman.proper.com (8.14.4/8.13.5/Submit) id p3UJKQEb078221; Sat, 30 Apr 2011 12:20:26 -0700 (MST) (envelope-from owner-atom-syntax@mail.imc.org)
X-Authentication-Warning: hoffman.proper.com: majordom set sender to owner-atom-syntax@mail.imc.org using -f
Received: from cm02fe.IST.Berkeley.EDU (cm02fe.IST.Berkeley.EDU [169.229.218.143]) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p3UJKOmO078214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <atom-syntax@imc.org>; Sat, 30 Apr 2011 12:20:25 -0700 (MST) (envelope-from dret@berkeley.edu)
Received: from 173-228-119-48.dsl.dynamic.sonic.net ([173.228.119.48] helo=dretair.local) by cm02fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1QGFiJ-0007bH-71; Sat, 30 Apr 2011 12:20:24 -0700
Message-ID: <4DBC60F4.7000402@berkeley.edu>
Date: Sat, 30 Apr 2011 12:20:20 -0700
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Atom-Syntax <atom-syntax@imc.org>
Subject: Atom Content Negotiation (follow-up)
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-atom-syntax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/atom-syntax/mail-archive/>
List-Unsubscribe: <mailto:atom-syntax-request@imc.org?body=unsubscribe>
List-ID: <atom-syntax.imc.org>
hello. on http://dret.typepad.com/dretblog/2011/04/atom-content-negotiation.html i suggested a <link> usage that is not allowed by atom (because extension attributes need to be namespaced), but i think the problem is worth a solution and i'm planning to write a small draft for it. the problem is that this link relation needs a parameter (specifying what the media type of the linked feed/entry/content is) and maybe some title text. following typical XML usage, it might be useful to define an extension attribute (for the machine readable information) and allow a title (for an optional human readable label). the link relation then would be used this way (pointing to a feed with XML content): <link rel="alternate-content" href="..." alternate-content:content-type="application/xml" title="XML version based on bla.xsd"/> i am wondering what people are thinking about this kind of link relation. is it looking to unusual (an attribute that would be required for this link relation)? if so, what other way of representing it would you prefer? thanks and kind regards, dret. -- erik wilde | mailto:dret@berkeley.edu - tel:+1-510-6432253 | | UC Berkeley - School of Information (ISchool) | | http://dret.net/netdret http://twitter.com/dret |
- Atom Content Negotiation (follow-up) Erik Wilde
- RE: Atom Content Negotiation (follow-up) James Holderness
- Re: Atom Content Negotiation (follow-up) Erik Wilde
- Re: Atom Content Negotiation (follow-up) Peter Krantz
- Re: Atom Content Negotiation (follow-up) Erik Wilde
- RE: Atom Content Negotiation (follow-up) James Holderness
- Re: Atom Content Negotiation (follow-up) Erik Wilde
- Re: Atom Content Negotiation (follow-up) Hadrien Gardeur
- Re: Atom Content Negotiation (follow-up) Erik Wilde
- Re: Atom Content Negotiation (follow-up) Hadrien Gardeur
- Re: Atom Content Negotiation (follow-up) Erik Wilde
- Re: Atom Content Negotiation (follow-up) Hadrien Gardeur