Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (nike.apache.org: domain of akarasulu@gmail.com designates
 74.125.82.44 as permitted sender)
MIME-Version: 1.0
Sender: akarasulu@gmail.com
In-Reply-To: 
 <CADwPi+FBLOz78N8M9Jf+SzBTVwm4rTw5XPgVsrOCre-LV1QN5g@mail.gmail.com>
References: <1554570.NjuOaEdBII@venus>
	<CADwPi+FBLOz78N8M9Jf+SzBTVwm4rTw5XPgVsrOCre-LV1QN5g@mail.gmail.com>
Date: Mon, 30 Apr 2012 12:53:36 +0300
Message-ID: 
 <CADwPi+FGtkyZMg-taEm3Uc7YxbR-V3=4ZitBjZvc8HMX2BuKVg@mail.gmail.com>
Subject: Re: [ApacheDS] subschema subentries and DIT structure rules etc.
From: Alex Karasulu <akarasulu@apache.org>
To: users@directory.apache.org
Content-Type: multipart/alternative; boundary=f46d041824ee87713c04bee26d78

--f46d041824ee87713c04bee26d78
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 30, 2012 at 12:52 PM, Alex Karasulu <akarasulu@apache.org>wrote:

>
>
> On Mon, Apr 30, 2012 at 11:53 AM, Karl Weber <karl.weber99@googlemail.com>wrote:
>
>> Hi,
>>
>> as far as I read in the documentation for ApacheDS 1.5.7, ApacheDS does
>> support subentries according to RFC 3672 with the exception of subschema
>> subentries.
>>
>>
> Yes it does and so will all other implementations to come like 2.0 below.
>

Ooop I read in correctly (thought you meant subentries), I see you mean
schema subentries. True we don't suport this.


>
>
>> Is this still valid for the current 2.0.0 milestone? Unfortunately the
>> links
>> to the documentation are broken. The support of subschema subentries has
>> been
>> announced in the 1.5.7 documentation for the "future"...
>>
>>
> We need help with docs :).
>
>
>> Does ApacheDS support DIT structure rules and DIT content rules?
>
>
> Unfortunately it has all the machinery but enforcement of these rules
> don't take place and that peeves me a great deal. For really great schema
> design these are a must. Unfortunately many don't understand just how
> important these are including NameForms for carving out the namespace
> properly.
>
>
>> The
>> documentation for 1.5.7 claims that ApacheDS is RFC 4512 compliant,
>> however
>> support for these rules is optional, so some clarification is needed.
>>
>
> Yes we may have falsely advertised this if these features are required.
>
>
>> Furthermore, in order to use DIT structure rules, administrative areas
>> with
>> there own subschemas would make sence. (DIT structure rules do not have
>> global
>> OIDs but only integer IDs which have to be unique within the controlling
>> schema.) Furthermore, quote of RFC 4512:
>>
>>        If no superior rules are identified, the DIT structure rule applies
>>        to an autonomous administrative point (e.g., the root vertex of the
>>        subtree controlled by the subschema) [X.501].
>>
>
> Schema right now applies globally to the entire DIT and I don't like this
> myself. However it's really hard to make it work with AAP and IAPs. I hope
> we get to this at some point.
>
> --
> Best Regards,
> -- Alex
>
>


-- 
Best Regards,
-- Alex

--f46d041824ee87713c04bee26d78--