Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: neutral (herse.apache.org: 212.27.42.35 is neither permitted nor
 denied by domain of elecharny@gmail.com)
Message-ID: <462B0D43.3090102@gmail.com>
Date: Sun, 22 Apr 2007 09:22:43 +0200
From: Emmanuel Lecharny <elecharny@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923)
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [DAS] Type's ObjectClass Entry
References: <462AAD20.2080201@gmail.com>
In-Reply-To: <462AAD20.2080201@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Ole Ersoy a �crit :

> Hey Guys,
>
> When defining the Type ObjectClass
> entry I use
> m-may to define simple properties that are optional
> and m-must to define simple properties that
> are required.
>
> Then I need to define the ObjectClass's
> Complex Properties.
>
> So I need something like
> m-complexMay and m-complexMust.
>
> Looking at current meta ObjectClasses,
> I would think it makes sense to create another
> meta ObjectClass that has these attributes,
> possibly called metaSDOObjectClass?
>
> Thoughts?

Meta attributes are by no means intended to be used to describe user's 
defined elements. They are used to describe elements used internally by 
the server to deal with the schema itself. Think about meta-schema as 
metaData in a RDBMS

We won't add a m-xxx element. Just add the attribute/objectclass you 
need, it's not a problem, you will have to create a new schema (a little 
bit like the java.schema schema). This is the way to go.

Emmanuel