Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com
 designates 66.249.82.235 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=EZoQMbEjjcmpKBGXSk6Hb0akH6tiwsg4YqnLHxtlODT2UavzfKLVvc7gdoAOfiRYx3QkBIYNCYy24FMRNCrasYZacywwdM0h3hFGVOEWs7CCv0id+TniNWLw92wopIA4QQQGDRl/UZR8j78aWuVBTSBCWTHQLrYZCD5L2t7uvuA=
Message-ID: <510143ac0612070147t56d5852cu7dec80e93052d389@mail.gmail.com>
Date: Thu, 7 Dec 2006 11:47:33 +0200
From: "Jukka Zitting" <jukka.zitting@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: repository portability
In-Reply-To: <8be731880612070106n67d9be4eg352dad7cc2eec131@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5b3747160612040819i4b5d606eq3398c75b01ae7493@mail.gmail.com>
	 <1165325086.22514.5.camel@localhost>
	 <8be731880612050536k480c6899ra1a1145a169083a@mail.gmail.com>
	 <1165334207.22514.9.camel@localhost>
	 <8be731880612060034h5170e383m785c2fa3d05be347@mail.gmail.com>
	 <1165412197.6789.16.camel@localhost>
	 <8be731880612060544h5d74d3cif386551e0678a1c6@mail.gmail.com>
	 <1165430450.13288.17.camel@localhost> <45771A39.4060400@gmx.de>
	 <8be731880612070106n67d9be4eg352dad7cc2eec131@mail.gmail.com>

Hi,

On 12/7/06, Tobias Bocanegra <tobias.bocanegra@day.com> wrote:
> of course the application is free to choose what information to store
> in this property. for example, an zipped xml-file could have:
>   jcr:mimeType "text/xml"
>   jcr:encoding "gzip"
> although this might not make sense :-)

This is more in line with the HTTP Content-Encoding header than the
charset parameter of the MIME type as suggested by JSR 170. I think
that the Content-Encoding makes more sense, as there already is a
defined way to embed character encoding information in the MIME type.
For example:

    jcr:mimeType "text/plain; charset=UTF-8"
    jcr:encoding "gzip"

But since this contradicts JSR 170, I would argue that this should not
be done. The preferred alternatives being

    jcr:mimeType "text/plain; charset=UTF-8"
    jcr:encoding <unset>

and

    jcr:mimeType "text/plain"
    jcr:encoding "UTF-8"

Note that this way any content encodings need to be decoded before
storing the content in the jcr:data property.

BR,

Jukka Zitting