Re: [apps-discuss] New Version Notification for draft-wilde-xml-patch-00.txt
Erik Wilde <dret@berkeley.edu> Tue, 15 January 2013 08:26 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 E8A3321F8AC0 for <apps-discuss@ietfa.amsl.com>; Tue, 15 Jan 2013 00:26:57 -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 rUeL2qnSwZpJ for <apps-discuss@ietfa.amsl.com>; Tue, 15 Jan 2013 00:26:57 -0800 (PST)
Received: from cm02fe.IST.Berkeley.EDU (cm02fe.IST.Berkeley.EDU [169.229.218.143]) by ietfa.amsl.com (Postfix) with ESMTP id 292C921F8AB0 for <apps-discuss@ietf.org>; Tue, 15 Jan 2013 00:26:57 -0800 (PST)
Received: from 91-66-137-169-dynip.superkabel.de ([91.66.137.169] helo=dretair.local) by cm02fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1Tv1rD-000280-86; Tue, 15 Jan 2013 00:26:56 -0800
Message-ID: <50F512CA.6040003@berkeley.edu>
Date: Tue, 15 Jan 2013 09:26:50 +0100
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
References: <1CD55F04538DEA4F85F3ADF7745464AF2495A4A7@S-BSC-MBX1.nrn.nrcan.gc.ca> <CABP7RbdmxVpZn6CyjcHhUNNfmav9H1RDWGHKe5ODV-0y5YboPg@mail.gmail.com> <50F42C62.1080002@berkeley.edu> <01OOZ8YX62N000008S@mauve.mrochek.com>
In-Reply-To: <01OOZ8YX62N000008S@mauve.mrochek.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] New Version Notification for draft-wilde-xml-patch-00.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: Tue, 15 Jan 2013 08:26:58 -0000
hello ned. On 2013-01-14 20:33 , Ned Freed wrote: > Since in fact we do have such a registry now, you can take that as given. > And the use of the suffix is now a SHOULD; you can only not do it if you > have a > very good reason for that choice. I personally don't think that name > consistency with other types is even close to rising to that level; YMMV. http://tools.ietf.org/html/draft-ietf-appsawg-media-type-suffix-regs-08 is what you're referring to and this one is going to get published soon, right? in that case you'd recommend to go the xml-patch+xml way for the subtype, i guess? i am really wondering how this is going to play out for RDF, have their been discussions on how to handle this case (multiple serializations of the same data model) for the suffix registry? the reason why i am asking is that RDF needs a patch type as well, and there it will become an issue how to handle the fact that usually, a patch type's semantics are targeted at a model, while the type's syntax is based on some specific serialization. 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 |
- [apps-discuss] Fwd: New Version Notification for … Erik Wilde
- Re: [apps-discuss] New Version Notification for d… Rushforth, Peter
- Re: [apps-discuss] New Version Notification for d… James M Snell
- Re: [apps-discuss] New Version Notification for d… Julian Reschke
- Re: [apps-discuss] New Version Notification for d… Erik Wilde
- Re: [apps-discuss] New Version Notification for d… Erik Wilde
- Re: [apps-discuss] New Version Notification for d… James M Snell
- Re: [apps-discuss] New Version Notification for d… Ned Freed
- Re: [apps-discuss] New Version Notification for d… Erik Wilde
- Re: [apps-discuss] New Version Notification for d… Bjoern Hoehrmann
- Re: [apps-discuss] New Version Notification for d… Ned Freed
- Re: [apps-discuss] New Version Notification for d… Erik Wilde
- Re: [apps-discuss] New Version Notification for d… Nicholas Shanks