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

Carine Bournez <carine@w3.org> Fri, 13 April 2012 12:16 UTC

Return-Path: <carine@jay.w3.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 6AE5C21F8763 for <apps-discuss@ietfa.amsl.com>; Fri, 13 Apr 2012 05:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level:
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 b3P1yExRAua3 for <apps-discuss@ietfa.amsl.com>; Fri, 13 Apr 2012 05:16:00 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by ietfa.amsl.com (Postfix) with ESMTP id EAC1721F86B5 for <apps-discuss@ietf.org>; Fri, 13 Apr 2012 05:15:59 -0700 (PDT)
Received: from carine by jay.w3.org with local (Exim 4.69) (envelope-from <carine@jay.w3.org>) id 1SIfPy-0007vU-FX; Fri, 13 Apr 2012 08:15:58 -0400
Date: Fri, 13 Apr 2012 08:15:58 -0400
From: Carine Bournez <carine@w3.org>
To: Carsten Bormann <cabo@tzi.org>
Message-ID: <20120413121558.GD696@jay.w3.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> <FBCADBF9-D6FB-4E0D-9668-F5B3EF744037@tzi.org> <20120411164447.GA24351@jay.w3.org> <4DDB792A-4154-4C7B-A3EC-82573FE20D3E@tzi.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4DDB792A-4154-4C7B-A3EC-82573FE20D3E@tzi.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: "apps-discuss@ietf.org Discuss" <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: Fri, 13 Apr 2012 12:16:00 -0000

On Wed, Apr 11, 2012 at 10:43:07PM +0200, Carsten Bormann wrote:
> > If foo has an application/foo media type for which the schema is known, 
> > the application readily knows which schema to use when receiving the EXI
> > stream with the content-encoding header.
> 
> Ah, SVG actually is a great example for why I think there need to be separate +exi registrations.
> 
> So, for image/svg+xml (see http://www.w3.org/TR/SVG/mimereg.html), what is "the SVG schema"?

There's currently no schema defined for use with EXI, for various reasons
(other things in SVG are under discussion for future use with EXI).

> What values of schemaId are defined, and what do they point to?

The EXI 1.0 spec mentions the use of a URI as an example for schemaIds.

> What about "application/svg+xml"?  ?application/vnd.oipf.dae.svg+xml??

The +exi proposal would have the same question: either define the schema, or 
the mechanism to use schemaId, or another out-of-band mechanism.