Re: [apps-discuss] +exi

Mark Nottingham <mnot@mnot.net> Tue, 13 December 2011 22:37 UTC

Return-Path: <mnot@mnot.net>
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 B2A8B11E809D for <apps-discuss@ietfa.amsl.com>; Tue, 13 Dec 2011 14:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.96
X-Spam-Level:
X-Spam-Status: No, score=-104.96 tagged_above=-999 required=5 tests=[AWL=-2.361, BAYES_00=-2.599, 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 HPi6PqSZra3Y for <apps-discuss@ietfa.amsl.com>; Tue, 13 Dec 2011 14:37:35 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 96E8411E809B for <apps-discuss@ietf.org>; Tue, 13 Dec 2011 14:37:35 -0800 (PST)
Received: from [192.168.1.79] (unknown [118.209.24.155]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7B2A822E25A; Tue, 13 Dec 2011 17:37:29 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20111213215816.GI5525@jay.w3.org>
Date: Wed, 14 Dec 2011 09:37:27 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EFF390A-3D29-4F15-95BE-C81EFCF6D3D5@mnot.net>
References: <01O8EWMK2T8E00RCTX@mauve.mrochek.com> <4EC2DC42.7010307@stpeter.im> <01O8GE5O3B5K00RCTX@mauve.mrochek.com> <C68CB012D9182D408CED7B884F441D4D0611DAC31D@nambxv01a.corp.adobe.com> <4EC31F1E.6070304@stpeter.im> <8p86c7d6chvadsku6k5dhct20qkl7uk73l@hive.bjoern.hoehrmann.de> <4EC326FE.1010809@stpeter.im> <lu96c7hsl37325nn3184ub4vr88qjgja50@hive.bjoern.hoehrmann.de> <EDB50792-348B-4693-9FDF-04BA091F8BE9@sensinode.com> <4EE78F2F.2070601@stpeter.im> <20111213215816.GI5525@jay.w3.org>
To: Carine Bournez <carine@w3.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: paduffy@cisco.com, Thomas Herbst <therbst@silverspringnet.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] +exi
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, 13 Dec 2011 22:37:36 -0000

On 14/12/2011, at 8:58 AM, Carine Bournez wrote:

> On Tue, Dec 13, 2011 at 10:45:19AM -0700, Peter Saint-Andre wrote:
>> I chatted with a few folks about this in Taipei and afterward.
>> 
>> As I understand it (correct me if I'm wrong), EXI has two modes:
>> 
>> 1. Straight compression of the text representation of XML (text in,
>> EXI-compressed data out). To make use of the data, you then decompress
>> it back into the angle-brackety text representation of XML that we all
>> know and love.
>> 
>> 2. Direct, binary representation of the XML infoset. In this case, you
>> never have the data in a angle-brackety text representation, instead it
>> is always a binary representation.
> 
> It is not exactly 2 modes. The EXI 1.0 Recommendation only specifies a 
> compressed encoding of an XML Infoset. Applications that include an EXI 
> processor may use different approaches around the encoding/decoding process. 
> So, you can have applications with a (text) XML document as an input
> (what you describe as #1), and applications that never use a text
> serialization (your #2).


If I remember correctly, it also has modes where the schema (as a separate document) is required to be able to decode the document; is that still the case, Carine?

Cheers,

--
Mark Nottingham   http://www.mnot.net/