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 stefan.guggisberg@gmail.com
 designates 64.233.182.187 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=nOoBGJtfB36cJbjV7ZD8bxiY4vMb1ocoAmquEHz1GIDaJIWYkB4SV9EZ3LaF6LGlRXyqpfBBBqGWTkhwgqR0JWsjPw+jlg7pAW/EwVplSPchLSwNYIc4njj1nJgq6mwNemruIQJSYqnKuAE5j4WvJTRAc0GHd/dTSM4eVWRL73k=
Message-ID: <90a8d1c00610270144l2d3b1446q25c4909dc851ca56@mail.gmail.com>
Date: Fri, 27 Oct 2006 10:44:47 +0200
From: "Stefan Guggisberg" <stefan.guggisberg@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: Node Definitions
In-Reply-To: <45412978.2080203@decoursey.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <510143ac0610121347q18d6d5cdqa83de12144541242@mail.gmail.com>
	 <8F1EB0A9-FE0A-4A01-A13F-D84401A39B47@macnica.com>
	 <510143ac0610130835i56124afblf954a3ffc387e596@mail.gmail.com>
	 <96ab3ced0610260939w1c62cd13l8e9f81f1c7f5baac@mail.gmail.com>
	 <510143ac0610261311x15d498eal84ccc128a1842da2@mail.gmail.com>
	 <45412978.2080203@decoursey.net>

hi paul,

On 10/26/06, Paul J DeCoursey <paul@decoursey.net> wrote:
> Is there a way to define Node Types in a Implementation independent
> manner?  This is my first look at Content Repositories so forgive me if
> this question is naive.  I'm building a content management system and I
> need to make it completely independent of Jackrabbit so that our
> customers can just plug in whatever system they want.  For example once
> IBM gets Content Manager JSR-170 ready. Does this make sense?  Or is it
> that all systems will have their own way of defining node types and it
> just cannot be done through JCR?

jcr 2.0 will most probably cover node type management. jcr 2.0 is currently
in the works, for more details please see http://jcp.org/en/jsr/detail?id=283.

however, the final release is planned for may 2007, and this schedule is
subject to change...

another word of caution: don't expect too much wrt node type interoperability
amongst different vendors. just like every database vendor has his 'own' brew
of ddl syntax, most repository vendors will have specific restrictions
and features.

for example, currently none of the jcr implementations i know of support
nt:unstructured (except jackrabbit of course ;-).

cheers
stefan

>
> Thanks
>
>