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

OK. If you revise the draft, it might be helpful to add some examples to Section 2 to illustrate this (I know it's already there, but examples do help!).

Cheers,

On 11/04/2012, at 1:31 AM, Zach Shelby wrote:

> On Mar 31, 2012, at 1:55 PM, Mark Nottingham wrote:
> 
>> What's the use case here? Content negotiation, or something else?
> 
> In particular this would be aimed at M2M applications that make use of Schema-informed EXI.
> 
> - Content-negotiation when an application also uses other forms of its base media type (+xml, +json etc.)
> - Interoperability, this registration would force the schemaID to be defined precisely and thus solve a problem in EXI. This is why the use of this +exi form would only be for Schema informed use of EXI. 
> - This use of EXI is *not* content-encoding in my opinion, thus we are providing a better media type model and encouraging media types that mean something semantically. 
> 
> Zach
> 
>> 
>> Regards,
>> 
>> 
>> On 29/03/2012, at 10:52 PM, Zach Shelby wrote:
>> 
>>> I have posted a new version of the +exi registration draft. This version improves the Interoperability considerations of the registration requirements and further clarifies when this suffix may be used, as per the feedback on the list from Carine and others.
>>> 
>>> http://www.ietf.org/id/draft-shelby-exi-registration-01.txt
>>> 
>>> Regards,
>>> Zach
>>> 
>>> Begin forwarded message:
>>> 
>>>> From: internet-drafts@ietf.org
>>>> Date: March 29, 2012 10:47:32 PM GMT+02:00
>>>> To: zach@sensinode.com
>>>> Subject: New Version Notification for draft-shelby-exi-registration-01.txt
>>>> 
>>>> A new version of I-D, draft-shelby-exi-registration-01.txt has been successfully submitted by Zach Shelby and posted to the IETF repository.
>>>> 
>>>> Filename:	 draft-shelby-exi-registration
>>>> Revision:	 01
>>>> Title:		 The +exi Media Type Suffix
>>>> Creation date:	 2012-03-29
>>>> WG ID:		 Individual Submission
>>>> Number of pages: 5
>>>> 
>>>> Abstract:
>>>> Efficient XML Interchange (EXI) is an XML representation technique
>>>> specified by the W3C to provie a binary alternative to the standard
>>>> text XML representation.  This document defines a new Structure
>>>> Syntax Suffix &quot;+exi&quot; for use in a specific class of protocols, where
>>>> &quot;exi&quot; content-type encoding or the generic &quot;application/exi&quot; Media
>>>> Type are not applicable.
>>>> 
>>>> 
>>>> 
>>>> 
>>>> The IETF Secretariat
>>> 
>>> -- 
>>> Zach Shelby, Chief Nerd, Sensinode Ltd.
>>> http://www.sensinode.com
>>> http://zachshelby.org  - My blog "On the Internet of Things"
>>> http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
>>> Mobile: +358 40 7796297
>>> 
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>> 
>> --
>> Mark Nottingham
>> http://www.mnot.net/
>> 
>> 
>> 
>> 
> 
> -- 
> Zach Shelby, Chief Nerd, Sensinode Ltd.
> http://www.sensinode.com
> http://zachshelby.org  - My blog "On the Internet of Things"
> http://6lowpan.net - My book "6LoWPAN: The Wireless Embedded Internet"
> Mobile: +358 40 7796297
> 

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