Re: [apps-discuss] Fwd: New Version Notification for draft-shelby-exi-registration-01.txt

Carsten Bormann <cabo@tzi.org> Wed, 11 April 2012 12:04 UTC

Return-Path: <cabo@tzi.org>
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 584DE21F84B6 for <apps-discuss@ietfa.amsl.com>; Wed, 11 Apr 2012 05:04:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 PLUqMNGHrg9G for <apps-discuss@ietfa.amsl.com>; Wed, 11 Apr 2012 05:04:15 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 00EFB21F84A6 for <apps-discuss@ietf.org>; Wed, 11 Apr 2012 05:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q3BC45xe010895; Wed, 11 Apr 2012 14:04:05 +0200 (CEST)
Received: from dynamic-218-h.informatik.uni-bremen.de (dynamic-218-h.informatik.uni-bremen.de [134.102.218.207]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3A5AA33E; Wed, 11 Apr 2012 14:04:05 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset="iso-8859-1"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20120411085920.GP18899@jay.w3.org>
Date: Wed, 11 Apr 2012 14:04:05 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FBCADBF9-D6FB-4E0D-9668-F5B3EF744037@tzi.org>
References: <20120329204732.13711.266.idtracker@ietfa.amsl.com> <5580A282-E191-4962-9410-6CF9FB14EDFC@sensinode.com> <20120402124522.GX16698@jay.w3.org> <8B84EAAD-CD22-4461-9BC6-AB78974A94A2@sensinode.com> <20120411075024.GN18899@jay.w3.org> <4F85410D.20802@toshiba.co.jp> <20120411085920.GP18899@jay.w3.org>
To: Carine Bournez <carine@w3.org>
X-Mailer: Apple Mail (2.1257)
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Fwd: New Version Notification for draft-shelby-exi-registration-01.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, 11 Apr 2012 12:04:16 -0000

On Apr 11, 2012, at 10:59, Carine Bournez wrote:

> Rephrasing: the EXI 1.0 spec has a mechanism to tell the other end that
> schema-informed mode is in use, and the EXI 1.0 spec says that the 
> application level has to take care of defining the form of schemaID.

Let me try to translate this into language pertaining to the discussion at hand:

EXI can be used as a content-coding for XML documents in "Built-In" mode.
This would be the usage for the "Content-Encoding: EXI" that has been registered.

EXI requires out of band information to use the "Schema-Informed" mode.
In the Internet, This would normally be provided in an Internet media-type definition.
The media-type definition may also want to constrain the allowable values for the numerous options EXI provides, allowing for constrained implementations of EXI.

No existing application/foo+xml media type provides the latter kind of information.
With Content-Encoding: EXI, they are therefore limited to "Built-In" mode.
Any application that needs a tailored, schema-informed version of EXI should therefore register one or more application/foo+exi media types.

The next thing we should do is write down a template for all the information that needs to be nailed down in an application/foo+exi media type registration.

Grüße, Carsten