[apps-discuss] Fwd: New Version Notification for draft-wilde-xml-patch-03.txt

Erik Wilde <dret@berkeley.edu> Wed, 20 February 2013 14:09 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 AEED721F8810 for <apps-discuss@ietfa.amsl.com>; Wed, 20 Feb 2013 06:09:03 -0800 (PST)
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 lOPueUJuCZIa for <apps-discuss@ietfa.amsl.com>; Wed, 20 Feb 2013 06:09:03 -0800 (PST)
Received: from cm01fe.IST.Berkeley.EDU (cm01fe.IST.Berkeley.EDU [169.229.218.142]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA3421F872C for <apps-discuss@ietf.org>; Wed, 20 Feb 2013 06:09:03 -0800 (PST)
Received: from 46-126-158-51.dynamic.hispeed.ch ([46.126.158.51] helo=dretpro.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 1U8AM0-0001da-5b; Wed, 20 Feb 2013 06:09:02 -0800
Message-ID: <5124D8F7.5080408@berkeley.edu>
Date: Wed, 20 Feb 2013 15:08:55 +0100
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "apps-discuss@ietf.org application-layer protocols" <apps-discuss@ietf.org>
References: <20130220134257.14795.68954.idtracker@ietfa.amsl.com>
In-Reply-To: <20130220134257.14795.68954.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130220134257.14795.68954.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] Fwd: New Version Notification for draft-wilde-xml-patch-03.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: Wed, 20 Feb 2013 14:09:03 -0000

hello.

draft-wilde-xml-patch is ready for last call by now, apart from 
questions about how to best deal with dependencies with an underlying 
RFC (5261) and errata for it, which i will address in a separate email.

since i believe this draft is ready for publication, and this is an 
independent submission, if i recall correctly the next step is to find a 
sponsor for this draft. i'd be grateful if somebody would be willing to 
take on this role.

thanks and cheers,

dret.


-------- Original Message --------
Subject: New Version Notification for draft-wilde-xml-patch-03.txt
Date: Wed, 20 Feb 2013 05:42:57 -0800
From: internet-drafts@ietf.org


A new version of I-D, draft-wilde-xml-patch-03.txt
has been successfully submitted by Erik Wilde and posted to the
IETF repository.

Filename:	 draft-wilde-xml-patch
Revision:	 03
Title:		 A Media Type for XML Patch Operations
Creation date:	 2013-02-20
Group:		 Individual Submission
Number of pages: 14
URL: 
http://www.ietf.org/internet-drafts/draft-wilde-xml-patch-03.txt
Status:          http://datatracker.ietf.org/doc/draft-wilde-xml-patch
Htmlized:        http://tools.ietf.org/html/draft-wilde-xml-patch-03
Diff:            http://www.ietf.org/rfcdiff?url2=draft-wilde-xml-patch-03

Abstract:
    The XML Patch media type "application/xml-patch+xml" defines an XML
    document structure for expressing a sequence of patch operations that
    are applied to an XML document.  The XML Patch document format's
    foundations are defined in RFC 5261, this specification defines a
    document format and a media type registration, so that XML Patch
    documents can be labeled with a media type, for example in HTTP
    conversations.

Note to Readers

    This draft should be discussed on the apps-discuss mailing list [14].
    Online access to all versions and files is available on github [15].