Re: [ietf-types] Mimetype approval request for type jcr-cnd

Peeter Piegaze <ppiegaze@adobe.com> Wed, 07 March 2012 12:03 UTC

Return-Path: <ppiegaze@adobe.com>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 915D321F86F1 for <ietf-types@ietfa.amsl.com>; Wed, 7 Mar 2012 04:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.165
X-Spam-Level:
X-Spam-Status: No, score=-106.165 tagged_above=-999 required=5 tests=[AWL=0.434, BAYES_00=-2.599, 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 54+Hl1oSs1fU for <ietf-types@ietfa.amsl.com>; Wed, 7 Mar 2012 04:03:01 -0800 (PST)
Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) by ietfa.amsl.com (Postfix) with ESMTP id EB06321F86C4 for <ietf-types@ietf.org>; Wed, 7 Mar 2012 04:03:00 -0800 (PST)
Received: from exprod6og106.obsmtp.com (exprod6og106.obsmtp.com [64.18.1.191]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id q27C2cqe005455 for <ietf-types@iana.org>; Wed, 7 Mar 2012 12:02:59 GMT
Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob106.postini.com ([64.18.5.12]) with SMTP ID DSNKT1dOWwZ2ODyayRLthIFHJKY32B3oJ+sS@postini.com; Wed, 07 Mar 2012 04:03:00 PST
Received: from inner-relay-4.eur.adobe.com (inner-relay-4b [10.128.4.237]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q27C2YN3029929; Wed, 7 Mar 2012 04:02:34 -0800 (PST)
Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-4.eur.adobe.com (8.12.10/8.12.9) with ESMTP id q27C2XPl007657; Wed, 7 Mar 2012 04:02:33 -0800 (PST)
Received: from SJ1SWM219.corp.adobe.com (10.5.77.61) by nahub02.corp.adobe.com (10.8.189.98) with Microsoft SMTP Server (TLS) id 8.3.192.1; Wed, 7 Mar 2012 04:02:32 -0800
Received: from nambx05.corp.adobe.com ([10.8.189.124]) by SJ1SWM219.corp.adobe.com ([fe80::d55c:7209:7a34:fcf7%12]) with mapi; Wed, 7 Mar 2012 04:02:32 -0800
From: Peeter Piegaze <ppiegaze@adobe.com>
To: "iesg@ietf.org" <iesg@ietf.org>, "ietf-types@iana.org" <ietf-types@iana.org>
Date: Wed, 07 Mar 2012 04:02:30 -0800
Thread-Topic: [ietf-types] Mimetype approval request for type jcr-cnd
Thread-Index: Acz8Wix8nSlcKXnTS8S1zvrz61nm+g==
Message-ID: <0E3320AE-47AC-4A84-BD7F-91474257D434@adobe.com>
References: <C62C495F-F721-44FD-A8C3-BAEDB5D01204@adobe.com> <4F563D6D.3000009@gmx.de>
In-Reply-To: <4F563D6D.3000009@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Wed, 07 Mar 2012 12:03:00 +0000 (UTC)
Cc: "julian.reschke@gmx.de" <julian.reschke@gmx.de>, Julian Reschke <jreschke@adobe.com>
Subject: Re: [ietf-types] Mimetype approval request for type jcr-cnd
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 12:03:02 -0000

Thanks Julian, for the correction. The updated proposal for type text/jcr-cnd is as follows:



--------

Type name: text

Subtype name: jcr-cnd

Required parameters: None

Optional parameters: "charset" as defined for text/plain [RFC2046]; encodings other than UTF-8 [RFC3629] MUST NOT be used.

Encoding considerations: 8bit

Security considerations: None known

Interoperability considerations: None

Published specification: JSR-283 Content Repository Specification for Java Technology (JCR)(http://jcp.org/en/jsr/detail?id=283). See especially sections 3.7 and 25.2. If approved, this MIME type will be included in the next revision of JCR, which is under development as JCR-333 (http://jcp.org/en/jsr/detail?id=333)

Applications that use this media type: Used by content repositories that implement the Content Repository For Java API (JCR) 

Additional information:

    File extension(s): .cnd

Person & email address to contact for further information: Peeter Piegaze <ppiegaze at adobe.com>, David Nuescheler <uncled at adobe.com>

Intended usage: Common

Restrictions on usage: None

Author: JSR-333 Expert Group

Change controller: Peeter Piegaze <ppiegaze at adobe.com>


Files of this media type define node types in JCR-compliant content repositories. Nodes are the structural components that make up the content storage in a JCR repository. A node type defines the characteristics that a node can have. Files of this media type are typically processed by a repository, thus registering the defined node types, making them available to users of the repository. Files of this media type are typically referred to as Compact Node Type Definition files or CND files.

-------






On Mar 6, 2012, at 5:38 PM, Julian Reschke wrote:

> Looks good to me, except parameters/encoding. You may want to steal from 
> <http://tools.ietf.org/html/rfc6350#section-10.1>:
> 
> -- snip --
>    Optional parameters:  version
> 
>       "charset": as defined for text/plain [RFC2046]; encodings other
>       than UTF-8 [RFC3629] MUST NOT be used.
> 
>    Encoding considerations:  8bit
> -- snip --
> 
> 
> Best regards, Julian
> 
> 
> On 2012-03-06 14:16, Peeter Piegaze wrote:
>> The following proposal for a new type was submitted to the ietf types mailing list some time ago.
>> 
>> I would like to move the process forward and request approval for this type.
>> 
>> 
>> Cheers,
>> 
>> Peeter Piegaze
>> 
>> Adobe Research Switzerland
>> 
>> Basel Switzerland
>> 
>> 
>> ==============
>> 
>> 
>> Type name: text
>> 
>> Subtype name: jcr-cnd
>> 
>> Required parameters: None
>> 
>> Optional parameters: None
>> 
>> Encoding considerations: 8 bit (UTF-8)
>> 
>> Security considerations: None known
>> 
>> Interoperability considerations: None
>> 
>> Published specification: JSR-283 Content Repository Specification for Java Technology (JCR)
>> (http://jcp.org/en/jsr/detail?id=283). See especially sections 3.7 and 25.2.
>> If approved, this MIME type will be included in the next revision of JCR,
>> which is under development as JCR-333 (http://jcp.org/en/jsr/detail?id=333)
>> 
>> Applications that use this media type: Used by content repositories that implement the
>> Content Repository For Java API (JCR)
>> 
>> Additional information:
>> File extension(s): .cnd
>> 
>> Person&  email address to contact for further information:
>> Peeter Piegaze ppiegaze atadobe.com  <http://adobe.com>
>> David Nuescheler uncled atadobe.com  <http://adobe.com>
>> 
>> Intended usage: Common
>> 
>> Restrictions on usage: None
>> 
>> Author: JSR-333 Expert Group
>> 
>> Change controller: Peeter Piegaze ppiegaze atadobe.com  <http://adobe.com>
>> 
>> Files of this media type define node types in JCR-compliant content repositories. Nodes are the structural components that make up the content storage in a JCR repository. A node type defines the characteristics that a node can have. Files of this media type are typically processed by a repository, thus registering the defined node types, making them available to users of the repository. Files of this media type are typically referred to as Compact Node Type Definition files or CND files.
>> 
>> 
>> 
>> 
>> _______________________________________________
>> ietf-types mailing list
>> ietf-types@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-types
>