From users-return-4631-apmail-directory-users-archive=directory.apache.org@directory.apache.org Mon Apr 30 09:51:46 2012
Return-Path:
X-Original-To: apmail-directory-users-archive@www.apache.org
Delivered-To: apmail-directory-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id F1D959B24
for ; Mon, 30 Apr 2012 09:51:45 +0000 (UTC)
Received: (qmail 10034 invoked by uid 500); 30 Apr 2012 09:51:45 -0000
Delivered-To: apmail-directory-users-archive@directory.apache.org
Received: (qmail 9948 invoked by uid 500); 30 Apr 2012 09:51:43 -0000
Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: users@directory.apache.org
Delivered-To: mailing list users@directory.apache.org
Received: (qmail 9925 invoked by uid 99); 30 Apr 2012 09:51:42 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2012 09:51:42 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 209.85.214.50 as permitted sender)
Received: from [209.85.214.50] (HELO mail-bk0-f50.google.com) (209.85.214.50)
by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2012 09:51:34 +0000
Received: by bkcjg9 with SMTP id jg9so256907bkc.37
for ; Mon, 30 Apr 2012 02:51:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=message-id:date:from:reply-to:user-agent:mime-version:to:subject
:references:in-reply-to:content-type:content-transfer-encoding;
bh=qq4g3+56eXqv8/dc8s6sWHbZjm9O5TAMDsdvdUf12uA=;
b=xItoBdmJazy4Q01gHKWehPM5gasUEY+DmQhnwjjCPn0ZNI6mdryHhoJGaM0iklRlOB
J94lqcH3uU1u9ZDwSKbqOa6Pw60tbIfAkof4FhJ3dREyLe2bdk6MhhoLF0l4bm6fXQm5
FobXph57wVTq0Xv+DlNl4AheMZjA9XC3OkVFuFSfRFvCyXZrfHWaL143tmP8WE/02cZq
/oS4LeGLBaRpZYUaqHcJAlTnFQJgWbOYNwtlO5ep8xhcgRcE4AjCTkwmRgzs6pDxpPLX
zXigG0zz7HoHot94crMvmOFI7yFZbOSZXDqKcVPH0h0hGZPv34dA6KdarGQV2dqe4/hI
oTyA==
Received: by 10.204.9.195 with SMTP id m3mr7411354bkm.78.1335779474221;
Mon, 30 Apr 2012 02:51:14 -0700 (PDT)
Received: from Emmanuels-MacBook-Pro.local (lon92-10-78-226-4-211.fbx.proxad.net. [78.226.4.211])
by mx.google.com with ESMTPS id g5sm25563536bkt.9.2012.04.30.02.51.13
(version=SSLv3 cipher=OTHER);
Mon, 30 Apr 2012 02:51:13 -0700 (PDT)
Message-ID: <4F9E6090.7030106@gmail.com>
Date: Mon, 30 Apr 2012 11:51:12 +0200
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?=
Reply-To: elecharny@apache.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: users@directory.apache.org
Subject: Re: [ApacheDS] subschema subentries and DIT structure rules etc.
References: <1554570.NjuOaEdBII@venus>
In-Reply-To: <1554570.NjuOaEdBII@venus>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Le 4/30/12 10:53 AM, Karl Weber a écrit :
> 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.
>
> 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"...
Yep. This is something we have to add, we worked on it last year, but
it's not finished yet.
Note that we currently support (partially) collective attributes and
access control, which are part of the Administrative Model the Subschema
is associated with. The schema is still global at this point.
>
> Does ApacheDS support DIT structure rules and DIT content rules?
No, not yet. This is something we must implement, as for NameForms and
MarchingRuleUse
> 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.
I hope I have clarified those points.
> 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.)
Yep. We have already made the SchemaManager an insolated module so that
it will be possible to have many instance of it in the server, thus
allowing the use of SubschmaSubentries
> 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].
Right : e have only one schema atm, and it's for the whole DIT.
Atm, I do think we will get a 2.0 out before being able to have
subschema added, but be sure that one of the next minor iteration (2.1
or 2.2) will have such a feature.
Hope it helps.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com