[apps-discuss] Fw: New Version Notification for draft-wilde-atom-profile-02.txt
Erik Wilde <dret@berkeley.edu> Mon, 29 July 2013 07:52 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 6F01321F9D01 for <apps-discuss@ietfa.amsl.com>; Mon, 29 Jul 2013 00:52:14 -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 hcgGH2uAHa1Q for <apps-discuss@ietfa.amsl.com>; Mon, 29 Jul 2013 00:52:09 -0700 (PDT)
Received: from cm05fe.IST.Berkeley.EDU (cm05fe.IST.Berkeley.EDU [169.229.218.146]) by ietfa.amsl.com (Postfix) with ESMTP id C4AA821F99B0 for <apps-discuss@ietf.org>; Mon, 29 Jul 2013 00:52:09 -0700 (PDT)
Received: from 46-126-158-51.dynamic.hispeed.ch ([46.126.158.51] helo=dretpro.local) 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 1V3iFS-0007Dd-HR; Mon, 29 Jul 2013 00:52:08 -0700
Message-ID: <51F61F2A.8030403@berkeley.edu>
Date: Mon, 29 Jul 2013 09:52:10 +0200
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>, Atom-Syntax <atom-syntax@imc.org>, Atom-Protocol <atom-protocol@imc.org>
References: <20130729071438.10957.87683.idtracker@ietfa.amsl.com>
In-Reply-To: <20130729071438.10957.87683.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: REST-Discuss <rest-discuss@yahoogroups.com>
Subject: [apps-discuss] Fw: New Version Notification for draft-wilde-atom-profile-02.txt
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, 29 Jul 2013 07:52:14 -0000
hello. a new version of draft-wilde-atom-profile has been posted. if you are using profiles with atom, and specifically the proposed profile media type parameter, please get in touch. it would be great to add implementations to http://tools.ietf.org/html/draft-wilde-atom-profile-02#section-5 (please see http://tools.ietf.org/html/rfc6982#section-2 for a description of the implementation information needed). thanks and cheers, dret. ---------------------------------------------------------------------- On 2013-07-29 9:14 , internet-drafts@ietf.org wrote: > A new version of I-D, draft-wilde-atom-profile-02.txt > has been successfully submitted by Erik Wilde and posted to the > IETF repository. > > Filename: draft-wilde-atom-profile > Revision: 02 > Title: Profile Support for the Atom Syndication Format > Creation date: 2013-07-29 > Group: Individual Submission > Number of pages: 9 > URL: http://www.ietf.org/internet-drafts/draft-wilde-atom-profile-02.txt > Status: http://datatracker.ietf.org/doc/draft-wilde-atom-profile > Htmlized: http://tools.ietf.org/html/draft-wilde-atom-profile-02 > Diff: http://www.ietf.org/rfcdiff?url2=draft-wilde-atom-profile-02 > > Abstract: > The Atom syndication format is a generic XML format for representing > collections. Profiles are one way how Atom feeds can indicate that > they support specific extensions. To make this support visible on > the media type level, this specification adds an optional "profile" > media type parameter to the Atom media type. This allows profiles to > become visible at the media type level, so that servers as well as > clients can indicate support for specific Atom profiles in > conversations, for example when communicating via HTTP. This > specification updates RFC 4287 by adding the "profile" media type > parameter to the application/atom+xml media type registration.
- [apps-discuss] Fw: New Version Notification for d… Erik Wilde
- Re: [apps-discuss] New Version Notification for d… Rushforth, Peter