OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dsml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: Question


Sorry for leaving misconceptions. Thanks for the help. Comments below.

				bill

-----Original Message-----
From: Steve Fisher [mailto:s.a.fisher@btinternet.com]
Sent: Wednesday, August 02, 2000 6:19 PM
To: Curtin, William; 'Steven Livingstone'; DSML
Subject: Re: Question

<snip>

A content rule is a way of doing something similar to the above, but for all
instances of the structural object class.

[I thought that is what the question was trying to do]

The way on which a DIT is structured is defined using DIT structure rules.
These simply describe which object classes can appear at which points within
the DIT

and which attributes are used to name (i.e used to construct the
RDN) 

[By use of Name Form]

at each of those points. There are no built in rules and a person entry
can, if the designer of the DIT wishes, appear 'above' an organization
entry.

[Yes, your right. Didn't mean to leave the impression that structure rules
were etched in granite, although many products default to the structure rule
defined in X.521

sr13	STRUCTURE-RULE	 ::= {
	NAME FORM		orgPersonNameForm
	SUPERIOR RULES	{ sr2 | sr3 | sr4 }*****Read that as
"Organization"******
	ID				13 }
sr14	STRUCTURE-RULE 	::= {
	NAME FORM		orgPersonNameForm
	SUPERIOR RULES	{ sr10 | sr11 | sr12 }****Read that as
Organizational Unit*******
	ID				14 }

]



regards

Steve Fisher

Steve Fisher
BT Syncordia Solutions T&I
0771 310 7125
0118 975 0560
s.a.fisher@btinternet.com

<snip>

								bill


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC