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

Ned Freed <ned.freed@mrochek.com> Tue, 15 January 2013 18:46 UTC

Return-Path: <ned.freed@mrochek.com>
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 BCC1911E80C5 for <apps-discuss@ietfa.amsl.com>; Tue, 15 Jan 2013 10:46:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 iPhQXJqf64Ua for <apps-discuss@ietfa.amsl.com>; Tue, 15 Jan 2013 10:46:22 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id F0C0711E80A6 for <apps-discuss@ietf.org>; Tue, 15 Jan 2013 10:46:21 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OP0LGF5EJ4005A9E@mauve.mrochek.com> for apps-discuss@ietf.org; Tue, 15 Jan 2013 10:45:32 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OOJ8U2Q2U800008S@mauve.mrochek.com>; Tue, 15 Jan 2013 10:45:27 -0800 (PST)
Message-id: <01OP0LGBJ20S00008S@mauve.mrochek.com>
Date: Tue, 15 Jan 2013 10:36:42 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Tue, 15 Jan 2013 09:26:50 +0100" <50F512CA.6040003@berkeley.edu>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format="flowed"
References: <1CD55F04538DEA4F85F3ADF7745464AF2495A4A7@S-BSC-MBX1.nrn.nrcan.gc.ca> <CABP7RbdmxVpZn6CyjcHhUNNfmav9H1RDWGHKe5ODV-0y5YboPg@mail.gmail.com> <50F42C62.1080002@berkeley.edu> <01OOZ8YX62N000008S@mauve.mrochek.com> <50F512CA.6040003@berkeley.edu>
To: Erik Wilde <dret@berkeley.edu>
Cc: Ned Freed <ned.freed@mrochek.com>, "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 18:46:22 -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?

When it gets published is irrelevant. It's already approved as a standard
and specifies the current rules we operate under. The relevant IANA web
pages already cite it.

I'll note in passing that this use by IANA and others of documents that haven't
completed the publication process is not up to me; it's just how things work.

> in that case you'd recommend to go the xml-patch+xml way for the
> subtype, i guess?

Yes, that's what I would recommend, but really, it's not a question of what I
recommend. It's instead a question of what the standards require. I already
stated the requirements; if you believe you can make a compelling case for
omitting the suffix for this type you are free to do so.

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

That a question to be answered if and when someone proposes a suffix for rdf.
AFAIK there isn't one at present. I personally don't know enough about RDF and
how it is used to comment, although I'll note that the XML format has the
application/rdf+xml assigned. I will also note that EXI was considered and
rejected as a suffix.

				Ned